From jira-events at lists.jboss.org  Mon Oct  1 02:11:41 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 1 Oct 2007 02:11:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-786) String remove()
	method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28478858.1191219101646.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Andrew Rubinger updated EJBTHREE-786:
-------------------------------------

    JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=120053

Stand corrected, revoking "spec violation" argument.

See linked Forum topic.

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: Branch_4_2, HEAD
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 02:27:41 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Mon, 1 Oct 2007 02:27:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1237) Upgrade MVEL
 library to 1.2.final
Message-ID: <5418439.1191220061206.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade MVEL library to 1.2.final
---------------------------------

                 Key: JBRULES-1237
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1237
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.1
            Reporter: Joshua Jackson
         Assigned To: Mark Proctor
            Priority: Minor
             Fix For: 4.0.2


Upgrade the current mvel library that is used by drools to mvel 1.2.final as it has some fixes


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
Message-ID: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>

HTTP session replication failover failures with async buddy replication
-----------------------------------------------------------------------

                 Key: JBAS-4766
                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering, Web (Tomcat) service
    Affects Versions: JBossAS-4.2.0.GA
         Environment: 4 nodes, buddy async replication, 100 clients
            Reporter: Dominik Pospisil
         Assigned To: Brian Stansberry
         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log

Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26504102.1191224141612.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: test.log

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7567825.1191224141761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: driver.log

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3264253.1191224141926.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf01.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:42 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19808037.1191224142091.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf02.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:42 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11082282.1191224142254.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf03.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:37:50 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:37:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29884110.1191224270728.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf04.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 04:03:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 04:03:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4764) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <366369.1191043241063.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7605157.1191225821217.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4764?page=all ]

Dimitris Andreadis updated JBAS-4764:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.0.3 SP1)

One a new jira you cannot set fix version one that has already been released.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4764
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4764
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-3.2.8.SP1
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 04:35:42 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 04:35:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4767) Upgrade jbossws to
 2.0.1 (from 1.2.1.GA)
Message-ID: <16412352.1191227742601.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade jbossws to 2.0.1 (from 1.2.1.GA)
----------------------------------------

                 Key: JBAS-4767
                 URL: http://jira.jboss.com/jira/browse/JBAS-4767
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Web Services
            Reporter: Dimitris Andreadis
             Fix For: JBossAS-4.2.2.GA




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:05:45 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:05:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1052)
 getAllTaskInstances(), getAllProcessInstances()
In-Reply-To: <24526709.1189013891148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28673240.1191229545014.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1052?page=comments#action_12379504 ] 
            
Fady Matar commented on JBPM-1052:
----------------------------------

Another solution to avoid probable cross-database differences would be to create the hibernate query that would retrieve all the task instances and allow the "super manager" as stated before to view / perform action on them.

Please note that this query might be an over kill when the existing tasks grow large and there has to be a mechanism to allow ordering, grouping and sorting those tasks to reduce the processing time

> getAllTaskInstances(), getAllProcessInstances()
> -----------------------------------------------
>
>                 Key: JBPM-1052
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1052
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: s b
>         Assigned To: Tom Baeyens
>            Priority: Minor
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Businesses often want a "super manager" to have the ability to see and work on the tasks of all users.  With the current jBPM, it is very difficult to generate a list of all TaskInstances.
> The feature requested is a method for listing all TaskInstances regardless of user.  It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds.
> One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances.  I don't know if that is portable to all databases; it works well for Oracle.
> It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours.
> A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons.
> A criticism is that the method would introduce scalability / performance problems.  That is always an issue that is difficult to avoid completely depending on the application.  For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:16:43 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:16:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1053) jBPM Build Files
 Search for build.properties in ${user.home}/jbpm/build.properties
In-Reply-To: <20341275.1189026614587.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29056963.1191230203324.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1053?page=comments#action_12379506 ] 
            
Fady Matar commented on JBPM-1053:
----------------------------------

jBPM is already defaulted to a sensible configuration file within the system build/build.properties. Users can override this functionality by implementing their creating their own build.properties in their home directories. 

> jBPM Build Files Search for build.properties in ${user.home}/jbpm/build.properties
> ----------------------------------------------------------------------------------
>
>                 Key: JBPM-1053
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1053
>             Project: JBoss jBPM
>          Issue Type: Release
>            Reporter: Christopher Brock
>         Assigned To: Tom Baeyens
>
> This has become a pretty serious problem in our attempts to create automated build and patches for SOA.   It creates a mess by forcing us to have our scripts create directories outside the build structure.  
> It would be helpful if the either a delegate configuration file was introduced to allow us to override this, or better yet, if jBPM simply defaulted to a sensible configuration file inside it's source structure.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:21:41 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 1 Oct 2007 05:21:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1729) AjaxInterceptor
 with a different context root
In-Reply-To: <13290468.1191167861321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15068575.1191230501354.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1729?page=all ]

Thomas Heute updated JBPORTAL-1729:
-----------------------------------

    Fix Version/s: 2.6.3 Final
                       (was: 2.6.2 Final)

> AjaxInterceptor with a different context root
> ---------------------------------------------
>
>                 Key: JBPORTAL-1729
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1729
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.1 Final
>         Environment: fedora 7, eclipse europa, java 5 update 12
>            Reporter: Luca Stancapiano
>             Fix For: 2.6.3 Final
>
>         Attachments: patch_AjaxInterceptor.zip
>
>
> about org.jboss.portal.core.controller.ajax.AjaxInterceptor class
> row 75:
> pageProps.put(DynaConstants.RESOURCE_BASE_URL, "/portal-ajax/dyna");
> It uses a static hard coded link to use portal-ajax application , but if we need to change context root, it points to the same link and so in some cases there can to be redirect problems.
> In my case, I have two portal instances on two different hosts and through mod_jk I redirect the first instance using /portal* path and the second with /two_portal* path.
> I cannot o use /portal-ajax path from the second host because mod_jk see that path and it redirects to the first portal instance, then I need to use a different path else I pay a unnecessary connection.
> To resolve this problem I added a property TargetContextPath (as for org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor class) into AjaxInterceptor and substituted it to /portal-ajax/ link.
> private String targetContextPath = "/portal-ajax";
>    public String getTargetContextPath()
>    {
>       return targetContextPath;
>    }
>    public void setTargetContextPath(String context)
>    {
>       targetContextPath = context;
>    }
> it can to be configured through AjaxInterceptor MBean into META-INF/jboss-service.xml. Here there is an example:
>    <mbean
>       code="org.jboss.portal.core.controller.ajax.AjaxInterceptor"
>       name="portal:service=Interceptor,type=Command,name=Ajax"
>       xmbean-dd=""
>       xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
>       <xmbean/>
>       <attribute name="TargetContextPath">/portal-ajax</attribute>
>    </mbean>

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:24:41 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:24:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1054) deprecate
 expression on action in favour of execute
In-Reply-To: <26830440.1189074491245.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6407296.1191230681470.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1054?page=comments#action_12379507 ] 
            
Fady Matar commented on JBPM-1054:
----------------------------------

Let's create an alias and deprecate the existing expression attribute, we'll maintain the deprecation all along the line of 3.x releases and remove it by version 4. The documentation must reflect those changes as well and the process designer needs to throw out a warning regarding this deprecation

> deprecate expression on action in favour of execute
> ---------------------------------------------------
>
>                 Key: JBPM-1054
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1054
>             Project: JBoss jBPM
>          Issue Type: Task
>    Affects Versions:  jBPM jPDL 3.2.1
>            Reporter: Pete Muir
>         Assigned To: Tom Baeyens
>            Priority: Critical
>
> As discussed on the forum, add an execute attribute (as an alias to expression) to the action element, and (TBD) deprecate the expression.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:24:41 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 05:24:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-601) Parallelizing test
	suite
In-Reply-To: <4314937.1190966381352.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8426757.1191230681610.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-601?page=comments#action_12379508 ] 
            
Bela Ban commented on JGRP-601:
-------------------------------

Comment from Ryan, suggesting Husdon instead of DTF:
The DTF is more than just running jobs in parallel, it's a comprehensive test system with it's own test definition and reporting sub-systems.  So to take full advantage of it, you would want to author your tests in the DTF test specification format.  It can run JUnit tests, but is not particularly better at this than Hudson.  And the reporting and control interfaces are probably worse.

Richard, do you mind sending Bela a link to the documentation we have for the DTF?  This will at least give him an idea of what is required and can be accomplished.

If you just want to parallelize your test suites, you can do that very easily in Hudson without requiring you guys to have to learn how to write tests for the DTF.  For instance, Kabir did this for AOP:

http://hudson.qa.jboss.com/hudson/view/AOP/

He can now run all of his test suites across our "linux" slave pool with the click of a few buttons.

We also use it to run the JBoss test suite across HPUX, Solaris, Windows, and Linux and multiple JVM's on each platform:

http://hudson.qa.jboss.com/hudson/view/EAP/

Steve Ebersole uses it to run the Hibernate test suite across a matrix of DB's and Drivers:

http://hudson.qa.jboss.com/hudson/job/hibernate-3.2/

So if you just want to run JUnit jobs in parallel, or perhaps across a configuration matrix, Hudson is what you want.  
Ryan 

> Parallelizing test suite
> ------------------------
>
>                 Key: JGRP-601
>                 URL: http://jira.jboss.com/jira/browse/JGRP-601
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.x
>
>
> Run the following in parallel
> - functional tests
> - stack-specific tests
> E.g. run UDP tests in parallel with TCP
> Look at DTF (Distributed Test Framework) for 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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:30:41 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:30:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1189) Implement
 JGroups Connect + State Transfer in JBC
In-Reply-To: <18329595.1190729863300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6501380.1191231041840.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1189?page=all ]

Vladimir Blagojevic resolved JBCACHE-1189.
------------------------------------------

    Resolution: Done

Implemented in CacheImpl#internalStart

> Implement JGroups Connect + State Transfer in JBC
> -------------------------------------------------
>
>                 Key: JBCACHE-1189
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1189
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:30:42 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:30:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1189) Implement
 JGroups Connect + State Transfer in JBC
In-Reply-To: <18329595.1190729863300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17872641.1191231042285.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1189?page=comments#action_12379511 ] 
            
Vladimir Blagojevic commented on JBCACHE-1189:
----------------------------------------------

Verified that all state transfer tests pass.

> Implement JGroups Connect + State Transfer in JBC
> -------------------------------------------------
>
>                 Key: JBCACHE-1189
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1189
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:49:45 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:49:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-616) prevent duplicate
 form submissions
Message-ID: <16013877.1191232185238.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-616?page=comments#action_12379512 ] 
            
Fady Matar commented on JBPM-616:
---------------------------------

This is purely related to JSF, we need to investigate an existing JSF token implementation or implement our own until this is supported in the next releases of JSF

> prevent duplicate form submissions
> ----------------------------------
>
>                 Key: JBPM-616
>                 URL: http://jira.jboss.com/jira/browse/JBPM-616
>             Project: JBoss jBPM
>          Issue Type: Task
>          Components: Web Interface
>            Reporter: Tom Baeyens
>         Assigned To: David Lloyd
>             Fix For: jBPM 3.3
>
>
> for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:49:45 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:49:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-597) Allow generic view
	payload
In-Reply-To: <25895767.1190794361110.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18967299.1191232185613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-597?page=all ]

Vladimir Blagojevic resolved JGRP-597.
--------------------------------------

    Resolution: Done

Added event PREPARE_VIEW that is passed up/down stack right after we construct a new view. Thus any protocol or building block can append a payload to a new view to be installed.

> Allow generic view payload
> --------------------------
>
>                 Key: JGRP-597
>                 URL: http://jira.jboss.com/jira/browse/JGRP-597
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> View installation is one of the most important events in group/cluster communication. However, currently we do not allow building blocks to append any custom data to views being installed. At coordinator, during view preparation, building block should be notified that a new view is being created so that building block can append payload to the view that is going to be installed for the cluster. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:51:41 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:51:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-337) Make STOP_FLUSH
 phase in FLUSH asynchronous
In-Reply-To: <26343747.1159867721489.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6962168.1191232301367.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-337?page=all ]

Vladimir Blagojevic resolved JGRP-337.
--------------------------------------

    Resolution: Done

Commit set: 
protocols/pbcast/FLUSH.java 1.67

> Make STOP_FLUSH phase in FLUSH asynchronous
> -------------------------------------------
>
>                 Key: JGRP-337
>                 URL: http://jira.jboss.com/jira/browse/JGRP-337
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.4
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 2.6
>
>
> Revert back from synchronous. Only possible if we make the STOP_FLUSH message *out-of-band* !

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:15:42 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 1 Oct 2007 06:15:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1051) A bean without
 a security domain doesn't propagate caller
In-Reply-To: <25811297.1190098631036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2404851.1191233742684.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1051?page=comments#action_12379519 ] 
            
Carlo de Wolf commented on EJBTHREE-1051:
-----------------------------------------

I fixed the stateless test. It gobled up a NPE, which appears now in testUnsecureToSecureWithoutCredentials. And testUnsecureToSecureWithCredentials is now directly related to this issue.

> A bean without a security domain doesn't propagate caller
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1051
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1051
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Security
>            Reporter: Carlo de Wolf
>         Assigned To: Anil Saldhana
>
> In rev 65440 I changed the stateful unit test so that StatelessBean does have a security domain. But it should also work without one.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:28:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:28:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-259) Activate
 compression in marshaller
Message-ID: <29272003.1191234521301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ]

Tim Fox closed JBMESSAGING-259.
-------------------------------

    Resolution: Rejected

> Activate compression in marshaller
> ----------------------------------
>
>                 Key: JBMESSAGING-259
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Activate compression in marshaller for messages > x bytes. Make it configurable

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:32:52 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:32:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-681) Consolidate
 JMS related aspects into one JMS aspect
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24899560.1191234772760.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=comments#action_12379525 ] 
            
Tim Fox commented on JBMESSAGING-681:
-------------------------------------

We should remove AOP usage from the standard stack, and use java.lang.reflect proxies as EJB3 does to allow users to specify a stack of interceptors on both client and server side.

The functionality currently in the client side JMS aspects should be moved into a set of standard classes:

ConnectionFactory, Connection, Session, Consumer.

Note that this *do not* correspond to JMS connection factory, connection, consumer classes. These are a simpler abstraction.

We maintain the standard JMS object implementations which should delegate to these classes.

> Consolidate JMS related aspects into one JMS aspect
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:32:52 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 06:32:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1190) Eviction
 configuration should consider buddy backup regions as well.
Message-ID: <32922469.1191234772880.JavaMail.jira@cloud.prod.atl2.jboss.com>

Eviction configuration should consider buddy backup regions as well.
--------------------------------------------------------------------

                 Key: JBCACHE-1190
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eviction
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.2.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:32:53 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:32:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor AOP
	usage
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6495778.1191234773089.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

    Summary: Refactor AOP usage  (was: Consolidate JMS related aspects into one JMS aspect)

> Refactor AOP usage
> ------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:34:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:34:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor AOP
	usage
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32471100.1191234881389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)
    Priority: Critical  (was: Major)

> Refactor AOP usage
> ------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:34:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:34:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-25) Microcontainer
	integration
Message-ID: <14762022.1191234882023.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ]

Tim Fox updated JBMESSAGING-25:
-------------------------------

    Description: 
We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.

The microcontainer can also provide MBean interfaces transparently if needed.

This task is critical in allowing an "embedded JBM".

This is critical to kick start ESB.

  was:
We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.

The microcontainer can also provide MBean interfaces transparently if needed.

This task is critical in allowing an "embedded JBM".

This is critical to kick start ESB

       Priority: Critical  (was: Major)

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Aaron Walker
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:36:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-25)
	Microcontainer integration
Message-ID: <19968730.1191235001641.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=comments#action_12379527 ] 
            
Tim Fox commented on JBMESSAGING-25:
------------------------------------

We should also remove all references to JNDI from our core POJOs.

JBM should be usable, embedded without any use of JNDI.

All JNDI usage should occur in a separate layer.

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Aaron Walker
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:36:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-815) Extra message
 created if server fails when send and ACK are synchronized
In-Reply-To: <5708755.1170803906788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29808311.1191235001862.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ]

Tim Fox updated JBMESSAGING-815:
--------------------------------

    Priority: Major  (was: Critical)

> Extra message created if server fails when send and ACK are synchronized
> ------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-815
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-815
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.0.1.SP3
>            Reporter: Clebert Suconic
>             Fix For: 2.0.0 Beta 1
>
>
> MultiThreadFailoverTest::testFailureOnSendReceiveSynchronized fails for this bug
> This test poisons the server to wait consumer and sender to be in a same point before crashing it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:38:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:38:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-406) Enabled local
 persistent storage per node
Message-ID: <13266561.1191235121384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ]

Tim Fox updated JBMESSAGING-406:
--------------------------------

       Summary: Enabled local persistent storage per node  (was: Enable file based persistent stores)
    Issue Type: Task  (was: Feature Request)
      Priority: Critical  (was: Major)

> Enabled local persistent storage per node
> -----------------------------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Implement non shared file based persistent store.
> Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this.
> Also look at HOWL. http://howl.objectweb.org/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:42:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:42:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Enabled
 local persistent storage per node
Message-ID: <26321063.1191235361348.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12379532 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

Currently messages are persisted via a RDBMs which is shared by all nodes in the cluster.

This provides a bottleneck. Also RDBMs are not well suited for persisting queue like data.

Each node should have its own persistent store for performance and scalability.

For failover all persistent stores should available by all nodes on a shared file system (e.g. GFS) - failover then becomes a simple matter of reopening the file based store on a different node on failover.

Where a shared filesystem is not available we will have to consider replicating to a buddy.

The best candidate for implementing local persistence currently is Berkely DB. However, due to the Berkely DB licence we cannot distribute it with JBM, therefore it would be up to the user to drop the Berkely DB jar in manually as part of the install.

We we would also need to provide a very simple JDBC PersistenceManager implementation to allow to run the tests and play about with the default distribution - this can work with HSQLDB.

> Enabled local persistent storage per node
> -----------------------------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Implement non shared file based persistent store.
> Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this.
> Also look at HOWL. http://howl.objectweb.org/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:44:49 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:44:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-608) Add a new
 compatibity and stress test layer based on JMS CTS
In-Reply-To: <13967074.1160688881540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20017340.1191235489517.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-608?page=all ]

Tim Fox updated JBMESSAGING-608:
--------------------------------

    Priority: Minor  (was: Major)

> Add a new compatibity and stress test layer based on JMS CTS
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-608
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-608
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> http://jmscts.sourceforge.net/index.html
> The stress part is especially interesting.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:46:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:46:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-989) Core refactoring
In-Reply-To: <20687334.1181830811626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24277185.1191235601183.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-989?page=all ]

Tim Fox closed JBMESSAGING-989.
-------------------------------

    Resolution: Rejected

We don't really need a separate task for this.

Various core changes will take place via other tasks.

> Core refactoring
> ----------------
>
>                 Key: JBMESSAGING-989
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-989
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Core refactoring-
> The old core classes are in dire need of reviewing and refactoring.
> The hierarchy of channel classes should be collapsed for simplicity, since there is only one real implementation of a channel.
> And the router class should be re-examined - do we need iterator etc
> Do we need iterator on the channel?
> All classes should be made cluster aware (including router).
> We can simplify things a *lot*!

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:46:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:46:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-752) Create safe
 mode where session concurrent access is checked
In-Reply-To: <32776071.1169034952624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23352622.1191235601300.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-752?page=all ]

Tim Fox updated JBMESSAGING-752:
--------------------------------

    Priority: Minor  (was: Major)

> Create safe mode where session concurrent access is checked
> -----------------------------------------------------------
>
>                 Key: JBMESSAGING-752
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-752
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> As per JMS spec, a JMS session is supposed to be only accessed from one thread at a time.
> This is so the implementor does not have to synchronize access which might degrade performance.
> However, users are often unaware of this and use the session concurrent by multiple threads, resulting in subtle or hard to identify bugs.
> We should create a "safeMode", where if enabled, concurrent access is checked.
> safeMode should be turned on for development and off for production, so no performance penalty is incurred in production.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:48:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-873) Down cache
	optimisation
In-Reply-To: <17669332.1172085995882.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21967604.1191235721233.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-873?page=all ]

Tim Fox closed JBMESSAGING-873.
-------------------------------

    Resolution: Out of Date

This is redundance - since using local persistence will involve refactoring of the paging code.

> Down cache optimisation
> -----------------------
>
>                 Key: JBMESSAGING-873
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-873
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db
> and just transfer from the downcache to the in memory list when loading

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:48:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1039) HTTP poller
	doesn't stop
In-Reply-To: <3265708.1186657442806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28570820.1191235721369.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1039?page=all ]

Tim Fox updated JBMESSAGING-1039:
---------------------------------

    Priority: Minor  (was: Major)

> HTTP poller doesn't stop
> ------------------------
>
>                 Key: JBMESSAGING-1039
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1039
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> I have temporarily commented out clusterviewupdatetst::testUpdateMixedConnectionFactory since, once started, the HTTP poller doesn't stop.
> Maybe this is a bug in remoting - need to investigate.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:48:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1049) Exceptions in
 logs after clustering test run
In-Reply-To: <28422090.1187257381307.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16000172.1191235721552.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1049?page=all ]

Tim Fox updated JBMESSAGING-1049:
---------------------------------

    Priority: Minor  (was: Major)

> Exceptions in logs after clustering test run
> --------------------------------------------
>
>                 Key: JBMESSAGING-1049
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1049
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> After running clustering tests, several exceptions are found in the logs.
> These seem innocuous since the test suite passes but we should investigate.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:50:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-242) Investigate
 requirements for different routing strategies
Message-ID: <28297212.1191235841219.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-242?page=all ]

Tim Fox updated JBMESSAGING-242:
--------------------------------

    Priority: Minor  (was: Major)

> Investigate requirements for different routing strategies
> ---------------------------------------------------------
>
>                 Key: JBMESSAGING-242
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-242
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Investigate whether we need to provide routers with different strategies, a la ReceiversImpl in JBossMQ

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:50:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-806) Allow JBM
 client to run in a jnlp (or other) sandbox
In-Reply-To: <25824752.1170441321637.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32581180.1191235841459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-806?page=all ]

Tim Fox updated JBMESSAGING-806:
--------------------------------

       Summary: Allow JBM client to run in a jnlp (or other) sandbox  (was: JBM is assuming it can look up system properties on the client side)
    Issue Type: Task  (was: Bug)
      Priority: Minor  (was: Major)

> Allow JBM client to run in a jnlp (or other) sandbox
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-806
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.2.0.Beta1, 1.0.1.SP3
>            Reporter: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work.
> This causes an exception to be thrown and the connection is not created.
> Need to catch the exception and set to null.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:52:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:52:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-377) Competing
 consumer on subscriptions
Message-ID: <12151542.1191235961347.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-377?page=all ]

Tim Fox updated JBMESSAGING-377:
--------------------------------

    Priority: Minor  (was: Major)

> Competing consumer on subscriptions
> -----------------------------------
>
>                 Key: JBMESSAGING-377
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-377
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:52:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:52:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1014) Look at
	JGroups anycast
In-Reply-To: <9508348.1184347872500.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26993600.1191235961491.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1014?page=all ]

Tim Fox closed JBMESSAGING-1014.
--------------------------------

    Resolution: Rejected

> Look at JGroups anycast
> -----------------------
>
>                 Key: JBMESSAGING-1014
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1014
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> To avoid issue with having to multicast even when there is only one subscriber

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:52:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:52:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-153) Support for
 very large messages
Message-ID: <23427483.1191235961933.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ]

Tim Fox updated JBMESSAGING-153:
--------------------------------

    Summary: Support for very large messages  (was: JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred))

> Support for very large messages
> -------------------------------
>
>                 Key: JBMESSAGING-153
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.0.0 alpha PR3
>            Reporter: Karl de Boer
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 4 minutes
>  Remaining Estimate: 4 minutes
>
> As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:54:52 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:54:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-180) Improve
 message priority algorithm
Message-ID: <25722780.1191236092545.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-180?page=all ]

Tim Fox updated JBMESSAGING-180:
--------------------------------

    Priority: Minor  (was: Major)

> Improve message priority algorithm
> ----------------------------------
>
>                 Key: JBMESSAGING-180
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-180
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The current message priority strategy is very crude and always delivers higher priority messages first if they exist.
> This can cause starvation of lower priority messages.
> The algorithm should be improved to prevent starvation.
> It may be an idea to make the algorithm pluggable using the strategy pattern.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:54:53 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:54:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-874) INVM
 persistent message optimisation
In-Reply-To: <1124366.1172086122591.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3043316.1191236093340.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-874?page=all ]

Tim Fox updated JBMESSAGING-874:
--------------------------------

    Priority: Minor  (was: Major)

> INVM persistent message optimisation
> ------------------------------------
>
>                 Key: JBMESSAGING-874
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-874
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:56:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:56:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-875) Non durable
 subscription optimisation
In-Reply-To: <8504212.1172086235512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8850294.1191236201226.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-875?page=all ]

Tim Fox closed JBMESSAGING-875.
-------------------------------

    Resolution: Out of Date

> Non durable subscription optimisation
> -------------------------------------
>
>                 Key: JBMESSAGING-875
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-875
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs.
> Basically I think we can acknowledge them before they are sent from server to client.
> This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks.
> On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver.
> This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:56:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:56:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-872) Convert
	destinations to ints
In-Reply-To: <10164095.1172085776484.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5420076.1191236201380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-872?page=all ]

Tim Fox closed JBMESSAGING-872.
-------------------------------

    Resolution: Rejected

I don't see any great gains by doing this

> Convert destinations to ints
> ----------------------------
>
>                 Key: JBMESSAGING-872
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-872
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers.
> When sending a message the destination (and possibly the replyto) need to be serialized with the message.
> If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize.
> This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:58:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:58:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-839) Recover
 deliveries does not deal with paged references
In-Reply-To: <27585099.1171499561997.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3666283.1191236321139.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-839?page=all ]

Tim Fox closed JBMESSAGING-839.
-------------------------------

    Resolution: Rejected

Will become redundant with refactored paging

> Recover deliveries does not deal with paged references
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-839
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-839
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> When recovering deliveries ChannelSupport::recoverDeliveries after failover then there is a small possibility that the deliveries are not in memory but paged in storage  - we should cater for this situation.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:58:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:58:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-312) Refactor
	persistencemanager
Message-ID: <31886620.1191236321386.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ]

Tim Fox closed JBMESSAGING-312.
-------------------------------

    Resolution: Out of Date

> Refactor persistencemanager
> ---------------------------
>
>                 Key: JBMESSAGING-312
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Refactor PersistenceManager to make less monolithic.
> The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store.
> Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState.
> The TransactionCallback should be removed to it's own java file.
> The locking operations should occur in the caller.
> There should be an abstraction PMTxContext which can be passed into PM operations to group them.
> This should dramatically clarify and simplify things

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:00:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-868) Ordering issue
 when mixing unicast and multicast
In-Reply-To: <6386295.1172060495647.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26932910.1191236441264.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-868?page=all ]

Tim Fox closed JBMESSAGING-868.
-------------------------------

    Resolution: Won't Fix

> Ordering issue when mixing unicast and multicast
> ------------------------------------------------
>
>                 Key: JBMESSAGING-868
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-868
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.CR1
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> When routing a set of messages to nodes in a cluster, if some are routed using unicast and others using multicast (as an optimisation), then earlier messages can "overtake" later sent messages, so they are received in the wrong order on the recipient.
> This caused DefaultClusteredPostOfficeTest::testClusteredNonPersistentRouteWithFilterRecoverable to fail because messages were received out of order

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:00:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-576) Separate paging
 and persistence functionality
In-Reply-To: <17187039.1159815521510.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5872998.1191236441419.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-576?page=all ]

Tim Fox closed JBMESSAGING-576.
-------------------------------

    Resolution: Rejected

> Separate paging and persistence functionality
> ---------------------------------------------
>
>                 Key: JBMESSAGING-576
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-576
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.2.0.Alpha1, 1.0.1.CR5
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Reference management gets complex when we have to take into account messages and refs paged and not paged to storage especially if
> the database is shared, this means we end up having to do extra queries to work out if the ref is alredy in the database etc.
> We should separate the paging functionality out, so it doesn't page to the normal persistent store, but to a separate paging store which
> typically would be a local file based store using HOWL or some other fast logger.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:00:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:00:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-676) Unreliable link
	scenario
In-Reply-To: <29509260.1165555418180.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23220141.1191236442948.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-676?page=all ]

Tim Fox closed JBMESSAGING-676.
-------------------------------

    Resolution: Rejected

> Unreliable link scenario
> ------------------------
>
>                 Key: JBMESSAGING-676
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-676
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Ovidiu Feodorov
>             Fix For: 2.0.0 Beta 1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:02:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4768) TransactionLocal
 cannot be locked when transaction is marked rollback only
Message-ID: <30772673.1191236561517.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------

                 Key: JBAS-4768
                 URL: http://jira.jboss.com/jira/browse/JBAS-4768
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Transaction Manager
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Adrian Brock
         Assigned To: Jonathan Halliday
            Priority: Critical
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA


Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.

Here's the stacktrace of the error:

2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
java.lang.IllegalStateException: Transaction not active
        at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
        at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
        at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
        at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
        at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
        at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
        at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
        at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)

You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-543) Use a file
 based transaction logger instead of logging in the database
In-Reply-To: <4467615.1158151954233.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10589639.1191236561798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-543?page=all ]

Tim Fox closed JBMESSAGING-543.
-------------------------------

    Resolution: Duplicate Issue

> Use a file based transaction logger instead of logging in the database
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-543
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-543
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Currently we are logging prepared state transactions in the database.
> Instead, we should utilise a tried and tested transaction logger for performance reasons.
> We should evaluate both JBoss TS objectstore, and HOWL to take this role

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:42 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:02:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4768) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <30772673.1191236561517.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11125223.1191236562245.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4768?page=all ]

Dimitris Andreadis deleted JBAS-4768:
-------------------------------------


> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4768
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4768
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1053) Write a test
 for JBMESSAGING-1031
In-Reply-To: <2848037.1187894843075.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4958503.1191236562372.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1053?page=all ]

Tim Fox updated JBMESSAGING-1053:
---------------------------------

    Priority: Minor  (was: Major)

> Write a test for JBMESSAGING-1031
> ---------------------------------
>
>                 Key: JBMESSAGING-1053
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1053
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: diff.patch
>
>
> I have fixed JBMESSAGING-1031 using a manual test.. we need to add a testcase.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1048) Test DB2
 config against Hudson
In-Reply-To: <16680822.1187133001211.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32639393.1191236562736.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1048?page=all ]

Tim Fox updated JBMESSAGING-1048:
---------------------------------

    Priority: Minor  (was: Major)

> Test DB2 config against Hudson
> ------------------------------
>
>                 Key: JBMESSAGING-1048
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1048
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:43 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-26) Standalone
 Messaging configuration.
Message-ID: <4385477.1191236563036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ]

Tim Fox closed JBMESSAGING-26.
------------------------------

    Resolution: Rejected

> Standalone Messaging configuration.
> -----------------------------------
>
>                 Key: JBMESSAGING-26
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. 
> Must have at least the JNDI server, Logging, Remoting and AOP support.
> We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:04:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:04:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-983) Messages can
 be delivered after connection is stopped
In-Reply-To: <20962966.1181209274478.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20081795.1191236681151.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-983?page=all ]

Tim Fox updated JBMESSAGING-983:
--------------------------------

    Priority: Minor  (was: Major)

> Messages can be delivered after connection is stopped
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-983
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-983
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> Stopping a connection does not currently block until all current onMessage invocations are complete, as per JMS spec.
> We need to make sure it does.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:04:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:04:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4769) TransactionLocal
 cannot be locked when transaction is marked rollback only
Message-ID: <2618872.1191236681324.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------

                 Key: JBAS-4769
                 URL: http://jira.jboss.com/jira/browse/JBAS-4769
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Transaction Manager
            Reporter: Dimitris Andreadis
         Assigned To: Adrian Brock
             Fix For:  JBossAS-5.0.0.Beta3


Apply JBAS-4675 fix to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:46 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4769) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <2618872.1191236681324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21682821.1191236806944.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4769?page=all ]

Dimitris Andreadis updated JBAS-4769:
-------------------------------------

    Component/s: JB5-Transaction Manager
                     (was: Transaction Manager)
       Assignee: Jonathan Halliday  (was: Adrian Brock)

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4769
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4769
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Apply JBAS-4675 fix to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1086) Implement
	Database updater
Message-ID: <14676569.1191236807091.JavaMail.jira@cloud.prod.atl2.jboss.com>

Implement Database updater
--------------------------

                 Key: JBMESSAGING-1086
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1086
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 2.0.0 Beta 1


JBM 2.0 will use local persistent storage per node, in most cases non relational.

Some users still like to see their messages in a database.

We should implement a component that can optionally run on each node, that intermittently checks the local storage to new messages / delete messages and updates a shared database with the message data.

Hibernate should be used for this component so it can work with any supported RDBMs.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4675) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <27607648.1189008194281.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22866091.1191236807442.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]

Dimitris Andreadis closed JBAS-4675.
------------------------------------

    Fix Version/s:     (was: JBossAS-4.2.2.GA)
       Resolution: Done

Closing this for 4.2.x. Created a different issue for AS5.

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4675
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4675
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4675) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <27607648.1189008194281.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29782219.1191236807650.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]

Dimitris Andreadis reopened JBAS-4675:
--------------------------------------

             

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4675
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4675
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4675) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <27607648.1189008194281.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5727287.1191236807897.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]

Dimitris Andreadis closed JBAS-4675.
------------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
                       (was:  JBossAS-5.0.0.Beta3)
       Resolution: Done

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4675
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4675
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:48 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:06:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16840047.1191236808031.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=all ]

Tim Fox updated JBMESSAGING-544:
--------------------------------

        Summary: Replace client-server transport with NIO based transport  (was: Use NBIO for connection model)
    Description: 
For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.

Unfortunately the JBoss remoting model does not currently allows this.

We can either drive JBoss Remoting to support this model (may take some time)

Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.

This would also solve the problem of providing a functional and performant multiplex transport.

Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.

On top of that we can introduce simple framing in order to provide multiplex functionality.

  was:
For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server.

Unfortunately the JBoss remoting model does not currently allows this.

We can either drive JBoss Remoting to support this model (may take some time)

Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.

This would also solve the problem of providing a functional and performant multiplex transport.

Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.

On top of that we can introduce simple framing in order to provide multiplex functionality.

       Priority: Critical  (was: Major)

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:08:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-848) Incorrect
 mail.smtp.host property + configurable mail from address
In-Reply-To: <17596894.1172162918880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8017960.1191236921890.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-848?page=comments#action_12379543 ] 
            
Tom Baeyens commented on JBPM-848:
----------------------------------

Fady, i don't get your remark.

As far as I remember, it should be possible for people to specify the property jbpm.mail.from.address in their jbpm.cfg.xml file.  Can you try to reproduce and compare the problem report of Sebastian with the docs and the code ?

In case our code is the problem, how do you think we should fix it ?

> Incorrect mail.smtp.host property + configurable mail from address
> ------------------------------------------------------------------
>
>                 Key: JBPM-848
>                 URL: http://jira.jboss.com/jira/browse/JBPM-848
>             Project: JBoss jBPM
>          Issue Type: Patch
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2 beta 2
>            Reporter: Bruno Dumon
>         Assigned To: Tom Baeyens
>             Fix For: jBPM jPDL 3.2.2
>
>         Attachments: mailpatch_20070222.txt, mailpatch_v2.txt
>
>
> jBPM incorrectly sets "jbpm.mail.smtp.host" instead of "mail.smtp.host" in the properties passed to JavaMail. As a consequence, JavaMail always tries to send to localhost. It seems this was introduced by accident here:
> http://fisheye.jboss.com/browse/JBPM/jbpm.3/src/java.jbpm/org/jbpm/mail/Mail.java?r1=1.4&r2=1.5
> The attached patch fixes this.
> Also, the from address for mails is currently hardcoded to "jbpm at noreply". Many SMTP servers don't allow an invalid origin domain name (as do many spam filters), this is the exception I get:
> javax.mail.SendFailedException: Sending failed;
>   nested exception is:
>         class javax.mail.SendFailedException: Invalid Addresses;
>   nested exception is:
>         class javax.mail.SendFailedException: 450 <jbpm at noreply>: Sender address rejected: Domain not found
> The attached patch also makes the from address configurable via jbpm.cfg.xml.
> Patches are against current CVS and taken with the jbpm.3/jpdl directory as root.
> Thanks for taking the time to look at 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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:08:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22576267.1191236922165.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=comments#action_12379544 ] 
            
Tim Fox commented on JBMESSAGING-544:
-------------------------------------

After discusssion with the remoting team and other interested parties, our requirements will eventually be catered for by the new Remoting 3.

However Remoting 3 will not be released in time for JBM 2.0, therefore we will use MINA directly and swap it out later for JBR 3.

We need to make sure that MINA satisfies our requirements for HTTP, HTTPS, SSL etc

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:42 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:08:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
Message-ID: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionLocal.get() not sufficiently pluggable
-------------------------------------------------

                 Key: JBAS-4770
                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JB5-Transaction Manager
            Reporter: Dimitris Andreadis
         Assigned To: Mark Little
             Fix For:  JBossAS-5.0.0.Beta3


JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:08:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1025) Add test in
 GroupManagementTest
In-Reply-To: <24748680.1186597189354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33319407.1191236922508.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1025?page=all ]

Tim Fox updated JBMESSAGING-1025:
---------------------------------

    Priority: Minor  (was: Major)

> Add test in GroupManagementTest
> -------------------------------
>
>                 Key: JBMESSAGING-1025
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1025
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> .... that tests that failover map is created in vew order

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:10:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17893203.1191237041241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4770?page=all ]

Dimitris Andreadis reassigned JBAS-4770:
----------------------------------------

    Assignee: Jonathan Halliday  (was: Mark Little)

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:10:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4748)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <19029355.1190647481599.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9968477.1191237041375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4748?page=all ]

Dimitris Andreadis updated JBAS-4748:
-------------------------------------

        Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
    Affects Version/s:     (was: JBossAS-5.0.0.Beta2)

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4748
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4748
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Jonathan Halliday
>         Assigned To: Jonathan Halliday
>             Fix For: JBossAS-4.2.2.GA
>
>
> per discussion in forum thread ref below, the TransactionLocal.get() method calls storeValue in certain cases. Although the javadoc warns that the method may throw IllegalStateException, not all of the code in the app server that uses it can actually deal with that. With the old delegate implementation it did not need to. With changes to the way the TransactionLocalDelegate is implemented by JBossTS, this stared to cause problems.  Per Adrian's suggestion this is resolved by masking the exception if it occurs.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:10:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4748)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <19029355.1190647481599.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14347409.1191237041512.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4748?page=all ]

Dimitris Andreadis closed JBAS-4748.
------------------------------------

    Resolution: Done

Closed in 4.2.x. Created a separate task for Trunk.

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4748
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4748
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Jonathan Halliday
>         Assigned To: Jonathan Halliday
>             Fix For: JBossAS-4.2.2.GA
>
>
> per discussion in forum thread ref below, the TransactionLocal.get() method calls storeValue in certain cases. Although the javadoc warns that the method may throw IllegalStateException, not all of the code in the app server that uses it can actually deal with that. With the old delegate implementation it did not need to. With changes to the way the TransactionLocalDelegate is implemented by JBossTS, this stared to cause problems.  Per Adrian's suggestion this is resolved by masking the exception if it occurs.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:12:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:12:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1052)
 getAllTaskInstances(), getAllProcessInstances()
In-Reply-To: <24526709.1189013891148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29473795.1191237161277.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1052?page=comments#action_12379546 ] 
            
Tom Baeyens commented on JBPM-1052:
-----------------------------------

Current web app blurs the authorization a bit.  Basically, there is no real authorization scheme yet.  One of the things that certainly should be fixed is that by default users should only be able to see their own task lists.

Maybe we could have a navigation link to the full list of tasks separately, but that link should only be visible/accessible based on a security role manager.  or something like that.

> getAllTaskInstances(), getAllProcessInstances()
> -----------------------------------------------
>
>                 Key: JBPM-1052
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1052
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: s b
>         Assigned To: Tom Baeyens
>            Priority: Minor
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Businesses often want a "super manager" to have the ability to see and work on the tasks of all users.  With the current jBPM, it is very difficult to generate a list of all TaskInstances.
> The feature requested is a method for listing all TaskInstances regardless of user.  It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds.
> One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances.  I don't know if that is portable to all databases; it works well for Oracle.
> It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours.
> A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons.
> A criticism is that the method would introduce scalability / performance problems.  That is always an issue that is difficult to avoid completely depending on the application.  For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:12:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:12:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-942) Performance
	comparisons
In-Reply-To: <2148587.1176983619628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1812759.1191237161415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-942?page=all ]

Tim Fox updated JBMESSAGING-942:
--------------------------------

    Fix Version/s: Performance metrics, benchmarks and scalability testing
                       (was: Unscheduled)

> Performance comparisons
> -----------------------
>
>                 Key: JBMESSAGING-942
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-942
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>             Fix For: Performance metrics, benchmarks and scalability testing
>
>
> We need to make perfomance comparisons between JBR and MINA.
> Also between JBM and ActiveMQ and QPid

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:12:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:12:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-942) Performance
	comparisons
In-Reply-To: <2148587.1176983619628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26982150.1191237161536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-942?page=all ]

Tim Fox updated JBMESSAGING-942:
--------------------------------

    Description: Make performance comparisons between JBM and other messaging systems.  (was: We need to make perfomance comparisons between JBR and MINA.

Also between JBM and ActiveMQ and QPid)

> Performance comparisons
> -----------------------
>
>                 Key: JBMESSAGING-942
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-942
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>             Fix For: Performance metrics, benchmarks and scalability testing
>
>
> Make performance comparisons between JBM and other messaging 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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:14:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:14:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-603) Performance
	graphs
In-Reply-To: <23921338.1160165441490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2319217.1191237281271.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-603?page=all ]

Tim Fox closed JBMESSAGING-603.
-------------------------------

    Resolution: Duplicate Issue

> Performance graphs
> ------------------
>
>                 Key: JBMESSAGING-603
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-603
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>             Fix For: Unscheduled
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:14:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:14:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1087) Clustering
 scalability tests
Message-ID: <1256813.1191237281609.JavaMail.jira@cloud.prod.atl2.jboss.com>

Clustering scalability tests
----------------------------

                 Key: JBMESSAGING-1087
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1087
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: Performance metrics, benchmarks and scalability testing


Setup clustering scalabiity tests on the clustering lab.

Design metrics and see how performance varies with number of nodes etc.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:17:12 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:17:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1053) jBPM Build Files
 Search for build.properties in ${user.home}/jbpm/build.properties
In-Reply-To: <20341275.1189026614587.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30879988.1191237432326.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1053?page=comments#action_12379547 ] 
            
Tom Baeyens commented on JBPM-1053:
-----------------------------------

Christopher, please explain your requirements a bit more concrete.

This is what we currently have: a cvs structure that performs a full build with defaults in cvs.  The idea is that during continious integration, the cvs sources are fetched as is so that the complete sources can be cleaned and fetched again.  So any specific build configurations by default have to go outside the cvs sources structure.  That is why I don't get your request.  You don't *have* to have a custom build.properties file.  It's only necessary when you want to override default properties.  Maybe the defaults that we have are not as you want.  In that case, be more specific.

> jBPM Build Files Search for build.properties in ${user.home}/jbpm/build.properties
> ----------------------------------------------------------------------------------
>
>                 Key: JBPM-1053
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1053
>             Project: JBoss jBPM
>          Issue Type: Release
>            Reporter: Christopher Brock
>         Assigned To: Tom Baeyens
>
> This has become a pretty serious problem in our attempts to create automated build and patches for SOA.   It creates a mess by forcing us to have our scripts create directories outside the build structure.  
> It would be helpful if the either a delegate configuration file was introduced to allow us to override this, or better yet, if jBPM simply defaulted to a sensible configuration file inside it's source structure.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:17:12 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:17:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1054) deprecate expression
 on action in favour of execute
In-Reply-To: <26830440.1189074491245.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19585034.1191237432484.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1054?page=all ]

Tom Baeyens updated JBPM-1054:
------------------------------

    Fix Version/s: jBPM jPDL 3.2.3

> deprecate expression on action in favour of execute
> ---------------------------------------------------
>
>                 Key: JBPM-1054
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1054
>             Project: JBoss jBPM
>          Issue Type: Task
>    Affects Versions:  jBPM jPDL 3.2.1
>            Reporter: Pete Muir
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> As discussed on the forum, add an execute attribute (as an alias to expression) to the action element, and (TBD) deprecate the expression.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:18:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:18:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPM-616) prevent duplicate
 form submissions
Message-ID: <20429096.1191237521131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-616?page=all ]

Tom Baeyens reassigned JBPM-616:
--------------------------------

    Assignee: Tom Baeyens  (was: David Lloyd)

> prevent duplicate form submissions
> ----------------------------------
>
>                 Key: JBPM-616
>                 URL: http://jira.jboss.com/jira/browse/JBPM-616
>             Project: JBoss jBPM
>          Issue Type: Task
>          Components: Web Interface
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>             Fix For: jBPM 3.3
>
>
> for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:18:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:18:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-616) prevent duplicate
	form submissions
Message-ID: <1886975.1191237521270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-616?page=all ]

Tom Baeyens updated JBPM-616:
-----------------------------

    Priority: Minor  (was: Major)

> prevent duplicate form submissions
> ----------------------------------
>
>                 Key: JBPM-616
>                 URL: http://jira.jboss.com/jira/browse/JBPM-616
>             Project: JBoss jBPM
>          Issue Type: Task
>          Components: Web Interface
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>            Priority: Minor
>             Fix For: jBPM 3.3
>
>
> for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:24:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:24:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4667) Wrong logic in
 CachedConnectionManager.getCloseConnectionSynchronization()
In-Reply-To: <33485329.1188920711605.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23262613.1191237881862.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4667?page=all ]

Dimitris Andreadis closed JBAS-4667.
------------------------------------

    Resolution: Done

Closing this task for 4.2.x. Created separate issues to track the changes in JBoss trunk. Essentially we are waiting there for the next jbossts upgrade.

> Wrong logic in CachedConnectionManager.getCloseConnectionSynchronization()
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4667
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4667
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.0.4.GA
>            Reporter: Oleg Nitz
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>         Attachments: testbmtsfsb.zip
>
>
> If the tx is not active (for example it has STATUS_PREPARING), then the method always returns null, even if the associated CloseConnectionSynchronization exists.
> This results in wrong warnings about non-closed connections, since when the close() is called for a connector, in CachedConnectionManager.unregisterConnection() a null value is returned from getCloseConnectionSynchronization() and the connector remains in the list of non-closed resources for the transaction.
> I think this bug was introduced here: http://jira.jboss.com/jira/browse/JBAS-31#action_12310798
> I propose the following solution:
> --- CachedConnectionManager.java.orig	2005-11-22 02:10:41.000000000 +0200
> +++ CachedConnectionManager.java	2007-09-04 18:42:48.000000000 +0300
> @@ -544,13 +544,13 @@
>        try
>        {
>           Transaction tx = tm.getTransaction();
> -         if (TxUtils.isActive(tx))
> +         if (tx != null)
>           {
>              TransactionSynchronizer.lock(tx);
>              try
>              {
>                 CloseConnectionSynchronization cas = (CloseConnectionSynchronization) TransactionSynchronizer.getCCMSynchronization(tx);
> -               if (cas == null && createIfNotFound)
> +               if (cas == null && createIfNotFound && TxUtils.isActive(tx))
>                 {
>                    cas = new CloseConnectionSynchronization();
>                    TransactionSynchronizer.registerCCMSynchronization(tx, cas);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:26:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:26:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4767) Upgrade jbossws to
 2.0.1 (from 1.2.1.GA)
In-Reply-To: <16412352.1191227742601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32763163.1191238001105.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4767?page=all ]

Dimitris Andreadis reassigned JBAS-4767:
----------------------------------------

    Assignee: Thomas Diesler

> Upgrade jbossws to 2.0.1 (from 1.2.1.GA)
> ----------------------------------------
>
>                 Key: JBAS-4767
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4767
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:37:41 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 07:37:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1237) Upgrade MVEL
 library to 1.2.final
In-Reply-To: <5418439.1191220061206.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11340953.1191238661510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1237?page=all ]

Mark Proctor closed JBRULES-1237.
---------------------------------

    Resolution: Out of Date

4.0.2 will use the latest version of MVEL on it's release, which is already beyond 1.2final.

> Upgrade MVEL library to 1.2.final
> ---------------------------------
>
>                 Key: JBRULES-1237
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1237
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> Upgrade the current mvel library that is used by drools to mvel 1.2.final as it has some fixes

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:44:41 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 07:44:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-811) Use
 InvocationContext to avoid multiple searches for a node
In-Reply-To: <31984417.1161791681504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26405054.1191239081200.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]

Manik Surtani updated JBCACHE-811:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> Use InvocationContext to avoid multiple searches for a node
> -----------------------------------------------------------
>
>                 Key: JBCACHE-811
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-811
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> When an interceptor finds a node, why not throw it in the InvocationContext or something similar and pass it through the stack that way? Subsequent calls to find the node can check the context first before walking the cache tree. Saves redundant walking of the tree.
> We'd need to think very carefully about this, as it exposes 2 paths to access a node -- from a thread's context and from the tree.  Need to ensure concurrent threads always access the same node object for a given Fqn.
> (Side thought -- perhaps disable this for weak isolation levels where the locking behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same Fqn).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:08:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 08:08:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-886) change ejb timers
 from SLSB to an entity bean approach
In-Reply-To: <22781626.1173088271818.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14847136.1191240521299.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-886?page=comments#action_12379554 ] 
            
Tom Baeyens commented on JBPM-886:
----------------------------------

some more explanations:

currently, the EjbSchedulerService will use the ejb timer service of the TimerServiceBean (SLSB) to create an ejb timer.  that way, all ejb timers are created in one single SLSB.

so if later, we need to cancel a timer, we need to scan through all the ejb timers in order to find the right one.  (there is no querying capability in ejb timers)

the solution is can see is that we use one timer entity bean per timer instead of the single SLSB for all timers.

then we can first query the right timer beans, knowing that each timer bean will have exectly 1 timer associated with it.


> change ejb timers from SLSB to an entity bean approach
> ------------------------------------------------------
>
>                 Key: JBPM-886
>                 URL: http://jira.jboss.com/jira/browse/JBPM-886
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> the problem is that all the timers are put on a single slsb.  so we have to loop through all the timers to cancel or find one.  that is a bottleneck.
> we need to change that approach to the use of entity beans.  1 entity bean per job.  so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:10:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 08:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-886) change ejb timers
 from SLSB to an entity bean approach
In-Reply-To: <22781626.1173088271818.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17781158.1191240641216.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-886?page=comments#action_12379555 ] 
            
Tom Baeyens commented on JBPM-886:
----------------------------------

the timer entity bean should leverage the existing JBPM_JOB table.  most difficult part will be to do a flush between the moment when a new job is persisted with the hibernate session and then you need to flush before loading that same record as an  entity bean to schedule the ejb timer on it.

> change ejb timers from SLSB to an entity bean approach
> ------------------------------------------------------
>
>                 Key: JBPM-886
>                 URL: http://jira.jboss.com/jira/browse/JBPM-886
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> the problem is that all the timers are put on a single slsb.  so we have to loop through all the timers to cancel or find one.  that is a bottleneck.
> we need to change that approach to the use of entity beans.  1 entity bean per job.  so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:26:43 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 08:26:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-25) Microcontainer
	integration
Message-ID: <13678388.1191241603381.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ]

Tim Fox reassigned JBMESSAGING-25:
----------------------------------

    Assignee: Andy Taylor  (was: Aaron Walker)

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Andy Taylor
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:30:43 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 08:30:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1191) Work with
 contributor to translate JBoss Cache documentation into Spanish
Message-ID: <25972580.1191241843360.JavaMail.jira@cloud.prod.atl2.jboss.com>

Work with contributor to translate JBoss Cache documentation into Spanish
-------------------------------------------------------------------------

                 Key: JBCACHE-1191
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1191
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Manik Surtani
         Assigned To: Michael Smith
             Fix For: 2.2.0.GA


See email sent in to the jbosscache-dev list:

http://lists.jboss.org/pipermail/jbosscache-dev/2007-September/002031.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:13:42 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 09:13:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-470) Add a pointcut
 construction to match the field of a Class as being a type
Message-ID: <21666519.1191244422558.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add a pointcut construction to match the field of a Class as being a type
-------------------------------------------------------------------------

                 Key: JBAOP-470
                 URL: http://jira.jboss.com/jira/browse/JBAOP-470
             Project: JBoss AOP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Flavia Rainone


The idea is to allow the especification of a field value of a class as being the type of any pointcut expression.

The idea is to allow 
my.package.MyClass.field

whenever the following constructs are accepted:
- the name of a class
- annotated (@)
- implements
- type def 
- instanceof

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:53 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 09:17:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-910)
 TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
In-Reply-To: <7891202.1166570293319.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4194615.1191244673128.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-910?page=all ]

Manik Surtani resolved JBCACHE-910.
-----------------------------------

    Resolution: Done

> TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
> -----------------------------------------------------
>
>                 Key: JBCACHE-910
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-910
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.ALPHA2
>            Reporter: Elias Ross
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA
>
>
> This method is called by the region manager.
> There's a bunch of Voodoo taking place here, legacy bits mixed with some newer stuff.
> One thing that strikes me as wrong already is this code:
> child = factory.createDataNode(type, name,
>                        subtree.getFqnChild(i + 1),
>                        parent, lock_table, coordinator, null, this.rootSpi);
> For some reason, it is passing the lock_table into the Node as the data to initialize the node with.
> Somehow I think the right way to fix this would be to do a Cache.addChild(Fqn) call in RegionManager and remove this method.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:54 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 09:17:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-989) Create performance
 test suite to test failover
In-Reply-To: <26116759.1172673610805.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2716063.1191244674034.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-989?page=all ]

Manik Surtani updated JBCACHE-989:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> Create performance test suite to test failover
> ----------------------------------------------
>
>                 Key: JBCACHE-989
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-989
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Phillip Thurmond
>             Fix For: 2.2.0.GA
>
>
> Should be ideally integrated into cruise control builds, and should test a variety of configurations including sync and async replication, BR, etc.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:54 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 09:17:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-63) JBossCache
	benchmarks
Message-ID: <5442979.1191244674215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-63?page=all ]

Manik Surtani updated JBCACHE-63:
---------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> JBossCache benchmarks
> ---------------------
>
>                 Key: JBCACHE-63
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-63
>             Project: JBoss Cache
>          Issue Type: Task
>    Affects Versions: 1.2.4SP1
>            Reporter: Bela Ban
>         Assigned To: Phillip Thurmond
>             Fix For: 2.2.0.GA
>
>   Original Estimate: 4 weeks
>  Remaining Estimate: 4 weeks
>
> Also bench against other caches

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:54 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 09:17:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-602) Update FLUSH diagrams
 for joining and for state transfer
Message-ID: <16456584.1191244674372.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update FLUSH diagrams for joining and for state transfer
--------------------------------------------------------

                 Key: JGRP-602
                 URL: http://jira.jboss.com/jira/browse/JGRP-602
             Project: JGroups
          Issue Type: Task
            Reporter: Bela Ban
         Assigned To: Bela Ban
            Priority: Minor
             Fix For: 2.6


Update the 2 png files to reflect the new simplified FLUSH protocol

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:26:41 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 09:26:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-470) Add a pointcut
 construction to match the field of a Class as being a type
In-Reply-To: <21666519.1191244422558.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21352050.1191245201219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-470?page=comments#action_12379573 ] 
            
Flavia Rainone commented on JBAOP-470:
--------------------------------------

Consider the typedef expression:
<typedef name="TD" expr="(class(POJO.field)" />

Where POJO class follows:
public class POJO
{
  public POJO2 field;
}

I can think of the following approache to identify the matching objects:
- add a field "Collection<ClassName> isInside<ClassName>_<fieldName>" on the class that is the type of the field <ClassName>.<fieldName> especfied on the pointcut expression. This field would track whether an object is the value  <ClassName>.<fieldName> for one or more instances of ClassName. The goal is to identify positively only when isInside<ClassName>_<fieldName>.size() is larger then 0.

Probably there are other solutions beside this one.

> Add a pointcut construction to match the field of a Class as being a type
> -------------------------------------------------------------------------
>
>                 Key: JBAOP-470
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-470
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Flavia Rainone
>
> The idea is to allow the especification of a field value of a class as being the type of any pointcut expression.
> The idea is to allow 
> my.package.MyClass.field
> whenever the following constructs are accepted:
> - the name of a class
> - annotated (@)
> - implements
> - type def 
> - instanceof

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:36:41 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 09:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-602) Update FLUSH
 diagrams for joining and for state transfer
In-Reply-To: <16456584.1191244674372.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27027765.1191245801829.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-602?page=comments#action_12379580 ] 
            
Bela Ban commented on JGRP-602:
-------------------------------

Also update doc/design/FLUSH.txt

> Update FLUSH diagrams for joining and for state transfer
> --------------------------------------------------------
>
>                 Key: JGRP-602
>                 URL: http://jira.jboss.com/jira/browse/JGRP-602
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.6
>
>
> Update the 2 png files to reflect the new simplified FLUSH protocol

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:42:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 09:42:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-124) implement APR
	transport
Message-ID: <29100667.1191246161566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-124?page=all ]

David Lloyd closed JBREM-124.
-----------------------------

    Resolution: Won't Fix
      Assignee: David Lloyd

This task will not be done directly.  Remoting 3 will depend on MINA, which will ultimately get an APR transport layer, so we'll get this for free.

> implement APR transport
> -----------------------
>
>                 Key: JBREM-124
>                 URL: http://jira.jboss.com/jira/browse/JBREM-124
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: transport
>    Affects Versions: 1.2.0 final
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>            Priority: Critical
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Need to add support of Apache APR based transport.  The APR code (from tomcat-connector project) uses native code to manage threads and sockets.  The end result is a much better performance using a NIO type approach where only have threads in use for processing data off the socket.  When socket is idle, the threads are released and the native code will callback to activate a thread to process the data.  
> This effort has already been started in JBossRemoting on a branch called apr_transport.  Will probably not be fully implemented till after 1.2.0 release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:48:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 09:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-237) There is No String
 and Guage monitors in jboss
Message-ID: <30842737.1191246521522.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-237?page=comments#action_12379584 ] 
            
David Lloyd commented on JBREM-237:
-----------------------------------

If no update is posted to this issue within a week, I will close it.

> There is No String and Guage monitors in jboss
> ----------------------------------------------
>
>                 Key: JBREM-237
>                 URL: http://jira.jboss.com/jira/browse/JBREM-237
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: jmx remoting
>            Reporter: sree roja
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:48:41 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 09:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-598) Simplify FLUSH
In-Reply-To: <10363312.1190795201069.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25758910.1191246521914.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-598?page=comments#action_12379586 ] 
            
Bela Ban commented on JGRP-598:
-------------------------------

Update: maybe we nevertheless still need a FLUSH-COMPLETED phase, as someone might send a message in block() and we can only block all members from sending messages when all block()s have been called.

> Simplify FLUSH
> --------------
>
>                 Key: JGRP-598
>                 URL: http://jira.jboss.com/jira/browse/JGRP-598
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.4, 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> #1 Superfluous FLUSH-COMPLETED phase ?
> --------------------------------------
> It seems we don't need the FLUSH-COMPLETED phase, it is sufficient for
> the FLUSH leader to do a START-FLUSH and wait for all FLUSH-OK
> messages. Why ? Because the reconciliation protocol will reconcile
> messages before the view installation (or state transfer).
> Example: {A,B,C}. E sends message M and then crashes. Only C receives
> M.
> - A does a START-FLUSH
> - B and C send a FLUSH-OK back to A. This means that all multicasts
> from B will be seen by A *before* B's FLUSH-OK is received, and all
> multicasts from C will be seen by A before C's FLUSH-OK is received by
> A. HOWEVER, C will not necessarily send M to A before sending the
> FLUSH-OK message. This is only done through the reconciliation
> protocol !
> - FLUSH-COMPLETED can be removed, the digest that's part of
> FLUSH-COMPLETED has to moved to FKLUSH-OK phase.
> - FLUSH-OK is unicast *not* multicast.
> #2 Superfluous STOP-FLUSH-OK phase ?
> ------------------------------------
> Why do we need the acks here ? JGroups guarantees the STOP-FLUSH
> message is delivered to all non-faulty members, so why wait fr the
> STOP-FLUSH-OK ? 
> If we make STOP-FLUSH *OOB* (JGRP-337), then this should work ! We can
> get rid of STOP-FLUSH-OK !! Just send STOP-FLUSH as OOB multicast.
> Note: this requires the concurrent stack, so possibly check for
> concurrent stack. Throw an exception if concurrent stack is not
> present when FLUSH is used. So, these changes cannot be applied to
> 2.4, only to 2.5 and 2.6.
> #3 Timeouts
> -----------
> - ClientGmsImpl: has a hard coded timeout of 4 secs
> - CoordGmsImpl also has a timeout for block()
> - If we *need* timeouts, we should get them from the FLUSH protocol !
> CoorsGmsImpl.startFlush() should *not* have a timeout, this should be
> in FLUSH itself. startFlush() should block forever, until it gets the ack
> #4 Spurious FLUSH-OK in the diagram
> -----------------------------------
> In the JOIN diagram, probably also in the state transfer diagram

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:54:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 09:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-410) look at adding httpc
 as http client invoker
Message-ID: <20405734.1191246881527.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-410?page=all ]

David Lloyd closed JBREM-410.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Won't Fix
         Assignee: David Lloyd

Looks like nhttpc is abandonware at this point.  We'll always have MINA if we need this type of HTTP client.

> look at adding httpc as http client invoker
> -------------------------------------------
>
>                 Key: JBREM-410
>                 URL: http://jira.jboss.com/jira/browse/JBREM-410
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>
> https://nhttpc.dev.java.net/
> NIO HTTP Client
> An HTTP client built using JDK 1.4 NIO. Scales to thousands of
> concurrent client connections per VM with almost no CPU overhead.
> BSD license.
> In particular, need to see if has NTLM support

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:54:43 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ortwin_Gl=C3=BCck_=28JIRA=29?=)
Date: Mon, 1 Oct 2007 09:54:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-337) EJBException
 should set cause
Message-ID: <15405954.1191246883904.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-337?page=comments#action_12379590 ] 
            
Ortwin Gl?ck commented on EJBTHREE-337:
---------------------------------------

Seems that this bug is also in another place in EJB-3.0RC8 (sorry can't test this on later versions) when an EJBException caused by a NPE is propagated back through another EJB call as a EJBTransactionRolledbackException:

javax.ejb.EJBTransactionRolledbackException: java.lang.NullPointerException
 at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:93)
 at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
 at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:201)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:167)
 at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:100)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:181)
 at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79)


> EJBException should set cause
> -----------------------------
>
>                 Key: EJBTHREE-337
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-337
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC3
>         Environment: AS-4.0.3SP1, EJB-3.0RC3
>            Reporter: Ortwin Gl?ck
>         Assigned To: William DeCoste
>            Priority: Trivial
>             Fix For: EJB 3.0 RC4 - PFD
>
>
> When a NullPointerException is thrown in a session bean method the EJBException only provides the wrapped exception via getCausedByException()  and not via the Throwable#getCause() method. That causes stack traces to abort at the EJBException and the real exception is lost. It makes debugging harder.
> Caused by: javax.ejb.EJBException: null; CausedByException is:
> 	null
> 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:46)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:70)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:32)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:204)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:107)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:37)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:88)
> Painful Workaround:
> try {
>             bean.method();
> } catch (EJBException e) {
>             if (e.getCause() == null) e.initCause(e.getCausedByException());
>             throw e;
> }

-- 
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

       



From jira-events at lists.jboss.org  Mon Oct  1 10:00:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-103) Transport progress
 notification for client
Message-ID: <24902186.1191247241753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd updated JBREM-103:
------------------------------

    Component/s: r3 api
                     (was: marshall)
       Assignee: David Lloyd  (was: Tom  Elrod)

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:00:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-103) Transport progress
 notification for client
Message-ID: <26747218.1191247241961.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd updated JBREM-103:
------------------------------

    Fix Version/s: 3.0.0.Alpha1 (Otter)
                       (was: 4.0.0.Beta1)

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:02:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:02:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-13) NIO transport
Message-ID: <23841136.1191247365659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-13?page=all ]

David Lloyd closed JBREM-13.
----------------------------

    Fix Version/s: 3.0.0.Alpha1 (Otter)
                       (was: 4.0.0.Beta1)
       Resolution: Won't Fix
         Assignee: David Lloyd  (was: Tom  Elrod)

Remoting 3 will use MINA primarily, so NIO and APR are both free.

> NIO transport
> -------------
>
>                 Key: JBREM-13
>                 URL: http://jira.jboss.com/jira/browse/JBREM-13
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: transport
>    Affects Versions: 1.0.1 alpha
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>            Priority: Optional
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Add NIO transport.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:04:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:04:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-103) Transport progress
 notification for client
Message-ID: <149243.1191247481194.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd closed JBREM-103.
-----------------------------

    Resolution: Done

Implemented in current Remoting 3 API/Core.

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:10:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 10:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-306) Supports
	recovery flag
Message-ID: <1236287.1191247841397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ]

Tim Fox updated JBMESSAGING-306:
--------------------------------

    Priority: Minor  (was: Major)

> Supports recovery flag
> ----------------------
>
>                 Key: JBMESSAGING-306
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-306
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Should have flag "supports XA recovery" on persistencemanager.
> If = false then only tx id, not all xid fields are persisted on prepare. This should improve performance when xa recovery is not required.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:27:42 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:27:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-433) point to
 multipoint invocation api
Message-ID: <3512824.1191248862258.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-433?page=comments#action_12379602 ] 
            
David Lloyd commented on JBREM-433:
-----------------------------------

One possible use that came up in recent meetings: The ability to send a request and verify that all replies match, or to send a request and accept the first reply that meets certain criteria.

I still don't know any real-world use cases for this though.

> point to multipoint invocation api
> ----------------------------------
>
>                 Key: JBREM-433
>                 URL: http://jira.jboss.com/jira/browse/JBREM-433
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time.  The responses for each target server would be aggregated into one response as return to the client call.  Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for 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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:47:41 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 10:47:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4572) EJB 3 testsuite 100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25132549.1191250061672.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4572?page=all ]

William DeCoste closed JBAS-4572.
---------------------------------

    Resolution: Done

> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:56:55 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 10:56:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3142) Add UnifiedInvoker
 (JBSer and JavaSer) into Version MatrixTestSuite
Message-ID: <17635778.1191250615646.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3142?page=all ]

Clebert Suconic updated JBAS-3142:
----------------------------------

    Priority: Optional  (was: Major)

> Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite
> -------------------------------------------------------------------
>
>                 Key: JBAS-3142
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3142
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Optional
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:00:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 11:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-45)   Remoting watchdog
Message-ID: <22931246.1191250841588.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-45?page=all ]

David Lloyd closed JBREM-45.
----------------------------

    Resolution: Out of Date
      Assignee: David Lloyd  (was: Tom  Elrod)

This issue is in three parts:

1) Build in ability for the server to be aware of clients that exist and their status.

Remoting 3 does not have a notion of client vs. server.  That said, an Endpoint will always be aware of the status of its Sessions.

2) Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references.

This is probably out of scope for Remoting 3 - I'm inclined to let this die until a specific issue arises.  Specifically, Remoting 3 doesn't normally utilize the idea of a remote object.  Anything that does, will be built on top of Remoting 3 and will probably be responsible for dealing with this functionality.

3) Need ability to disconnect client from server when there has been an extended period of inactivity.

This would be very specific to the protocol.  Additionally complicated by the addition of Context/Session layers.

>   Remoting watchdog
> -------------------
>
>                 Key: JBREM-45
>                 URL: http://jira.jboss.com/jira/browse/JBREM-45
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.0.1 beta
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> Build in ability for the server to be aware of clients that exist and their status. Will be needed for doing distributed garbage collection, client connection timeout, etc.
> Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references.
> Need ability to disconnect client from server when there has been an extended period of inactivity.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:12:43 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 11:12:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <33379958.1191251563655.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379620 ] 
            
David Lloyd commented on JBREM-305:
-----------------------------------

Thomas, are there any specific requirements regarding the format of the JMS message?  Or do you just want your message to be moved from one endpoint to another?

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: Tom  Elrod
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:36:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 11:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-324) Facility for
 real-time decision
 on best InvokerLocator by which to contact a given handler.
Message-ID: <25880124.1191253001427.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12379624 ] 
            
David Lloyd commented on JBREM-324:
-----------------------------------

The Routing/Discovery API of Remoting 3 should facilitate this ability, if I understand correctly.  It will maintain a list of paths to endpoints, and choose the best one available at any given time.

> Facility for real-time decision on best InvokerLocator by which to contact a given handler.
> -------------------------------------------------------------------------------------------
>
>                 Key: JBREM-324
>                 URL: http://jira.jboss.com/jira/browse/JBREM-324
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.0.Beta1
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 4.0.0.Beta1
>
>
> The basic idea is to be able to communicate with a single handler by way of different InvokerLocators.  For example, if you're working over the internet, compression might be advantageous, but if you're local it might not be.  So you could have two Connectors sharing a handler, one using the compression marshaller and one not.
> How about a client that
> 1. gets the InvokerLocators for all of the Connectors for a certain handler, via a detector,
> 2. sends some sample invocations to each and times them, and
> 3. displays the results.
> It could be used for real time decision making or to collect information for a set of rules.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:54:41 2007
From: jira-events at lists.jboss.org (Eric Brennan (JIRA))
Date: Mon, 1 Oct 2007 11:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1731) Document /
 Tutorial Data Display from Database using Hibernate
Message-ID: <2367872.1191254081355.JavaMail.jira@cloud.prod.atl2.jboss.com>

Document / Tutorial Data Display from Database using Hibernate
--------------------------------------------------------------

                 Key: JBPORTAL-1731
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1731
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Reference Guide
    Affects Versions: 2.6.2 Final
         Environment: Portal 2.6.1 GA
Oracle backend. 
            Reporter: Eric Brennan
         Assigned To: Julien Viet
            Priority: Optional


It would be nice to have a tutorial on Displaying records from a Database using hibernate. Could expand the Helloworld example to pull two fields from a database. 

How to configure Hibernate CFG so that it pulls a generic DS. 
Nice to have records displayed bases on login ID. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:15:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 12:15:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-759) Client
 username/password
 authentication mechanism to provide JAAS UserPrincipal
In-Reply-To: <22936251.1182273876546.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13061203.1191255341140.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-759?page=comments#action_12379636 ] 
            
David Lloyd commented on JBREM-759:
-----------------------------------

Remoting 3 will definitely support this functionality.

> Client username/password authentication mechanism to provide JAAS UserPrincipal
> -------------------------------------------------------------------------------
>
>                 Key: JBREM-759
>                 URL: http://jira.jboss.com/jira/browse/JBREM-759
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: security
>            Reporter: Clark Updike
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Per the forum thread, Remoting needs a username/password-style authentication mechanism similar to JNDI for situations that require secure authentication but cannot support the infrastructure required for client certificates.  The mechanism should populate a JAAS UserPrinciple that can be used to access the authenticated client identity on the remote side.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:23:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 12:23:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-608) Add a new
 compatibity and stress test layer based on JMS CTS
In-Reply-To: <13967074.1160688881540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21000680.1191255821241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-608?page=all ]

Tim Fox closed JBMESSAGING-608.
-------------------------------

    Resolution: Rejected

We already have JORAM and CTS

> Add a new compatibity and stress test layer based on JMS CTS
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-608
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-608
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> http://jmscts.sourceforge.net/index.html
> The stress part is especially interesting.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:27:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:27:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ
 to Messaging migration guide
Message-ID: <23567470.1191256061244.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ]

Clebert Suconic closed JBMESSAGING-388.
---------------------------------------

    Resolution: Done

> Write a JBossMQ to Messaging migration guide
> --------------------------------------------
>
>                 Key: JBMESSAGING-388
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Documentation and Training
>            Reporter: Ovidiu Feodorov
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:27:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:27:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-388) Write a
 JBossMQ to Messaging migration guide
Message-ID: <31829155.1191256061463.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ]

Clebert Suconic reopened JBMESSAGING-388:
-----------------------------------------

      Assignee: Clebert Suconic
             

> Write a JBossMQ to Messaging migration guide
> --------------------------------------------
>
>                 Key: JBMESSAGING-388
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Documentation and Training
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:29:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:29:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ
 to Messaging migration guide
Message-ID: <28377154.1191256181124.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ]

Clebert Suconic closed JBMESSAGING-388.
---------------------------------------

    Resolution: Done

JBM already cover migration (just look at installation docs)

> Write a JBossMQ to Messaging migration guide
> --------------------------------------------
>
>                 Key: JBMESSAGING-388
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Documentation and Training
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:50:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-641) Make sure smoke
 tests pass on an un-scoped JBoss5/Messaging instance
In-Reply-To: <743036.1163646941500.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6571655.1191257441380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-641?page=all ]

Clebert Suconic closed JBMESSAGING-641.
---------------------------------------

    Resolution: Done
      Assignee: Clebert Suconic

> Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-641
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-641
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> Will take care of this on the second pass of integration with JBoss 5, which will be after 1.2.0 anyway.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:50:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-639) AS Integration
In-Reply-To: <12502423.1163644661476.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22080242.1191257441573.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-639?page=all ]

Clebert Suconic closed JBMESSAGING-639.
---------------------------------------

    Resolution: Done

> AS Integration
> --------------
>
>                 Key: JBMESSAGING-639
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-639
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> Container task for anything related to integration.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 13:52:56 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 13:52:56 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1052) doc for SFSB
	removal timeout
In-Reply-To: <33479921.1190342891021.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9854260.1191261176113.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1052?page=all ]

William DeCoste closed EJBTHREE-1052.
-------------------------------------

    Fix Version/s: Branch_4_2
       Resolution: Done

> doc for SFSB removal timeout
> ----------------------------
>
>                 Key: EJBTHREE-1052
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1052
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Mon Oct  1 13:52:56 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 13:52:56 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1035) get latest
	tutorials online
In-Reply-To: <18674529.1187814989070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10352596.1191261176283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1035?page=all ]

William DeCoste closed EJBTHREE-1035.
-------------------------------------

    Resolution: Done

> get latest tutorials online
> ---------------------------
>
>                 Key: EJBTHREE-1035
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1035
>             Project: EJB 3.0
>          Issue Type: Task
>            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

        


From jira-events at lists.jboss.org  Mon Oct  1 15:39:41 2007
From: jira-events at lists.jboss.org (Matt Cristantello (JIRA))
Date: Mon, 1 Oct 2007 15:39:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4747) WebAuthentication
 programmatic login prevents the user from ever logging out
In-Reply-To: <2656556.1190410691242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5335662.1191267581274.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4747?page=all ]

Matt Cristantello closed JBAS-4747.
-----------------------------------

    Resolution: Cannot Reproduce Bug

I can't duplicate this anymore, it must have been an issue with some weird cookies being set in my browser.

Sorry,
~Matt

> WebAuthentication programmatic login prevents the user from ever logging out
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4747
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4747
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: CentOS 3, JDK 1.5.0_12, JBoss Portal 2.6.1.GA with JBoss AS 4.2.1.GA, set up in ClusteredSingleSignOn mode
>            Reporter: Matt Cristantello
>         Assigned To: Scott M Stark
>
> When using the WebAuthentication login(String,String) method, it is not possible to log out even if the logoff() method of the WebAuthentication is called.
> Code:
> auto_login.jsp
> <%@page import="org.jboss.web.tomcat.security.login.WebAuthentication"%>
> <%
> 	WebAuthentication pwl = new WebAuthentication();
> 	pwl.login("user", "user");
> 	
> 	response.sendRedirect("test.jsp");
> %>
> logout.jsp
> <%@page import="org.jboss.web.tomcat.security.login.WebAuthentication"%>
> <%
> 	WebAuthentication pwl = new WebAuthentication();
> 	pwl.logout();
> %>
> <p>Successfully logged out</p>
> test.jsp
> <html>
> <head>
> 	<title>Test Page</title>
> </head>
> <body>
> <p>Username: <%=request.getRemoteUser() %></p>
> <p><a href="logout.jsp">Log Out</a></p>
> </body>
> </html>
> web.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app id="WebApp_ID" version="2.4"
> 	xmlns="http://java.sun.com/xml/ns/j2ee"
> 	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> 	xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
> 	<display-name>test</display-name>
> 	<welcome-file-list>
> 		<welcome-file>index.html</welcome-file>
> 		<welcome-file>index.htm</welcome-file>
> 		<welcome-file>index.jsp</welcome-file>
> 		<welcome-file>default.html</welcome-file>
> 		<welcome-file>default.htm</welcome-file>
> 		<welcome-file>default.jsp</welcome-file>
> 	</welcome-file-list>
> 	<security-constraint>
> 		<web-resource-collection>
> 			<web-resource-name>test</web-resource-name>
> 			<url-pattern>/test.jsp</url-pattern>
> 			<http-method>POST</http-method>
> 			<http-method>GET</http-method>
> 		</web-resource-collection>
> 		<auth-constraint>
> 			<description>Authentication required</description>
> 			<role-name>Authenticated</role-name>
> 		</auth-constraint>
> 	</security-constraint>
> 	<login-config>
> 		<auth-method>FORM</auth-method>
> 		<realm-name>JBoss Portal</realm-name>
> 		<form-login-config>
> 			<form-login-page>/login.jsp</form-login-page>
> 			<form-error-page>/error.jsp</form-error-page>
> 		</form-login-config>
> 	</login-config>
> 	<security-role>
> 		<role-name>Authenticated</role-name>
> 	</security-role>
> </web-app>
> jboss-web.xml
> <?xml version="1.0"?>
> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
> <jboss-web>
> 	<security-domain>java:jaas/portal</security-domain>
> </jboss-web>
> Steps:
> 1. Log in by navigating to auto_login.jsp
> 2. Click the log out link, or otherwise navigate to the logout.jsp page.
> 3. Navigate back to the test.jsp page.
> You will still be logged in.
> This problem also occurs with the JBoss Portal 2.6.1, where I am automatically logged into the JBoss portal after running auto_login.jsp, but I cannot log out of the Portal using its logout button or the logout.jsp provided as an example above.
> I am not seeing any entries in my server.log files when the logout methods are called, even with debug messages being logged.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:01:41 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 16:01:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-471) Method
 enforceArgsConsistency()
 not found on field interception with @Arg-annotated param
Message-ID: <12708972.1191268901563.JavaMail.jira@cloud.prod.atl2.jboss.com>

Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
-----------------------------------------------------------------------------------------

                 Key: JBAOP-471
                 URL: http://jira.jboss.com/jira/browse/JBAOP-471
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
            Reporter: Flavia Rainone
         Assigned To: Flavia Rainone
             Fix For: 2.0.0.beta2


The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
The result:
Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
rgsPOJO.field5]
        at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
        at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
        at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
        at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
        at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
        at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
Caused by: java.lang.RuntimeException: Error creating invokeNext method: {   try{      switch(++super.currentInterceptor){      case 1:enforceArgsConsistency
();    around6.around1(this.arg0);
      break;      case 2:enforceArgsConsistency();    around7.around2(this.arg0);
      break;      case 3:enforceArgsConsistency();    around8.around3(this.arg0);
      break;      case 4:enforceArgsConsistency();    around9.around4(this.arg0);
      break;      case 5:enforceArgsConsistency();    around10.around6(this.arg0);
      break;      default:         this.dispatch();      }   }finally{      --super.currentInterceptor;   }   return null;}
        at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
        at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
        ... 26 more
Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
_16
        at javassist.CtBehavior.setBody(CtBehavior.java:367)
        at javassist.CtBehavior.setBody(CtBehavior.java:334)
        at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
        ... 28 more
Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
        at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
        at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
        at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
        at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
        at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
        at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
        at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
        at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:11:41 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 16:11:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-472) Wrappers lack the
 generic type information
Message-ID: <5055386.1191269501072.JavaMail.jira@cloud.prod.atl2.jboss.com>

Wrappers lack the generic type information
------------------------------------------

                 Key: JBAOP-472
                 URL: http://jira.jboss.com/jira/browse/JBAOP-472
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
            Reporter: Flavia Rainone
             Fix For: 2.0.0.beta2


This issue has already been fixed by Kabir with method wrappers.

This task consists of fixing the issue for all other joinpoint types.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:24:43 2007
From: jira-events at lists.jboss.org (RefuX Zanzeebarr (JIRA))
Date: Mon, 1 Oct 2007 16:24:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JASSIST-36) static flag
 inconsistently applied to clinit
Message-ID: <24683018.1191270283396.JavaMail.jira@cloud.prod.atl2.jboss.com>

static flag inconsistently applied to clinit
--------------------------------------------

                 Key: JASSIST-36
                 URL: http://jira.jboss.com/jira/browse/JASSIST-36
             Project: Javassist
          Issue Type: Bug
            Reporter: RefuX Zanzeebarr
         Assigned To: Shigeru Chiba


In CtClassType we have:
            m = new MethodInfo(cf.getConstPool(), "<clinit>", "()V");
            m.setAccessFlags(AccessFlag.STATIC);

In ProxyFactory
         MethodInfo minfo = new MethodInfo(cp, "<clinit>", "()V");

but no static flag.

We actually ran into this issue because the JVM on the iSeries was very unhappy about the lack of the static flag in clinit. IBM are now updating their JVM to work correctly with the missing static flag.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:44:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 16:44:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1088) Refactor code
 to use Java 5 generics
Message-ID: <25143580.1191271481231.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor code to use Java 5 generics
------------------------------------

                 Key: JBMESSAGING-1088
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1088
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 2.0.0 Beta 1


In many places the code uses non parameterized collections since we moved recently from Java 1.4 to Java 5.

We should update the code accordingly.

Also use Java 5 enums where appropriate.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 17:10:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 1 Oct 2007 17:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-910) upgrade GWT to 1.4
In-Reply-To: <11898024.1181114658622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31242499.1191273041457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-910?page=all ]

Fernando Meyer closed JBRULES-910.
----------------------------------

    Fix Version/s: 4.0.2
                       (was: FUTURE)
       Resolution: Done

Michale got some issues testing on firefox 3 beta, but I got everything wokring fine with FF2, safari and IE 6

> upgrade GWT to 1.4
> ------------------
>
>                 Key: JBRULES-910
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-910
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Michael Neale
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> Would also be nice to use the new RichText widget on the documentation (for the doucmentation widget on the rule editors).
> Also, using the Vertical and horizontal splitters would be awesome for the rule editor (so people can drag stuff around).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 17:14:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 1 Oct 2007 17:14:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1238) Upgrade BRMS to
 use jboss seam version 2.0
Message-ID: <25446154.1191273281034.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade BRMS to use jboss seam version 2.0 
-------------------------------------------

                 Key: JBRULES-1238
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1238
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer
             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Mon Oct  1 17:27:46 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 17:27:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16022452.1191274066025.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

William DeCoste reassigned EJBTHREE-883:
----------------------------------------

    Assignee: William DeCoste

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:17:55 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 18:17:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1239) Fix class loaders
 so that
 creating multiple rulebase with separate class loader hirarchy works
Message-ID: <16578372.1191277075861.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works
----------------------------------------------------------------------------------------------

                 Key: JBRULES-1239
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1239
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, Reteoo
    Affects Versions: 4.0.1
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.0.2


Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:23:41 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 18:23:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1239) Fix class
 loaders so that
 creating multiple rulebase with separate class loader hirarchy works
In-Reply-To: <16578372.1191277075861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16513714.1191277421166.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1239?page=all ]

Edson Tirelli resolved JBRULES-1239.
------------------------------------

    Resolution: Done

commited.

Tag before the commit is here: https://svn.labs.jboss.com/labs/jbossrules/tags/4.0.2_SNAPSHOT_before_classloader_changes/

> Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1239
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1239
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder, Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>
> Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:29:41 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 18:29:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23075090.1191277781249.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

William DeCoste closed EJBTHREE-883.
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 5.0.0.Beta3)
       Resolution: Done

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:31:41 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 18:31:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1212) Rete throws
 NoClassDefFoundError when asserting facts with classess loaded by
 inaccessible classloader.
In-Reply-To: <21352351.1190454754072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11806315.1191277901200.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1212?page=comments#action_12379736 ] 
            
Edson Tirelli commented on JBRULES-1212:
----------------------------------------

Alexander,

I just fixed http://jira.jboss.com/jira/browse/JBRULES-1239 and I think your use case is covered now. I developed 2 tests, as you can see bellow: one using thread context API and the other using drools configuration classes:

    public void testClassLoaderSwitchsUsingConf() throws Exception {
        try {
            // Creates first class loader and use it to load fact classes
            ClassLoader loader1 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                      this.getClass().getClassLoader() );
            Class cheeseClass = loader1.loadClass( "org.drools.Cheese" );

            PackageBuilderConfiguration conf = new PackageBuilderConfiguration( loader1 );
            PackageBuilder builder = new PackageBuilder( conf );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            // must set the classloader for rulebase conf too
            RuleBaseConfiguration rbconf = new RuleBaseConfiguration( loader1 );
            RuleBase ruleBase = RuleBaseFactory.newRuleBase( rbconf );
            Package pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            StatefulSession wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();

            // Creates second class loader and use it to load fact classes
            ClassLoader loader2 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                            this.getClass().getClassLoader() );
            cheeseClass = loader2.loadClass( "org.drools.Cheese" );

            conf = new PackageBuilderConfiguration( loader2 );
            builder = new PackageBuilder( conf );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            rbconf = new RuleBaseConfiguration( loader2 );
            ruleBase = RuleBaseFactory.newRuleBase( rbconf );
            pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();
        } catch ( ClassCastException cce ) {
            cce.printStackTrace();
            fail( "No ClassCastException should be raised." );
        }

    }

    public void testClassLoaderSwitchsUsingContext() throws Exception {
        try {
            // Creates first class loader and use it to load fact classes
            ClassLoader original = Thread.currentThread().getContextClassLoader();
            ClassLoader loader1 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                      this.getClass().getClassLoader() );
            Thread.currentThread().setContextClassLoader( loader1 );
            Class cheeseClass = loader1.loadClass( "org.drools.Cheese" );

            PackageBuilder builder = new PackageBuilder( );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            RuleBase ruleBase = RuleBaseFactory.newRuleBase();
            Package pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            StatefulSession wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();

            // Creates second class loader and use it to load fact classes
            ClassLoader loader2 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                            this.getClass().getClassLoader() );
            Thread.currentThread().setContextClassLoader( loader2 );
            cheeseClass = loader2.loadClass( "org.drools.Cheese" );

            builder = new PackageBuilder( );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            ruleBase = RuleBaseFactory.newRuleBase();
            pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();

            Thread.currentThread().setContextClassLoader( original );
        } catch ( ClassCastException cce ) {
            cce.printStackTrace();
            fail( "No ClassCastException should be raised." );
        }
    }

    public class SubvertedClassLoader extends URLClassLoader {

        private static final long serialVersionUID = 400L;

        public SubvertedClassLoader(final URL[] urls,
                                    final ClassLoader parentClassLoader) {
            super( urls,
                   parentClassLoader );
        }

        protected synchronized Class loadClass(String name,
                                               boolean resolve) throws ClassNotFoundException {
            // First, check if the class has already been loaded
            Class c = findLoadedClass( name );
            if ( c == null ) {
                try {
                    c = findClass( name );
                } catch( ClassNotFoundException e ) {
                    c = super.loadClass( name, resolve );
                }
            }
            return c;
        }
    }

    Can you please try out and let us know if it covers your scenarios?

    Thanks,
      Edson

> Rete throws NoClassDefFoundError when asserting facts with classess loaded by inaccessible classloader. 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1212
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1212
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Alexander Gavrilov
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>         Attachments: ReteShadowProxyTest.java
>
>
> We using drools as part of security enfocement engine in our application, based on Tapestry4 framework. Tapestry4 pages and components is abstract classes with some abstract methods, for which tapestry generates implementation at runtime. For example, if i declare page 
> public abstract SomePage extends BasePage  {
> }
> Tapestry will generate class in default package like 
> public SomePage$_0 extends BasePage  {
> }
> On page loading whe using instantiated page objects ans Drools Facts to ensure, that current user has permissions to load this page. In the previos verions we used (3.0.6) all worked fine. After update to version 4.0.1 whe got the NoClassDefFoundError  when triyng to assert Page object into working memory. 
> This is becouse tapestry creates classes for pages in private classloader, which is child of the application classloader. When Drools tries to generate shadowing proxy for generated Page class it generate code like 
> public class SomePage$_0ShadowProxy extends SomePage$_0 {
> }
> Later, when it tries to load this class with MapBackedClassLoader, it can not find definition for class SomePage$_0 and throws NoClassDefFoundError. This type of error does not handled correctly by drools. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:45:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 18:45:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12591030.1191278741235.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Clebert Suconic updated JBREM-811:
----------------------------------

    Attachment: diff.patch

Attaching a patch

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>             Fix For: 2.2.2.SP1
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:49:41 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 1 Oct 2007 18:49:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3502) Use
 ProcessExpiresFrequency to speed tests involving session timeout
In-Reply-To: <300803.1155154392870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10212194.1191278981271.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3502?page=all ]

Brian Stansberry reassigned JBAS-3502:
--------------------------------------

    Assignee: Brian Stansberry

> Use ProcessExpiresFrequency to speed tests involving session timeout
> --------------------------------------------------------------------
>
>                 Key: JBAS-3502
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3502
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering, Test Suite
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: JBossAS-5.0.0.GA
>
>
> Tomcat Manager impls expose a property ProcessExpiresFrequency, which controls how often the manager responds to the TC background process thread.  By default it is set to 6, which means the manager does a session cleanup every 6 cycles.  By default the thread runs every 10 secs, so that means session are expired once per minute.
> Need to add ProcessExpiresFrequency=1 to a context.xml deployed with session test webapps so we can reduce the time it takes for tests involving session expiration to 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

        


From jira-events at lists.jboss.org  Mon Oct  1 19:02:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 19:02:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13085784.1191279761173.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Clebert Suconic updated JBREM-811:
----------------------------------

    Priority: Blocker  (was: Major)

I'm changing this back to blocker, but the fix is pretty simple.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.2.2.SP1
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 19:29:41 2007
From: jira-events at lists.jboss.org (Remy Maucherat (JIRA))
Date: Mon, 1 Oct 2007 19:29:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBWEB-95) Provide a
 com.sun.net.httpserver.HttpServerProvider implementation
In-Reply-To: <4296152.1190984561683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5079376.1191281381209.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBWEB-95?page=all ]

Remy Maucherat reassigned JBWEB-95:
-----------------------------------

    Assignee: Remy Maucherat  (was: Mladen Turk)

> Provide a com.sun.net.httpserver.HttpServerProvider implementation
> ------------------------------------------------------------------
>
>                 Key: JBWEB-95
>                 URL: http://jira.jboss.com/jira/browse/JBWEB-95
>             Project: JBoss Web
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Tomcat Module
>            Reporter: Scott M Stark
>         Assigned To: Remy Maucherat
>
> To plug jbossweb into jdk6, we need a com.sun.net.httpserver.HttpServerProvider implementation
> http://java.sun.com/javase/6/docs/jre/api/net/httpserver/spec/com/sun/net/httpserver/spi/HttpServerProvider.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 19:37:52 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 19:37:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1224) regular
 expressions inside mvel expressions require escaping
In-Reply-To: <8850663.1190828212431.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6981057.1191281872547.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1224?page=all ]

Edson Tirelli closed JBRULES-1224.
----------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done
         Assignee: Edson Tirelli  (was: Mark Proctor)

Fixed.

Thanks for reporting.

> regular expressions inside mvel expressions require escaping
> ------------------------------------------------------------
>
>                 Key: JBRULES-1224
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1224
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Godmar Back
>         Assigned To: Edson Tirelli
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> The documentation states that regular expressions do not require Java-style backslash escaping. However, this only holds for some expressions, not for all.
> For details, read: http://lists.jboss.org/pipermail/rules-users/2007-September/003309.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:19:42 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 20:19:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21822307.1191284382451.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=all ]

Mark Proctor updated JBRULES-1221:
----------------------------------

    Assignee: Michael Neale  (was: Mark Proctor)

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:22:32 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 20:22:32 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1219) Using DSL and
 accumulate in Drools BRMS leads to unexpected results
In-Reply-To: <5139335.1190709101221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31091817.1191284552256.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1219?page=all ]

Mark Proctor updated JBRULES-1219:
----------------------------------

    Assignee: Michael Neale  (was: Mark Proctor)

> Using DSL and accumulate in Drools BRMS leads to unexpected results
> -------------------------------------------------------------------
>
>                 Key: JBRULES-1219
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1219
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05" 
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/Using-DSL-and-accumulate-in-Drools-BRMS-leads-to-unexpected-results-tf4421763.html#a12612164

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:45:42 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 20:45:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1206) ParserException on
 misplaced parenthesis
In-Reply-To: <997956.1190212517082.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23396042.1191285942137.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1206?page=all ]

Edson Tirelli closed JBRULES-1206.
----------------------------------

    Resolution: Done

Done.

Thanks for reporting and providing test case.

> ParserException on misplaced parenthesis
> ----------------------------------------
>
>                 Key: JBRULES-1206
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1206
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>         Environment: Windows XP SP2
>            Reporter: Matija Kejzar
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>         Attachments: wp-rules-exception.txt
>
>
> The following exception is thrown on parsing of the attached rules (see attached file). Take note of the incorrect parenthesis in the eval statement on the WorkerPerformanceContext condition lines. Also, please note these rules were generated by the spreadsheet compiler from an .xls decision table.
> Here is the exception:
> Caused by: org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)
> ... application code

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:53:41 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 1 Oct 2007 20:53:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15363662.1191286421176.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=comments#action_12379754 ] 
            
Michael Neale commented on JBRULES-1221:
----------------------------------------

I haven't been able to get this to happen in 4.0.2 trunk - could you try this again on that? 

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:55:41 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 20:55:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1219) Using DSL and
 accumulate in Drools BRMS leads to unexpected results
In-Reply-To: <5139335.1190709101221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10854162.1191286541187.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1219?page=all ]

Edson Tirelli updated JBRULES-1219:
-----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)
         Assignee: Edson Tirelli  (was: Michael Neale)

The "-" feature can not be used with accumulate right now and the fix for that will not make the 4.0.2 cut. So, moving it to FUTURE.

> Using DSL and accumulate in Drools BRMS leads to unexpected results
> -------------------------------------------------------------------
>
>                 Key: JBRULES-1219
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1219
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05" 
>            Reporter: Cristiano Giuffrida
>         Assigned To: Edson Tirelli
>             Fix For: FUTURE
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/Using-DSL-and-accumulate-in-Drools-BRMS-leads-to-unexpected-results-tf4421763.html#a12612164

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 21:01:41 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 1 Oct 2007 21:01:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21239960.1191286901101.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=comments#action_12379756 ] 
            
Michael Neale commented on JBRULES-1221:
----------------------------------------

Have tried in a few different ways, this is probably related to quite a few other fixes since 4.0.1 time (it has been a while). 

Give it a try with the latest snapshot. If it still happens, let me know with some more detail (app server etc).

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 21:18:41 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 1 Oct 2007 21:18:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7188519.1191287921284.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=all ]

Michael Neale closed JBRULES-1221.
----------------------------------

    Resolution: Done

Fixed in 4.0.2 due to incorrect ContentPackageAssembler handling of configuration

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 21:32:41 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 21:32:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1240) Remove Dialect
 state from PackageBuilderConfiguration
Message-ID: <22006922.1191288761051.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove Dialect state from PackageBuilderConfiguration
-----------------------------------------------------

                 Key: JBRULES-1240
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1240
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.1
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2


We are getting issues, particularly in threading scenarios, where PackageBuilderConfiguration holding onto the JavaDialect instance is causing problems. We need to make PackageBuilderConfiguration stateless, or atleast immutable.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:01:41 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 23:01:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1241) Dynamic rules
 should be able
 to lock for a series of updates and fireAllRules should be optional
Message-ID: <31771190.1191294101057.JavaMail.jira@cloud.prod.atl2.jboss.com>

Dynamic rules should be able to lock for a series of updates and fireAllRules should be optional
------------------------------------------------------------------------------------------------

                 Key: JBRULES-1241
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1241
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2


add lock() and unlock() to RuleBase and setup a rulebase listener to progated the fireAllRules calls.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:50:42 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:50:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JASSIST-36) static flag
 inconsistently applied to clinit
In-Reply-To: <24683018.1191270283396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25125826.1191297042500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-36?page=all ]

Shigeru Chiba resolved JASSIST-36.
----------------------------------

    Resolution: Done

Thank you.  I have fixed it.

> static flag inconsistently applied to clinit
> --------------------------------------------
>
>                 Key: JASSIST-36
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-36
>             Project: Javassist
>          Issue Type: Bug
>            Reporter: RefuX Zanzeebarr
>         Assigned To: Shigeru Chiba
>
> In CtClassType we have:
>             m = new MethodInfo(cf.getConstPool(), "<clinit>", "()V");
>             m.setAccessFlags(AccessFlag.STATIC);
> In ProxyFactory
>          MethodInfo minfo = new MethodInfo(cp, "<clinit>", "()V");
> but no static flag.
> We actually ran into this issue because the JVM on the iSeries was very unhappy about the lack of the static flag in clinit. IBM are now updating their JVM to work correctly with the missing static flag.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:50:42 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:50:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JASSIST-36) static flag
 inconsistently applied to clinit
In-Reply-To: <24683018.1191270283396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1287731.1191297042648.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-36?page=all ]

Shigeru Chiba closed JASSIST-36.
--------------------------------


> static flag inconsistently applied to clinit
> --------------------------------------------
>
>                 Key: JASSIST-36
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-36
>             Project: Javassist
>          Issue Type: Bug
>            Reporter: RefuX Zanzeebarr
>         Assigned To: Shigeru Chiba
>
> In CtClassType we have:
>             m = new MethodInfo(cf.getConstPool(), "<clinit>", "()V");
>             m.setAccessFlags(AccessFlag.STATIC);
> In ProxyFactory
>          MethodInfo minfo = new MethodInfo(cp, "<clinit>", "()V");
> but no static flag.
> We actually ran into this issue because the JVM on the iSeries was very unhappy about the lack of the static flag in clinit. IBM are now updating their JVM to work correctly with the missing static flag.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:54:41 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JASSIST-29) StackMapTable
	support
In-Reply-To: <30858754.1162154141561.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11931202.1191297281113.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-29?page=all ]

Shigeru Chiba resolved JASSIST-29.
----------------------------------

    Resolution: Done

by version 3.6.0

> StackMapTable support
> ---------------------
>
>                 Key: JASSIST-29
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-29
>             Project: Javassist
>          Issue Type: Feature Request
>            Reporter: Shigeru Chiba
>         Assigned To: Shigeru Chiba
>            Priority: Blocker
>
> All class files must support StackMapTable in Java SE 6.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:54:41 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JASSIST-29) StackMapTable support
In-Reply-To: <30858754.1162154141561.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27749175.1191297281222.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-29?page=all ]

Shigeru Chiba closed JASSIST-29.
--------------------------------


> StackMapTable support
> ---------------------
>
>                 Key: JASSIST-29
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-29
>             Project: Javassist
>          Issue Type: Feature Request
>            Reporter: Shigeru Chiba
>         Assigned To: Shigeru Chiba
>            Priority: Blocker
>
> All class files must support StackMapTable in Java SE 6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:09:59 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Tue, 2 Oct 2007 01:09:59 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1231) Functions do not
 get added to new BRMS package when package imported from drl file
In-Reply-To: <29309043.1190993621096.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13076643.1191301799603.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1231?page=all ]

Michael Neale closed JBRULES-1231.
----------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done
         Assignee: Michael Neale  (was: Mark Proctor)

not really a bug, but done anyway.

> Functions do not get added to new BRMS package when package imported from drl file
> ----------------------------------------------------------------------------------
>
>                 Key: JBRULES-1231
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1231
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: BRMS running on Windows XP SP2, with JBoss 4.2GA
>            Reporter: Shahad Ahmed
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> When you create a new package in the BRMS by importing an existing DRL file then any functions in the DRL file do not get added to the list of functions for the newly created package. Instead, the functions appear along with the import statements in the "header" text box found when you click on "Edit Package configuration" for the new package!
> To recreate:
> Put the example rules below into a .drl file and import it into the BRMS by creating a new package and choosng the option to load it from a .drl file.
> Click on the newly created package com.acme.example in the package browser. Click on the Functions tab for the package. No functions are present. 
> Click on com.acme.example in the package browser and then select "Edit Package configuration". In the Header text box you should see the two functions defined in the example DRL file given below.
> package com.acme.example
> import java.util.Set;
> function int firstFunction ()
> {
>     return 1;
> }
> function int secondFunction ()
> {
>     return 2;
> }
> rule "Rule 1"
> 	when
> 		eval(firstFunction() == 1)
> 	then 
> 	    System.out.println("Function 1");
> end
> rule "Rule 2"
> 	when
> 		eval(secondFunction() == 2)
> 	then 
> 	    System.out.println("Function 2");
> End

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1227) Add
 drools-analytics support to drools-ant
In-Reply-To: <5171179.1190831322186.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29068757.1191302741457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1227?page=all ]

Fernando Meyer closed JBRULES-1227.
-----------------------------------

    Fix Version/s: 4.0.2
                       (was: FUTURE)
       Resolution: Done

> Add drools-analytics support to drools-ant 
> -------------------------------------------
>
>                 Key: JBRULES-1227
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1227
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1238) Upgrade BRMS to
 use jboss seam version 2.0
In-Reply-To: <25446154.1191273281034.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23754585.1191302741785.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1238?page=all ]

Fernando Meyer closed JBRULES-1238.
-----------------------------------

    Resolution: Done

> Upgrade BRMS to use jboss seam version 2.0 
> -------------------------------------------
>
>                 Key: JBRULES-1238
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1238
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-996) Admin screen option
 to remove archive items
In-Reply-To: <18780102.1184139752013.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32315490.1191302741986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-996?page=all ]

Fernando Meyer closed JBRULES-996.
----------------------------------

    Fix Version/s: 4.0.2
                       (was: FUTURE)
       Resolution: Done

> Admin screen option to remove archive items
> -------------------------------------------
>
>                 Key: JBRULES-996
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-996
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions:  4.0.0.MR3
>            Reporter: Michael Neale
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> This is for V2 (not NOW !). 
> Should have a feature (for admins) to permanently delete all items marked as archived (packages and assets).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:43 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-995) Show archived
 items with option to restore (packages rules)
In-Reply-To: <10034616.1184139631678.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33372883.1191302743101.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-995?page=comments#action_12379790 ] 
            
Fernando Meyer commented on JBRULES-995:
----------------------------------------

It's already done for Assets, just missing this feature for packages

> Show archived items with option to restore (packages rules)
> -----------------------------------------------------------
>
>                 Key: JBRULES-995
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-995
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions:  4.0.0.MR3
>            Reporter: Michael Neale
>         Assigned To: Fernando Meyer
>             Fix For: FUTURE
>
>
> This is for V2 only !
> Should be able to show archived packages, and restore them. With rules, we can search for archived ones, should also be able to restore them (ie if they are archived, have a button to "unarchive" them).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 04:29:15 2007
From: jira-events at lists.jboss.org (Ross McDonald (JIRA))
Date: Tue, 2 Oct 2007 04:29:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1064) mail nodes cannot
 resolve variables with hyphenated names
Message-ID: <18886359.1191313755641.JavaMail.jira@cloud.prod.atl2.jboss.com>

mail nodes cannot resolve variables with hyphenated names
---------------------------------------------------------

                 Key: JBPM-1064
                 URL: http://jira.jboss.com/jira/browse/JBPM-1064
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions:  jBPM jPDL 3.2.1
         Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
            Reporter: Ross McDonald
         Assigned To: Tom Baeyens


In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed.  Changing this variable to be 'myVariable' instead resolves it correctly.  

I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.  

Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 04:48:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <11520876.1191314883372.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379805 ] 
            
Thomas Diesler commented on JBREM-305:
--------------------------------------

It should be possible for WS client to send a SOAP JMS message to a queue/topic in the same way a JMS client would.

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: Tom  Elrod
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 04:50:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 04:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-305) Provide support for
 JMS transport
Message-ID: <20514884.1191315003405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-305?page=all ]

Thomas Diesler reassigned JBREM-305:
------------------------------------

    Assignee: David Lloyd  (was: Tom  Elrod)

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 06:16:03 2007
From: jira-events at lists.jboss.org (Darran Lofthouse (JIRA))
Date: Tue, 2 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4771) Backport
 RoleMappingLoginModule to JBoss 4.0.3.SP1
Message-ID: <6777814.1191320163407.JavaMail.jira@cloud.prod.atl2.jboss.com>

Backport RoleMappingLoginModule to JBoss 4.0.3.SP1
--------------------------------------------------

                 Key: JBAS-4771
                 URL: http://jira.jboss.com/jira/browse/JBAS-4771
             Project: JBoss Application Server
          Issue Type: Support Patch
      Security Level: Public (Everyone can see)
          Components: Security
    Affects Versions: JBossAS-4.0.3 SP1
            Reporter: Darran Lofthouse
         Assigned To: Darran Lofthouse


http://wiki.jboss.org/wiki/Wiki.jsp?page=RoleMappingLoginModule

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 07:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14486524.1191323343305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=all ]

Tim Fox updated JBMESSAGING-1084:
---------------------------------

    Fix Version/s: AS 5.0 Integration

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:11:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
Message-ID: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade to JGroups 2.5
----------------------

                 Key: JBMESSAGING-1089
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration


Update to JGroups 2.5 to take advantage of better throughput.

We need to ensure the post office code is sufficiently thread safe.

We may need to do another release for 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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:11:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1017) Upgrade to
	JGroups 2.5
In-Reply-To: <11640655.1185028990023.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12381236.1191323463410.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1017?page=all ]

Tim Fox closed JBMESSAGING-1017.
--------------------------------

    Resolution: Duplicate Issue

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1017
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1017
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:26:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 2 Oct 2007 07:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPM-1064) mail nodes cannot
 resolve variables with hyphenated names
In-Reply-To: <18886359.1191313755641.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26608331.1191324363717.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1064?page=all ]

Ronald van Kuijk resolved JBPM-1064.
------------------------------------

    Resolution: Rejected

In EL, it is not allowed to have hyphens in names, just like it is not allowed in java names. So it is processed as a mathematical  expression where the hyphen is treated as a minus. 

> mail nodes cannot resolve variables with hyphenated names
> ---------------------------------------------------------
>
>                 Key: JBPM-1064
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1064
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions:  jBPM jPDL 3.2.1
>         Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>
> In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed.  Changing this variable to be 'myVariable' instead resolves it correctly.  
> I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.  
> Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:26:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 2 Oct 2007 07:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBPM-1064) mail nodes cannot
 resolve variables with hyphenated names
In-Reply-To: <18886359.1191313755641.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20956281.1191324363878.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1064?page=all ]

Ronald van Kuijk closed JBPM-1064.
----------------------------------


> mail nodes cannot resolve variables with hyphenated names
> ---------------------------------------------------------
>
>                 Key: JBPM-1064
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1064
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions:  jBPM jPDL 3.2.1
>         Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>
> In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed.  Changing this variable to be 'myVariable' instead resolves it correctly.  
> I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.  
> Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:28:03 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Tue, 2 Oct 2007 07:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1242) Archived package
 assets cannot be restored
Message-ID: <10651989.1191324483301.JavaMail.jira@cloud.prod.atl2.jboss.com>

Archived package assets cannot be restored
------------------------------------------

                 Key: JBRULES-1242
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1242
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets?

The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of  archived assets.



-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 2 Oct 2007 07:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
Message-ID: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>

org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
-----------------------------------------------------------------------------------------------

                 Key: JBAS-4772
                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Test Suite
            Reporter: Dimitris Andreadis
         Assigned To: Thomas Diesler
            Priority: Critical
             Fix For: JBossAS-4.2.2.GA


See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:06:03 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Tue, 2 Oct 2007 08:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
Message-ID: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add appropriate Exception handling when hitting MaxSize
-------------------------------------------------------

                 Key: JBMESSAGING-1090
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
            Reporter: Jay Howell
         Assigned To: Tim Fox


When using MaxSize for a queue and topic the following behaviors exist

Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.

Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.

What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.

I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  

We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  

Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:06:03 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Tue, 2 Oct 2007 08:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
In-Reply-To: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28548265.1191326763527.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1090?page=all ]

Jay Howell reassigned JBMESSAGING-1090:
---------------------------------------

    Assignee: Jay Howell  (was: Tim Fox)

> Add appropriate Exception handling when hitting MaxSize
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1090
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Jay Howell
>
> When using MaxSize for a queue and topic the following behaviors exist
> Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.
> Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.
> What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.
> I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  
> We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  
> Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:22:35 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:22:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
In-Reply-To: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31972561.1191327755653.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1089?page=comments#action_12379865 ] 
            
Tim Fox commented on JBMESSAGING-1089:
--------------------------------------

This is needed for JBAS 5.0

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1089
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Update to JGroups 2.5 to take advantage of better throughput.
> We need to ensure the post office code is sufficiently thread safe.
> We may need to do another release for 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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:22:35 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:22:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
In-Reply-To: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17372275.1191327755885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1089?page=all ]

Tim Fox updated JBMESSAGING-1089:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: AS 5.0 Integration)

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1089
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Update to JGroups 2.5 to take advantage of better throughput.
> We need to ensure the post office code is sufficiently thread safe.
> We may need to do another release for 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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:27:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1091) Selector
 parser should
 literal strings for DeliveryMode in selector expressions
Message-ID: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>

Selector parser should literal strings for DeliveryMode in selector expressions
-------------------------------------------------------------------------------

                 Key: JBMESSAGING-1091
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:27:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27000367.1191328023844.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=all ]

Tim Fox updated JBMESSAGING-1084:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: AS 5.0 Integration)

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:29:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9556864.1191328143241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox updated JBMESSAGING-1091:
---------------------------------

    Summary: Selector parser should use string literals for DeliveryMode in selector expressions  (was: Selector parser should literal strings for DeliveryMode in selector expressions)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:31:30 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:31:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7641129.1191328290776.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox updated JBMESSAGING-1091:
---------------------------------

    Description: In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.  (was: In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should "PERSISTENT" or "NON_PERSISTENT" string literals.)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 08:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
In-Reply-To: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12090202.1191328863387.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4772?page=comments#action_12379872 ] 
            
Thomas Diesler commented on JBAS-4772:
--------------------------------------

What do I need to do to setup the JACC config?
i.e. how can I reproduce this?

> org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4772
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:49:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 2 Oct 2007 08:49:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
In-Reply-To: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29144609.1191329345069.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4772?page=comments#action_12379874 ] 
            
Dimitris Andreadis commented on JBAS-4772:
------------------------------------------

Maybe cd testsuite; build tests-jacc-security  | tests-jacc-securitymgr

> org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4772
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:59:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Tue, 2 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
Message-ID: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>

NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
------------------------------------------------------------------------------

                 Key: JBCOMMON-35
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: common-old
    Affects Versions: 1.0.0.GA
            Reporter: Vicky Kak
         Assigned To: Vicky Kak
             Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA


http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:59:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Tue, 2 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4429287.1191329943898.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=all ]

Vicky Kak updated JBCOMMON-35:
------------------------------

    Component/s: common-core

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:07:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Tue, 2 Oct 2007 09:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
Message-ID: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>

ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
----------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBCOMMON-36
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: common-core, common-old
    Affects Versions: 1.0.0.GA
            Reporter: Vicky Kak
         Assigned To: Vicky Kak
             Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA


In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
>>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:11:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1937438.1191330663660.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf reopened EJBTHREE-883:
------------------------------------

             

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:11:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30448357.1191330663861.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf updated EJBTHREE-883:
-----------------------------------

    Fix Version/s: AS 4.2.2.GA
                       (was: Branch_4_2)

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:11:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:11:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15763385.1191330664056.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf resolved EJBTHREE-883.
------------------------------------

    Resolution: Done

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:13:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Tue, 2 Oct 2007 09:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAOP-471) Method
 enforceArgsConsistency()
 not found on field interception with @Arg-annotated param
In-Reply-To: <12708972.1191268901563.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27146941.1191330783227.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-471?page=all ]

Flavia Rainone resolved JBAOP-471.
----------------------------------

    Resolution: Done

> Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAOP-471
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-471
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
> The result:
> Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
> java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
> rgsPOJO.field5]
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
>         at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
>         at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
> Caused by: java.lang.RuntimeException: Error creating invokeNext method: {   try{      switch(++super.currentInterceptor){      case 1:enforceArgsConsistency
> ();    around6.around1(this.arg0);
>       break;      case 2:enforceArgsConsistency();    around7.around2(this.arg0);
>       break;      case 3:enforceArgsConsistency();    around8.around3(this.arg0);
>       break;      case 4:enforceArgsConsistency();    around9.around4(this.arg0);
>       break;      case 5:enforceArgsConsistency();    around10.around6(this.arg0);
>       break;      default:         this.dispatch();      }   }finally{      --super.currentInterceptor;   }   return null;}
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
>         ... 26 more
> Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
> _16
>         at javassist.CtBehavior.setBody(CtBehavior.java:367)
>         at javassist.CtBehavior.setBody(CtBehavior.java:334)
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
>         ... 28 more
> Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
>         at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
>         at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
>         at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
>         at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
>         at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
>         at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:17:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Tue, 2 Oct 2007 09:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-472) Wrappers lack the
 generic type information
In-Reply-To: <5055386.1191269501072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19090252.1191331023579.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-472?page=all ]

Flavia Rainone reassigned JBAOP-472:
------------------------------------

    Assignee: Flavia Rainone

> Wrappers lack the generic type information
> ------------------------------------------
>
>                 Key: JBAOP-472
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-472
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> This issue has already been fixed by Kabir with method wrappers.
> This task consists of fixing the issue for all other joinpoint types.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:29:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:29:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31987406.1191331755813.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-384?page=all ]

Bela Ban updated JGRP-384:
--------------------------

    Fix Version/s: 2.6
                       (was: 2.7)

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:29:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:29:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <580903.1191331755986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-384?page=all ]

Bela Ban updated JGRP-384:
--------------------------

    Attachment: bla2.java

bla2 is the corrected program, which wraps unlock() into a try-catch clause.

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:33:05 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:33:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28093779.1191331985785.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-384?page=comments#action_12379893 ] 
            
Bela Ban commented on JGRP-384:
-------------------------------

Okay, the program throws an exception on unlock(). If you simply wrap unlock() into a try-catch clause, then the next lock() will be successful and the subsequent unlock() as well (see attached bla2.java program).

The reason unlock() throws an exception is the following:
- {A,B}, A has the lock
- B is killed
- A tries to unlock by asking itself and B for agreement
- However there won't be any response from B, so unlock() fails
- As soon as the failure detector kicks in, B will get kicked out of the group, and a will succeed with lock() and unlock()

I suggest to add FD_SOCK to your stack, because that will detect crashes much faster, therefore the new view {A} will get established much sooner and unlock() won't fail.


> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:35:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15790059.1191332103669.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-384?page=comments#action_12379895 ] 
            
Bela Ban commented on JGRP-384:
-------------------------------

Note that - in order to determine a coordinator - you don't need a cluster wide lock; you could simply take the view, which is the *same on all nodes in a cluster*, and (for example) pick the first (= oldest member) in the list. This is faster and doesn't require communication.

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:35:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17986067.1191332103857.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-384?page=all ]

Bela Ban resolved JGRP-384.
---------------------------

    Resolution: Done

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:39:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Tue, 2 Oct 2007 09:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <23258979.1191332343592.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379897 ] 
            
David Lloyd commented on JBREM-305:
-----------------------------------

OK - but what does Remoting give you then?  After all, the JMS API can send a JMS message, and unlike, say, HTTP, JMS only has one client API (that I know of anyway).

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:59:14 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1243) Pattern matching
 does not allow spaces
Message-ID: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>

Pattern matching does not allow spaces
--------------------------------------

                 Key: JBRULES-1243
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
             Project: JBoss Drools
          Issue Type: Bug
            Reporter: Markus Wolf
         Assigned To: Mark Proctor
            Priority: Blocker


When I have a rule condition like this:
  Something( test matches "abc def")
I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
When I remove the space and replace it with \s it does compile well.

Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:59:14 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1243) Pattern matching
 does not allow spaces
In-Reply-To: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17202926.1191333554599.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1243?page=all ]

Markus Wolf updated JBRULES-1243:
---------------------------------

    Affects Version/s: 4.0.1
             Priority: Major  (was: Blocker)

> Pattern matching does not allow spaces
> --------------------------------------
>
>                 Key: JBRULES-1243
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> When I have a rule condition like this:
>   Something( test matches "abc def")
> I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
> When I remove the space and replace it with \s it does compile well.
> Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:23:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Tue, 2 Oct 2007 10:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-471) Method
 enforceArgsConsistency()
 not found on field interception with @Arg-annotated param
In-Reply-To: <12708972.1191268901563.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3649404.1191334983258.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-471?page=all ]

Flavia Rainone closed JBAOP-471.
--------------------------------


> Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAOP-471
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-471
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
> The result:
> Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
> java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
> rgsPOJO.field5]
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
>         at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
>         at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
> Caused by: java.lang.RuntimeException: Error creating invokeNext method: {   try{      switch(++super.currentInterceptor){      case 1:enforceArgsConsistency
> ();    around6.around1(this.arg0);
>       break;      case 2:enforceArgsConsistency();    around7.around2(this.arg0);
>       break;      case 3:enforceArgsConsistency();    around8.around3(this.arg0);
>       break;      case 4:enforceArgsConsistency();    around9.around4(this.arg0);
>       break;      case 5:enforceArgsConsistency();    around10.around6(this.arg0);
>       break;      default:         this.dispatch();      }   }finally{      --super.currentInterceptor;   }   return null;}
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
>         ... 26 more
> Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
> _16
>         at javassist.CtBehavior.setBody(CtBehavior.java:367)
>         at javassist.CtBehavior.setBody(CtBehavior.java:334)
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
>         ... 28 more
> Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
>         at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
>         at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
>         at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
>         at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
>         at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
>         at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:25:17 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 10:25:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-651)
 javax.ejb.SessionContext.getBusinessObject has wrong signature
In-Reply-To: <10970126.1152819852031.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13922528.1191335117059.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-651?page=all ]

Carlo de Wolf reassigned EJBTHREE-651:
--------------------------------------

    Assignee: Carlo de Wolf

> javax.ejb.SessionContext.getBusinessObject has wrong signature
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-651
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-651
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3
>
>
> javax.ejb.SessionContext.getBusinessObject must have the following signature:
> <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException;
> See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getBusinessObject(java.lang.Class)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:25:17 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 10:25:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-651)
 javax.ejb.SessionContext.getBusinessObject has wrong signature
In-Reply-To: <10970126.1152819852031.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32002984.1191335117207.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-651?page=all ]

Carlo de Wolf resolved EJBTHREE-651.
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
       Resolution: Done

> javax.ejb.SessionContext.getBusinessObject has wrong signature
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-651
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-651
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3
>
>
> javax.ejb.SessionContext.getBusinessObject must have the following signature:
> <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException;
> See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getBusinessObject(java.lang.Class)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:29:03 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Tue, 2 Oct 2007 10:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1243) Pattern matching
 does not allow spaces
In-Reply-To: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25685389.1191335343277.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1243?page=all ]

Markus Wolf updated JBRULES-1243:
---------------------------------


The given rule is not exactlly, to reproduct one have to use the following condition:
  Something( prop1.prop2 matches "abc def")
I've read that this matching is delegated to MVEL - maybe the bug belongs to MVEL then.

> Pattern matching does not allow spaces
> --------------------------------------
>
>                 Key: JBRULES-1243
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> When I have a rule condition like this:
>   Something( test matches "abc def")
> I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
> When I remove the space and replace it with \s it does compile well.
> Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:37:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 10:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4523) Verify
 installation of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25436566.1191335823296.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4523?page=comments#action_12379914 ] 
            
Heiko Braun commented on JBAS-4523:
-----------------------------------

Testsuite: org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase
Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 0.095 sec
------------- Standard Output ---------------
cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsconsume.sh -k -o /home/hbraun/
dev/prj/jbossws/stack/native/trunk/output/tests/wsconsume/java /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/
tests/resources/jaxws/smoke/tools/wsdl/TestServiceCatalog.wsdl
test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsprovide.sh -k -w -o /home/hbra
un/dev/prj/jbossws/stack/native/trunk/output/tests/wsprovide/java --classpath /home/hbraun/dev/prj/jbossws/stack/nativ
e/trunk/output/tests/classes org.jboss.test.ws.jaxws.smoke.tools.CalculatorBean
test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
------------- ---------------- ---------------

Testcase: testWSConsumeFromCommandLine took 0.006 sec
        Caused an ERROR
java.io.IOException: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsconsume.sh: no
t found
java.io.IOException: java.io.IOException: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA
/bin/wsconsume.sh: not found
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
        at java.lang.Runtime.exec(Runtime.java:591)
        at java.lang.Runtime.exec(Runtime.java:429)
        at java.lang.Runtime.exec(Runtime.java:367)
        at org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase.executeCommand(ScriptTestCase.java:110)
        at org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase.testWSConsumeFromCommandLine(ScriptTestCase.java:69)


> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:41:04 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 2 Oct 2007 10:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13634875.1191336064658.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-570?page=comments#action_12379916 ] 
            
Vladimir Blagojevic commented on JGRP-570:
------------------------------------------

ThreadNamaingPattern is applied to all thread pools. However, there are still leftover short lifespan threads that are not renamed.

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:49:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-553) Run AS (4.x and
 5.x) integration tests with Messaging
In-Reply-To: <27353135.1159216981170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8922364.1191336543453.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-553?page=all ]

Clebert Suconic closed JBMESSAGING-553.
---------------------------------------

    Resolution: Done

> Run AS (4.x and 5.x) integration tests with Messaging
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-553
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-553
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> This is the container task for everthing required to run JBoss AS JMS integration tests with JBoss Messaging. The existing integration test framework should be modified in such a manner to allow interchangeably running the same JMS tests with JBossMQ and JBoss Messaging. None of the existing JBossMQ tests should be removed, they must be at most refactored so the JBossMQ-specific tests will be executed with JBossMQ only (as part of the JBossMQ functional testsuite) and generic JMS tests will be executed with both JBossMQ and JBoss Messaging.
> More details in the sub-tasks.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:51:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1092) Fix the
 JBossHead testsuite
Message-ID: <27131273.1191336663430.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix the JBossHead testsuite
---------------------------

                 Key: JBMESSAGING-1092
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1092
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration



There are still tests failing because of config issues...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:51:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-387) Modify the
 admin console to
 work with Messaging while keeping JBossMQ compatibility
Message-ID: <22530056.1191336663923.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-387?page=all ]

Clebert Suconic closed JBMESSAGING-387.
---------------------------------------

    Resolution: Partially Completed

> Modify the admin console to work with Messaging while keeping JBossMQ compatibility
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-387
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-387
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>             Fix For: AS 5.0 Integration
>
>
> JSR77
> Charles

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:53:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1093) Verify/Update
 the "all" configuration on JBossHead
Message-ID: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>

Verify/Update the "all" configuration on JBossHead
--------------------------------------------------

                 Key: JBMESSAGING-1093
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Tim Fox




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:53:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:53:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-384) Modify
 jboss-head build
 script to include Messaging instead of JBossMQ in the "all" configuration
Message-ID: <30803679.1191336784113.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-384?page=all ]

Clebert Suconic closed JBMESSAGING-384.
---------------------------------------

    Resolution: Done

> Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-384
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-384
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> Make sure JBossMQ still works as an alternate JMS provider

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:53:05 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:53:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1094) Integrate
	JSR-77
Message-ID: <9255952.1191336785142.JavaMail.jira@cloud.prod.atl2.jboss.com>

Integrate JSR-77
----------------

                 Key: JBMESSAGING-1094
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1094
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration, EAP 4.3 Integration




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1093)
 Verify/Update the "all" configuration on JBossHead
In-Reply-To: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25698247.1191336903451.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1093?page=all ]

Clebert Suconic reassigned JBMESSAGING-1093:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Verify/Update the "all" configuration on JBossHead
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1093
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1093) Verify/Update
 the "all" configuration on JBossHead
In-Reply-To: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9473174.1191336903560.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1093?page=all ]

Clebert Suconic updated JBMESSAGING-1093:
-----------------------------------------

    Fix Version/s: AS 5.0 Integration

> Verify/Update the "all" configuration on JBossHead
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1093
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1094) Integrate
	JSR-77
In-Reply-To: <9255952.1191336785142.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23004120.1191336903772.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1094?page=all ]

Clebert Suconic reassigned JBMESSAGING-1094:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Integrate JSR-77
> ----------------
>
>                 Key: JBMESSAGING-1094
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1094
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-382) Make Messaging
 the default JMS provider for JBoss 5.0
Message-ID: <17054107.1191336903979.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-382?page=all ]

Clebert Suconic closed JBMESSAGING-382.
---------------------------------------

    Resolution: Done

> Make Messaging the default JMS provider for JBoss 5.0
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-382
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-382
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:57:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1092) Fix the
 JBossHead testsuite
In-Reply-To: <27131273.1191336663430.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7882484.1191337023387.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1092?page=all ]

Clebert Suconic reassigned JBMESSAGING-1092:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Fix the JBossHead testsuite
> ---------------------------
>
>                 Key: JBMESSAGING-1092
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1092
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> There are still tests failing because of config issues...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:59:14 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-726) Write/Ellect
 some
 Clustering tests to go into Integration Testsuite on ApplicationServer
In-Reply-To: <1288401.1168296267440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28763649.1191337154896.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-726?page=all ]

Clebert Suconic updated JBMESSAGING-726:
----------------------------------------

    Fix Version/s: AS 5.0 Integration

> Write/Ellect some Clustering tests to go into Integration Testsuite on ApplicationServer
> ----------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-726
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-726
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.2.0.Beta1
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:03:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 11:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3556) Add non-integration
 based testing to cluster module
In-Reply-To: <8862893.1156352389582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19498659.1191337383408.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3556?page=all ]

Brian Stansberry reassigned JBAS-3556:
--------------------------------------

    Assignee: Brian Stansberry

> Add non-integration based testing to cluster module
> ---------------------------------------------------
>
>                 Key: JBAS-3556
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3556
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Test Suite
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-5.0.1.CR1
>
>
> All the unit tests for the AS cluster module are run via the testsuite tests-clustering target, which starts two AS instances.  This is painful and time consuming and discourages writing of simple unit tests that exercise a particular class, with no need for a larger integration.
> Need to set up a src/tests tree in the cluster module, add simple unit tests to it, and integrate that into the overall testsuite run.  The security module has this kind of setup; look to that to see how the overall testsuite integration is done.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:03:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
Message-ID: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot change roles of user names containing a backslash character
------------------------------------------------------------------

                 Key: JBPORTAL-1732
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Identity
    Affects Versions: 2.6.2 Final
         Environment: Any
            Reporter: Luc Boudreau
            Priority: Critical


In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.

ie. DOMAIN\username

I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.

2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)





-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:03:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5613738.1191337383665.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12379921 ] 
            
Luc Boudreau commented on JBPORTAL-1732:
----------------------------------------

The correct username would have been SIM\boudrel here...

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>            Priority: Critical
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:09:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 2 Oct 2007 11:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16403093.1191337743250.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=all ]

Thomas Heute updated JBPORTAL-1732:
-----------------------------------

    Fix Version/s: 2.6.3 Final
         Priority: Major  (was: Critical)

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:31:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 11:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31936128.1191339063373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf reassigned EJBTHREE-900:
--------------------------------------

    Assignee: Carlo de Wolf

> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:49:12 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:49:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26572771.1191340152876.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12379929 ] 
            
Luc Boudreau commented on JBPORTAL-1732:
----------------------------------------

This bug also affects the user deletion. Probably other functionnalities too.

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:57:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
Message-ID: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>

CMS admin role hardcoded somewhere
----------------------------------

                 Key: JBPORTAL-1733
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal CMS
         Environment: Any
            Reporter: Luc Boudreau
         Assigned To: Sohil Shah


 - Modify platform to use another admin role name
 - Create user with new admin role and old Admin role
 - Change security on root node of CMS and make the new role the manager
 - Change the user's roles by removing the old Admin role
 - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:57:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2559844.1191340623525.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_12379930 ] 
            
Luc Boudreau commented on JBPORTAL-1733:
----------------------------------------

On the last thing to do, I meant :

 -  - Try to secure the root node : Access Denided

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 12:01:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 2 Oct 2007 12:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27919516.1191340863719.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=all ]

Thomas Heute updated JBPORTAL-1733:
-----------------------------------

        Fix Version/s: 2.6.3 Final
    Affects Version/s: 2.6.2 Final

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:29:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 13:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
Message-ID: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot gravitate data only stored in cache loader
-------------------------------------------------

                 Key: JBCACHE-1192
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eviction, Replication
    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
            Priority: Critical
             Fix For: 1.4.1.SP6, 2.1.0.GA


If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:34:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1190) Eviction
 configuration should consider buddy backup regions as well.
In-Reply-To: <32922469.1191234772880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13515307.1191346443882.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1190?page=all ]

Brian Stansberry updated JBCACHE-1190:
--------------------------------------

    Workaround:   (was: [Workaround Exists])

Removing the suggested workaround; JBCACHE-1192 means it won't work.

> Eviction configuration should consider buddy backup regions as well.
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1190
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:59:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 13:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4523) Verify installation
 of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33252356.1191347943683.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4523?page=all ]

Heiko Braun updated JBAS-4523:
------------------------------

    Comment: was deleted

> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:59:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 13:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4523) Verify
 installation of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30014359.1191347943865.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4523?page=comments#action_12379956 ] 
            
Heiko Braun commented on JBAS-4523:
-----------------------------------

Testing AS 4.2.2:

one-test:
    [junit] Running org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase
    [junit] cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsconsume.sh -k -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsconsume/java /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/resources/jaxws/smoke/tools/wsdl/TestServiceCatalog.wsdl
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsprovide.sh -k -w -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsprovide/java --classpath /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/classes org.jboss.test.ws.jaxws.smoke.tools.CalculatorBean
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.564 sec


> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:59:04 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 13:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4523) Verify
 installation of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8148466.1191347944047.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4523?page=comments#action_12379957 ] 
            
Heiko Braun commented on JBAS-4523:
-----------------------------------

Testing AS 5.0:

one-test:
    [junit] Running org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase
    [junit] cmd: /home/hbraun/dev/prj/jbossas/trunk/build/output/jboss-5.0.0.Beta3/bin/wsconsume.sh -k -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsconsume/java /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/resources/jaxws/smoke/tools/wsdl/TestServiceCatalog.wsdl
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] cmd: /home/hbraun/dev/prj/jbossas/trunk/build/output/jboss-5.0.0.Beta3/bin/wsprovide.sh -k -w -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsprovide/java --classpath /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/classes org.jboss.test.ws.jaxws.smoke.tools.CalculatorBean
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.648 sec


> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:01:08 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 14:01:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4523) Verify installation
 of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32783713.1191348068132.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4523?page=all ]

Heiko Braun resolved JBAS-4523.
-------------------------------

    Resolution: Done

The tests should actually move to the AS code base. I'll create a separate issue for it.

> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:03:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 14:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4773) Move the JBossWS
 integration tests to the AS test module
Message-ID: <24000477.1191348183624.JavaMail.jira@cloud.prod.atl2.jboss.com>

Move the JBossWS integration tests to the AS test module
--------------------------------------------------------

                 Key: JBAS-4773
                 URL: http://jira.jboss.com/jira/browse/JBAS-4773
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Test Suite
            Reporter: Heiko Braun
         Assigned To: Heiko Braun
             Fix For: JBossAS-4.2.3.GA


The JBossWS integration test need to reside with the AS. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:05:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 14:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1190) Eviction
 configuration should consider buddy backup regions as well.
In-Reply-To: <32922469.1191234772880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24235989.1191348303293.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1190?page=all ]

Brian Stansberry updated JBCACHE-1190:
--------------------------------------

    Workaround Description:   (was: Explicitly configure parallel eviction policies for all buddy backup Fqn patterns)

> Eviction configuration should consider buddy backup regions as well.
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1190
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:35:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 14:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1192) Cannot
 gravitate data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27277455.1191350103505.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=comments#action_12379970 ] 
            
Brian Stansberry commented on JBCACHE-1192:
-------------------------------------------

Test for this is BuddyReplicationWithCacheLoaderTest.testGravitationOfEvictedNodes()

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication, Eviction
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 1.4.1.SP6
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 15:05:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 15:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
In-Reply-To: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4659551.1191351903700.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4772?page=all ]

Thomas Diesler resolved JBAS-4772.
----------------------------------

    Resolution: Done

Use tests.classpath  instead of tests.compile.classpath

--- imports/server-config.xml   (revision 65767)
+++ imports/server-config.xml   (working copy)
@@ -686,7 +686,7 @@
                <pathelement location="${build.resources}"/>
                <!-- This may need to be externalized -->
                <pathelement location="${build.resources}/security"/>
-               <path refid="tests.compile.classpath"/>
+               <path refid="tests.classpath"/>
             </classpath>


> org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4772
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 15:07:15 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 15:07:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4767) Upgrade jbossws to
 2.0.1 (from 1.2.1.GA)
In-Reply-To: <16412352.1191227742601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9685952.1191352035861.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4767?page=all ]

Thomas Diesler resolved JBAS-4767.
----------------------------------

    Resolution: Done

Done.

Please note, jbossws-jboss42.jar must be removed from jbossws.sar during the AS build.

> Upgrade jbossws to 2.0.1 (from 1.2.1.GA)
> ----------------------------------------
>
>                 Key: JBAS-4767
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4767
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 15:51:14 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 2 Oct 2007 15:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4695) Update the release
 notes for JBossAS 4.2.2.GA
In-Reply-To: <21520758.1189414871155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1197145.1191354674968.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4695?page=all ]

Dimitris Andreadis closed JBAS-4695.
------------------------------------

    Resolution: Done

It's ok, needs a final pass.

> Update the release notes for JBossAS 4.2.2.GA
> ---------------------------------------------
>
>                 Key: JBAS-4695
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4695
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 17:31:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Tue, 2 Oct 2007 17:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-812) Specify an API to
 discover services
Message-ID: <11944998.1191360663233.JavaMail.jira@cloud.prod.atl2.jboss.com>

Specify an API to discover services
-----------------------------------

                 Key: JBREM-812
                 URL: http://jira.jboss.com/jira/browse/JBREM-812
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: r3 api
            Reporter: David Lloyd
         Assigned To: David Lloyd
            Priority: Minor
             Fix For: 3.0.0.Alpha1 (Otter)


The Remoting 3 API presently has a mechanism to discover endpoints and supply information about how to connect to discovered endpoints.

A mechanism is also needed to allow a user to find any endpoint that provides a specific service.  This mechanism would preferably work in tandem with the existing discovery API.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 17:58:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 2 Oct 2007 17:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1506310.1191362283374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4180?page=all ]

Galder Zamarreno updated JBAS-4180:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120214

dev forum link added

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:05:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 18:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
Message-ID: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>

ServerPeer won't survive a stop/start of the service
----------------------------------------------------

                 Key: JBMESSAGING-1095
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic


Few NullPointerExceptions would happen..


This won't affect any production system... 

It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:05:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 18:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33011350.1191362703550.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Clebert Suconic updated JBMESSAGING-1095:
-----------------------------------------

        Fix Version/s: 1.4.0.SP1
    Affects Version/s: 1.4.0.GA

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:11:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 18:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <678285.1191363063246.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Clebert Suconic updated JBMESSAGING-1095:
-----------------------------------------

    Fix Version/s: AS 5.0 Integration
                   EAP 4.3 Integration

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:25:07 2007
From: jira-events at lists.jboss.org (Ben Truitt (JIRA))
Date: Tue, 2 Oct 2007 18:25:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1235) Multiple
 Criteria break BRMS rule editor
In-Reply-To: <24987902.1191139841173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24789832.1191363907349.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1235?page=comments#action_12380034 ] 
            
Ben Truitt commented on JBRULES-1235:
-------------------------------------

Hi Michael -
 I'm afraid I can't share the jar / source due to IP stuff with my employer.  What I'll try to do is create a trivial example that I can share that reproduces the problem.
-Ben

> Multiple Criteria break BRMS rule editor
> ----------------------------------------
>
>                 Key: JBRULES-1235
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1235
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Ben Truitt
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>         Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg, screenshot3.jpeg
>
>
> In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
> Two ways to trigger:
> 1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
> 2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
> I'll attach screenshots, which should help explain.
> Sorry if this is a dupe - I looked, but didn't find anything like 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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:18:03 2007
From: jira-events at lists.jboss.org (Kris Verlaenen (JIRA))
Date: Tue, 2 Oct 2007 20:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1244) Ruleflows should
 have a package name
Message-ID: <20387486.1191370683368.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ruleflows should have a package name
------------------------------------

                 Key: JBRULES-1244
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1244
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Rule Flow
            Reporter: Kris Verlaenen
         Assigned To: Kris Verlaenen
             Fix For: 4.0.2


Ruleflows should be added as part of their own package.
This allows
 - adding ruleflows before adding rules
 - adding only ruleflows to a package


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:22:03 2007
From: jira-events at lists.jboss.org (Kris Verlaenen (JIRA))
Date: Tue, 2 Oct 2007 20:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1244) Ruleflows should
 have a package name
In-Reply-To: <20387486.1191370683368.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6456595.1191370923247.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1244?page=all ]

Kris Verlaenen resolved JBRULES-1244.
-------------------------------------

    Resolution: Done

Process now has a packageName

> Ruleflows should have a package name
> ------------------------------------
>
>                 Key: JBRULES-1244
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1244
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rule Flow
>            Reporter: Kris Verlaenen
>         Assigned To: Kris Verlaenen
>             Fix For: 4.0.2
>
>
> Ruleflows should be added as part of their own package.
> This allows
>  - adding ruleflows before adding rules
>  - adding only ruleflows to a package

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:29:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
Message-ID: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>

ServletServerInvoker should return an exception instead of just an error message
--------------------------------------------------------------------------------

                 Key: JBREM-813
                 URL: http://jira.jboss.com/jira/browse/JBREM-813
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.4.0.Beta1 (Pinto)


The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  

Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:29:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28273730.1191371343935.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-813?page=all ]

Ron Sigal updated JBREM-813:
----------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:37:13 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:37:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-809) Verify that the
 behavior of the
 HTTPUnMarshaller re stripping CR and LF characters is correct
In-Reply-To: <4580360.1190730941269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29920730.1191371833435.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-809?page=all ]

Ron Sigal updated JBREM-809:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP1
                       2.4.0.Beta1 (Pinto)
                           (was: 2.2.1.GA)

> Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBREM-809
>                 URL: http://jira.jboss.com/jira/browse/JBREM-809
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP1
>            Reporter: Tom Fennelly
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> At the moment, the HTTPUnMarshaller uses a BufferedReader to read a HTTP char stream.  This causes it to modify the message payload by removing the CR and LF characters.  This causes a problem for us on the ESB because it means that signature checks fail on signed SOAP messages since the sig was generated from the message containing the CR and LF chars.  It's even worse than that... it actually corrupts the signature within the message because the canonical form of the sig contains CRLF chars.
> We got around this in the ESB (in the short term) by setting our own modified version of the HTTPUnMarshaller - one that doesn't use a BufferedReader.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:37:13 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:37:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-808) Remove dependencies
 on ObjectNameFactory from JBoss JMX
In-Reply-To: <161557.1189940062854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22118309.1191371833996.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-808?page=all ]

Ron Sigal updated JBREM-808:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP1
                       2.4.0.Beta1 (Pinto)

> Remove dependencies on ObjectNameFactory from JBoss JMX
> -------------------------------------------------------
>
>                 Key: JBREM-808
>                 URL: http://jira.jboss.com/jira/browse/JBREM-808
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP1
>            Reporter: Julien Viet
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> It happens when my POJO has not been bound on the transporter server, it looks like the transporter client is trying to do some fail over.
> This make JBoss Remoting depends on the JBoss JMX implementation. That makes JBoss Remoting more difficult to embed and reuse.
> I think that the ObjectNameFactory class could be easily ported to JBoss Remoting without any harm done. However perhaps JBoss Remoting has more dependencies on JBoss JMX that I don't know that would prevent to remove such dependency.
>    [junit_] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/mx/util/ObjectNameFactory
>    [junit_]     at org.jboss.remoting.transporter.InternalTransporterServices.<clinit>(InternalTransporterServices.java:41)
>    [junit_]     at org.jboss.remoting.transporter.TransporterClient.findAlternativeTarget(TransporterClient.java:330)
>    [junit_]     at org.jboss.remoting.transporter.TransporterClient.invoke(TransporterClient.java:301)
>    [junit_]     at $Proxy0.getInfo(Unknown Source)
>    [junit_]     at org.jboss.portal.test.framework.driver.remote.RemoteTestDriverClient.getInfo(RemoteTestDriverClient.java:107)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:39:06 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:39:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-810) coyote.RequestMap
 not storing all request properties in the Map.Entry set
In-Reply-To: <12166936.1190807921122.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31450323.1191371946039.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-810?page=all ]

Ron Sigal updated JBREM-810:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP1
                       2.4.0.Beta1 (Pinto)

> coyote.RequestMap not storing all request properties in the Map.Entry set
> -------------------------------------------------------------------------
>
>                 Key: JBREM-810
>                 URL: http://jira.jboss.com/jira/browse/JBREM-810
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.2.SP1
>            Reporter: Tom Fennelly
>         Assigned To: Trustin Lee
>            Priority: Minor
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> Small thing, but the RequestMap overrides the get method for some of the request properties e.g. "Path" and "HttpVersion".  This is fine if the code using the request Map (from InvocationRequest) accesses the properties via the get method.  However, if it iterates over the Map.Entry set, these values will come back as null because they're not actually stored in the map entry set.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 22:30:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 22:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18997650.1191378603312.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Clebert Suconic closed JBMESSAGING-1095.
----------------------------------------

    Resolution: Done

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 22:36:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 22:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1091) Selector
 parser should
 use string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30453892.1191378963366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Clebert Suconic reassigned JBMESSAGING-1091:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 22:36:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 22:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31683545.1191378963541.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Clebert Suconic closed JBMESSAGING-1091.
----------------------------------------

    Resolution: Done

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 23:13:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Tue, 2 Oct 2007 23:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1240) Remove Dialect
 state from PackageBuilderConfiguration
In-Reply-To: <22006922.1191288761051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2050594.1191381183230.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1240?page=all ]

Mark Proctor closed JBRULES-1240.
---------------------------------

    Resolution: Done

> Remove Dialect state from PackageBuilderConfiguration
> -----------------------------------------------------
>
>                 Key: JBRULES-1240
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1240
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> We are getting issues, particularly in threading scenarios, where PackageBuilderConfiguration holding onto the JavaDialect instance is causing problems. We need to make PackageBuilderConfiguration stateless, or atleast immutable.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 00:36:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Wed, 3 Oct 2007 00:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1193) Tests should not
 call Transaction.commit/rollback()
Message-ID: <5880125.1191386163241.JavaMail.jira@cloud.prod.atl2.jboss.com>

Tests should not call Transaction.commit/rollback()
---------------------------------------------------

                 Key: JBCACHE-1193
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1193
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Jason T. Greene
         Assigned To: Jason T. Greene
             Fix For: 2.1.0.GA


The JTA spec says that the thread association of a transaction can only be controlled by TransactionManager. The reason is that a Transaction can be bound to multple threads. In order to be compliant, and work with JBoss JTA, we need to ensure that all operations go through TransactionManager

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 00:58:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Wed, 3 Oct 2007 00:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4696) Arrange community
 documents for 4.2.2.GA
In-Reply-To: <25461197.1189416611004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20967489.1191387483421.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4696?page=comments#action_12380057 ] 
            
Michael Smith commented on JBAS-4696:
-------------------------------------

Status Update:
===========
Step 1: Move JBEAP4.2 forked content (x6 languages) back into upstream Target is 28 Sept and branch as Enterprise.
   |_DONE: Enterprise branch is JBEAP42CP01. Note will only build on linux with the documentation-devel package

Step 2: Create test branch and rearchitect to build with Maven2
   |_DONE: Content in trunk has been moved across and can be built with maven plugin.
      |_Installation_Guide: Ported the 4.2 content
      |_Getting_Started_Guide:  Ported BRANCH_4_0_4  
      |_Clustering_Guide: Ported BRANCH_4_0_4
      |_Server_Configuration_Guide: Ported JBEAP42CP01

*NOTE* The Installation Guide and Getting Started Guide work done for the Enterprise Platform was independant of the previous AS content.
*NOTE* Your team can now pull down the content from trunk and build with the maven plugin.

Step 3: Cleaning Each Guide: Each book needs to be gone through to clean up the output with Maven. 
   |_IN PROCESS: Maven presents the content differently than the previous Ant version. I am budgeting 1 day per book. ETA should be Tuesday, 9th Oct.

> Arrange community documents for 4.2.2.GA
> ----------------------------------------
>
>                 Key: JBAS-4696
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4696
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Michael Smith
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> We *must* produce community documents for AS.
> At the moment, the only 4.2.x documentation that exists is the EAP one.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 03:40:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Wed, 3 Oct 2007 03:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1191) Work with
 contributor to translate JBoss Cache documentation into Spanish
In-Reply-To: <25972580.1191241843360.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1629440.1191397203370.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1191?page=comments#action_12380075 ] 
            
Michael Smith commented on JBCACHE-1191:
----------------------------------------

Thanks, Manik.

We have a process set up for Japan. Let me contact the individual and initiate the same process. 

> Work with contributor to translate JBoss Cache documentation into Spanish
> -------------------------------------------------------------------------
>
>                 Key: JBCACHE-1191
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1191
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Michael Smith
>             Fix For: 2.2.0.GA
>
>
> See email sent in to the jbosscache-dev list:
> http://lists.jboss.org/pipermail/jbosscache-dev/2007-September/002031.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 03:44:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Wed, 3 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1727) CLONE -CMS
 saves pages in
 native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then
 national leters are damaged
In-Reply-To: <31403760.1190983541148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30670835.1191397443288.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1727?page=comments#action_12380076 ] 
            
Mariusz Smykula commented on JBPORTAL-1727:
-------------------------------------------

Patch for issue JBPORTAL-832 is resolving this problem too.

> CLONE -CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1727
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1727
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>         Environment: jboss4.2 (bundled version) and 4.0.5.GA
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged.
> I think that I have to encode the request in UTF-8 ??? 
> ---------------------------------------------
>  create file.html in Ru (in cms admin) with this text
> abc???
> then look at the last record of JBP_CMS_VERSION_BINVAL
> (six bytes in BINVAL_DATA field):
> 61 62 63 e0 e1 e2
> it is cp1251 encoding !!!!
> why this text non unicoded ???
> then when i retrive it i have - 'abc???'
> I think that problem isn't in ContentTypeInterceptor because it succefully
> sets UTF8, because localized resources seems right (in russian).
> may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ???
> -----------------------------------------------------------
> but when I upload file on UTF-8 with russian characters - all correct.
> I think that cms saves the content in one byte encoding (cp1250 or same). 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 03:46:08 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Wed, 3 Oct 2007 03:46:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1727) CLONE -CMS saves
 pages in
 native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then
 national leters are damaged
In-Reply-To: <31403760.1190983541148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5776654.1191397568192.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1727?page=all ]

Mariusz Smykula updated JBPORTAL-1727:
--------------------------------------

    Affects Version/s: 2.6.2 Final

> CLONE -CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1727
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1727
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final, 2.6.2 Final
>         Environment: jboss4.2 (bundled version) and 4.0.5.GA
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged.
> I think that I have to encode the request in UTF-8 ??? 
> ---------------------------------------------
>  create file.html in Ru (in cms admin) with this text
> abc???
> then look at the last record of JBP_CMS_VERSION_BINVAL
> (six bytes in BINVAL_DATA field):
> 61 62 63 e0 e1 e2
> it is cp1251 encoding !!!!
> why this text non unicoded ???
> then when i retrive it i have - 'abc???'
> I think that problem isn't in ContentTypeInterceptor because it succefully
> sets UTF8, because localized resources seems right (in russian).
> may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ???
> -----------------------------------------------------------
> but when I upload file on UTF-8 with russian characters - all correct.
> I think that cms saves the content in one byte encoding (cp1250 or same). 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:29:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
Message-ID: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>

FLUSH: problems with TCP and concurrent startup/shutdowns
---------------------------------------------------------

                 Key: JGRP-603
                 URL: http://jira.jboss.com/jira/browse/JGRP-603
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Vladimir Blagojevic


The attached ZIP file has code that reproduces this.

Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.

To reproduce:
- Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
- This works fine without FLUSH

- With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
- Randomly kill and restart instances




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:29:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 04:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4572) EJB 3 testsuite 100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22297808.1191400143605.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4572?page=all ]

Dimitris Andreadis reopened JBAS-4572:
--------------------------------------

             
Reopening the issue to see how to deal with the failures that appeared after the jbossws-2.0 upgrade:

Both hudsons agree on the results, we have 8 failures:
http://dev45.qa.atl.jboss.com:8585/hudson/view/EJB3/job/ejb3-4.2-testsuite/lastBuild/testReport/
http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_4.2/93/testReport/

org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(BR-enabled).testStatefulPassivation
org.jboss.ejb3.test.ejbthree832.unit.EntityTestCase.test1
org.jboss.ejb3.test.iiop.unit.IiopRemoteUnitTestCase(jacorb).testTxPropegation
org.jboss.ejb3.test.interceptors2.unit.InterceptorsTestCase.testOverrideOrdering
org.jboss.ejb3.test.jacc.unit.JaccTestCase.testSomeEntity
org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testClientAccessRPC
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef3
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef4 

We need to create subtasks for the individual failures and resolve by the end of the week (9/5th).

> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:31:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2861242.1191400263310.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: jgtest.zip

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <677799.1191400383292.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Fix Version/s: 2.6
         Priority: Critical  (was: Major)

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:43:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-603) FLUSH: problems
 with TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26994108.1191400983371.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12380083 ] 
            
Bela Ban commented on JGRP-603:
-------------------------------

Actually, this works really well with "udp" (I probably tested "tcp" when I thought I was testing "udp")...
But there are definitely issues with "tcp". Most issues are with "tcp-nio", and we should look into those, although tcp-nio has not yet been really well tested (and supported).

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:51:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 04:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11054206.1191401463368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1732:
---------------------------------------------

    Assignee: Boleslaw Dawidowicz

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:51:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 04:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1707) New
 UserModule/RoleModule finders
In-Reply-To: <6276632.1190228243214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20320732.1191401463738.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1707?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1707:
---------------------------------------------

    Assignee: Boleslaw Dawidowicz  (was: Julien Viet)

> New UserModule/RoleModule finders
> ---------------------------------
>
>                 Key: JBPORTAL-1707
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1707
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final
>            Reporter: Andrew Oliver
>         Assigned To: Boleslaw Dawidowicz
>
> While working with clients using the portal API some efficiency issues with regards to finders have become apparent:
> It is presently possible to find users having a role by calling MembershipModule.getUsers(role).  However it is not possible to get a list of users with a set of roles, a list of users who do NOT have a role or set of roles.  (there are ways in both HQL and LDAP to construct each type of query).  I suggest something similar to hibernate conditions.
> MembershipModule.getUsers().addCondition(
>    Condition.and(
>         Condition.not(roleSet), Condition.with(roleSet)
>    )
> )
> this would result in roughly:
> from Users where roles in (:roleSet) and roles not in (:roleSet2)
> and something like 
> (& (|(role=roleName)(role=roleName)  )
>      (&(!role=roleName)(!role=roleName) )
> )
> in LDAP
> the attribute name can be based on the type.  As it stands you have to do something like:
> 		try {			
> 			Role roleApproved = rolemodule.findRoleByName("approved");
> 			Role roleUsers = rolemodule.findRoleByName("User");
> 			//todo create transient wrapper set.
> 		    Set users = membership.getUsers(roleUsers);
> 		    dirtyStinkyHackToGetAroundPortalAPIBugACO(users);
> 		    System.err.println("Total number of users with User Role  : " + users.size() );
> 		    Set temp = new HashSet();
> 		    temp = dirtyStinkyHackToGetAroundPortalAPIBugACO(users); //because the hibernate set doesn't have removeall
> 		    users = temp;
> 			Set usersApproved = membership.getUsers(roleApproved);
> 			System.err.println("number of users with approved role: "+usersApproved.size());
> 			users.removeAll(usersApproved);
> 			System.err.println("Total number of users with User Role and NO approved role : " + users.size() );
> 			Map profiles = profiles(users);
> 			response.setRenderParameter("op", "new");
> 			request.getPortletSession().setAttribute("users", users);
> 			request.getPortletSession().setAttribute("profiles", profiles);
> 		} catch (IdentityException e) {
> 			//todo type this and catch it up higher to make a 
> 			//smarter error message
> 			throw new RuntimeException(e);
> 		}
> 	private Map profiles(Set users) throws IdentityException {
> 		Iterator i = users.iterator();
> 		Map retval = new HashMap();
> 		while(i.hasNext()) {
> 			User user = (User) i.next();
> 			retval.put(user, profileModule.getProperties(user));
> 		}
> 		return retval;
> 	}
> 	
> 	private Set dirtyStinkyHackToGetAroundPortalAPIBugACO(Set users) {
> 		Iterator i = users.iterator();
> 		Set retval = new HashSet();
> 		while(i.hasNext()) {
> 			User u = (User)i.next();
> 			u.getUserName();
> 			retval.add(u);
> 		}
> 		return retval;
> 	}
> Just to get the list of users who DONT have the "approved" role.  For our immediate needs:
> UserModule.getUsersWithout(role) would work...until next time.
> -Andy

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:55:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 04:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31461216.1191401703958.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380084 ] 
            
Boleslaw Dawidowicz commented on JBPORTAL-1732:
-----------------------------------------------

what is your LDAP server and identity configuration? I wonder why this goes thru HibernateUserModuleImpl.

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:00:14 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:00:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32423617.1191402014565.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380085 ] 
            
Thomas Heute commented on JBPORTAL-1732:
----------------------------------------

It happens with plain DB actually.
It might be a core-identity bug though, i just quickly tried.



> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:02:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 05:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-603) FLUSH: problems
 with TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18466159.1191402123582.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12380086 ] 
            
Bela Ban commented on JGRP-603:
-------------------------------

Okay, tcp and tcp-nio now work too if the following changes are made:
- Remove UNICAST from the tcp and tcp-nio stacks
- Set suspect_on_send_failure="true" in TCP and TCP_NIO

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:04:03 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 05:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1245) class cast
	exception
Message-ID: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>

class cast exception
--------------------

                 Key: JBRULES-1245
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.2
         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
            Reporter: ekkehard gentz
         Assigned To: Mark Proctor
            Priority: Critical
             Fix For: 4.0.2


Package.readExternalPackage gives me this exception

java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
	at org.drools.rule.Package.readExternal(Package.java:180)

----
running 4.0.1 it works well

ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:11:21 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 05:11:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13006245.1191402681342.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380087 ] 
            
Boleslaw Dawidowicz commented on JBPORTAL-1732:
-----------------------------------------------

I'm asking about LDAP because I know that in MSAD you authenticate providing DOMAINNAME\USERNAME which doesn't mean that user entry looks like that.

Thomas. So you are saying that portal DB configuration doesn't handle properly user names that contain backslashes?

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:22:14 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:22:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17808004.1191403334713.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380091 ] 
            
Thomas Heute commented on JBPORTAL-1732:
----------------------------------------

Actually the problem is in the new UI portlets.
The workaround is to keep using the former User and Role portlets till 2.6.3  (I just tried to make sure)

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:24:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19394701.1191403444343.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=all ]

Thomas Heute updated JBPORTAL-1732:
-----------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:28:04 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 05:28:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
Message-ID: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>

HomeHandleImplIIOP not using the HandleDelegate
-----------------------------------------------

                 Key: JBAS-4801
                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: IIOP service
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Adrian Brock
         Assigned To: Adrian Brock
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA


The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.

This is because the read/writeObject methods are public when they should be private to be invoked by
Serialization.

Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
currently writing the ior), we need a system property such that people can revert to the previous
serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 05:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1053) State changes in
 @PrePassivate don't get replicated if passivate before
 replication is disabled
Message-ID: <24689323.1191403685280.JavaMail.jira@cloud.prod.atl2.jboss.com>

State changes in @PrePassivate don't get replicated if passivate before replication is disabled
-----------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1053
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1053
             Project: EJB 3.0
          Issue Type: Bug
          Components: Clustering
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


Passivation doesn't trigger replication, so a bean might get passivated on 1 node and not on another. If the bean provider does state changes in pre-passivate these will not be visible on the other node.

By default replication does trigger passivation, so a bean first gets passivated and then replicated. Thus the problem only occurs if passivate before replication is explicitly disabled.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:28:05 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 05:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33170883.1191403685599.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

Adrian Brock updated JBAS-4801:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120219

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:32:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24257466.1191403924493.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380095 ] 
            
Thomas Heute commented on JBPORTAL-1732:
----------------------------------------

I meant "in the new Identity portlets"

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:34:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 05:34:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1054) Buddy
 replication can lead to a memory leak
Message-ID: <23615598.1191404044129.JavaMail.jira@cloud.prod.atl2.jboss.com>

Buddy replication can lead to a memory leak
-------------------------------------------

                 Key: EJBTHREE-1054
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


JBC passivation code is broken with buddy replication enabled.
Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:34:05 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 05:34:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28627084.1191404045377.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=comments#action_12380097 ] 
            
ekkehard gentz commented on JBRULES-1245:
-----------------------------------------

btw: this was the scenario:
....
ois = new ObjectInputStream(fis);
.....
final Package p = new Package();
p.readExternal(ois);
....

running 4.0.1 there was no problem

ekke

> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:34:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 05:34:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1054) Buddy
 replication can lead to a memory leak
In-Reply-To: <23615598.1191404044129.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5674459.1191404046103.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1054?page=all ]

Carlo de Wolf updated EJBTHREE-1054:
------------------------------------

              Component/s: Clustering
    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120207

> Buddy replication can lead to a memory leak
> -------------------------------------------
>
>                 Key: EJBTHREE-1054
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>
> JBC passivation code is broken with buddy replication enabled.
> Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:15:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 06:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
Message-ID: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>

WebServiceContext is not injected before post construct is called
-----------------------------------------------------------------

                 Key: EJBTHREE-1055
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf


JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:17:15 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 06:17:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11573518.1191406635237.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4801?page=comments#action_12380111 ] 
            
Adrian Brock commented on JBAS-4801:
------------------------------------

This has been done.

It will now serialize via the delegate.

There is a system property which can be set
-Dorg.jboss.proxy.ejb.old.homehandle.serialization=true
if this change causes problems.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:19:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 06:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26070396.1191406743369.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

Adrian Brock reassigned JBAS-4801:
----------------------------------

    Assignee: William DeCoste  (was: Adrian Brock)

Passed to Bill to confirm this fixes the problem he was seeing.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:23:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3331194.1191406983482.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4801?page=comments#action_12380113 ] 
            
Dimitris Andreadis commented on JBAS-4801:
------------------------------------------

Adrian, thanks a bunch for the quick response.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:32:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 06:32:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4572) EJB 3 testsuite
	100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30451213.1191407522963.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4572?page=comments#action_12380116 ] 
            
Dimitris Andreadis commented on JBAS-4572:
------------------------------------------

I created "depends" links to the EJB3 issue that *must* be solved, and "related" links to the known failures, according to Carlo's input:


> > org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(BR-enabled).testStatefulPassivation 
EJBTHREE-1053 + EJBTHREE-1054 (to some extend)

> > org.jboss.ejb3.test.ejbthree832.unit.EntityTestCase.test1
EJBTHREE-832: known issue

> > org.jboss.ejb3.test.iiop.unit.IiopRemoteUnitTestCase(jacorb).testTxPropegation
EJBTHREE-892: known issue

> > org.jboss.ejb3.test.interceptors2.unit.InterceptorsTestCase.testOverrideOrdering
EJBTHREE-896: known issue

> > org.jboss.ejb3.test.jacc.unit.JaccTestCase.testSomeEntity
EJBTHREE-894: known issue

> > org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testClientAccessRPC
EJBTHREE-757: is sessionContext.getMessageContext supposed to work? It's
for JAX-RPC which is obsolete, right?
Rephrase: do we do JAX-RPC with EJB 3?

> > org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef3
> > org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef4
EJBTHREE-899: web service ref injection via dd

I've added a test for the post construct issue: EJBTHREE-1055.


> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 07:32:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 3 Oct 2007 07:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1246) Package deploy to
 deploy source drl as option (alternative to .pkg)
Message-ID: <18576826.1191411123242.JavaMail.jira@cloud.prod.atl2.jboss.com>

Package deploy to deploy source drl as option (alternative to .pkg)
-------------------------------------------------------------------

                 Key: JBRULES-1246
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1246
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE


Would be nice to be able to exppose .drl the way we do .pkg now - so that means some systems can just build their own rules (will require changes to the agent). Could solve some hassles with version incompatabilities. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 08:16:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 3 Oct 2007 08:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1235) Multiple
 Criteria break BRMS rule editor
In-Reply-To: <24987902.1191139841173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16254070.1191413763542.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1235?page=comments#action_12380130 ] 
            
Michael Neale commented on JBRULES-1235:
----------------------------------------

Thanks ben. Perhaps create a new fact class with the same private variables. My guess is that there is some data type that is tripping up the code that introspects and builds a model for the GUI. 

PS, I was thinking how awesome your contributions were about a year ago - they are still alive and kicking today ! 

> Multiple Criteria break BRMS rule editor
> ----------------------------------------
>
>                 Key: JBRULES-1235
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1235
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Ben Truitt
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>         Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg, screenshot3.jpeg
>
>
> In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
> Two ways to trigger:
> 1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
> 2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
> I'll attach screenshots, which should help explain.
> Sorry if this is a dupe - I looked, but didn't find anything like 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

        


From jira-events at lists.jboss.org  Wed Oct  3 08:24:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 3 Oct 2007 08:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <572936.1191414243305.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=comments#action_12380131 ] 
            
Mark Proctor commented on JBRULES-1245:
---------------------------------------

there where binary changes between 4.0.0, 4.0.1 and 4.0.2, you'll have to re-create your packages again. The BRMs is able to re-publish all binary packages, I believe.

> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 09:55:03 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 09:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20141226.1191419703543.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=comments#action_12380158 ] 
            
ekkehard gentz commented on JBRULES-1245:
-----------------------------------------

thanks for the info, Mark,

now my Unit-tests are green again :-)

I wasn't aware of those possible changes. good to know, because I want to store my streams in a database.
but its no problem - I'll add a step to re-create all streams after upgrading to new versions and I have to verify,
that all users have to use the same versions.

thanks for soon help

ekke


> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 09:57:23 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 09:57:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2524693.1191419843103.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=all ]

ekkehard gentz closed JBRULES-1245.
-----------------------------------

    Resolution: Done

after recreating the package streams with 4.0.2 Snapshot I was able to re-import them without an exception.

> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 11:22:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 11:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4572) EJB 3 testsuite
	100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10240746.1191424923552.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4572?page=comments#action_12380199 ] 
            
Dimitris Andreadis commented on JBAS-4572:
------------------------------------------

The current list of failures after the know failures were excluded:
http://dev45.qa.atl.jboss.com:8585/hudson/view/EJB3/job/ejb3-4.2-testsuite/lastBuild/testReport/

org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testService2
org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testClientAccessRPC
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef3
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef4 


> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 11:26:16 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 3 Oct 2007 11:26:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28245086.1191425176168.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=comments#action_12380202 ] 
            
Andrew Rubinger commented on EJBTHREE-785:
------------------------------------------

All fixes and tests committed to trunk.

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: Branch_4_2, HEAD
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 11:49:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 11:49:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1054) Buddy
 replication can lead to a memory leak
In-Reply-To: <23615598.1191404044129.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3257588.1191426545864.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1054?page=all ]

Carlo de Wolf updated EJBTHREE-1054:
------------------------------------

    Workaround Description: To 'force' eviction of a bean make sure there is an explicit removal timeout set.
                Workaround: [Workaround Exists]

> Buddy replication can lead to a memory leak
> -------------------------------------------
>
>                 Key: EJBTHREE-1054
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>
> JBC passivation code is broken with buddy replication enabled.
> Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 12:52:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 3 Oct 2007 12:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1180172.1191430323695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=all ]

William DeCoste reassigned EJBTHREE-899:
----------------------------------------

    Assignee: William DeCoste

> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 13:23:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Wed, 3 Oct 2007 13:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25129985.1191432183801.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380248 ] 
            
Luc Boudreau commented on JBPORTAL-1732:
----------------------------------------

Doesn't matter which LDAP I'm using, the user record is properly synchrinized with the database.

Just for the info, we are not using LDAP directly, we are using a custom CAS server which sends back the roles data.

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 14:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 14:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30752375.1191437643363.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380264 ] 
            
Dimitris Andreadis commented on JBCOMMON-35:
--------------------------------------------

Are you committing soon? I want to release 2.2.2.GA.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 14:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 14:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <258429.1191437643521.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380265 ] 
            
Dimitris Andreadis commented on JBCOMMON-35:
--------------------------------------------

Are you committing soon? I want to release 2.2.2.GA.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 15:02:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 15:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28413435.1191438123287.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=all ]

Dimitris Andreadis updated JBCOMMON-35:
---------------------------------------

    Comment: was deleted

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 15:04:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 15:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6926585.1191438243755.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=comments#action_12380266 ] 
            
Dimitris Andreadis commented on JBCOMMON-36:
--------------------------------------------

Are you committing soon? I want to release 2.2.2.GA.

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 15:30:18 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 3 Oct 2007 15:30:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4802) FirstAvailable
 target should not be transient
Message-ID: <32958772.1191439818126.JavaMail.jira@cloud.prod.atl2.jboss.com>

FirstAvailable target should not be transient
---------------------------------------------

                 Key: JBAS-4802
                 URL: http://jira.jboss.com/jira/browse/JBAS-4802
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor


If a bean proxy that already has a target established gets serialized (e.g. passed through a remote call), the sticky target is lost on the other end.  This can lead to invocations against the same target bean on multiple servers.

I don't see any reason for FirstAvailable.electedTarget to be transient.

Problem here is changing this changes the serialized form of the class, breaking interoperability.  Class also does not implement Externalizable.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 17:53:23 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 3 Oct 2007 17:53:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10325955.1191448403961.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Brian Stansberry updated JBAS-4766:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120331

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 17:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Wed, 3 Oct 2007 17:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1096) Document
 bisocket and
 remove references from the old Callback Manager on the documentation
Message-ID: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>

Document bisocket and remove references from the old Callback Manager on the documentation
------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1096
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic


Documentation still refer the old callback mechanism:

http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback


We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 17:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Wed, 3 Oct 2007 17:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1096) Document
 bisocket and
 remove references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15389998.1191448503520.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Clebert Suconic updated JBMESSAGING-1096:
-----------------------------------------

          Component/s: Documentation and Training
        Fix Version/s: 1.4.0.SP1
    Affects Version/s: 1.4.0.GA

> Document bisocket and remove references from the old Callback Manager on the documentation
> ------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:14:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20946572.1191453243345.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal updated JBREM-811:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)
                       (was: 2.2.2.SP1)

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:19:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 19:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1640) provide OpenSSO
	integration
In-Reply-To: <21988026.1187645118595.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25356071.1191453543301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1640?page=all ]

Boleslaw Dawidowicz resolved JBPORTAL-1640.
-------------------------------------------

    Fix Version/s: 2.6.2 Final
                       (was: 2.8 Final)
                       (was: 2.6.3 Final)
       Resolution: Done

Setup described here: http://jbossportal.blogspot.com/2007/10/jboss-portal-with-opensso-and-opends.html

> provide OpenSSO integration
> ---------------------------
>
>                 Key: JBPORTAL-1640
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1640
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.2 Final
>
>
> Provide integration with OpenSSO using tomcat valve mechanism

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:27:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 3 Oct 2007 19:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1241) Dynamic rules
 should be able to
 lock for a series of updates and fireAllRules should be optional
In-Reply-To: <31771190.1191294101057.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16451161.1191454023237.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1241?page=all ]

Mark Proctor closed JBRULES-1241.
---------------------------------

    Resolution: Done

> Dynamic rules should be able to lock for a series of updates and fireAllRules should be optional
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1241
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1241
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> add lock() and unlock() to RuleBase and setup a rulebase listener to progated the fireAllRules calls.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:31:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19973127.1191454263417.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal updated JBREM-811:
----------------------------

        Fix Version/s: 2.2.2.SP2
                       2.2.2.GA_CP01
    Affects Version/s: 2.4.0.Beta1 (Pinto)

This fix should be available for EAP 4.2.0.GA_CP02, AS 4.2.3 (?) and AS 5.0.0.Beta3.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:31:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25473422.1191454268653.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal reopened JBREM-750:
-----------------------------

             
This issue needs to be fixed in a CP release for EAP 4.2.0.GA_CP02.

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:33:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26523020.1191454383320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal updated JBREM-750:
----------------------------

    Fix Version/s: 2.2.2.GA_CP01

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1, 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:33:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-814) CLONE -Logger in
 HTTPClientInvoker should be static.
Message-ID: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>

CLONE -Logger in HTTPClientInvoker should be static.
----------------------------------------------------

                 Key: JBREM-814
                 URL: http://jira.jboss.com/jira/browse/JBREM-814
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.2.2.SP1, 2.2.2.GA_CP01


When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.

The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:35:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4943019.1191454503330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal updated JBREM-750:
----------------------------

    Fix Version/s:     (was: 2.2.2.GA_CP01)

Instead of reopening this issue for 2.2.2.GA_CP01, cloned it.

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:41:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-814) CLONE -Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16089617.1191454863246.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-814?page=all ]

Ron Sigal updated JBREM-814:
----------------------------

    Fix Version/s:     (was: 2.2.2.SP1)

> CLONE -Logger in HTTPClientInvoker should be static.
> ----------------------------------------------------
>
>                 Key: JBREM-814
>                 URL: http://jira.jboss.com/jira/browse/JBREM-814
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3319205.1191456783317.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal closed JBREM-750.
---------------------------

    Resolution: Done

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-814) Logger in
 HTTPClientInvoker should be static (CLONE of JBREM-750)
In-Reply-To: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22751817.1191456783450.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-814?page=all ]

Ron Sigal updated JBREM-814:
----------------------------

    Summary: Logger in HTTPClientInvoker should be static (CLONE of JBREM-750)  (was: CLONE -Logger in HTTPClientInvoker should be static.)

> Logger in HTTPClientInvoker should be static (CLONE of JBREM-750)
> -----------------------------------------------------------------
>
>                 Key: JBREM-814
>                 URL: http://jira.jboss.com/jira/browse/JBREM-814
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:26:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 3 Oct 2007 20:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24651634.1191457563739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Andrew Rubinger resolved EJBTHREE-785.
--------------------------------------

    Resolution: Done

Fixes Merged and Verified in Branch 4.2

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: Branch_4_2, HEAD
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:32:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
Message-ID: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>

allow user to set content-type for http responses (CLONE of JBREM-653)
----------------------------------------------------------------------

                 Key: JBREM-815
                 URL: http://jira.jboss.com/jira/browse/JBREM-815
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: transport
    Affects Versions: 2.2.2.GA
            Reporter: Tom  Elrod
         Assigned To: Ron Sigal
             Fix For: 2.2.2.SP1


Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.

Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:34:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
In-Reply-To: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24215336.1191458043316.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-815?page=comments#action_12380334 ] 
            
Ron Sigal commented on JBREM-815:
---------------------------------

Comment by Tom Fennelly:

This issue is really a bug as far as JBossESB is concerned. JBossESB supports a number of transports/connectors via JBossRemoting. A number of other features also rely on JBossRemoting e.g. SOAP/HTTP. Therefore, in the case of webservices support, not being able to set the Content-Type on http responses effectively means we can't guarantee interoperability since many clients will refuse to process responses that don't have indicate an appropriate Content-Type. 

> allow user to set content-type for http responses (CLONE of JBREM-653)
> ----------------------------------------------------------------------
>
>                 Key: JBREM-815
>                 URL: http://jira.jboss.com/jira/browse/JBREM-815
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
> Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:34:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
In-Reply-To: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17046746.1191458043473.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-815?page=all ]

Ron Sigal updated JBREM-815:
----------------------------

    Fix Version/s: 2.2.2.GA_CP01
                       (was: 2.2.2.SP1)

> allow user to set content-type for http responses (CLONE of JBREM-653)
> ----------------------------------------------------------------------
>
>                 Key: JBREM-815
>                 URL: http://jira.jboss.com/jira/browse/JBREM-815
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
> Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:36:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25820431.1191458163263.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-813?page=all ]

Ron Sigal updated JBREM-813:
----------------------------

    Fix Version/s: 2.2.2.SP2
                   2.2.2.GA_CP01

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:36:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24702814.1191458163379.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12380335 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Arose in support case https://na1.salesforce.com/50030000003iBdA.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 00:29:24 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Thu, 4 Oct 2007 00:29:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9545552.1191472164778.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380345 ] 
            
Vicky Kak commented on JBCOMMON-35:
-----------------------------------

I am planning to fix it by this weekend , how soon do you want it to be done .

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 00:31:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Thu, 4 Oct 2007 00:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5111485.1191472263230.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=comments#action_12380346 ] 
            
Vicky Kak commented on JBCOMMON-36:
-----------------------------------

I am planning to fix it by this weekend , how soon do you want it to be done .

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:03:26 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 4 Oct 2007 03:03:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4696) Arrange community
 documents for 4.2.2.GA
In-Reply-To: <25461197.1189416611004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30304185.1191481406590.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4696?page=comments#action_12380348 ] 
            
Michael Smith commented on JBAS-4696:
-------------------------------------

Mark,

Steps 1-3 Complete. Porting and retrofit to build with maven is complete.
========================================================

Next Steps:
=========
Step 4: Mark, I need you to pull down trunk, build with maven and do a cursory glance to make sure I retrofitted the right content. (Mark)

Step 5: Build a stage for the HTML/PDF docs for tech review (Mark)

Step 6: Once you give me a green light on Step 4, Samson and I will begin the re-write. Our process will be simple: once a chapter is ready for tech-review, we will open a Jira declaring that chapter X is ready for techreview and inform the project mailing list with a link to the chapter on the stage. (Mike & Samson)

> Arrange community documents for 4.2.2.GA
> ----------------------------------------
>
>                 Key: JBAS-4696
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4696
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Michael Smith
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> We *must* produce community documents for AS.
> At the moment, the only 4.2.x documentation that exists is the EAP one.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:08:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 03:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-37) Add jboss-common
 1.2.1.GA to the JBoss maven repository
Message-ID: <28010800.1191481683727.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add jboss-common 1.2.1.GA to the JBoss maven repository
-------------------------------------------------------

                 Key: JBCOMMON-37
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
             Project: JBoss Common
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 1.2.1.GA
         Environment: n/a
            Reporter: Anders Hammar
         Assigned To: Dimitris Andreadis


I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. I'm For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.



-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:15:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 03:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-37) Add jboss-common
 1.2.1.GA to the JBoss maven repository
In-Reply-To: <28010800.1191481683727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22416175.1191482103412.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-37?page=all ]

Anders Hammar updated JBCOMMON-37:
----------------------------------

    Description: 
I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.



  was:
I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. I'm For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.




> Add jboss-common 1.2.1.GA to the JBoss maven repository
> -------------------------------------------------------
>
>                 Key: JBCOMMON-37
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
>             Project: JBoss Common
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.1.GA
>         Environment: n/a
>            Reporter: Anders Hammar
>         Assigned To: Dimitris Andreadis
>
> I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. For the transitive dependency to work, the jboss-common artifact is needed.
> Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:30:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14046273.1191483003405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf updated EJBTHREE-900:
-----------------------------------

    Fix Version/s: AS 4.2.2.GA
                       (was: Branch_4_2)

> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:32:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1684086.1191483123395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf resolved EJBTHREE-900.
------------------------------------

    Resolution: Done

> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:44:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-124)
 @PersistenceContext(EXTENDED) should follow new Spec defined rules
Message-ID: <27213328.1191483843352.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ]

Carlo de Wolf updated EJBTHREE-124:
-----------------------------------

    Fix Version/s:     (was: AS 4.2.2.GA)

> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-124
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:44:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-124)
 @PersistenceContext(EXTENDED) should follow new Spec defined rules
Message-ID: <31191240.1191483843496.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ]

Carlo de Wolf reassigned EJBTHREE-124:
--------------------------------------

    Assignee: Carlo de Wolf

> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-124
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:44:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-124)
 @PersistenceContext(EXTENDED) should follow new Spec defined rules
Message-ID: <26247021.1191483843707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ]

Carlo de Wolf closed EJBTHREE-124.
----------------------------------

    Resolution: Deferred

> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-124
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:58:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 03:58:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-757)
 getMessageContext Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5253252.1191484685544.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=comments#action_12380355 ] 
            
Thomas Diesler commented on EJBTHREE-757:
-----------------------------------------

AFAIK

EJB3 only supports JAX-WS
EJB21 only supports JAX-RPC

IMHO it is illegal for an EJB3 endpoint to obtain a JAX-RPC MessageContext via the SessionContext. 
The way to obtain a JAX-WS MessageContext is via injection.


> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:00:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 04:00:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8428744.1191484804779.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=comments#action_12380357 ] 
            
Thomas Diesler commented on EJBTHREE-899:
-----------------------------------------

This should be supported

> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:10:34 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 04:10:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext
 Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5015458.1191485434574.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf updated EJBTHREE-757:
-----------------------------------

    Fix Version/s: AS 4.2.2.GA
                       (was: Branch_4_2)

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:30:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 04:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-757)
 getMessageContext Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4640106.1191486603426.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf resolved EJBTHREE-757.
------------------------------------

    Resolution: Rejected

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:32:14 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Thu, 4 Oct 2007 04:32:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30815270.1191486734259.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

David Roberts updated GPD-169:
------------------------------

        Summary: GPD Diagram node and text positioning not saving.  (was: Transition text position not saving)
    Description: 
Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:

When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.

Transition text also has a problem:
All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

  was:
Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:

All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 

I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 


I thought it was just the transition text positioning that was not saving correctly. I found that node positions are also not saving correctly.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:57:03 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Thu, 4 Oct 2007 04:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25394616.1191488223905.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

David Roberts updated GPD-169:
------------------------------

    Attachment: Before and After.jpg

Here are two images of a process definition. The first is when I line up my nodes etc into a logical order, and save it. The second is after I have closed the process definition, and re-opened it.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:01:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6962612.1191488463331.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=comments#action_12380367 ] 
            
Thomas Diesler commented on EJBTHREE-1055:
------------------------------------------

Yes, this should be supported as it is in AS5.0

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 05:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30096564.1191489003334.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf reassigned EJBTHREE-1055:
---------------------------------------

    Assignee: Thomas Diesler

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Thomas Diesler
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:15:09 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:15:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6671284.1191489309863.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=comments#action_12380371 ] 
            
Thomas Diesler commented on EJBTHREE-1055:
------------------------------------------

InvocationHandlerEJB3 is the integration point. It lives in the AS code base and should probably be modified to handle context injection properly.

         MethodInfo info = container.getMethodInfo(method);
         EJBContainerInvocation<StatelessContainer, StatelessBeanContext> ejb3Inv = new EJBContainerInvocation<StatelessContainer, StatelessBeanContext>(info);
         ejb3Inv.setAdvisor(container);
         ejb3Inv.setArguments(args);
         ejb3Inv.setContextCallback(new CallbackImpl(epInv));



> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Thomas Diesler
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:20:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 05:20:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-757)
 getMessageContext Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30167083.1191489604531.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf reopened EJBTHREE-757:
------------------------------------

             
Cheered too soon.
EJB 3 3.5.2 defines the use of JAX-RPC clients.

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:20:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:20:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19697468.1191489605604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Thomas Diesler reassigned EJBTHREE-1055:
----------------------------------------

    Assignee: Carlo de Wolf  (was: Thomas Diesler)

Carlo, please call me to discuss this.


> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:26:12 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Thu, 4 Oct 2007 05:26:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17207412.1191489972984.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12380379 ] 
            
David Roberts commented on GPD-169:
-----------------------------------

I said above that "Each time I open my process definition", the nodes are re-ordered. My mistake, it's not each time for the nodes, it's each time for the text positioning. The node positioning problem is intermittent, and has only happened a few times. However, the text position is every time I re-open.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:26:13 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:26:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <6054286.1191489973144.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380380 ] 
            
Thomas Diesler commented on JBREM-305:
--------------------------------------

Yes, but clients want to use the JAX-WS API to send a web service request. The transport (i.e. JMS) should be a configurable aspect and should not require usage of a different API.

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 06:11:22 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 06:11:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-938) Expired messages
 are being delivered
In-Reply-To: <22096346.1175683086452.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2357423.1191492682052.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-938?page=all ]

Carlo de Wolf resolved EJBTHREE-938.
------------------------------------

    Resolution: Won't Fix

JBoss MQ is no longer being supported.

> Expired messages are being delivered
> ------------------------------------
>
>                 Key: EJBTHREE-938
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-938
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: mdb unit test
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** ExpirationTestMDB onMessage 1 in org.jboss.ejb3.test.mdb.ExpirationTestMDB at 27977433
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** now = 1175680736566
> 2007-04-04 11:58:56,567 INFO  [STDOUT] *** message = SpyTextMessage {
> Header {
>    jmsDestination  : QUEUE.expirationtest
>    jmsDeliveryMode : 1
>    jmsExpiration   : 1175680735655
>    jmsPriority     : 4
>    jmsMessageID    : ID:436-11756807355552
>    jmsTimeStamp    : 1175680735555
>    jmsCorrelationID: null
>    jmsReplyTo      : null
>    jmsType         : null
>    jmsRedelivered  : false
>    jmsProperties   : {foo=bar, currentTest=testExpiration, null=null}
>    jmsPropReadWrite: false
>    msgReadOnly     : true
>    producerClientId: ID:436
> }
> Body {
>    text            :expire on server
> }

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 06:52:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 4 Oct 2007 06:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCOMMON-37) Add jboss-common
 1.2.1.GA to the JBoss maven repository
In-Reply-To: <28010800.1191481683727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31190739.1191495123805.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-37?page=all ]

Dimitris Andreadis reassigned JBCOMMON-37:
------------------------------------------

    Assignee: Paul Gier  (was: Dimitris Andreadis)

JBoss common 1.2.x is not mavenized itself.

The sources for 1.2.1.GA can be found here:
https://svn.jboss.org/repos/common/common-old/tags/JBossCommon_1_2_1_GA/

The binaries are uploaded in this location:
https://svn.jboss.org/repos/repository.jboss.org/jboss/common/1.2.1.GA/

If Paul can generate the maven2 artifacts to put there:
https://svn.jboss.org/repos/repository.jboss.org/maven2/jboss/jboss-common/

that would be great.


> Add jboss-common 1.2.1.GA to the JBoss maven repository
> -------------------------------------------------------
>
>                 Key: JBCOMMON-37
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
>             Project: JBoss Common
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.1.GA
>         Environment: n/a
>            Reporter: Anders Hammar
>         Assigned To: Paul Gier
>
> I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. For the transitive dependency to work, the jboss-common artifact is needed.
> Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:06:16 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 4 Oct 2007 07:06:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27684437.1191495977006.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380421 ] 
            
Dimitris Andreadis commented on JBCOMMON-35:
--------------------------------------------

It doesn't look a fix is need when running under jdk5.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:17:26 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 4 Oct 2007 07:17:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8674517.1191496646953.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=comments#action_12380424 ] 
            
Dimitris Andreadis commented on JBCOMMON-36:
--------------------------------------------

Before doing any commit, has anyone reviewed what you propose?

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:34:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 07:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9845984.1191497643222.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf updated EJBTHREE-1055:
------------------------------------

        Fix Version/s: AS 4.2.2.GA
    Affects Version/s: AS 4.2.1.GA

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:38:10 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Thu, 4 Oct 2007 07:38:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1247) Bug during rule
	parsing
Message-ID: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>

Bug during rule parsing
-----------------------

                 Key: JBRULES-1247
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
             Project: JBoss Drools
          Issue Type: Bug
            Reporter: Markus Wolf
         Assigned To: Mark Proctor
            Priority: Blocker


org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:38:10 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Thu, 4 Oct 2007 07:38:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4379610.1191497890777.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Markus Wolf updated JBRULES-1247:
---------------------------------

    Affects Version/s: 4.0.1
             Priority: Major  (was: Blocker)

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:53:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Thu, 4 Oct 2007 07:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1248)
 <literal-restriction> requires
 an 'value' attribute, but it can't be null
Message-ID: <83704.1191498783244.JavaMail.jira@cloud.prod.atl2.jboss.com>

<literal-restriction> requires an 'value' attribute, but it can't be null 
--------------------------------------------------------------------------

                 Key: JBRULES-1248
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1248
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.1,  4.0.0.GA,  4.0.0.MR3, 4.0.0.MR2
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer
             Fix For: 4.0.2


<literal-restriction> requires an 'value' attribute, but the parser fails when we use a null value. 

The parser should be able to parse this xml rule. 

<?xml version="1.0"?>
<rule name="Check_NotNullof_rfqId">
  <rule-attribute name="agenda-group" value="Check"/>
  <lhs>
    <pattern object-type="RFQBean">
      <or-constraint-connective>
        <field-constraint field-name="m_rfqId">
          <literal-restriction evaluator="==" value="null"/>
        </field-constraint>
        <field-constraint field-name="m_rfqId">
          <literal-restriction evaluator="==" value=""/>
        </field-constraint>
      </or-constraint-connective>
    </pattern>
  </lhs>
  <rhs> response.setStatus("For RFQ Bean: The value of m_rfqId is null.");

System.out.println(response.getStatus());

</rhs>
</rule>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:59:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Thu, 4 Oct 2007 07:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1248)
 <literal-restriction>
 requires an 'value' attribute, but it can't be null
In-Reply-To: <83704.1191498783244.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29542350.1191499143239.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1248?page=all ]

Fernando Meyer resolved JBRULES-1248.
-------------------------------------

    Resolution: Done

> <literal-restriction> requires an 'value' attribute, but it can't be null 
> --------------------------------------------------------------------------
>
>                 Key: JBRULES-1248
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1248
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.0.MR2,  4.0.0.MR3,  4.0.0.GA, 4.0.1
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> <literal-restriction> requires an 'value' attribute, but the parser fails when we use a null value. 
> The parser should be able to parse this xml rule. 
> <?xml version="1.0"?>
> <rule name="Check_NotNullof_rfqId">
>   <rule-attribute name="agenda-group" value="Check"/>
>   <lhs>
>     <pattern object-type="RFQBean">
>       <or-constraint-connective>
>         <field-constraint field-name="m_rfqId">
>           <literal-restriction evaluator="==" value="null"/>
>         </field-constraint>
>         <field-constraint field-name="m_rfqId">
>           <literal-restriction evaluator="==" value=""/>
>         </field-constraint>
>       </or-constraint-connective>
>     </pattern>
>   </lhs>
>   <rhs> response.setStatus("For RFQ Bean: The value of m_rfqId is null.");
> System.out.println(response.getStatus());
> </rhs>
> </rule>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 08:49:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 4 Oct 2007 08:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <9575392.1191502143281.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380443 ] 
            
David Lloyd commented on JBREM-305:
-----------------------------------

For the user, of course they should be able to use the JAX-WS API - but Remoting does not provide this API.  My question is, what does Remoting add here?  It sounds like you want Remoting to act not so much as a remote invocation layer, but rather more as a generic transport facade.  Is this accurate?

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:03:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 09:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-473) Add 1.5.6 artifacts
 to the JBoss Maven respository
Message-ID: <10357650.1191502983487.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add 1.5.6 artifacts to the JBoss Maven respository
--------------------------------------------------

                 Key: JBAOP-473
                 URL: http://jira.jboss.com/jira/browse/JBAOP-473
             Project: JBoss AOP
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 1.5.6.GA
         Environment: n/a
            Reporter: Anders Hammar
         Attachments: jboss-aop-1.5.6.GA.pom, jboss-aop-jdk50-1.5.6.GA.pom

Please add the jdk1.4 and jdk5.0 artifacts of jboss-aop 1.5.6.GA to the maven repository. I've attached the pom files for both artifacts.

To be consistent with the deployed 1.5.0.GA artifact, I've keept the "jboss.jboss-aop" groupId and I also kept the "jboss-aop" artifactId for the jdk1.4 artifact. The jdk5.0 artifact uses the "jboss-aop-jdk50" artifactId to be consistent with the jar file in the distribution zip. (While this is not artifact naming standard used in 2.0.0.beta1.)


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:03:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 09:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-473) Add 1.5.6 artifacts
 to the JBoss Maven respository
In-Reply-To: <10357650.1191502983487.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25859987.1191502983599.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-473?page=all ]

Anders Hammar updated JBAOP-473:
--------------------------------

    Attachment: jboss-aop-1.5.6.GA.pom
                jboss-aop-jdk50-1.5.6.GA.pom

> Add 1.5.6 artifacts to the JBoss Maven respository
> --------------------------------------------------
>
>                 Key: JBAOP-473
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-473
>             Project: JBoss AOP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.6.GA
>         Environment: n/a
>            Reporter: Anders Hammar
>         Attachments: jboss-aop-1.5.6.GA.pom, jboss-aop-jdk50-1.5.6.GA.pom
>
>
> Please add the jdk1.4 and jdk5.0 artifacts of jboss-aop 1.5.6.GA to the maven repository. I've attached the pom files for both artifacts.
> To be consistent with the deployed 1.5.0.GA artifact, I've keept the "jboss.jboss-aop" groupId and I also kept the "jboss-aop" artifactId for the jdk1.4 artifact. The jdk5.0 artifact uses the "jboss-aop-jdk50" artifactId to be consistent with the jar file in the distribution zip. (While this is not artifact naming standard used in 2.0.0.beta1.)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:12:03 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Thu, 4 Oct 2007 09:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23149661.1191503523377.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Markus Wolf updated JBRULES-1247:
---------------------------------


The above exception was caused by 'agenda-group = "action"'.
Maybe the error message could be a bit more specific.

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:12:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 09:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <17342448.1191503523566.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380454 ] 
            
Thomas Diesler commented on JBREM-305:
--------------------------------------

Whatever you want to call it, I'd like to use a jms like connection URI

jms://foo

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:44:04 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Thu, 4 Oct 2007 09:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-600) Investigate
 Multiplexer locking scopes
In-Reply-To: <8898592.1190881737185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20861180.1191505444329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-600?page=all ]

Vladimir Blagojevic resolved JGRP-600.
--------------------------------------

    Resolution: Done

Resolved by simplifying both JChannelFactory and Multiplexer. Commit set:
JChannelFactory.java 1.48
Multiplexer.java 1.75

> Investigate Multiplexer locking scopes
> --------------------------------------
>
>                 Key: JGRP-600
>                 URL: http://jira.jboss.com/jira/browse/JGRP-600
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> It seems that we are holding locks more that we need to in Multiplexer building block. Review all synchronization blocks and make changes if appropriate.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 10:50:06 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 4 Oct 2007 10:50:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-587) Lightweight FLUSH for
 state transfer
In-Reply-To: <33510599.1188575598551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13720765.1191509406217.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-587?page=all ]

Bela Ban updated JGRP-587:
--------------------------

    Description: 
We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected. 

For Multiplexer, JOIN's will still need to block everyone, because we're actually creating the underlying JChannel.

For state transfer on the Multiplexer, the example should be:
- Members {A,B,C}. A and B have services X and Y, C has only service Y
- Service B.X requests a state transfer (MuxChannel.getState())
- The FLUSH needs to be qualified with the service-id: FLUSH(X)
- A, B and C receive a START-FLUSH(X) message, which invokes A.X.block(), B.X.block().
- For C, since there is no X service, Multiplexer.block() simply returns
- When A has received all FLUSH-OK messages from A, B and C, we transfer the state from A.X to B.X
- Then we terminate the FLUSH by sending a STOP-FLUSH(x) to {A,B,C}
- This again calls A.X.unblock(), B.X.unblock() and is a no-op for C

This allows other services, e.g. Y, to be unaffected (ie., non-blocked) by the flushing of A.X

  was:We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected. 


> Lightweight FLUSH for state transfer
> ------------------------------------
>
>                 Key: JGRP-587
>                 URL: http://jira.jboss.com/jira/browse/JGRP-587
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.7
>
>
> We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected. 
> For Multiplexer, JOIN's will still need to block everyone, because we're actually creating the underlying JChannel.
> For state transfer on the Multiplexer, the example should be:
> - Members {A,B,C}. A and B have services X and Y, C has only service Y
> - Service B.X requests a state transfer (MuxChannel.getState())
> - The FLUSH needs to be qualified with the service-id: FLUSH(X)
> - A, B and C receive a START-FLUSH(X) message, which invokes A.X.block(), B.X.block().
> - For C, since there is no X service, Multiplexer.block() simply returns
> - When A has received all FLUSH-OK messages from A, B and C, we transfer the state from A.X to B.X
> - Then we terminate the FLUSH by sending a STOP-FLUSH(x) to {A,B,C}
> - This again calls A.X.unblock(), B.X.unblock() and is a no-op for C
> This allows other services, e.g. Y, to be unaffected (ie., non-blocked) by the flushing of A.X

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 11:21:03 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Thu, 4 Oct 2007 11:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (HIBERNATE-20) JDK Compatiblity
 Issue with Hibernate Tools project
Message-ID: <751956.1191511263679.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/HIBERNATE-20?page=all ]

Max Andersen closed HIBERNATE-20.
---------------------------------

    Resolution: Out of Date

> JDK Compatiblity Issue with Hibernate Tools project
> ---------------------------------------------------
>
>                 Key: HIBERNATE-20
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-20
>             Project: Hibernate
>          Issue Type: Bug
>         Environment: JDK1.4
>            Reporter: hari prasad
>         Assigned To: Gavin King
>
> In the latest release of Hibernate Tools, the DAO code generated is compatible ONLY to JDK1.5. Please provide a drop that generates 1.4 compatible code also.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 11:43:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 4 Oct 2007 11:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1193) Tests should not
 call Transaction.commit/rollback()
In-Reply-To: <5880125.1191386163241.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32052175.1191512583244.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1193?page=all ]

Jason T. Greene resolved JBCACHE-1193.
--------------------------------------

    Resolution: Done

> Tests should not call Transaction.commit/rollback()
> ---------------------------------------------------
>
>                 Key: JBCACHE-1193
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1193
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Jason T. Greene
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA
>
>
> The JTA spec says that the thread association of a transaction can only be controlled by TransactionManager. The reason is that a Transaction can be bound to multple threads. In order to be compliant, and work with JBoss JTA, we need to ensure that all operations go through TransactionManager

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:01:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 4 Oct 2007 12:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1056) Redo
 NestedBeanUnitTestCase.testConsistentPassivatedState()
Message-ID: <6265694.1191513663349.JavaMail.jira@cloud.prod.atl2.jboss.com>

Redo NestedBeanUnitTestCase.testConsistentPassivatedState()
-----------------------------------------------------------

                 Key: EJBTHREE-1056
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1056
             Project: EJB 3.0
          Issue Type: Sub-task
          Components: Clustering
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor


NestedBeanUnitTestCase.testConsistentPassivatedState() is a pretty weak test for the EJBTHREE-1053 condition; when the parent issue is fixed, replace this test with something better.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:18:03 2007
From: jira-events at lists.jboss.org (kavipriya gnanasambandam (JIRA))
Date: Thu, 4 Oct 2007 12:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
Message-ID: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>

Transaction Manager issue in JBOss Application Server 4.2.1
-----------------------------------------------------------

                 Key: JBAS-4803
                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Transaction Manager
    Affects Versions: JBossAS-4.2.1.GA
         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
            Reporter: kavipriya gnanasambandam
         Assigned To: Adrian Brock
            Priority: Critical


I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.

Please find the below log
org.springframework.transaction.NoTransactionException: No active JTA transaction
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:24:18 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 12:24:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1493674.1191515058700.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=comments#action_12380514 ] 
            
William DeCoste commented on EJBTHREE-899:
------------------------------------------

It's broken, but I am working on this. 

> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:28:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 4 Oct 2007 12:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7480051.1191515283648.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4803?page=all ]

Adrian Brock closed JBAS-4803.
------------------------------

    Resolution: Incomplete Description

This is not a bug report.

> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:37:03 2007
From: jira-events at lists.jboss.org (kavipriya gnanasambandam (JIRA))
Date: Thu, 4 Oct 2007 12:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21839773.1191515823459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4803?page=all ]

kavipriya gnanasambandam reopened JBAS-4803:
--------------------------------------------

             
Yes, jboss 4.2.1 causes org.springframework.transaction.NoTransactionException. 

The integration between Spring and JBOSS does not work properly anymore after upgrading jboss from 4.0.4 to 4.2.1.

In spring I'm using the JTA transaction manager as follows: 

Code: 
<bean id="txManager"
class="org.springframework.transaction.jta.JtaTransactionManager">
        <property name="transactionManagerName" value="java:/TransactionManager"/>
        <property name="userTransactionName" value="UserTransaction"/>
</bean>
 
I have a problem with a org.springframework.transaction.NoTransactionExcep tion when throwing an exception inside a bean that is wrapped with a TransactionProxyFactoryBean.
I'm using JBoss with Arjuna transaction manager When you use the org.springframework.transaction.jta.JtaTransaction Manager (which I'm using), then the Spring declarative transaction management should be integrated perfectly with JTA.This means that Spring does not roll back the transaction, but just marks it for rollback and then the Hibernate should not do anything about it because it is an application exception what I'm throwing from the spring bean (not a Runtime exception). Finally the JTA should rollback the transaction.
This was working on jboss 4.0.4, but is not working anymore on JBoss 4.2.1.


> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:06:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 4 Oct 2007 13:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19251010.1191517563293.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4803?page=all ]

Adrian Brock closed JBAS-4803.
------------------------------

    Resolution: Incomplete Description

If you re-open this again without using the forums thread I'll delete this issue.

> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:44:03 2007
From: jira-events at lists.jboss.org (kavipriya gnanasambandam (JIRA))
Date: Thu, 4 Oct 2007 13:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4803) Transaction
 Manager issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5540969.1191519843308.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4803?page=comments#action_12380535 ] 
            
kavipriya gnanasambandam commented on JBAS-4803:
------------------------------------------------

Delete this issue

> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:46:03 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Thu, 4 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29504924.1191519963575.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=comments#action_12380536 ] 
            
Andrew Oliver commented on JBPORTAL-1713:
-----------------------------------------

common...an up or down vote baby and hopefully application :-)

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:49:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 13:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-786) String remove()
	method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6136737.1191520143838.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Carlo de Wolf updated EJBTHREE-786:
-----------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                   AS 4.2.2.GA
                       (was: Branch_4_2)
                       (was: HEAD)

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:51:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 13:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32995919.1191520263867.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Carlo de Wolf updated EJBTHREE-785:
-----------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                   AS 4.2.2.GA
                       (was: Branch_4_2)
                       (was: HEAD)

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:57:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 4 Oct 2007 13:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29020950.1191520623322.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=comments#action_12380538 ] 
            
Thomas Heute commented on JBPORTAL-1713:
----------------------------------------

We'll apply it, or move to maven before don't worry...

Did you sign the contributor agreement ;)

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 16:45:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 16:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9792897.1191530703460.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=comments#action_12380576 ] 
            
William DeCoste commented on EJBTHREE-899:
------------------------------------------

Several problems here:

1) ServiceRefMetaData does not expose injection-target, so we don't know if and where to inject the service. Injectors are not being created for service-refs with injection-targets that come from xml
2) ServiceRefMetaData does not expose merge capability to combine metadata from ejb-jar.xml and jboss.xml



> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 17:35:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 17:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25556244.1191533703440.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

William DeCoste resolved JBAS-4801.
-----------------------------------

    Resolution: Done

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 17:37:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 17:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14815556.1191533823883.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4801?page=comments#action_12380584 ] 
            
William DeCoste commented on JBAS-4801:
---------------------------------------

I've confirmed the latest fix resolves the EJB3 IIOP test issue and resovled the JIRA. Thanks.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 18:07:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 18:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31725585.1191535623526.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

William DeCoste updated JBAS-4801:
----------------------------------

    Comment: was deleted

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 18:54:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 4 Oct 2007 18:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32296905.1191538445438.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=comments#action_12380591 ] 
            
Mark Proctor commented on JBRULES-1247:
---------------------------------------

there doesn't need to be an =

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 18:54:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 4 Oct 2007 18:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28878941.1191538445609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Mark Proctor updated JBRULES-1247:
----------------------------------

    Fix Version/s: 4.0.2

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 20:02:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 4 Oct 2007 20:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-786) String remove()
 method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <407673.1191542523880.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=comments#action_12380596 ] 
            
Andrew Rubinger commented on EJBTHREE-786:
------------------------------------------

Passing in Branch 4.2, awaiting merge back to trunk before resolution.

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 21:05:03 2007
From: jira-events at lists.jboss.org (Len DiMaggio (JIRA))
Date: Thu, 4 Oct 2007 21:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
Message-ID: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>

com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
-----------------------------------------------------------------------------------------------------

                 Key: JBPM-1065
                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Web Interface
         Environment: soa-standalone.zip (oct 1 2007) 

RHEL5 

java 
version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)

            Reporter: Len DiMaggio
         Assigned To: Tom Baeyens
            Priority: Minor


These errors are reported when the jBPM console is accessed - the console seems to run however.

10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 21:37:03 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Thu, 4 Oct 2007 21:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11880220.1191548223320.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=comments#action_12380601 ] 
            
Andrew Oliver commented on JBPORTAL-1713:
-----------------------------------------

Yes.  And it is work for hire for your customer done on your dime anyhow.

You're moving to maven...now I'm worried.  I've never understood masochism.

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 01:03:09 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Fri, 5 Oct 2007 01:03:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1220) Integration with
 jBPM does not work
In-Reply-To: <6567124.1190714261119.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17142817.1191560589662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1220?page=all ]

Jiri Pechanec reopened JBRULES-1220:
------------------------------------

             

> Integration with jBPM does not work
> -----------------------------------
>
>                 Key: JBRULES-1220
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1220
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
> 		workingMemory.setGlobalResolver(new GlobalResolver() {
> 			private static final long serialVersionUID = 1L;
> 			public Object resolveGlobal(String identifier) {
> 				System.out.println("!!!!!!!!!! resolve " + identifier);
> 				return ci.getVariable(identifier);
> 			}
> 			public void setGlobal(String identifier, Object value) {
> 				System.out.println("!!!!!!!!!! set " + identifier);
> 				ci.setVariable(identifier, value);
> 			}
> 		});
> And a rule file that serves as test
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> The output of the test is as expected
> 11:50:51,226 INFO  [STDOUT] !!!!!!!!!! resolve shipper
> 11:50:51,227 INFO  [STDOUT] None
> 11:50:51,227 INFO  [STDOUT] !!!!!!!!!! set shipper
> 11:50:51,227 INFO  [STDOUT] ship via FEDX 
> But if we modify the rule file to
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		eval ("None".equals(shipper))
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> then nothing is printed - no attempt to resolve shipper global variable

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 02:13:15 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Fri, 5 Oct 2007 02:13:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-474) Synchronize jar file
 names in distribution zip and maven repo
Message-ID: <109522.1191564795812.JavaMail.jira@cloud.prod.atl2.jboss.com>

Synchronize jar file names in distribution zip and maven repo
-------------------------------------------------------------

                 Key: JBAOP-474
                 URL: http://jira.jboss.com/jira/browse/JBAOP-474
             Project: JBoss AOP
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
         Environment: n/a
            Reporter: Anders Hammar


To avoid confusion, the jar file names in the distribution zip and the artifacts in the maven repository should be the same.
In the distribution file, the aop jar file for jdk1.4 is called "jboss-aop.jar" and the one for jdk5.0 is called "jboss-aop-jdk50.jar". However, in the maven repo the artifact "jboss-aop" refers to the jdk5.0 jar (and there is no jdk1.4 artifact).


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 02:18:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Fri, 5 Oct 2007 02:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-474) Synchronize jar
 file names in distribution zip and maven repo
In-Reply-To: <109522.1191564795812.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30500966.1191565083246.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-474?page=comments#action_12380630 ] 
            
Anders Hammar commented on JBAOP-474:
-------------------------------------

My suggestion is to use the "jboss-aop.jar" for the jdk5.0 version and name the jdk1.4 version "jboss-aop-jdk14.jar". This means changing the naming convention (for the aop jars) in the distribution zip. However, is seems as that would be consistent with the naming convention for jboss-common-core and jboss-container.


> Synchronize jar file names in distribution zip and maven repo
> -------------------------------------------------------------
>
>                 Key: JBAOP-474
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-474
>             Project: JBoss AOP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>         Environment: n/a
>            Reporter: Anders Hammar
>
> To avoid confusion, the jar file names in the distribution zip and the artifacts in the maven repository should be the same.
> In the distribution file, the aop jar file for jdk1.4 is called "jboss-aop.jar" and the one for jdk5.0 is called "jboss-aop-jdk50.jar". However, in the maven repo the artifact "jboss-aop" refers to the jdk5.0 jar (and there is no jdk1.4 artifact).

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:39:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 03:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
Message-ID: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>

SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
---------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1057
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf
             Fix For: AS 4.2.2.GA


SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
(Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:42:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 5 Oct 2007 03:42:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-604) ENCRYPT: issues with
	keystore
Message-ID: <17961930.1191570135647.JavaMail.jira@cloud.prod.atl2.jboss.com>

ENCRYPT: issues with keystore
-----------------------------

                 Key: JGRP-604
                 URL: http://jira.jboss.com/jira/browse/JGRP-604
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.7
         Attachments: tmp2.xml

If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception:

09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message
javax.crypto.BadPaddingException: Given final block not properly padded
	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
	at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
	at javax.crypto.Cipher.doFinal(DashoA12275)
	at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837)
	at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830)
	at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673)
	at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533)
	at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573)
	at org.jgroups.protocols.UNICAST.up(UNICAST.java:247)
	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704)
	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
	at org.jgroups.protocols.FD.up(FD.java:322)
	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:309)
	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:613)


To reproduce:
- Create a configuration with the following entries present:
  <ENCRYPT key_store_name="defaultStore.keystore"  store_password="changeit" alias="myKey"/>	
  <FRAG2 frag_size="60000"/>
- Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2).

Note that this error does not occur with
<ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/>



-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:42:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 5 Oct 2007 03:42:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-604) ENCRYPT: issues with
	keystore
In-Reply-To: <17961930.1191570135647.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4033930.1191570135773.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-604?page=all ]

Bela Ban updated JGRP-604:
--------------------------

    Attachment: tmp2.xml

Use this config with RpcDispatcher.testLargeReturnValue() to reproduce the issue.

> ENCRYPT: issues with keystore
> -----------------------------
>
>                 Key: JGRP-604
>                 URL: http://jira.jboss.com/jira/browse/JGRP-604
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7
>
>         Attachments: tmp2.xml
>
>
> If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception:
> 09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message
> javax.crypto.BadPaddingException: Given final block not properly padded
> 	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
> 	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
> 	at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
> 	at javax.crypto.Cipher.doFinal(DashoA12275)
> 	at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837)
> 	at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830)
> 	at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673)
> 	at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533)
> 	at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:247)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:309)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:613)
> To reproduce:
> - Create a configuration with the following entries present:
>   <ENCRYPT key_store_name="defaultStore.keystore"  store_password="changeit" alias="myKey"/>	
>   <FRAG2 frag_size="60000"/>
> - Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2).
> Note that this error does not occur with
> <ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/>

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:59:13 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 5 Oct 2007 03:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-786) String remove()
 method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1539693.1191571153379.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Andrew Rubinger resolved EJBTHREE-786.
--------------------------------------

    Resolution: Done

Fixes resolved/merged in both Branch 4.2 and trunk.

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:04:14 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:04:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12955514.1191571454362.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=comments#action_12380642 ] 
            
Carlo de Wolf commented on EJBTHREE-1057:
-----------------------------------------

EJB 3 4.3.3: The getEJBObject method returns the session bean's remote interface. Only session beans with a remote EJBObject interface can call this method.

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:23:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 5 Oct 2007 04:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
Message-ID: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
-------------------------------------------------------------------------------

                 Key: EJBTHREE-1058
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 5.0.0.Beta3, HEAD
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: AS 5.0.0.Beta3, HEAD


Assuming:

public interface StatefulRemote extends EJBObject{...}

...and:

@Stateful
@Remote(StatefulRemote.class)
@RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
public class StatefulRemoteBean

..when invoking:

Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
EJBObject ejbObject = (EJBObject) obj;
ejbObject.remove();

...the following exception is encountered:

Could not resolve beanClass method from proxy call
java.lang.RuntimeException: Could not resolve beanClass method from proxy call
	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
	at org.jboss.remoting.Client.invoke(Client.java:1634)
	at org.jboss.remoting.Client.invoke(Client.java:548)
	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1009) Add
 configurale defaults
 on ServerPeer for FullSize, PageSize, and DownCacheSize
In-Reply-To: <19490210.1183659547941.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28850207.1191573005291.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1009?page=all ]

Tim Fox updated JBMESSAGING-1009:
---------------------------------

    Fix Version/s: Unscheduled

> Add configurale defaults on ServerPeer for FullSize, PageSize, and DownCacheSize
> --------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1009
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1009
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.3.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I see all the other defaults on the ServerPeer, but there seems to be no way to set the defaults for all the queues for the paging.  I would ask that we add the following as properties on the serverpeer
> DefaultFullSize
> DefaultPageSize
> and Default DownCacheSize
> These constants should probably be taken out of org.jboss.jms.server.destination.ManagedDestination and put into the server peer as defaults.  It would be ok to put these defaults in the Serverpeer as default values, but they need to be able to be overridden by default configuration settings.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-784) Add
 Active/Passive
 deployment feature for JBoss Messaging in 2 node cluster (Need HA part and
 not Clustering part)
In-Reply-To: <7151892.1169843757653.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2003899.1191573005456.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-784?page=all ]

Tim Fox updated JBMESSAGING-784:
--------------------------------

    Fix Version/s: Unscheduled

> Add Active/Passive deployment feature for JBoss Messaging in 2 node cluster (Need HA part and not Clustering part)
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-784
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-784
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: JMS Clustering
>    Affects Versions: 1.4.0 CR3
>            Reporter: Rohit Chowdhary
>             Fix For: Unscheduled
>
>
> Need to be able to deploy JBoss Messaging nodes in a HA configuration, but not load-balanced. 
> Such that only one node is actively serving all the requests, if the current active node goes down, then the passive node picks up the load.
> Reason would be: To use the available h/w resources at best. 
> We have one dedicated physical server for running JBoss msg. Another physical server that hosts existing JBoss instance running some application. We want to use this second server running a passive JBossMsg instance. So in case when the dedicated JBossMsg goes down, then the second shared server can take the load temporarily automatically, till we bring back the dedicated up again. 
> Other reason would be that we bring down the dedicated JBossMsg server for OS level patching, essentially minimizing the app downtime and increase availablity.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1500988.1191573006029.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox updated JBMESSAGING-1047:
---------------------------------

    Fix Version/s: Unscheduled

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:08 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1081) Allow
 configuration of
 distribution policy for queues with multiple consumers
In-Reply-To: <16868356.1190815661831.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31569399.1191573008885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1081?page=all ]

Tim Fox updated JBMESSAGING-1081:
---------------------------------

    Fix Version/s: Unscheduled

> Allow configuration of distribution policy for queues with multiple consumers
> -----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1081
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1081
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The distribution policy for queues is currently hardwired to RoundRobinDistributor (in MessagingQueue.java) like this:
>    	localDistributor = new DistributorWrapper(new RoundRobinDistributor());   	
>    	remoteDistributor = new DistributorWrapper(new RoundRobinDistributor());   	
>    	distributor = new ClusterRoundRobinDistributor(localDistributor, remoteDistributor); 
> This is a good default for when multiple clients are consuming a queue for purposes of load balancing. However, when there are multiple consumers for purposes of fail-over it can be desirable to use the FirstReceiverDistributor policy instead so that a second consumer only gets messages when the first consumer fails. (I am aware that this is simplifying matters a bit, FirstReceiverDistributor makes no such guarantees.)
> This policy can currently only be changed by patching the source code and recompiling. It would be great if it would be possible to configure the distribution policy in a configuration file instead, ideally on a per-queue basis in destinations-service.xml.
> This would ideally allow specifying arbitrary class names so that it's possible to install custom distributors.
> All of this would obviously be useful for topics as well once JBMESSAGING-377 is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:09 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-979) Servlet
 transport for JBoss Messaging
In-Reply-To: <3826403.1180702448685.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28365174.1191573009551.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-979?page=all ]

Tim Fox updated JBMESSAGING-979:
--------------------------------

    Fix Version/s: Unscheduled

> Servlet transport for JBoss Messaging
> -------------------------------------
>
>                 Key: JBMESSAGING-979
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-979
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.SP1
>         Environment: Windows 2003 with IIS as front-end web server.
>            Reporter: Daniel Weeks
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> Although there is an https transport for JBoss Messaging, it does not support going over the same port that Tomcat is using like the JBoss MQ jbossmq-httpil.sar does.  This capability is required for environments in which port 443 is the only port that is open for communication.  Although url proxying/forwarding could be used under Apache to work around this issue, there is not a good solution for doing this with IIS (or for applications that don't use a front-end web server and are limited to port 443).  Many enterprise PKI solutions (such as DoD) favor the use of IIS over Apache due to cost of COTS products, so this is a show stopper for JBoss Messaging in those environments.
> This issue is preventing us from migrating an enterprise application that runs in the DoD environment to to JBoss Messaging.  The application makes heavy use of JMS and would benefit greatly from the improved performance that JBoss Messaging provides.
> This feature request is originating from a JBoss Customer Support Portal case at the following URL: 
> https://network.jboss.com/jbossnetwork/restricted/caseDetail.html?caseId=500300000034tnzAAA&viewType=comments

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:09 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1057)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
In-Reply-To: <17912445.1187942898273.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2377547.1191573009719.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1057?page=all ]

Tim Fox updated JBMESSAGING-1057:
---------------------------------

    Fix Version/s: Unscheduled

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
> -------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1057
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1057
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.SP1
>         Environment: boss-4.0.5.GA, java 1.4.2_07 , jboss messaging 1.2.0.SP1
>            Reporter: gerald zhou
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(Unknown Source)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>         at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
>         at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:245)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:958)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.access$000(LeasePinger.java:20)
>         at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:315)
>         at java.util.TimerThread.mainLoop(Timer.java:432)
>         at java.util.TimerThread.run(Timer.java:382)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:10 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1064) MessageID
 changes when the
 message is transfered over the cluster with JBM 1.3.0GA
In-Reply-To: <15594223.1188809418325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16615010.1191573010157.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1064?page=all ]

Tim Fox updated JBMESSAGING-1064:
---------------------------------

    Fix Version/s: Unscheduled

> MessageID changes when the message is transfered over the cluster with JBM 1.3.0GA
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1064
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1064
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.3.0.GA
>            Reporter: Daniel Bevenius
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> I'm seeing the same bug that was reported by JIRA:http://jira.jboss.com/jira/browse/JBMESSAGING-1063 with JBM 1.3.0GA.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:10 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-634) If Server is
 restarted, client leases IDs might be out of sync
In-Reply-To: <9440951.1162870121664.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9766847.1191573010291.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-634?page=all ]

Tim Fox updated JBMESSAGING-634:
--------------------------------

    Fix Version/s: Unscheduled

> If Server is restarted, client leases IDs might be out of sync
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-634
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>             Fix For: Unscheduled
>
>
> This is the scenario I have:
> I start the server...
> I have clients opening/closing connections in a loop...
> I kill the server...
> (will ignore the errors on client until I get restarted)
> I restart the server....
> I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs)
> Kill the client...
> after some time.. .the server gets into an unexpected state, after we have seen this exception:
> 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.access$300(Lease.java:39)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)
> I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-923) Creating
 queue/topic with
 JNDI subcontexts fails, e.g. names such as queue/foo/bar
In-Reply-To: <16664219.1173999154492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2990110.1191573011370.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-923?page=all ]

Tim Fox updated JBMESSAGING-923:
--------------------------------

    Fix Version/s: Unscheduled

> Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-923
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-923
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Elias Ross
>             Fix For: Unscheduled
>
>
> The following service.xml will generate an exception:
> <server>
>    <loader-repository>
>         jboss.messaging:loader=ScopedLoaderRepository
>         <loader-repository-config>
>                 java2ParentDelegation=false
>         </loader-repository-config>
>    </loader-repository>
>    <mbean code="org.jboss.jms.server.destination.QueueService"
>         name="jboss.messaging.destination:service=Queue,name=ppm/mt"
>         xmbean-dd="xmdesc/Queue-xmbean.xml">
>         <depends optional-attribute-name="ServerPeer">jboss.messaging:service=Se
> rverPeer</depends>
>       <depends>jboss.messaging:service=PostOffice</depends>
>    </mbean>
> </server>
> 15:46:12,205 ERROR [ExceptionUtil] Queue[/queue/ppm/bridge/mqube, name=ppm/bridg
> e/mqube] startService
> javax.naming.NameNotFoundException: ppm not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:165)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:168)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477)
>         at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(Destin
> ationJNDIMapper.java:146)
>         at org.jboss.jms.server.destination.QueueService.startService(QueueServi
> ce.java:142)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1013) Manual merge
 queue feature via JMX
In-Reply-To: <4003720.1184269443903.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30444658.1191573011817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1013?page=all ]

Tim Fox updated JBMESSAGING-1013:
---------------------------------

    Fix Version/s: Unscheduled

> Manual merge queue feature via JMX
> ----------------------------------
>
>                 Key: JBMESSAGING-1013
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1013
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management, JMS Clustering
>         Environment: Clustering/load balancing 
>            Reporter: Evgueni Smoliar
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> In a case of disaster recovery you are obliged always to recover last running cluster node. Otherwise some messages will remain in the queue waiting for this node to startup. Idd there is a workaround for this, but it's not always easy to do. Would me much nicer to have a manual function to merge queues ( or reallocate messages) preferably available via JMX.
> For more detail please check forum.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
In-Reply-To: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22660450.1191573011953.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1090?page=all ]

Tim Fox updated JBMESSAGING-1090:
---------------------------------

    Fix Version/s: Unscheduled

> Add appropriate Exception handling when hitting MaxSize
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1090
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Jay Howell
>             Fix For: Unscheduled
>
>
> When using MaxSize for a queue and topic the following behaviors exist
> Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.
> Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.
> What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.
> I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  
> We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  
> Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1076) Missing
 annotation parameter in example "web-service"
In-Reply-To: <11829604.1190281769508.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12702723.1191573012159.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1076?page=all ]

Tim Fox updated JBMESSAGING-1076:
---------------------------------

    Fix Version/s: Unscheduled

> Missing annotation parameter in example "web-service"
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-1076
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1076
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.CR2
>         Environment: jbossws-native-2.0.0.GA
>            Reporter: Pavel Kadlec
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>         Attachments: WebServiceExampleImpl-patch.java
>
>
> WebService annotation does not have determined parameter "serviceName" in example "web-service". The container (jbossws-native-2.0.0.GA) assigns serviceName, by default "WebServiceExampleImplService".  Client asks for service "JMSSampleService".   
> The full annotation should look like
> @WebService(serviceName="JMSSampleService", name="JMSSample")

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-977)
 JMSRemotingConnection.setFailed() has a redundant call to
 org.jboss.remoting.Client.disconnect()
In-Reply-To: <30695488.1180595168474.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2810946.1191573012367.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-977?page=all ]

Tim Fox updated JBMESSAGING-977:
--------------------------------

    Fix Version/s: Unscheduled

> JMSRemotingConnection.setFailed() has a redundant call to org.jboss.remoting.Client.disconnect()
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-977
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-977
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The call client.disconnect() occurs twice, and the first one should be removed.  The result of the first call is that the subsequent call to client.removeListener(callbackManager) fails:
> 2007-05-25 11:52:12,956 415134 DEBUG [org.jboss.jms.client.remoting.JMSRemotingConnection] (Thread-353:) JMSRemotingConnection[bisocket://10.5.2.224:4457/?NumberOfCallRetries=10&clientMaxPoolSize=100&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=5&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat] failed to cleanly remove callback manager from the client
> java.lang.Exception: Can not remove callback listener as remoting client is not connected to server.
> at org.jboss.remoting.Client.removeListener(Client.java:1090)
> at org.jboss.jms.client.remoting.JMSRemotingConnection.setFailed(JMSRemotingConnection.java:340)
> at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:100)
> at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:57)
> at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83)
> at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:346) 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-998) Implement
 security for temporary destinations
In-Reply-To: <6697586.1182343252095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3781590.1191573012554.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-998?page=all ]

Tim Fox updated JBMESSAGING-998:
--------------------------------

    Fix Version/s: Unscheduled

> Implement security for temporary destinations
> ---------------------------------------------
>
>                 Key: JBMESSAGING-998
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-998
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Security
>            Reporter: Sergey Koshcheyev
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> There should probably be some attribute on the ConnectionFactory to set permissions required to use temporary destinations. See the forum thread for discussion.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-662) Implement
 XAResource.forget()
In-Reply-To: <4832867.1164977697064.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10305047.1191573012691.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-662?page=all ]

Tim Fox updated JBMESSAGING-662:
--------------------------------

    Fix Version/s: Unscheduled

> Implement XAResource.forget()
> -----------------------------
>
>                 Key: JBMESSAGING-662
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-662
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Juha Lindfors
>             Fix For: Unscheduled
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> This is currently a no-op.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-965) JBoss
 Messaging client fails to reconnect after restart of the server
In-Reply-To: <29935925.1179359942450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18277096.1191573013038.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-965?page=all ]

Tim Fox updated JBMESSAGING-965:
--------------------------------

    Fix Version/s: Unscheduled

> JBoss Messaging client fails to reconnect after restart of the server
> ---------------------------------------------------------------------
>
>                 Key: JBMESSAGING-965
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-965
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.SP1
>         Environment: java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, 
> java.runtime.version=1.5.0_10-b03, 
> java.vm.version=1.5.0_10-b03, 
> java.vm.vendor=Sun Microsystems Inc., 
> java.vm.name=Java HotSpot(TM) Client VM, 
> java.vm.specification.name=Java Virtual Machine Specification, 
> java.vm.specification.vendor=Sun Microsystems Inc., 
> java.specification.name=Java Platform API Specification, 
> java.specification.version=1.5, 
> java.vendor=Sun Microsystems Inc., 
> os.name=Windows 2000, 
> os.version=5.0, 
> os.arch=x86, 
> sun.os.patch.level=Service Pack 4, 
> JBossAS version: 4.0.5
>            Reporter: pgervais
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> There seem to be a clean up problem with the client JBoss Messaging QueueConnection.
> When following these steps, everything works fine:
> Sequence A:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. close the connection
> 7. shutdown the JBoss server
> 8. restart the JBoss server
> 9. execute step 1-6
> Everything works fine
> But following these steps:
> Sequence B:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. shutdown the JBoss server
> 7. close the connection (I get an exception, it should be normal)
> 8. restart the JBoss server
> 9. execute step 1, I get an exception, this should not be normal
> Exception received in step 7 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:200)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$closing$aop(ClientConnectionDelegate.java:158)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java)
> 	at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:82)
> 	at TestJmsClient.main(TestJmsClient.java:32)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://142.117.14.44:4457/?NumberOfCallRetries=2&clientMaxPoolSize=50&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=1&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.remoting.Client.invoke(Client.java:518)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
> 	... 17 more
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:346)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:796)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:521)
> 	... 23 more
> Exception received in step 9 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:179)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
> 	at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
> 	at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
> 	at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:54)
> 	at TestJmsClient.main(TestJmsClient.java:36)
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at java.net.Socket.connect(Socket.java:469)
> 	at java.net.Socket.<init>(Socket.java:366)
> 	at java.net.Socket.<init>(Socket.java:179)
> 	at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:217)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:328)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.addCallbackListener(Client.java:1613)
> 	at org.jboss.remoting.Client.addListener(Client.java:907)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:221)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:287)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146)
> 	... 13 more
> After investigating, I think that the problem happens when the close is executed in the second case. It seems that an exception is thrown before all the clean up has been done, because I see a thread named WorkerThread#1[142.117.14.44:3421] (which is my machine address and what seems to be the port on which the thread is listening). That thread was not present in the first case, it disappeared after executing close on the QueueConnection.  
> After further investigation, it seems that the problem is due to a clean up problem with the org.jboss.remoting.InvokerRegistry. The client invoker and server invoker from the previously created connection are not unregistered when the close method fails.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-927)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid
 for deserialization
In-Reply-To: <17070968.1174574674654.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21057489.1191573013221.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-927?page=all ]

Tim Fox updated JBMESSAGING-927:
--------------------------------

    Fix Version/s: Unscheduled

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-927
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-927
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.GA
>         Environment: jboss 4.2.0CR1, java 1.5, jboss messaging 1.2.0ga
>            Reporter: David
>             Fix For: Unscheduled
>
>         Attachments: dave-jms.tar.bz2
>
>
> 09:58:12,495 ERROR [ServerThread] failed
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> 	at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
> 	at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1205)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:72)
> 	at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:307)
> 	at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:641)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id 5c4o1w13-o9260j-ezjuc4ur-1-ezjuc5w1-4, but no collection of clients have been set.
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id null, but no collection of clients have been set.
> That exception can be caused when using the jboss-messaging-client.jar that ships with the jboss-messaging release.   The jboss-messaging-client.jar contains a version of EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment that implements Serializable.  However, the jboss app server contains a "concurrent.jar" that has a version of ConcurrentHashMap$Segment  that does not implement Serializable.  Replacing the version of lib/concurrent.jar with a version of concurrent.jar that contains a ConcurrentHashMap$Segment that implements Serializable will solve this issue.
> This situation occurs when you have a remote client that sends a message to a Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-814) MBean class is
 incorrect at performance framework
In-Reply-To: <26839623.1170789019738.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11410243.1191573014115.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-814?page=all ]

Tim Fox updated JBMESSAGING-814:
--------------------------------

    Fix Version/s: Unscheduled

> MBean class is incorrect at performance framework
> -------------------------------------------------
>
>                 Key: JBMESSAGING-814
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-814
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Tests and Performance
>    Affects Versions: 1.2.0.Beta2
>            Reporter: Vinicius Carvalho
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I have downloaded the performance tests from svn trunk today. Trying to get it running I was getting the following error from my jboss instance: No ClassLoaders found for: org.jboss.jms.server.destination.Queue. When checking the artifacts/message-destinations-service.xml I've noticied that instead of org.jboss.jms.server.destination.QueueService for my mbean classes it contains: org.jboss.jms.server.destination.Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1073) JMS messages
 are not taken from the queue after database connection recovery
In-Reply-To: <22436968.1190115251065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5604923.1191573013993.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1073?page=all ]

Tim Fox updated JBMESSAGING-1073:
---------------------------------

    Fix Version/s: Unscheduled

> JMS messages are not taken from the queue after database connection recovery
> ----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1073
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1073
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.3.0.GA
>         Environment: JBoss.4.2.1 JBossMessaging 1.3GA Oracle 10g database jdk 1.5 on solaris intel
>            Reporter: Evgueni Smoliar
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> We have  2 jboss server running in the cluster. Messaging is also configured with clustered queues. 
> At one moment we had a database crash. Database was recovered in 5 minutes and connections from jboss were reestablished . All applications works OK, new messages processed correctly. The problem is with the messages processed during the crash time. JMS could not commit them and couldn't rollback at the time. After reestablishing of the connection this messages are not redelivered anymore. 
> The only way to get those message delivered is to restart jboss servers. 
> This is strange problem which we never experienced with old jboss-jms implementation.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1003) Update queue
 and topic smoke tests to work with new message redistribution
In-Reply-To: <20452317.1183071484090.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2254193.1191573014285.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1003?page=all ]

Tim Fox updated JBMESSAGING-1003:
---------------------------------

    Fix Version/s: Unscheduled

> Update queue and topic smoke tests to work with new message redistribution
> --------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1003
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1003
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1018) Possibly fix
 timeout due
 to bug in remoting that may allow clients to hang forever.
In-Reply-To: <23514132.1185206447289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8211520.1191573014503.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1018?page=all ]

Tim Fox updated JBMESSAGING-1018:
---------------------------------

    Fix Version/s: Unscheduled

> Possibly fix timeout due to bug in remoting that may allow clients to hang forever.
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1018
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1018
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Remoting
>    Affects Versions: 1.3.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> This goes back to JBMESSAGING-171, when we changed the timeout on the bisocket to 0.  That would have meant that it would wait forever which is what we want.  There is now a bug in remoting that if this is set to 0 and the client is unreachable, then it is possible that it will hang.  We may have one case of this now, but it is still unverified.  The remoting bug is JBREM-767.  This is fixed in the 2.4 beta of remoting, but it may present a problem before we can integrate that version in.  We may want to consider changing this to a high number, so it doesn't timeout easily, but so it will timeout.    Just want to put it up for concideration.  The other route is to get the remoting team to put out another sp version with.  They could put it in  2.2.0.SP4_CP02, but that will only go out as part of the Platform 4.2 CR release, so we may want to ask them to put it out as an 2.2.0SP5, so it will go into general population where Messaging has alot of customers.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:34:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
In-Reply-To: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19097472.1191573243521.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1058?page=all ]

Carlo de Wolf updated EJBTHREE-1058:
------------------------------------

        Fix Version/s:     (was: HEAD)
    Affects Version/s:     (was: AS 5.0.0.Beta3)
                           (was: HEAD)

> Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
> -------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1058
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Assuming:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean
> ..when invoking:
> Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
> EJBObject ejbObject = (EJBObject) obj;
> ejbObject.remove();
> ...the following exception is encountered:
> Could not resolve beanClass method from proxy call
> java.lang.RuntimeException: Could not resolve beanClass method from proxy call
> 	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1634)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
> 	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:34:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-923) Creating
 queue/topic with
 JNDI subcontexts fails, e.g. names such as queue/foo/bar
In-Reply-To: <16664219.1173999154492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2509463.1191573243960.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-923?page=all ]

Tim Fox closed JBMESSAGING-923.
-------------------------------

    Resolution: Rejected

> Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-923
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-923
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Elias Ross
>             Fix For: Unscheduled
>
>
> The following service.xml will generate an exception:
> <server>
>    <loader-repository>
>         jboss.messaging:loader=ScopedLoaderRepository
>         <loader-repository-config>
>                 java2ParentDelegation=false
>         </loader-repository-config>
>    </loader-repository>
>    <mbean code="org.jboss.jms.server.destination.QueueService"
>         name="jboss.messaging.destination:service=Queue,name=ppm/mt"
>         xmbean-dd="xmdesc/Queue-xmbean.xml">
>         <depends optional-attribute-name="ServerPeer">jboss.messaging:service=Se
> rverPeer</depends>
>       <depends>jboss.messaging:service=PostOffice</depends>
>    </mbean>
> </server>
> 15:46:12,205 ERROR [ExceptionUtil] Queue[/queue/ppm/bridge/mqube, name=ppm/bridg
> e/mqube] startService
> javax.naming.NameNotFoundException: ppm not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:165)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:168)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477)
>         at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(Destin
> ationJNDIMapper.java:146)
>         at org.jboss.jms.server.destination.QueueService.startService(QueueServi
> ce.java:142)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:34:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:34:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-634) If Server is
 restarted, client leases IDs might be out of sync
In-Reply-To: <9440951.1162870121664.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15817026.1191573244215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-634?page=all ]

Tim Fox closed JBMESSAGING-634.
-------------------------------

    Resolution: Out of Date

> If Server is restarted, client leases IDs might be out of sync
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-634
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>             Fix For: Unscheduled
>
>
> This is the scenario I have:
> I start the server...
> I have clients opening/closing connections in a loop...
> I kill the server...
> (will ignore the errors on client until I get restarted)
> I restart the server....
> I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs)
> Kill the client...
> after some time.. .the server gets into an unexpected state, after we have seen this exception:
> 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.access$300(Lease.java:39)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)
> I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:36:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-965) JBoss Messaging
 client fails to reconnect after restart of the server
In-Reply-To: <29935925.1179359942450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8224859.1191573363542.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-965?page=all ]

Tim Fox closed JBMESSAGING-965.
-------------------------------

    Resolution: Out of Date

> JBoss Messaging client fails to reconnect after restart of the server
> ---------------------------------------------------------------------
>
>                 Key: JBMESSAGING-965
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-965
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.SP1
>         Environment: java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, 
> java.runtime.version=1.5.0_10-b03, 
> java.vm.version=1.5.0_10-b03, 
> java.vm.vendor=Sun Microsystems Inc., 
> java.vm.name=Java HotSpot(TM) Client VM, 
> java.vm.specification.name=Java Virtual Machine Specification, 
> java.vm.specification.vendor=Sun Microsystems Inc., 
> java.specification.name=Java Platform API Specification, 
> java.specification.version=1.5, 
> java.vendor=Sun Microsystems Inc., 
> os.name=Windows 2000, 
> os.version=5.0, 
> os.arch=x86, 
> sun.os.patch.level=Service Pack 4, 
> JBossAS version: 4.0.5
>            Reporter: pgervais
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> There seem to be a clean up problem with the client JBoss Messaging QueueConnection.
> When following these steps, everything works fine:
> Sequence A:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. close the connection
> 7. shutdown the JBoss server
> 8. restart the JBoss server
> 9. execute step 1-6
> Everything works fine
> But following these steps:
> Sequence B:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. shutdown the JBoss server
> 7. close the connection (I get an exception, it should be normal)
> 8. restart the JBoss server
> 9. execute step 1, I get an exception, this should not be normal
> Exception received in step 7 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:200)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$closing$aop(ClientConnectionDelegate.java:158)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java)
> 	at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:82)
> 	at TestJmsClient.main(TestJmsClient.java:32)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://142.117.14.44:4457/?NumberOfCallRetries=2&clientMaxPoolSize=50&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=1&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.remoting.Client.invoke(Client.java:518)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
> 	... 17 more
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:346)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:796)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:521)
> 	... 23 more
> Exception received in step 9 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:179)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
> 	at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
> 	at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
> 	at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:54)
> 	at TestJmsClient.main(TestJmsClient.java:36)
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at java.net.Socket.connect(Socket.java:469)
> 	at java.net.Socket.<init>(Socket.java:366)
> 	at java.net.Socket.<init>(Socket.java:179)
> 	at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:217)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:328)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.addCallbackListener(Client.java:1613)
> 	at org.jboss.remoting.Client.addListener(Client.java:907)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:221)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:287)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146)
> 	... 13 more
> After investigating, I think that the problem happens when the close is executed in the second case. It seems that an exception is thrown before all the clean up has been done, because I see a thread named WorkerThread#1[142.117.14.44:3421] (which is my machine address and what seems to be the port on which the thread is listening). That thread was not present in the first case, it disappeared after executing close on the QueueConnection.  
> After further investigation, it seems that the problem is due to a clean up problem with the org.jboss.remoting.InvokerRegistry. The client invoker and server invoker from the previously created connection are not unregistered when the close method fails.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:36:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1064) MessageID
 changes when the
 message is transfered over the cluster with JBM 1.3.0GA
In-Reply-To: <15594223.1188809418325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24892458.1191573363886.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1064?page=all ]

Tim Fox closed JBMESSAGING-1064.
--------------------------------

    Resolution: Duplicate Issue

> MessageID changes when the message is transfered over the cluster with JBM 1.3.0GA
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1064
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1064
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.3.0.GA
>            Reporter: Daniel Bevenius
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> I'm seeing the same bug that was reported by JIRA:http://jira.jboss.com/jira/browse/JBMESSAGING-1063 with JBM 1.3.0GA.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:40:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1003) Update queue
 and topic smoke tests to work with new message redistribution
In-Reply-To: <20452317.1183071484090.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21024500.1191573603479.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1003?page=all ]

Tim Fox closed JBMESSAGING-1003.
--------------------------------

    Resolution: Out of Date

> Update queue and topic smoke tests to work with new message redistribution
> --------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1003
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1003
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:40:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1057)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
In-Reply-To: <17912445.1187942898273.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6140427.1191573604286.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1057?page=all ]

Tim Fox closed JBMESSAGING-1057.
--------------------------------

    Resolution: Duplicate Issue

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
> -------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1057
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1057
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.SP1
>         Environment: boss-4.0.5.GA, java 1.4.2_07 , jboss messaging 1.2.0.SP1
>            Reporter: gerald zhou
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(Unknown Source)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>         at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
>         at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:245)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:958)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.access$000(LeasePinger.java:20)
>         at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:315)
>         at java.util.TimerThread.mainLoop(Timer.java:432)
>         at java.util.TimerThread.run(Timer.java:382)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:40:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-927)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid
 for deserialization
In-Reply-To: <17070968.1174574674654.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32598430.1191573604460.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-927?page=all ]

Tim Fox closed JBMESSAGING-927.
-------------------------------

    Resolution: Duplicate Issue

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-927
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-927
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.GA
>         Environment: jboss 4.2.0CR1, java 1.5, jboss messaging 1.2.0ga
>            Reporter: David
>             Fix For: Unscheduled
>
>         Attachments: dave-jms.tar.bz2
>
>
> 09:58:12,495 ERROR [ServerThread] failed
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> 	at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
> 	at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1205)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:72)
> 	at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:307)
> 	at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:641)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id 5c4o1w13-o9260j-ezjuc4ur-1-ezjuc5w1-4, but no collection of clients have been set.
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id null, but no collection of clients have been set.
> That exception can be caused when using the jboss-messaging-client.jar that ships with the jboss-messaging release.   The jboss-messaging-client.jar contains a version of EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment that implements Serializable.  However, the jboss app server contains a "concurrent.jar" that has a version of ConcurrentHashMap$Segment  that does not implement Serializable.  Replacing the version of lib/concurrent.jar with a version of concurrent.jar that contains a ConcurrentHashMap$Segment that implements Serializable will solve this issue.
> This situation occurs when you have a remote client that sends a message to a Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:42:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-977)
 JMSRemotingConnection.setFailed() has a redundant call to
 org.jboss.remoting.Client.disconnect()
In-Reply-To: <30695488.1180595168474.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5018319.1191573723688.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-977?page=all ]

Tim Fox closed JBMESSAGING-977.
-------------------------------

    Resolution: Out of Date

> JMSRemotingConnection.setFailed() has a redundant call to org.jboss.remoting.Client.disconnect()
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-977
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-977
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The call client.disconnect() occurs twice, and the first one should be removed.  The result of the first call is that the subsequent call to client.removeListener(callbackManager) fails:
> 2007-05-25 11:52:12,956 415134 DEBUG [org.jboss.jms.client.remoting.JMSRemotingConnection] (Thread-353:) JMSRemotingConnection[bisocket://10.5.2.224:4457/?NumberOfCallRetries=10&clientMaxPoolSize=100&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=5&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat] failed to cleanly remove callback manager from the client
> java.lang.Exception: Can not remove callback listener as remoting client is not connected to server.
> at org.jboss.remoting.Client.removeListener(Client.java:1090)
> at org.jboss.jms.client.remoting.JMSRemotingConnection.setFailed(JMSRemotingConnection.java:340)
> at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:100)
> at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:57)
> at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83)
> at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:346) 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:44:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-814) MBean class is
 incorrect at performance framework
In-Reply-To: <26839623.1170789019738.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31951646.1191573843463.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-814?page=all ]

Tim Fox closed JBMESSAGING-814.
-------------------------------

    Resolution: Out of Date

> MBean class is incorrect at performance framework
> -------------------------------------------------
>
>                 Key: JBMESSAGING-814
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-814
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Tests and Performance
>    Affects Versions: 1.2.0.Beta2
>            Reporter: Vinicius Carvalho
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I have downloaded the performance tests from svn trunk today. Trying to get it running I was getting the following error from my jboss instance: No ClassLoaders found for: org.jboss.jms.server.destination.Queue. When checking the artifacts/message-destinations-service.xml I've noticied that instead of org.jboss.jms.server.destination.QueueService for my mbean classes it contains: org.jboss.jms.server.destination.Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-815) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
In-Reply-To: <995728.1166795738121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1731344.1191574563890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-815?page=all ]

Carlo de Wolf resolved EJBTHREE-815.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-815
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-815
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> Testcase: testQuerySingleResultExceptions took 0.058 sec
>         Caused an ERROR
> javax.persistence.NoResultException: No entity found for query
> javax.ejb.EJBException: javax.persistence.NoResultException: No entity found for query
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: javax.persistence.NoResultException: No entity found for query
>         at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:82)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySingleResultExceptions(ExceptionTestBean.java:269)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySingleResultExceptions(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySingleResultExceptions(EntityExceptionTestCa
> se.java:96)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-816) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
In-Reply-To: <23148785.1166796163032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12841527.1191574564050.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-816?page=all ]

Carlo de Wolf resolved EJBTHREE-816.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-816
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-816
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> Testcase: testQuerySetHintAndParameter took 0.035 sec
>         Caused an ERROR
> java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
> javax.ejb.EJBException: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterDescriptor(ParameterMetadata.java:55)
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterExpectedType(ParameterMetadata.java:61)
>         at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:397)
>         at org.hibernate.impl.AbstractQueryImpl.setParameter(AbstractQueryImpl.java:369)
>         at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:234)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySetHintAndParameter(ExceptionTestBean.java:311)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySetHintAndParameter(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySetHintAndParameter(EntityExceptionTestCase.
> java:103)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-817) test failure -
 org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
In-Reply-To: <25680060.1166796342815.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12143958.1191574564205.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-817?page=all ]

Carlo de Wolf resolved EJBTHREE-817.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-817
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-817
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> Testcase: testRuntimeException took 2.058 sec
>         FAILED
> expected:<1> but was:<0>
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
>         at org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase.testRuntimeException(MDBUnitTestCase.java:292)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-818) test failure -
 org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
In-Reply-To: <1942068.1166797118725.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11543412.1191574564369.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-818?page=all ]

Carlo de Wolf resolved EJBTHREE-818.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-818
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-818
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> Testcase: testRollback took 5.05 sec
>         FAILED
> null
> junit.framework.AssertionFailedError
>         at org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase.testRollback(MDBUnitTestCase.java:128)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-819) test failure -
 org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
In-Reply-To: <4167073.1166798501804.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11617612.1191574564551.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-819?page=all ]

Carlo de Wolf resolved EJBTHREE-819.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-819
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-819
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> Testcase: testSSLBindings took 35.731 sec
>         Caused an ERROR
> Could not dereference object
> javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.remoting.CannotConnectException: Can not 
> get connection to server.  Problem establishing socket connection.]
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase.testSSLBindings(SSLUnitTestCase.java:68)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server.  Problem establishing socket connection.
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:267)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:48)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
>         at $Proxy1.createProxy(Unknown Source)
>         at org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:52)
>         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
>         at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
>         ... 25 more
> Caused by: java.lang.reflect.InvocationTargetException
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createClientSocket(SocketClientInvoker.java:518)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.getConnection(SocketClientInvoker.java:485)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:263)
>         ... 38 more
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:742)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:678)
>         at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
>         at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2213)
>         at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
>         at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)
>         at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:761)
>         at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
>         at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
>         at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:83)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
>         ... 45 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>         at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-838) test failure -
 org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
In-Reply-To: <8353072.1169064476539.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30373431.1191574564707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-838?page=all ]

Carlo de Wolf resolved EJBTHREE-838.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> -------------------------------------------------------------------
>
>                 Key: EJBTHREE-838
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-838
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: [java.version: 1.5.0_08]
> [java.vendor: BEA Systems, Inc.]
> [java.vm.version: R27.1.0-109-73164-1.5.0_08-20061129-1418-linux-ia32]
> [java.vm.name: BEA JRockit(R)]
> [java.vm.info: compiled mode]
> [os.name: Linux]
> [os.arch: i386]
> [os.version: 2.6.9-42.0.3.ELsmp]
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> Test:        testStackTrace
> Type:        failure
> Exception:   junit.framework.AssertionFailedError
> junit.framework.AssertionFailedError
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testStackTrace(RemoteUnitTestCase.java:250)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-865) test failure -
 org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with
 Sun 1.5.0_11
In-Reply-To: <12695397.1170729619498.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17705177.1191574564966.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-865?page=all ]

Carlo de Wolf resolved EJBTHREE-865.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with Sun 1.5.0_11 
> -------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-865
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-865
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: Boss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.webservices.unit.WsUnitTestCase
> Test:        testDeployment
> Type:        error
> Exception:   org.jboss.deployment.DeploymentException
> Message:     Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ej
> b3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.tes
> t.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> org.jboss.deployment.DeploymentException: Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> 	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:991)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:471)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.processWebMethod(JSR181MetaDataBuilder.java:568)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:193)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75)
> 	at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy30.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	... 53 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: org.jboss.ws.jaxrpc.ParameterWrapping$WrapperType
> 	at javassist.CtClassType.getClassFile2(CtClassType.java:204)
> 	at javassist.CtClassType.getConstructorsCache(CtClassType.java:892)
> 	at javassist.CtClassType.getDeclaredConstructors(CtClassType.java:878)
> 	at javassist.CtNewClass.inheritAllConstructors(CtNewClass.java:87)
> 	at javassist.CtNewClass.toBytecode(CtNewClass.java:63)
> 	at javassist.CtClass.toBytecode(CtClass.java:1181)
> 	at javassist.ClassPool.toClass(ClassPool.java:883)
> 	at javassist.ClassPool.toClass(ClassPool.java:846)
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:467)
> 	... 67 more

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-866) test failure -
 org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) -
 with Sun 1.5.0_11
In-Reply-To: <31270078.1170729763045.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30759789.1191574565172.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-866?page=all ]

Carlo de Wolf resolved EJBTHREE-866.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure -  org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) - with Sun 1.5.0_11 
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-866
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-866
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase
> Test:        testEJBServlet
> Type:        error
> Exception:   java.io.IOException
> Message:     Expected reply code:200, actual=500
> Expected reply code:200, actual=500
> java.io.IOException: Expected reply code:200, actual=500
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:140)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:109)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:97)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:83)
> 	at org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase.testEJBServlet(EarServletUnitTestCase.java:49)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:02:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:02:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-880) Non persistent
 messages can be sent one way
In-Reply-To: <13732117.1172086955491.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27702553.1191574924213.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-880?page=all ]

Tim Fox closed JBMESSAGING-880.
-------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: 2.0.0 Beta 1)
       Resolution: Done

Added temporary solution for this until we get MINA in

> Non persistent messages can be sent one way
> -------------------------------------------
>
>                 Key: JBMESSAGING-880
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-880
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> When sending non persistent messages from client to server. They can be sent oneway, i.e. no need to wait for a response that the message has been receive on the server.
> This should massively increase performance since we will not be hostage to networks with large RTT.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:21:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:21:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-754) Allow for
 multiple service containers to be started in same VM
In-Reply-To: <972857.1169053192768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24509222.1191576075022.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-754?page=all ]

Tim Fox updated JBMESSAGING-754:
--------------------------------

    Summary: Allow for multiple service containers to be started in same VM  (was: Allow for multiple service containes to be started in same VM)

> Allow for multiple service containers to be started in same VM
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-754
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-754
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> ServerManagement currently allows multiple remote ServiceContainers to be started and stopped, but it does not allow multiple ServiceContainers to be started and stopped in the same VM.
> This means tests like the bridge tests can only be run in remote 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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:31:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-662) Implement
 XAResource.forget()
In-Reply-To: <4832867.1164977697064.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1057780.1191576663329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-662?page=all ]

Tim Fox updated JBMESSAGING-662:
--------------------------------

    Fix Version/s: 2.0.0 Beta 1
                       (was: Unscheduled)

> Implement XAResource.forget()
> -----------------------------
>
>                 Key: JBMESSAGING-662
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-662
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Juha Lindfors
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> This is currently a no-op.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:33:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21732641.1191576783696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox closed JBMESSAGING-1047.
--------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)
       Resolution: Done

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:35:03 2007
From: jira-events at lists.jboss.org (Dirk Gfroerer (JIRA))
Date: Fri, 5 Oct 2007 05:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4484)
 org.jboss.security.auth.callback.MapCallback not serializable
In-Reply-To: <10497493.1181723591903.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19205401.1191576903793.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4484?page=all ]

Dirk Gfroerer updated JBAS-4484:
--------------------------------

    Affects Version/s: JBossAS-4.2.1.GA

> org.jboss.security.auth.callback.MapCallback not serializable
> -------------------------------------------------------------
>
>                 Key: JBAS-4484
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4484
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.1.GA
>         Environment: Linux ghlx06 2.4.21-50.EL #1 SMP Tue May 8 17:10:00 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> RHEL 3 x86_64
>            Reporter: Dirk Gfroerer
>         Assigned To: Scott M Stark
>
> I'm securing access to my EJBs via a security domain. Everything was working fine until I had to add a second login module to my application-policy in login-config.xml. I now do have to login-modules both of them are flagged as being sufficient. However if now a user tries to login and uses an invalid account / password I get the following exception:
> Exception in thread "main" java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: 
> 	java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback
> 	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217)
> 	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
> 	at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
> 	at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
> 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
> 	at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
> 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
> 	at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
> 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
> 	at $Proxy0.create(Unknown Source)
> 	at de.guhsoft.eDHR.OrderManager.testclient.GetUserInformation.doAction(GetUserInformation.java:71)
> 	at de.guhsoft.eDHR.OrderManager.testclient.GetUserInformation.main(GetUserInformation.java:92)
> Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
> 	... 12 more
> Caused by: java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
> 	at java.lang.Throwable.writeObject(Throwable.java:648)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:343)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:159)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> 	at java.lang.Thread.run(Thread.java:619)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:45:03 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Fri, 5 Oct 2007 05:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21142466.1191577503299.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: buddy-sync-20s.tgz

Attaching test run logs of failed test with sync buddy replication. Buddy communication timeout set to 20s.

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: buddy-sync-20s.tgz, driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:49:06 2007
From: jira-events at lists.jboss.org (thilker (JIRA))
Date: Fri, 5 Oct 2007 05:49:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23020311.1191577746350.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12380663 ] 
            
thilker commented on GPD-169:
-----------------------------

I have the same problem here.
I had nodes with simular names in my workflow, like "CalculateAmount1", "CalculateAmount2", ..
So I thought the fact that the first letters are the same is the problem.
I renamed the nodes to "N001CalculateAmount",  "N002CalculateAmount", ...
Since I did this the problem disappeared.

But in your example the node-names are completely different.
Strange.

Regards,

Thorsten

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:06:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4689) Upgrade JBoss
 messaging to 1.4.0.GA
In-Reply-To: <16306175.1189160291086.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10100436.1191578763348.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4689?page=all ]

Dimitris Andreadis closed JBAS-4689.
------------------------------------

    Resolution: Done

I suppose we can close this. There are still a lot of failures in the AS testsuite related to jboss messaging:

http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/lastBuild/testReport/

> Upgrade JBoss messaging to 1.4.0.GA
> -----------------------------------
>
>                 Key: JBAS-4689
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4689
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Dimitris Andreadis
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> We are currently at 1.4.0.CR2

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:06:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4716) Update common-core
	to 2.2.2.GA
In-Reply-To: <9279917.1189681040331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31193525.1191578763510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4716?page=all ]

Dimitris Andreadis reassigned JBAS-4716:
----------------------------------------

    Assignee: Dimitris Andreadis

> Update common-core to 2.2.2.GA
> ------------------------------
>
>                 Key: JBAS-4716
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4716
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Common-core has fixes we need. Since further fixes are possible maybe move to a 2.2.2-snapshot release first.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:19:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22686925.1191579543319.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4688?page=all ]

Dimitris Andreadis reopened JBAS-4688:
--------------------------------------

             
Re-using this task to track upgrade to S 4.3.beta2 (from beta1).

Jonathan, when the release is available, please let me know, thanks.

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:23:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9581424.1191579783309.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12380669 ] 
            
Jonathan Halliday commented on JBAS-4688:
-----------------------------------------

oops, sorry. JBossTS release has been out since Tuesday. I still need to put a fix into the transactions-spi and release that too though.

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13013799.1191580263320.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12380671 ] 
            
Dimitris Andreadis commented on JBAS-4688:
------------------------------------------

Where does the transaction-spi live ?

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:33:24 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 06:33:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23401514.1191580404105.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12380672 ] 
            
Jonathan Halliday commented on JBAS-4688:
-----------------------------------------

It's part of https://svn.jboss.org/repos/jbossas/projects/integration/trunk

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:45:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4660) Fix
 jboss-head-testsuite-sun-1.5
 regression when the testsuite runs under hudson
In-Reply-To: <9933141.1188908538489.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7543478.1191581103647.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4660?page=all ]

Dimitris Andreadis updated JBAS-4660:
-------------------------------------

    Priority: Major  (was: Critical)

> Fix jboss-head-testsuite-sun-1.5 regression when the testsuite runs under hudson
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4660
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4660
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Rajesh Rajasekaran wrote:
> > >> Dimitris,
> > >>
> > >> This looks like a bug in the web layer, when the server is bound to an
> > >> ip (onn hudson). Please take a look at all the web related tests.
> > >> http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/lastSuccessfulBuild/artifact/trunk/testsuite/output/reports/html/index.html
> > >>
> > >>
> > >> whereas on CC the testsuite is run on localhost and these errors dont
> > >> show up.
> > >> http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-sun-1.5/20070829063207/results/index.html
> > >>
> > >>
> > >> If you think the same, i will make this run on hudson public, with 871
> > >> failures as regressions.
> > >> All other runs, jboss-3.x, 4.0.x, 4.2.x are stable on  hudson and
> > >> ready to be public.
> > >> All CC runs will be shutdown then.
> > >> And then you can have as many runs as you want  :) 
> > >>
> > >> Thanks
> > >> rajesh
> > >>
> > >> Dimitris Andreadis wrote:
> >> >>> I'm not sure why, but Hudson seems to produce different error counts:
> >> >>>
> >> >>> 871 failures
> >> >>> http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/lastSuccessfulBuild/testReport/
> >> >>>
> >> >>>
> >> >>> vs CC 334 failures
> >> >>> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5?log=log20070829063207

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:47:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2149)
	ByValueContainerInvoker
Message-ID: <7994404.1191581223392.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2149?page=all ]

Dimitris Andreadis updated JBAS-2149:
-------------------------------------

    Comment: was deleted

> ByValueContainerInvoker
> -----------------------
>
>                 Key: JBAS-2149
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2149
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Remove the use of ByValueInvokerInterceptor from the testsuite.
> This was deprecated in JBoss4 and removed in JBoss5, it should be using the MarshalledInvokerInterceptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:49:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:49:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-2145) Testsuite JBossMQ
 destination deployment is broken
Message-ID: <2821403.1191581355890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2145?page=all ]

Dimitris Andreadis closed JBAS-2145.
------------------------------------

    Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
       Resolution: Out of Date

I suppose this is not current anymore?

> Testsuite JBossMQ destination deployment is broken
> --------------------------------------------------
>
>                 Key: JBAS-2145
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2145
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Adrian Brock
>         Assigned To: Sacha Labourey
>
> The change to only deploy destinations as part of the testsuite run
> is broken. e.g.
> 2005-08-19 15:03:28,885 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/scratch/cruisecontrol/checkout/jboss-head-testsuite/testsuite/outp
> ut/resources/messaging/test-destinations-full-service.xml
> org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:name=A,service=Queue
>         at org.jboss.system.ServiceCreator.install(ServiceCreator.java:72)
>         at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:429)
>         at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:151)
>         at org.jboss.system.ServiceController.install(ServiceController.java:216)
>         at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
> Sacha, why did you change this?
> This needs fixing properly anyway such that the tests run against both JBossMQ and JBoss Messaging.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:51:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3151) Convert HA-JNDI
 stubs to Remoting
Message-ID: <18969963.1191581463549.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3151?page=all ]

Dimitris Andreadis reassigned JBAS-3151:
----------------------------------------

    Assignee: Ron Sigal  (was: Tom  Elrod)

Assign to Ron. It could also be rescheduled.

> Convert HA-JNDI stubs to Remoting
> ---------------------------------
>
>                 Key: JBAS-3151
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3151
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Naming, Remoting
>            Reporter: Brian Stansberry
>         Assigned To: Ron Sigal
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code.  We should convert this to use Remoting.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:51:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4644) fix
 org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC) - 5 errors
In-Reply-To: <9681728.1188322458268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13616430.1191581463778.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4644?page=comments#action_12380677 ] 
            
Dimitris Andreadis commented on JBAS-4644:
------------------------------------------

The fix for this needs to be brought in from Branch_4_2.

> fix org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC) - 5 errors
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4644
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4644
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Problem appears either as:
> testRoleSecuredServiceAccess Error Call invocation failed; nested exception is: java.io.IOException: Could not transmit message
> java.rmi.RemoteException: Call invocation failed; nested exception is: 
> 	java.io.IOException: Could not transmit message
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536)
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
> 	at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151)
> 	at $Proxy4.getContactInfo(Unknown Source)
> 	at org.jboss.test.webservice.jbws309.JBWS309TestCase.testRoleSecuredServiceAccess(JBWS309TestCase.java:190)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> Caused by: java.io.IOException: Could not transmit message
> 	at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:204)
> 	at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
> 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337)
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
> 	... 25 more
> Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:332)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183)
> 	... 28 more
> Caused by: org.jboss.ws.WSException: Invalid HTTP server response [401] - Unauthorized
> 	at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:77)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304)
> 	... 33 more
> Or
> testRoleSecuredSLSB Error SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> java.rmi.AccessException: SecurityException; nested exception is: 
> 	javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> 	at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
> 	at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136)
> 	at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
> 	at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640)
> 	at org.jboss.ejb.Container.invoke(Container.java:1006)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:230)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
> 	at $Proxy14.invoke(Unknown Source)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> Caused by: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> 	at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:212)
> 	at org.jboss.security.auth.spi.UsersRolesLoginModule.login(UsersRolesLoginModule.java:152)
> 	at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
> 	at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
> 	at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
> 	at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
> 	at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:524)
> 	at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:458)
> 	at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:353)
> 	at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:317)
> 	at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:185)
> 	at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invokeHome(PreSecurityInterceptor.java:140)
> 	at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
> 	at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
> 	at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640)
> 	at org.jboss.ejb.Container.invoke(Container.java:1006)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:230)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
> 	at $Proxy14.invoke(Unknown Source)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:161)
> 	at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:244)
> 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:181)
> 	at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
> 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:86)
> 	at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
> 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
> 	at $Proxy1.create(Unknown Source)
> 	at org.jboss.test.webservice.jbws309.JBWS309TestCase.testRoleSecuredSLSB(JBWS309TestCase.java:93)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
>  

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:55:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:55:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-59) JCA work for
	JBoss-5.0.0Beta
Message-ID: <24998505.1191581707886.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-59?page=comments#action_12380678 ] 
            
Dimitris Andreadis commented on JBAS-59:
----------------------------------------

What other work relates to this task? The only subtask is scheduled for CR1.

> JCA work for JBoss-5.0.0Beta
> ----------------------------
>
>                 Key: JBAS-59
>                 URL: http://jira.jboss.com/jira/browse/JBAS-59
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>            Reporter: Adrian Brock
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Schedule 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:58:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4720) Ensure
 security-domain is picked up by JCA Deployer
In-Reply-To: <25591894.1189710491347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <782831.1191581883274.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4720?page=all ]

Dimitris Andreadis updated JBAS-4720:
-------------------------------------

    Priority: Critical  (was: Major)

This should be critical as it affects a great deal of the testsuite, right?

> Ensure security-domain is picked up by JCA Deployer
> ---------------------------------------------------
>
>                 Key: JBAS-4720
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4720
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Anil Saldhana
>         Assigned To: Weston Price
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Ensure that the security-domain settings are read into the metadata to be used by ConnectionManager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:06:07 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Fri, 5 Oct 2007 07:06:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1249) Allow repository
 location to be specified in BRMS web client
Message-ID: <26599863.1191582367386.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow repository location to be specified in BRMS web client
------------------------------------------------------------

                 Key: JBRULES-1249
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1249
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


At present, any custom location of the repository is set in a components.xml file inside the WEB-INF directory of the BRMS war file. It would be better if the user could specify the location using the BRMS web client itself, rather than have to unzip, modify and zip up the WAR file. Perhaps this functionality could be added to the Admin section of the BRMS.

One advantage of this is that users could also then work with multiple repositories (e.g. for different projects). In effect there would be an option to create a new repository (specified by a directory given by the user), open an existing repository and close a repository.


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:10:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 07:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30599167.1191582603387.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4770?page=comments#action_12380681 ] 
            
Jonathan Halliday commented on JBAS-4770:
-----------------------------------------

per 

The current TransactionLocal.get() implementation in the app server actually tries to write the value in certain cases. If it's called after transaction resolution, that storeValue now throws an IllegalStateException, causing get() to blow up.

I've changed the behavior so the exception is masked and the result of initialValue() is returned from the get in such cases. 

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:10:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 07:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21630492.1191582603569.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4770?page=comments#action_12380682 ] 
            
Jonathan Halliday commented on JBAS-4770:
-----------------------------------------

oops forgot the link: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119313 

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:12:03 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Fri, 5 Oct 2007 07:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1250) Allow option to
 completely remove an asset from the repository
Message-ID: <16475001.1191582723288.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow option to completely remove an asset from the repository
--------------------------------------------------------------

                 Key: JBRULES-1250
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1250
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


If you use the archive feature to remove a rule or package from the BRMS it is not really seen as gone, as if you attempt to create a new rule or package with the same name as the archived rules or package then you get an error saying that the rule or package already exists (looking at the  source code, the repository does not care if an item is archived or not, so it will always throw an error if an asset with an existing name is created).

I'm assuming this is the designed behaviour and not a bug (I've asked about this a couple of times on the user list and got no replies to the contrary).

However, it would be very useful to be able to remove a rule or package so that you can then recreate it (e.g by importing new versions from a drl file). At present, you have to laboriously rename the rules and packages you want to remove, so that when they are archived their names do not clash with the new versions of the rules and packages you want to import or recreate. Perhaps all that is involved in implementing this new remove feature is to just automatically rename the package and its rules before archiving it?


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:24:03 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Fri, 5 Oct 2007 07:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1251) Cannot remove a
 category if it was used in an archived rule
Message-ID: <29917794.1191583443584.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot remove a category if it was used in an archived rule
-----------------------------------------------------------

                 Key: JBRULES-1251
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1251
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


The BRMS manual says you can delete a category if it is not in use by any current version of a rule. However, if you archive a rule that uses a category X, say, then you cannot remove category X in the Admin section, even if no other rules in the repository use category X. You get the following error message:

"The category still has some assets linked to it. You will need to remove the links so you can delete the cateogory"

(PS not the spelling mistake cateogory in the error message)

Either the manual (Section 9.4.2.2) should be updated with a warning that you cannot remove a category used by archived rules, or is there is a bug in the remove category functionality for archived assets, as you can remove categories which are only used in old versions of a rule?


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:09:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 08:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
In-Reply-To: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5193201.1191586143296.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1058?page=all ]

Carlo de Wolf updated EJBTHREE-1058:
------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091956

> Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
> -------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1058
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Assuming:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean
> ..when invoking:
> Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
> EJBObject ejbObject = (EJBObject) obj;
> ejbObject.remove();
> ...the following exception is encountered:
> Could not resolve beanClass method from proxy call
> java.lang.RuntimeException: Could not resolve beanClass method from proxy call
> 	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1634)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
> 	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:29:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Fri, 5 Oct 2007 08:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
In-Reply-To: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13183389.1191587343334.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1065?page=comments#action_12380690 ] 
            
David Lloyd commented on JBPM-1065:
-----------------------------------

They're not errors, they are actually JDK logging messages reported by Facelets.  In the older JBossAS versions (< 4.2.0 for sure), JDK logging messages go to STDERR, and so log4j grabs them an logs them at level ERROR.  Notice how after the timestamp and the "ERROR [STDERR]" part, there's another timestamp, the log category, and the word "INFO" - this is the REAL log level of the message.

Probably the easiest fix is to provide a JDK logging configuration file that disables logging.

> com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1065
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>         Environment: soa-standalone.zip (oct 1 2007) 
> RHEL5 
> java 
> version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>            Reporter: Len DiMaggio
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> These errors are reported when the jBPM console is accessed - the console seems to run however.
> 10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
> 10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
> 10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
> 10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
> 10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
> 10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
> 10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
> 10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
> 10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
> 10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
> 10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
> 10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
> 10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
> 10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
> 10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:31:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Fri, 5 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-305) Provide support for
	JMS transport
Message-ID: <24528029.1191587463283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-305?page=all ]

David Lloyd updated JBREM-305:
------------------------------

    JBoss Forum Reference: http://jboss.com/index.html?module=bb&op=viewtopic&t=120444

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:43:03 2007
From: jira-events at lists.jboss.org (Tyronne Wickramarathne (JIRA))
Date: Fri, 5 Oct 2007 08:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1097) Cleaning JBM
 Tables During Startup
Message-ID: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cleaning JBM Tables During Startup
----------------------------------

                 Key: JBMESSAGING-1097
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: Messaging Core Persistence
    Affects Versions: 1.4.0.GA
         Environment: JBossAS-4.2.0-GA
JBossMessaging-1.4.0-GA
            Reporter: Tyronne Wickramarathne
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:49:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 5 Oct 2007 08:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4520) Remove testsuite
 dependency on old transaction manager
In-Reply-To: <10023540.1183572471230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2146330.1191588543397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4520?page=all ]

Adrian Brock closed JBAS-4520.
------------------------------

    Resolution: Done

> Remove testsuite dependency on old transaction manager
> ------------------------------------------------------
>
>                 Key: JBAS-4520
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4520
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The parts of the testsuite that depend upon the old transaction manager need removing.
> They should either be replaced with JBossTM as an in-memory transaction manager (this could be done
> by changing the TransactionManagerLocator in the jboss-integration project)
> or the tests need moving to run inside the appserver.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:28:03 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Fri, 5 Oct 2007 10:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1252) DrlDumper does
 not dump import functions
Message-ID: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>

DrlDumper does not dump import functions
----------------------------------------

                 Key: JBRULES-1252
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: Damien Delautre
         Assigned To: Mark Proctor


When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:30:14 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Fri, 5 Oct 2007 10:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2073705.1191594614994.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Damien Delautre updated JBRULES-1252:
-------------------------------------

    Attachment: DrlDumper.patch

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Mark Proctor
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:32:03 2007
From: jira-events at lists.jboss.org (Ross McDonald (JIRA))
Date: Fri, 5 Oct 2007 10:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1066) equivalent of
 pooled-actors group functionality in mailnodes
Message-ID: <17576409.1191594724032.JavaMail.jira@cloud.prod.atl2.jboss.com>

equivalent of pooled-actors group functionality in mailnodes
------------------------------------------------------------

                 Key: JBPM-1066
                 URL: http://jira.jboss.com/jira/browse/JBPM-1066
             Project: JBoss jBPM
          Issue Type: Feature Request
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2,  jBPM jPDL 3.2.1
         Environment: any
            Reporter: Ross McDonald
         Assigned To: Tom Baeyens
            Priority: Minor


It would be nice to be able to specify a group to mail to within mail nodes, to save having to put semicolon separated actors in.  This would enable the database to control who is going to be emailed, and avoid the need to keep updating processes etc

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:54:03 2007
From: jira-events at lists.jboss.org (Francisco Reverbel (JIRA))
Date: Fri, 5 Oct 2007 10:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4519) The IIOP dependency
 on the old transaction needs removing
In-Reply-To: <2125312.1183572351674.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4756265.1191596043378.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4519?page=all ]

Francisco Reverbel closed JBAS-4519.
------------------------------------

    Resolution: Done

The hardcoded references to TxServerInterceptor have been removed from the CORBA servants in svn trunk. Now all three servants (the EJB3 one included) use the InboundTransactionCurrent SPI, which has been added to the integration project. The dependencies of the server-side tx interceptors (TxServerInterceptor and TxServerClientInterceptor) on DTM classes have also been removed, so that these interceptors can be used after the removal of the transaction module.

> The IIOP dependency on the old transaction needs removing
> ---------------------------------------------------------
>
>                 Key: JBAS-4519
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4519
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Adrian Brock
>         Assigned To: Francisco Reverbel
>             Fix For: JBossAS-5.0.0.GA
>
>
> The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 11:20:04 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Fri, 5 Oct 2007 11:20:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1233) Solver should
 use slf4j, like jbrms
In-Reply-To: <4568209.1191092801253.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22705001.1191597604385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1233?page=all ]

Geoffrey De Smet resolved JBRULES-1233.
---------------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done

Speed difference is minimal, maybe even better.

> Solver should use slf4j, like jbrms
> -----------------------------------
>
>                 Key: JBRULES-1233
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1233
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Solver
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>            Priority: Optional
>             Fix For: 4.0.2
>
>
> which can use log4j behind it

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:35:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:35:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1223) Concurrent problem
	in MVEL
In-Reply-To: <29709918.1190755901447.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2291185.1191602105395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1223?page=all ]

Mark Proctor closed JBRULES-1223.
---------------------------------

    Resolution: Done

no further help on reproducing this. So I'm closing until someone can reproduce the problem.

> Concurrent problem in MVEL
> --------------------------
>
>                 Key: JBRULES-1223
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1223
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>         Environment: Jboss 4.0.5 GA
>            Reporter: Ramses Gomez
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> java.util.ConcurrentModificationException: concurrent access to HashMap attempted by Thread[WorkManager(3)-6,5,JBoss Pooled Threads]
>         at java.util.HashMap.onExit(HashMap.java:217)
>         at java.util.HashMap.transfer(HashMap.java:514)
>         at java.util.HashMap.resize(HashMap.java:500)
>         at java.util.HashMap.addEntry(HashMap.java:800)
>         at java.util.HashMap.put(HashMap.java:441)
>         at org.mvel.AbstractParser._loadLanguageFeaturesByLevel(AbstractParser.java:1360)
>         at org.mvel.AbstractParser.setLanguageLevel(AbstractParser.java:1291)
>         at org.drools.rule.builder.dialect.mvel.MVELDialect.init(MVELDialect.java:127)
>         at org.drools.compiler.DialectRegistry.initAll(DialectRegistry.java:49)
>         at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:137)
>         at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:104)
>         at com.accenture.adsj.soa.spf.brp.BusinessRuleProcessor.createPackage(BusinessRuleProcessor.java:65)
>         at com.accenture.adsj.soa.spf.brp.BusinessRuleProcessor.getStatefulSession(BusinessRuleProcessor.java:53)
>         at com.accenture.adsj.soa.spf.brp.BusinessRuleProcessor.registerBO(BusinessRuleProcessor.java:115)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:35:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1212) Rete throws
 NoClassDefFoundError when asserting facts with classess loaded by
 inaccessible classloader.
In-Reply-To: <21352351.1190454754072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20371104.1191602104587.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1212?page=all ]

Mark Proctor closed JBRULES-1212.
---------------------------------

    Resolution: Done

not heard this isn't fixed, so closing now.

> Rete throws NoClassDefFoundError when asserting facts with classess loaded by inaccessible classloader. 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1212
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1212
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Alexander Gavrilov
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>         Attachments: ReteShadowProxyTest.java
>
>
> We using drools as part of security enfocement engine in our application, based on Tapestry4 framework. Tapestry4 pages and components is abstract classes with some abstract methods, for which tapestry generates implementation at runtime. For example, if i declare page 
> public abstract SomePage extends BasePage  {
> }
> Tapestry will generate class in default package like 
> public SomePage$_0 extends BasePage  {
> }
> On page loading whe using instantiated page objects ans Drools Facts to ensure, that current user has permissions to load this page. In the previos verions we used (3.0.6) all worked fine. After update to version 4.0.1 whe got the NoClassDefFoundError  when triyng to assert Page object into working memory. 
> This is becouse tapestry creates classes for pages in private classloader, which is child of the application classloader. When Drools tries to generate shadowing proxy for generated Page class it generate code like 
> public class SomePage$_0ShadowProxy extends SomePage$_0 {
> }
> Later, when it tries to load this class with MapBackedClassLoader, it can not find definition for class SomePage$_0 and throws NoClassDefFoundError. This type of error does not handled correctly by drools. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:35:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:35:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1217) RuleFlow Editor ->
 Constraint Editor -> Imports Editor context help
In-Reply-To: <20335396.1190661521138.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2253668.1191602105671.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1217?page=all ]

Mark Proctor closed JBRULES-1217.
---------------------------------

    Resolution: Done
      Assignee: Kris Verlaenen  (was: Mark Proctor)

I believe this is done now.

> RuleFlow Editor -> Constraint Editor -> Imports Editor context help
> -------------------------------------------------------------------
>
>                 Key: JBRULES-1217
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1217
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>         Environment: drools 4.0.1, OSX 10.4.10, Eclipse 3.3
>            Reporter: ekkehard gentz
>         Assigned To: Kris Verlaenen
>             Fix For: 4.0.2
>
>
> if you're using the eclipse RuleFlow Editor
> * opening Constraint editor
> ** then opening Imports editor
> the imports editor doesn't support context assist to find imports like the normal drl editor
> if you have a complex environment, then its very helpful to get context assist for import statements
> btw: the Constraint editor works well and supports context assist

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1213) Context assist in
 .drl when different to then
In-Reply-To: <564085.1190466911146.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16247662.1191602223813.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1213?page=all ]

Mark Proctor updated JBRULES-1213:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)
         Assignee: Kris Verlaenen  (was: Mark Proctor)

yes they use two different apis to achieve the code completion, its a lot of work to maintain both to the same level, this will have to be marked as a FUTURE for now.

> Context assist in .drl when different to then
> ---------------------------------------------
>
>                 Key: JBRULES-1213
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1213
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>         Environment: Drools 4.0.1, Eclipse 3.3, OSX 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Kris Verlaenen
>             Fix For: FUTURE
>
>
> context assist in .drl editor has different behaviour in "when" section compared to "then"
> using drools examples
> StateExampleUsingSalience.drl
> when ... State.  only shows (), null
> doing the same in
> then... State. shows class, this, FINISHED, NOT_RUN
> because in many cases tests in the LHS are against constants it would be good to show them

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1173)
 java.lang.ArrayIndexOutOfBoundsException: 2 in file named
 "TupleIndexHashTable.java" in toArray() Method. I have fix and works fine.
In-Reply-To: <3665950.1189032371957.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4471900.1191602224090.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1173?page=all ]

Mark Proctor updated JBRULES-1173:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

no futher help on reproducing this problem, so marking as a FUTURE for now.

> java.lang.ArrayIndexOutOfBoundsException: 2 in file named "TupleIndexHashTable.java" in toArray() Method. I have fix and works fine.
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1173
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1173
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions:  4.0.0.MR3
>         Environment: windows XP
>            Reporter: Nageshwar Kunichetty
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> Sometimes while asserting specific facts I get the following exception in drools-core-4.0.0 :
> > java.lang.ArrayIndexOutOfBoundsException: 26
> >         at org.drools.util.TupleIndexHashTable.toArray(TupleIndexHashTable.java:178)
> >         at org.drools.reteoo.CollectNode.assertObject(CollectNode.java:212)
> >         at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:317)
> >         at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:183)
> >         at org.drools.reteoo.Rete.assertObject(Rete.java:121)
> >         at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1174) debug steps into
 "when" statement
In-Reply-To: <22684591.1189043771218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11096039.1191602224553.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1174?page=all ]

Mark Proctor closed JBRULES-1174.
---------------------------------

    Resolution: Done

will re-create if further problems found.

> debug steps into "when" statement 
> ----------------------------------
>
>                 Key: JBRULES-1174
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1174
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>            Reporter: Mark Proctor
>         Assigned To: Ahti Kitsik
>             Fix For: 4.0.2
>
>         Attachments: .log, moz-screenshot-44.jpg
>
>
> I've re-created where it stepped into the "when" part, although it seems to do it on random.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1163) Update ORG
 homepage to be more up to date with 4.0
In-Reply-To: <14396251.1188797970409.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21985987.1191602225096.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1163?page=all ]

Mark Proctor closed JBRULES-1163.
---------------------------------

    Resolution: Done

done as much as needed for now, so closing.

> Update ORG homepage to be more up to date with 4.0
> --------------------------------------------------
>
>                 Key: JBRULES-1163
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1163
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: 4.0.1
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1124) Code completion
 does not work for 'with' blocks
In-Reply-To: <28780786.1188006918343.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8508865.1191602225284.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1124?page=all ]

Mark Proctor closed JBRULES-1124.
---------------------------------

    Resolution: Done

will re-create if further problems found.

> Code completion does not work for 'with' blocks
> -----------------------------------------------
>
>                 Key: JBRULES-1124
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1124
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions:  4.0.0.GA
>            Reporter: Mark Proctor
>         Assigned To: Philippe Ombredanne
>             Fix For: 4.0.2
>
>         Attachments: withCodeCompletion.JPG
>
>
> code completion should work for 'with' blocks. We also use a macro to make 'with' work with the 'modify' keyword.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:39:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1138) MVEL code
 completion does not work for nested expressions
In-Reply-To: <8066703.1188217998377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24357163.1191602343901.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1138?page=all ]

Mark Proctor closed JBRULES-1138.
---------------------------------

    Resolution: Done

will re-create if further problems found.

> MVEL code completion does not work for nested expressions
> ---------------------------------------------------------
>
>                 Key: JBRULES-1138
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1138
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>            Reporter: Mark Proctor
>         Assigned To: Philippe Ombredanne
>             Fix For: 4.0.2
>
>         Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> code completion does not work for parameters.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:39:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:39:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1235) Multiple Criteria
 break BRMS rule editor
In-Reply-To: <24987902.1191139841173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22649526.1191602344845.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1235?page=all ]

Mark Proctor updated JBRULES-1235:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

> Multiple Criteria break BRMS rule editor
> ----------------------------------------
>
>                 Key: JBRULES-1235
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1235
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Ben Truitt
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>         Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg, screenshot3.jpeg
>
>
> In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
> Two ways to trigger:
> 1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
> 2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
> I'll attach screenshots, which should help explain.
> Sorry if this is a dupe - I looked, but didn't find anything like 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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:39:07 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:39:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11165403.1191602347331.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Mark Proctor updated JBRULES-1247:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:01:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Fri, 5 Oct 2007 13:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
In-Reply-To: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1239652.1191603663667.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1065?page=all ]

Ronald van Kuijk resolved JBPM-1065.
------------------------------------

    Resolution: Won't Fix

The last remark of David is true. But these 'errors' also appear in seam apps etc.. so personally I'd close this issue and mark it as 'won't fix' At least not in jBPM (if JBoss AS provides something for this, it's fine) 

> com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1065
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>         Environment: soa-standalone.zip (oct 1 2007) 
> RHEL5 
> java 
> version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>            Reporter: Len DiMaggio
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> These errors are reported when the jBPM console is accessed - the console seems to run however.
> 10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
> 10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
> 10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
> 10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
> 10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
> 10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
> 10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
> 10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
> 10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
> 10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
> 10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
> 10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
> 10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
> 10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
> 10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:01:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Fri, 5 Oct 2007 13:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
In-Reply-To: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4227516.1191603663817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1065?page=all ]

Ronald van Kuijk closed JBPM-1065.
----------------------------------


n/t

> com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1065
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>         Environment: soa-standalone.zip (oct 1 2007) 
> RHEL5 
> java 
> version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>            Reporter: Len DiMaggio
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> These errors are reported when the jBPM console is accessed - the console seems to run however.
> 10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
> 10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
> 10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
> 10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
> 10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
> 10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
> 10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
> 10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
> 10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
> 10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
> 10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
> 10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
> 10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
> 10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
> 10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:46:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 5 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-81) Identity Trust
 context should handle security domain also
Message-ID: <17880822.1191606363435.JavaMail.jira@cloud.prod.atl2.jboss.com>

Identity Trust context should handle security domain also
---------------------------------------------------------

                 Key: SECURITY-81
                 URL: http://jira.jboss.com/jira/browse/SECURITY-81
             Project: JBoss Security and Identity Management
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JBossSX
    Affects Versions: 2.0.1-BETA1
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-BETA2


ITC can handle a security context that belongs to a different security domain.

Hence ITC needs to know the sec domain for the Identity Trust Manager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:46:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 5 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-81) Identity Trust
 context should handle security domain also
In-Reply-To: <17880822.1191606363435.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15794214.1191606363549.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-81?page=all ]

Anil Saldhana updated SECURITY-81:
----------------------------------

    Component/s: Security SPI

> Identity Trust context should handle security domain also
> ---------------------------------------------------------
>
>                 Key: SECURITY-81
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-81
>             Project: JBoss Security and Identity Management
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.1-BETA1
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-BETA2
>
>
> ITC can handle a security context that belongs to a different security domain.
> Hence ITC needs to know the sec domain for the Identity Trust Manager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 14:39:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 14:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1220) Integration
 with jBPM does not work
In-Reply-To: <6567124.1190714261119.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9785515.1191609543323.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1220?page=comments#action_12380802 ] 
            
Mark Proctor commented on JBRULES-1220:
---------------------------------------

Have you verified the global resolver it is using is the jbpm one, and that it hasn't lost the configuration and gone back to the drools default?

> Integration with jBPM does not work
> -----------------------------------
>
>                 Key: JBRULES-1220
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1220
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
> 		workingMemory.setGlobalResolver(new GlobalResolver() {
> 			private static final long serialVersionUID = 1L;
> 			public Object resolveGlobal(String identifier) {
> 				System.out.println("!!!!!!!!!! resolve " + identifier);
> 				return ci.getVariable(identifier);
> 			}
> 			public void setGlobal(String identifier, Object value) {
> 				System.out.println("!!!!!!!!!! set " + identifier);
> 				ci.setVariable(identifier, value);
> 			}
> 		});
> And a rule file that serves as test
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> The output of the test is as expected
> 11:50:51,226 INFO  [STDOUT] !!!!!!!!!! resolve shipper
> 11:50:51,227 INFO  [STDOUT] None
> 11:50:51,227 INFO  [STDOUT] !!!!!!!!!! set shipper
> 11:50:51,227 INFO  [STDOUT] ship via FEDX 
> But if we modify the rule file to
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		eval ("None".equals(shipper))
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> then nothing is printed - no attempt to resolve shipper global variable

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 14:52:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 14:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29452760.1191610323581.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

    Fix Version/s: 4.0.2

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 14:58:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 5 Oct 2007 14:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
Message-ID: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>

GenericHeaderAuthenticator injection of ssoid, sessioncookie name
-----------------------------------------------------------------

                 Key: JBAS-4804
                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Anil Saldhana
         Assigned To: Stefan Guilhen
             Fix For: JBossAS-4.2.3.GA


http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication


Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.

Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 15:14:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 5 Oct 2007 15:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
Message-ID: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>

DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
---------------------------------------------------------------

                 Key: JBCACHE-1194
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.4.1.SP5
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
            Priority: Critical
             Fix For: 1.4.1.SP6


It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4726.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 15:14:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 5 Oct 2007 15:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
In-Reply-To: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22237429.1191611644381.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1194?page=comments#action_12380810 ] 
            
Brian Stansberry commented on JBCACHE-1194:
-------------------------------------------

JBC trunk uses GroupRequest.GET_ALL.

> DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
> ---------------------------------------------------------------
>
>                 Key: JBCACHE-1194
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6
>
>
> It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4726.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 15:14:08 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 5 Oct 2007 15:14:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
In-Reply-To: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18749215.1191611648551.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1194?page=all ]

Brian Stansberry updated JBCACHE-1194:
--------------------------------------

    Description: It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4766.  (was: It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4726.)

> DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
> ---------------------------------------------------------------
>
>                 Key: JBCACHE-1194
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6
>
>
> It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4766.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 18:20:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 18:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1220) Integration with
 jBPM does not work
In-Reply-To: <6567124.1190714261119.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29607097.1191622803278.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1220?page=all ]

Mark Proctor closed JBRULES-1220.
---------------------------------

    Resolution: Rejected

You cannot set the global resolver AFTER the facts have been inserted, it must be done before.

> Integration with jBPM does not work
> -----------------------------------
>
>                 Key: JBRULES-1220
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1220
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
> 		workingMemory.setGlobalResolver(new GlobalResolver() {
> 			private static final long serialVersionUID = 1L;
> 			public Object resolveGlobal(String identifier) {
> 				System.out.println("!!!!!!!!!! resolve " + identifier);
> 				return ci.getVariable(identifier);
> 			}
> 			public void setGlobal(String identifier, Object value) {
> 				System.out.println("!!!!!!!!!! set " + identifier);
> 				ci.setVariable(identifier, value);
> 			}
> 		});
> And a rule file that serves as test
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> The output of the test is as expected
> 11:50:51,226 INFO  [STDOUT] !!!!!!!!!! resolve shipper
> 11:50:51,227 INFO  [STDOUT] None
> 11:50:51,227 INFO  [STDOUT] !!!!!!!!!! set shipper
> 11:50:51,227 INFO  [STDOUT] ship via FEDX 
> But if we modify the rule file to
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		eval ("None".equals(shipper))
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> then nothing is printed - no attempt to resolve shipper global variable

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 19:53:06 2007
From: jira-events at lists.jboss.org (s b (JIRA))
Date: Fri, 5 Oct 2007 19:53:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1067)
 token.getAvailableTransitions()
 -- need equivalent that returns ordered list.
Message-ID: <14222518.1191628386527.JavaMail.jira@cloud.prod.atl2.jboss.com>

token.getAvailableTransitions() -- need equivalent that returns ordered list.
-----------------------------------------------------------------------------

                 Key: JBPM-1067
                 URL: http://jira.jboss.com/jira/browse/JBPM-1067
             Project: JBoss jBPM
          Issue Type: Feature Request
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
         Environment: All OS
            Reporter: s b
         Assigned To: Tom Baeyens


This feature request is requesting:

1)  API which adds a version of token.getAvailableTransitions() which returns an ordered List that preserves the order of the transitions as defined in the processdefinition.xml file for the node, rather than returning an unordered Set object. 

2)  Also request that TaskInstance.getAvailableTransitions() be modified to return an ordered list rather than a randomly ordered list by calling the new method.

For example:

------------------------
public class TaskInstance extends VariableContainer implements Assignable {

...

public List getAvailableTransitions() {
    List transitions = null;
    if ( (! isLast())
         && (token!=null)
       ) {
      transitions = token.getAvailableTransitionsList(); // using new method
    }
    return transitions;
  }

...

----------------------------------------

Problem:

node.getLeavingTransitions() appears to preserve the order, but the order is apparently lost when the transistions are added to the Set which is returned by token.getAvailableTransitions(). 

Preserving the ordering is highly useful when implementing a minimal data-driven interface which presents the user with the transitions to choose from. The designer could exercise some control over the presentation of the choices if only the order were preserved as defined in the processdefinition.xml file. 

Solution:

Make a clone of "token.getAvailableTransitions()", name it "token.getAvailableTransitionsList()", and add the filtered transitions to a List instead of to a Collection, and return the list.  Make sure the order is preserved the same as the transitions were defined in the "processdefinition.xml" file.

Modify "TaskInstance.getAvailableTransitions()" to call token.getAvailableTransitionsList().

Summary:

Although workarounds exist with existing code, it would be very helpful (and consistent I think) to provide an API that retrieves a list of the "available transitions" that is ordered as defined in the processdefinition.xml file instead of an unordered Set or List as is currently available.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 22:05:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 5 Oct 2007 22:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
Message-ID: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>

drools-examples-drl  does not work under Java 6 as-is
-----------------------------------------------------

                 Key: JBRULES-1253
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
    Affects Versions: 4.0.2
         Environment: Eclipse 3.2.2, at least XP (possibly others)
            Reporter: Justin Wick
         Assigned To: Mark Proctor
            Priority: Blocker


The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 00:01:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Sat, 6 Oct 2007 00:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
In-Reply-To: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12654649.1191643263344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1253?page=all ]

Fernando Meyer updated JBRULES-1253:
------------------------------------

    Assignee: Philippe Ombredanne  (was: Mark Proctor)
    Priority: Optional  (was: Blocker)

Hey Philipe, could you please check if is possible have a generic JRE configuration for eclipse projects ?

> drools-examples-drl  does not work under Java 6 as-is
> -----------------------------------------------------
>
>                 Key: JBRULES-1253
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2.2, at least XP (possibly others)
>            Reporter: Justin Wick
>         Assigned To: Philippe Ombredanne
>            Priority: Optional
>
> The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 18:36:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 18:36:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21217433.1191710164021.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal reopened JBREM-687:
-----------------------------

             
Want to make this fix available in 2.2.2.SP2 (and possible 2.2.2.GA_CP01).

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 18:36:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 18:36:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2642655.1191710164173.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal updated JBREM-687:
----------------------------

    Fix Version/s: 2.2.2.SP2
                   2.2.2.GA_CP01

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 18:41:05 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 18:41:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24464869.1191710465444.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12380853 ] 
            
Ron Sigal commented on JBAS-4704:
---------------------------------

I've created a new release, 2.2.2.SP2, targeted for the next release of community AS 4.2.x (which looks like 4.2.3) and I've reopened JBREM-687 and added 2.2.2.SP2 as a fix version.

Two questions: 

1)  What is the time frame for the release of AS 4.2.3, and

2)  Does anyone know if this problem has ever appeared in a support case?  If so, I'll target the fix for a CP release as well.

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 20:30:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 20:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-809) Verify that the
 behavior of the
 HTTPUnMarshaller re stripping CR and LF characters is correct
In-Reply-To: <4580360.1190730941269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12758501.1191717003335.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-809?page=comments#action_12380855 ] 
            
Ron Sigal commented on JBREM-809:
---------------------------------

I think the appropriate solution is to make the behavior (to include or not include the CR/LF characters) configurable, with the current behavior the default.

> Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBREM-809
>                 URL: http://jira.jboss.com/jira/browse/JBREM-809
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP1
>            Reporter: Tom Fennelly
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> At the moment, the HTTPUnMarshaller uses a BufferedReader to read a HTTP char stream.  This causes it to modify the message payload by removing the CR and LF characters.  This causes a problem for us on the ESB because it means that signature checks fail on signed SOAP messages since the sig was generated from the message containing the CR and LF chars.  It's even worse than that... it actually corrupts the signature within the message because the canonical form of the sig contains CRLF chars.
> We got around this in the ESB (in the short term) by setting our own modified version of the HTTPUnMarshaller - one that doesn't use a BufferedReader.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 02:05:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sun, 7 Oct 2007 02:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-816) Add instructions to
 Remoting Guide for overriding a transport or create a new transport
Message-ID: <10644669.1191737103385.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add instructions to Remoting Guide for overriding a transport or create a new transport
---------------------------------------------------------------------------------------

                 Key: JBREM-816
                 URL: http://jira.jboss.com/jira/browse/JBREM-816
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP1
            Reporter: Ron Sigal
         Assigned To: Trustin Lee
            Priority: Minor
             Fix For: 2.4.0.CR1 (Pinto)


Client and server invokers are created by the org.jboss.remoting.InvokerRegistry class, which will look for classes called TransportClientFactory and TransportServerFactory in the directory org/jboss/remoting/transport/<transport> and use them to create client and server invokers for the <transport> transport.

The current discussion of this facility in the Remoting Guide is rather brief.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 02:25:17 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sun, 7 Oct 2007 02:25:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4456) Replace
 JRMPProxyService with a remoting based bean.
In-Reply-To: <33088772.1180642388459.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8650810.1191738317063.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4456?page=comments#action_12380870 ] 
            
Ron Sigal commented on JBAS-4456:
---------------------------------

>From Jay Howell:

Customers have
asked for a way to select the host name by the incoming client name.
For instance, if the incoming client address is 10.12.15.x, then I want
this client to use this host name for contacting the server.  They would
also like selection based on the domain name of the client. 

> Replace JRMPProxyService with a remoting based bean.
> ----------------------------------------------------
>
>                 Key: JBAS-4456
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4456
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> We need a pojo component that generates aop remoting proxies given a target and exposed interfaces, client aspects.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 10:12:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 10:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1254)
 drools-repository/jbrms should
 not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
Message-ID: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>

drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
-----------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1254
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Geoffrey De Smet
         Assigned To: Mark Proctor
             Fix For: 4.0.2


log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
In examples you'll probably want to make them runtime scoped.

slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.

See drools-repository/pom.xml where I 've commented what I propose to change:
 <dependency>
          <groupId>org.slf4j</groupId>
          <artifactId>slf4j-api</artifactId>
        </dependency>
        <dependency>
          <groupId>org.slf4j</groupId>
          <artifactId>slf4j-log4j12</artifactId>
          <scope>test</scope>
        </dependency>
        <dependency>
          <groupId>log4j</groupId>
          <artifactId>log4j</artifactId>
          <scope>test</scope>
        </dependency>


-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 11:54:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 11:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
In-Reply-To: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5839708.1191772443347.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1253?page=all ]

Mark Proctor updated JBRULES-1253:
----------------------------------

    Fix Version/s: 4.0.2

> drools-examples-drl  does not work under Java 6 as-is
> -----------------------------------------------------
>
>                 Key: JBRULES-1253
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2.2, at least XP (possibly others)
>            Reporter: Justin Wick
>         Assigned To: Philippe Ombredanne
>            Priority: Optional
>             Fix For: 4.0.2
>
>
> The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 11:56:08 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 11:56:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1255) add alternating
 coloured rows
 for rule analysis reporting and allow for user provided css
Message-ID: <17212584.1191772568224.JavaMail.jira@cloud.prod.atl2.jboss.com>

add alternating coloured rows for rule analysis reporting and allow for user provided css
-----------------------------------------------------------------------------------------

                 Key: JBRULES-1255
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1255
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Mark Proctor
         Assigned To: Fernando Meyer
             Fix For: 4.0.2


Mark the rows in the table alternate, use a nice software light pastel colour - like green or prink. Use a CSS to declare style so users can provide alternative css.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 11:58:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 11:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1256) publish source
	jars with maven
Message-ID: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>

publish source jars with maven
------------------------------

                 Key: JBRULES-1256
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Mark Proctor
         Assigned To: Fernando Meyer
             Fix For: 4.0.2


While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 12:05:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 12:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10244122.1191773103639.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 12:07:07 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 12:07:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1254)
 drools-repository/jbrms should
 not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13773732.1191773227659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=all ]

Mark Proctor updated JBRULES-1254:
----------------------------------

    Assignee: Michael Neale  (was: Mark Proctor)

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 13:02:10 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 13:02:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1256) publish source
 jars with maven
In-Reply-To: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3698494.1191776530718.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1256?page=comments#action_12380874 ] 
            
Geoffrey De Smet commented on JBRULES-1256:
-------------------------------------------

I am pretty sure I 've solved this, after the 4.0.1 release:

Look into the parent pom, for these sections:

       <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-source-plugin</artifactId>
          <version>2.0.2</version>
	        <executions>
	          <execution>
	            <goals>
	              <goal>jar</goal>
                  <goal>test-jar</goal>
	            </goals>
	          </execution>
	        </executions>
        </plugin>

    <plugins>
        <plugin>
          <!-- Entry needed to create, install and deploy sources jars -->
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-source-plugin</artifactId>
        </plugin>
    </plugins>

> publish source jars with maven
> ------------------------------
>
>                 Key: JBRULES-1256
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 13:02:10 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 13:02:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1256) publish source
 jars with maven
In-Reply-To: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19202243.1191776530871.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1256?page=comments#action_12380875 ] 
            
Geoffrey De Smet commented on JBRULES-1256:
-------------------------------------------

btw, AFAIK there's no cmd line switch to do this, only pom configuration :)

> publish source jars with maven
> ------------------------------
>
>                 Key: JBRULES-1256
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 13:12:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 13:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1254)
 drools-repository/jbrms
 should not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25796200.1191777123280.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=comments#action_12380876 ] 
            
Geoffrey De Smet commented on JBRULES-1254:
-------------------------------------------

it looks like jbrms is also used straight out of the box, as a war.
And not just extended by a company x's war, who will want to choose their logging implementation.

In the first case, they will want an out of the box logging implementation,
so you might want to make
slf4j-log4j12 and log4j scope "runtime" and optional "true".
This means they will be included in the "standalone jbrms war", but by default excluded if company x extends the jbrms war (and allow company x to choose their logging implementation).

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 15:05:05 2007
From: jira-events at lists.jboss.org (Nicolas Doye (JIRA))
Date: Sun, 7 Oct 2007 15:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4491) Server startup
 failure with JDK 1.6
In-Reply-To: <30746220.1182198611683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14481850.1191783905064.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12380878 ] 
            
Nicolas Doye commented on JBAS-4491:
------------------------------------

Another data point - this issue is also there with JDK 6 on Linux. (All other reporters mention versions of Windows).

> Server startup failure with JDK 1.6
> -----------------------------------
>
>                 Key: JBAS-4491
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4491
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: Windows
>            Reporter: Greg Zoller
>         Attachments: Signature.java
>
>
> An out-of-the-box installation of JBoss 5.0.0 Beta2 running with JDK 1.6 produces the following exception upon startup.  Not sure the whys or wherefores but am pretty sure its not a good thing.
> 13:24:13,467 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
> 13:24:13,467 INFO  [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017)
> 13:24:13,467 INFO  [ServerImpl] Home Dir: C:\Program Files\jboss-5.0.0.Beta2
> 13:24:13,467 INFO  [ServerImpl] Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/
> 13:24:13,467 INFO  [ServerImpl] Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/lib/
> 13:24:13,467 INFO  [ServerImpl] Patch URL: null
> 13:24:13,467 INFO  [ServerImpl] Server Name: default
> 13:24:13,467 INFO  [ServerImpl] Server Home Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:13,467 INFO  [ServerImpl] Server Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/
> 13:24:13,467 INFO  [ServerImpl] Server Data Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\data
> 13:24:13,467 INFO  [ServerImpl] Server Temp Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\tmp
> 13:24:13,467 INFO  [ServerImpl] Server Config URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/
> 13:24:13,467 INFO  [ServerImpl] Server Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/lib/
> 13:24:13,467 INFO  [ServerImpl] Root Deployment Filename: jboss-service.xml
> 13:24:13,499 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml
> 13:24:14,831 INFO  [ProfileImpl] Using profile root:C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:15,913 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter state=Described
> java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125)
> 	at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292)
> 	at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138)
> 	at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280)
> 	at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
> 	at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
> 	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
> 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
> 	at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBootstrap.java:295)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:222)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at java.net.URLClassLoader$1.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170)
> 	... 35 more
> 13:24:16,258 INFO  [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
> 13:24:16,305 INFO  [JMXKernel] Legacy JMX core initialized
> Failed to boot JBoss:
> java.lang.RuntimeException: Exception during Bootstrap
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
> VFSBootstrapScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeployerScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeploymentScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> *** CONTEXTS IN ERROR: Name -> Error
> DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileServiceBootstrap.java:389)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	... 5 more

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 23:59:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 23:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1257) Add Banking
 Example from John Dunning
Message-ID: <21119646.1191815943276.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add Banking Example from John Dunning
-------------------------------------

                 Key: JBRULES-1257
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1257
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2


John Dunny has blogged a nice banking tutorial at:
http://web.mac.com/johndunning/Life_on_a_Laptop/Drools/Entries/2007/10/7_Banking_on_DROOLS.html
And has kindly given us permission to add it to the manual.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 02:05:04 2007
From: jira-events at lists.jboss.org (Vt Ysh (JIRA))
Date: Mon, 8 Oct 2007 02:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1068) Possibility of
 UITaskFormButtonBase to use child action tags such as it done with
 h:commandButton
Message-ID: <20958100.1191823504155.JavaMail.jira@cloud.prod.atl2.jboss.com>

Possibility of UITaskFormButtonBase to use child action tags such as it done with h:commandButton
-------------------------------------------------------------------------------------------------

                 Key: JBPM-1068
                 URL: http://jira.jboss.com/jira/browse/JBPM-1068
             Project: JBoss jBPM
          Issue Type: Feature Request
          Components: Web Interface
    Affects Versions:  jBPM jPDL 3.2.1
            Reporter: Vt Ysh
         Assigned To: Tom Baeyens
            Priority: Optional


If i am trying to put custom action tags between for example <tf:saveButton value="Save"></tf:saveButton > such as it can be done with h:commandButton i am getting NullPointer exception with the next stack trace:

java.lang.NullPointerException
        at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.getEnclosingForm(UITask
FormButtonBase.java:30)
        at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.addActionListener(UITas
kFormButtonBase.java:44)
        at org.jbpm.jsf.core.handler.AbstractHandler.apply(AbstractHandler.java:
64)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.ui.DefineHandler.apply(DefineHandler.java:58)
        at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j
ava:128)
        at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(Def
aultFaceletContext.java:306)
        at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(Default
FaceletContext.java:279)
        at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at test.facelets.IfHandler.apply(IfHandler.java:33)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav
a:49)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:
25)
        at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)

        at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)

        at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)

        at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFac
eletContext.java:143)
        at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j
ava:113)
        at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav
a:49)
        at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:
25)
        at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
        at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java
:503)
        at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav
a:546)
        at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrap
per.java:178)
        at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha
se.java:106)
        at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
        at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:175)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:74)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
        at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
kerThread.java:112)
        at java.lang.Thread.run(Thread.java:595)

Seems that problem can be in HtmlCommandButton.getParent() method. Is there any suggestions how to fix this issue?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 04:03:03 2007
From: jira-events at lists.jboss.org (Tim McCune (JIRA))
Date: Mon, 8 Oct 2007 04:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (HIBERNATE-73) @OneToOne with
 @PrimaryKeyJoinColumn does not work right
Message-ID: <20389741.1191830583574.JavaMail.jira@cloud.prod.atl2.jboss.com>

@OneToOne with @PrimaryKeyJoinColumn does not work right
--------------------------------------------------------

                 Key: HIBERNATE-73
                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-73
             Project: Hibernate
          Issue Type: Bug
         Environment: JBoss 4.2.1
            Reporter: Tim McCune
         Assigned To: Steve Ebersole


Given the following code:

@Entity
public class Employee {
  @Id Integer id;
    
  @OneToOne @PrimaryKeyJoinColumn
  EmployeeInfo info;
  ...
}

@Entity
 public class EmployeeInfo {
   @Id Integer id;
        ...
}

Hibernate creates EMPLOYEE and EMPLOYEEINFO tables, but does not create a foreign key relationship from EMPLOYEEINFO to EMPLOYEE.

Furthermore, Hibernate does not set the EmployeeInfo's id correctly when persisting it.  The following code:

EmployeeInfo info = new EmployeeInfo();
employee.setInfo(info);

does insert a new row into EMPLOYEEINFO, but it has an id of "1" when it should have an id that is the same as the corresponding Employee.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 05:19:09 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 8 Oct 2007 05:19:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1069) Include common-io and
 common-fileupload in the ear configuration
Message-ID: <22824913.1191835149906.JavaMail.jira@cloud.prod.atl2.jboss.com>

Include common-io and common-fileupload in the ear configuration
----------------------------------------------------------------

                 Key: JBPM-1069
                 URL: http://jira.jboss.com/jira/browse/JBPM-1069
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
            Reporter: Fady Matar
         Assigned To: Tom Baeyens
            Priority: Trivial
             Fix For: jBPM 3.3


Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file)

The ear files can be appended to the JBoss AS configuration or can be packaged within the ear

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 05:25:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 8 Oct 2007 05:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1734) "edit mode"
 could be checked for authorization
Message-ID: <4615781.1191835503517.JavaMail.jira@cloud.prod.atl2.jboss.com>

"edit mode" could be checked for authorization
----------------------------------------------

                 Key: JBPORTAL-1734
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1734
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Julien Viet
             Fix For: 2.8 Final


An admin should be able to define which roles have access to the edit mode for a particular portlet.

Since it would break backward compatibility, it has to be part of a major release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:17:10 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 06:17:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-209) Trim string
	value
Message-ID: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>

Trim string value
-----------------

                 Key: JBMICROCONT-209
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: MetaData
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta5


In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:17:10 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 06:17:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-209) Trim string
	value
In-Reply-To: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26879124.1191838630537.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-209?page=all ]

Ales Justin resolved JBMICROCONT-209.
-------------------------------------

    Resolution: Done

You can now set trim=true|false on property or parameter.

> Trim string value
> -----------------
>
>                 Key: JBMICROCONT-209
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: MetaData
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:22:19 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 8 Oct 2007 06:22:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1059) Return a
 business interface from a home create method must not be allowed
Message-ID: <30915920.1191838939062.JavaMail.jira@cloud.prod.atl2.jboss.com>

Return a business interface from a home create method must not be allowed
-------------------------------------------------------------------------

                 Key: EJBTHREE-1059
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1059
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


EJB 3 4.6.8: The return type for a create<METHOD> method must be the session bean's remote interface type.

Using the proxy as if it would be an EJBObject results in class cast exceptions.

java.lang.ClassCastException: $Proxy9
	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject(RemoteUnitTestCase.java:208)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 8 Oct 2007 06:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18011799.1191839043270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf resolved EJBTHREE-1055.
-------------------------------------

    Resolution: Done

Resurrected the old injection code

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:25:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 8 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1059) Return a
 business interface from a home create method must not be allowed
In-Reply-To: <30915920.1191838939062.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21690070.1191839103970.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1059?page=all ]

Carlo de Wolf updated EJBTHREE-1059:
------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091956

> Return a business interface from a home create method must not be allowed
> -------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1059
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1059
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>
> EJB 3 4.6.8: The return type for a create<METHOD> method must be the session bean's remote interface type.
> Using the proxy as if it would be an EJBObject results in class cast exceptions.
> java.lang.ClassCastException: $Proxy9
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject(RemoteUnitTestCase.java:208)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:58:03 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 06:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-210) Change
 KernelBus implementation
Message-ID: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>

Change KernelBus implementation
-------------------------------

                 Key: JBMICROCONT-210
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
             Project: JBoss MicroContainer
          Issue Type: Task
          Components: Kernel
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta5


Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:00:08 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 07:00:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-210) Change
 KernelBus implementation
In-Reply-To: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15388928.1191841208044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-210?page=all ]

Ales Justin resolved JBMICROCONT-210.
-------------------------------------

    Resolution: Done

Changed BasicKernelBus to check for installed contexts.
Added BeanKernelRegistryEntry which implements AttributeDispatchContext.

> Change KernelBus implementation
> -------------------------------
>
>                 Key: JBMICROCONT-210
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
> Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:11:13 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 8 Oct 2007 07:11:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-560) Message greater
 than 16286 bytes is not received on MaxOS
In-Reply-To: <2848013.1184741447091.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32018620.1191841873081.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-560?page=comments#action_12380916 ] 
            
Manik Surtani commented on JGRP-560:
------------------------------------

While Jason's fix above does work, keep in mind that *some* OS X updates reset MTU settings for lo0!  Something I just noticed.  

> Message greater than 16286 bytes is not received on MaxOS
> ---------------------------------------------------------
>
>                 Key: JGRP-560
>                 URL: http://jira.jboss.com/jira/browse/JGRP-560
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> I'm new to JGroups, and I have a Mac OS X (10.4)-specific question. I've used
> JGroups 2.4.1sp3, 2.5.0CR1, and the new 2.5.0GA - I see the same issue with
> all versions.
> I've noticed that, for UDP, there seems to be a max message size of 16286
> bytes (a little less than 16K). This is using the default udp.xml config,
> and just a simple message to another node like:
> JChannel ch = new JChannel("udp.xml");
> ch.setReceiver(this);
> ch.connect("TEST");		
> //
> // 'target' is another group member besides myself
> //
> byte[] buf = new byte[size];
> Arrays.fill(buf, (byte)77);
> echo("Sending message: " + size + " bytes");
> Message msg = new Message(target, null, buf);
> ch.send(msg);
> A receiver node will NOT receive the message if 'size' is greater than
> 16286. In fact, after sending a too-large message, the receiver sees no
> message trafffic so it starts doing heartbeats and view changes). I've
> attached some debug output below.
> TCP transport does not have this problem.
> I'm aware of the tos="8" attribute warning in OS X, and changing the value
> to 0 to avoid the warning doesn't affect the max size issue. Though perhaps
> it's the same Mac quirk causing both problems...
> I've searched around, but haven't seen anything about this. Is it a known
> issue? Is there a workaround? Am I doing something wrong?
> Thanks in advance,
> Rick Pike
> Debug output:
> -------------------------
> SENDER:
> (Sends increasing size messages, 2 sec apart. As soon as the size goes
> beyond 16286, it notices a problem).
> Sending message: 16284 bytes
> Sending message: 16285 bytes
> Sending message: 16286 bytes
> 2007-07-17 12:06:25,934 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51607 (own address=192.168.2.71:51610)
> 2007-07-17 12:06:25,936 [DEBUG] FD received ack from 192.168.2.71:51607
> Sending message: 16287 bytes
> Sending message: 16288 bytes
> RECEIVER:
> (Gets messages OK until 16287. I assume FD starts because it sees no message
> traffic.)
> Received message: 16284 bytes
> Received message: 16285 bytes
> Received message: 16286 bytes
> 2007-07-17 12:06:25,876 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51610 (own address=192.168.2.71:51607)
> 2007-07-17 12:06:25,884 [DEBUG] FD received ack from 192.168.2.71:51610
> 2007-07-17 12:06:29,305 [DEBUG] MERGE2
> initial_mbrs=[[own_addr=192.168.2.71:51610, coord_addr=192.168.2.71:51607,
> is_server=true], [own_addr=192.168.2.71:51607,
> coord_addr=192.168.2.71:51607, is_server=true]]
> 2007-07-17 12:06:35,877 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51610 (own address=192.168.2.71:51607)
> 2007-07-17 12:06:35,880 [DEBUG] FD received ack from 192.168.2.71:51610
> 2007-07-17 12:06:42,496 [DEBUG] MERGE2
> initial_mbrs=[[own_addr=192.168.2.71:51610, coord_addr=192.168.2.71:51607,
> is_server=true], [own_addr=192.168.2.71:51607,
> coord_addr=192.168.2.71:51607, is_server=true]]
> 2007-07-17 12:06:45,879 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51610 (own address=192.168.2.71:51607)
> 2007-07-17 12:06:45,880 [DEBUG] FD received ack from 192.168.2.71:51610
> 2007-07-17 12:06:50,453 [DEBUG] FD_SOCK peer closed socket normally
> 2007-07-17 12:06:50,453 [DEBUG] FD_SOCK pinger thread terminated

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:52:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 07:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
Message-ID: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>

Message headers not preserved on bridged message
------------------------------------------------

                 Key: JBMESSAGING-1098
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:58:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 07:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1097) Cleaning JBM
 Tables During Startup
In-Reply-To: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28312464.1191844683348.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1097?page=all ]

Tim Fox updated JBMESSAGING-1097:
---------------------------------

    Fix Version/s: Unscheduled
                       (was: 1.4.0.SP1)
         Priority: Minor  (was: Major)

> Cleaning JBM Tables During Startup
> ----------------------------------
>
>                 Key: JBMESSAGING-1097
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.GA
>         Environment: JBossAS-4.2.0-GA
> JBossMessaging-1.4.0-GA
>            Reporter: Tyronne Wickramarathne
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 08:00:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 08:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1097) Cleaning
 JBM Tables During Startup
In-Reply-To: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24602892.1191844803380.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1097?page=comments#action_12380926 ] 
            
Tim Fox commented on JBMESSAGING-1097:
--------------------------------------

Can you explain what the motivation for this is?

If you don't want messages to survive server shutdown/startup then maybe you should be using non persistent messages, not persistent messages?

> Cleaning JBM Tables During Startup
> ----------------------------------
>
>                 Key: JBMESSAGING-1097
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.GA
>         Environment: JBossAS-4.2.0-GA
> JBossMessaging-1.4.0-GA
>            Reporter: Tyronne Wickramarathne
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 08:00:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 08:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22070410.1191844803764.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox closed JBMESSAGING-1098.
--------------------------------

    Resolution: Done

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:40:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 09:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3142) Add UnifiedInvoker
 (JBSer and JavaSer) into Version MatrixTestSuite
Message-ID: <8516922.1191850804330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3142?page=all ]

Dimitris Andreadis updated JBAS-3142:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

> Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite
> -------------------------------------------------------------------
>
>                 Key: JBAS-3142
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3142
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Optional
>             Fix For: JBossAS-4.2.3.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:56:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 09:56:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15853152.1191851773203.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox reopened JBMESSAGING-1098:
----------------------------------

             

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:56:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 09:56:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31520777.1191851773340.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox updated JBMESSAGING-1098:
---------------------------------

    Priority: Minor  (was: Major)

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:56:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 09:56:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30785556.1191851773462.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox closed JBMESSAGING-1098.
--------------------------------

    Resolution: Done

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 10:55:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 10:55:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4572) EJB 3 testsuite 100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29242432.1191855305183.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4572?page=all ]

Dimitris Andreadis closed JBAS-4572.
------------------------------------

    Resolution: Done

Updated the depends/related list. The "depends" are solved. The "related" are still open, but known. The ejb3 suite passes.

> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:01:06 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 11:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33159470.1191855666371.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12380979 ] 
            
Dimitris Andreadis commented on JBAS-4704:
------------------------------------------

4.2.3 probably sometime around Feb/08.

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-42) Container Task for
 JBoss RULES Integration with JBoss Security
In-Reply-To: <20259928.1175689858488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19058604.1191857523833.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-42?page=all ]

Anil Saldhana updated SECURITY-42:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Container Task for JBoss RULES Integration with JBoss Security
> --------------------------------------------------------------
>
>                 Key: SECURITY-42
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-42
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JEMS Integration
>    Affects Versions: 1.x
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Container Task for JBoss Rules integration with JBoss Security.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-24) Get OpenSaml2
 snapshot libraries into the JBoss repository
In-Reply-To: <26707524.1164815335686.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2730086.1191857524130.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-24?page=all ]

Anil Saldhana updated SECURITY-24:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Get OpenSaml2 snapshot libraries into the JBoss repository
> ----------------------------------------------------------
>
>                 Key: SECURITY-24
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-24
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: OnDemand, Repository
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-54) Technical White
 Paper: Single Sign On Options with JBoss
In-Reply-To: <8576238.1179338332302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10331074.1191857524344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-54?page=all ]

Anil Saldhana updated SECURITY-54:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Technical White Paper: Single Sign On Options with JBoss
> --------------------------------------------------------
>
>                 Key: SECURITY-54
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-54
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
> This wiki page has been the central focus of Single Sign On options with the JBoss Application Server.
> The proposed Technical White Paper should consolidate all the options into a single place.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-34) Container Task:
 Formalize Kerberos offering
In-Reply-To: <33197347.1173287004217.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13153922.1191857524814.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-34?page=all ]

Anil Saldhana updated SECURITY-34:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Container Task: Formalize Kerberos offering
> -------------------------------------------
>
>                 Key: SECURITY-34
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-34
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x, 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Spoken to Chris Delashmutt about formalizing the initial work he did for Kerberos/spnego.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=NegotiateKerberos
> This jira task is a container task for overall kerberos silent authentication tasks.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-74) Policy Management
 Console using JBoss SEAM
In-Reply-To: <14814510.1186178449283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28565157.1191857524995.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-74?page=all ]

Anil Saldhana updated SECURITY-74:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Policy Management Console using JBoss SEAM
> ------------------------------------------
>
>                 Key: SECURITY-74
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-74
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossXACML-Console
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Need for a progressive Policy Management console using JBoss SEAM.  The JAXB2 object model provided with JBoss XACML can be used to construct the policies.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-33) White Paper on
	Kerberos
In-Reply-To: <26768130.1173286648778.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2585422.1191857525247.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-33?page=all ]

Anil Saldhana updated SECURITY-33:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> White Paper on Kerberos 
> ------------------------
>
>                 Key: SECURITY-33
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-33
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> We have some kerberos/spnego interface available in JBoss as part of the initial work done by Chris DeLashmutt.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=NegotiateKerberos
> Need to bring this contribution to some formality and get a white paper out.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-29) Validate Jacc
 Policy Module handles all run-as scenarios
In-Reply-To: <25155900.1173285622888.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1923047.1191857525633.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-29?page=all ]

Anil Saldhana updated SECURITY-29:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Validate Jacc Policy Module handles all run-as scenarios
> --------------------------------------------------------
>
>                 Key: SECURITY-29
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-29
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.0.BETA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> With the roles being added to the security context via the mapping framework (for example), there may be cases where in run-as scenarios may not be adequately tested with the new Jacc authorization stuff.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-50) XACML EJB Layer:
 Role Reference Checks
In-Reply-To: <17517802.1178655352366.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15691616.1191857525849.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-50?page=all ]

Anil Saldhana updated SECURITY-50:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> XACML EJB Layer: Role Reference Checks
> --------------------------------------
>
>                 Key: SECURITY-50
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-50
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.0.BETA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Provide a mechanism to do EJBContext.isCallerInRole checks when xacml is enabled.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-65) Kerberos Aware
	Authenticators
In-Reply-To: <24662911.1183485481866.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32677509.1191857526061.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-65?page=all ]

Anil Saldhana updated SECURITY-65:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Kerberos Aware Authenticators
> -----------------------------
>
>                 Key: SECURITY-65
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-65
>             Project: JBoss Security and Identity Management
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Provide authenticators that can do negotiate headers back to the browser and fall back on the web app configured auth method (BASIC/FORM).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-8) LdapExtLoginModule
 should detect communication failures midstream
In-Reply-To: <1391642.1158350795955.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12997118.1191857526613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-8?page=all ]

Anil Saldhana updated SECURITY-8:
---------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

>  LdapExtLoginModule should detect communication failures midstream
> ------------------------------------------------------------------
>
>                 Key: SECURITY-8
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-8
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> http://jira.jboss.com/jira/browse/JBAS-3661
> There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the:
> http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotificationListener.html
> such that it can do graceful processing. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-60) XACML SPI
In-Reply-To: <16066515.1181580431734.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24893776.1191857526777.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-60?page=all ]

Anil Saldhana updated SECURITY-60:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> XACML SPI
> ---------
>
>                 Key: SECURITY-60
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-60
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Provide a XACML SPI in the JBossSX implementation such that external xacml implementations can be plugged in. The XACML module should make use of this spi.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-61) Use JBossSubject
 rather than JAAS Subject
In-Reply-To: <28927019.1181583131596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11513205.1191857527004.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-61?page=all ]

Anil Saldhana updated SECURITY-61:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Use JBossSubject rather than JAAS Subject
> -----------------------------------------
>
>                 Key: SECURITY-61
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-61
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> The JAAS Subject is quite inflexible.  There is a need for a customized Subject.  Let us call it JBossSubject which can internally hold a Jaas Subject.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-36) SASL Authentication
In-Reply-To: <20174150.1173881912358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12305340.1191857527542.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-36?page=all ]

Anil Saldhana updated SECURITY-36:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> SASL Authentication
> -------------------
>
>                 Key: SECURITY-36
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-36
>             Project: JBoss Security and Identity Management
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x
>         Environment: JBossAS: 4.0
>            Reporter: Michael Barker
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>         Attachments: sasl-cram-md5-patch.txt
>
>
> This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security.  Currently only supports CRAM-MD5.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-46) SASL Implementation
In-Reply-To: <28027983.1178057310177.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6215540.1191857527691.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-46?page=all ]

Anil Saldhana updated SECURITY-46:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> SASL Implementation  
> ---------------------
>
>                 Key: SECURITY-46
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-46
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, JEMS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Need to get an implementation of SASL for client/server kind of setup for JBoss AS.  This will work off of the Security Client implementation and then security managers on the server side.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:34:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-32) White Paper on
	Clustered SSO
In-Reply-To: <19027403.1173286522201.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12949159.1191857643354.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-32?page=all ]

Anil Saldhana updated SECURITY-32:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> White Paper on Clustered SSO
> ----------------------------
>
>                 Key: SECURITY-32
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-32
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Sakthi Samabsivam
>             Fix For: NO_VERSION
>
>
> White paper on the Clustered SSO offering from JBoss.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
> http://wiki.jboss.org/wiki/Wiki.jsp?page=BuddyReplicationAndClusteredSSO
> This is important because many customers are using this along with http session replication.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:36:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:36:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-38) Container Task for
 JBoss SEAM Integration with JBoss Security
In-Reply-To: <22124889.1174015112880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20692485.1191857766921.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-38?page=all ]

Anil Saldhana updated SECURITY-38:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Container Task for JBoss SEAM Integration with JBoss Security
> -------------------------------------------------------------
>
>                 Key: SECURITY-38
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-38
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JEMS Integration
>    Affects Versions: 1.x
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Container Task to link all the issues that are related to JBoss Seam's integration with JBoss Security.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:49:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 8 Oct 2007 11:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock
 could be not released after async transaction rollback
In-Reply-To: <19139966.1189557851483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2771268.1191858543452.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]

Manik Surtani updated JBCACHE-1183:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

Not observed in trunk (2.1.0)

> Acquired WL lock could be not released after async transaction rollback
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-1183
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: WindowsXP, jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: AsyncRollbackTxLockTest.java
>
>
> In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:42:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 8 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1168) Sometimes
 acquired locks are not released
In-Reply-To: <30832886.1187878698592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9596431.1191858123825.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1168?page=all ]

Manik Surtani updated JBCACHE-1168:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

Cannot reproduce in trunk (2.1.0)

> Sometimes acquired locks are not released
> -----------------------------------------
>
>                 Key: JBCACHE-1168
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4
>         Environment: Windows XP, jrockit90_150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: jbosscache.log, output.txt, TransactionStormTest.java
>
>
> Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache.
> Main loop:
> 		while (true) {
> 			for (int x = 0; x < 2; x++) {
> 				WorkThread t = new WorkThread(x == 1);
> 				threads.add(t);
> 				t.start();
> 			}
> 			for (WorkThread separateThread : threads) {
> 				separateThread.join();
> 				if (separateThread.getException() != null) {
> 					//separateThread.getException().getMessage();
> 				}
> 			}
> 			int locksNum = getNumberOfLocksHeld();
> //			System.out.println("Locks="+locksNum);
> 			// checkpoint
> 			if (cache.getNumberOfLocksHeld()>0){
> 				System.out.println("ERROR, locks="+locksNum);
> 				doDomethingOnCache(1);
> 			}
> 			assertEquals(0, locksNum);
> 		}
> Exception - after //checkpoint line numberOfLocks is grater than 0!
> JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 12:34:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 8 Oct 2007 12:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1252) DrlDumper does not
 dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21808404.1191861243320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Fernando Meyer closed JBRULES-1252.
-----------------------------------

    Resolution: Done

Patch applied and added support for function import into xml

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 12:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 12:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18932841.1191862623533.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12381007 ] 
            
Dimitris Andreadis commented on JBAS-4754:
------------------------------------------

Rajesh, I think we are ready.

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:02:20 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 8 Oct 2007 13:02:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11480488.1191862940467.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12381011 ] 
            
Rajesh Rajasekaran commented on JBAS-4754:
------------------------------------------

The runs are on the way.
http://hudson.qa.jboss.com/hudson/view/TCK14-AS4.2.x/
A couple of modules need to be looked at as far as the setup on hudson is concerned.
Will send out a report once there is a complete run.

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:22:05 2007
From: jira-events at lists.jboss.org (Michael Barker (JIRA))
Date: Mon, 8 Oct 2007 13:22:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (SECURITY-36) SASL
	Authentication
In-Reply-To: <20174150.1173881912358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18554828.1191864125394.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/SECURITY-36?page=comments#action_12381021 ] 
            
Michael Barker commented on SECURITY-36:
----------------------------------------

Feel free to close this JIRA task.  Given the time scale for implementation we are not going to require SASL authentication.

> SASL Authentication
> -------------------
>
>                 Key: SECURITY-36
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-36
>             Project: JBoss Security and Identity Management
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x
>         Environment: JBossAS: 4.0
>            Reporter: Michael Barker
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>         Attachments: sasl-cram-md5-patch.txt
>
>
> This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security.  Currently only supports CRAM-MD5.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:37:06 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 8 Oct 2007 13:37:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-475) Add a Dynamic AOP
	injboss example
Message-ID: <33115954.1191865026557.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add a Dynamic AOP injboss example
---------------------------------

                 Key: JBAOP-475
                 URL: http://jira.jboss.com/jira/browse/JBAOP-475
             Project: JBoss AOP
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Flavia Rainone
            Priority: Optional


Add a dynamic AOP example in jboss to our tutorial, where we show the power of dynamic AOP on a deployed application.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:44:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 13:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1258) serialising a
 package breaks function removal
Message-ID: <23220508.1191865443258.JavaMail.jira@cloud.prod.atl2.jboss.com>

serialising a package breaks  function removal
----------------------------------------------

                 Key: JBRULES-1258
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1258
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: FUTURE


DynamicRulesTest.testDynamicFunction breaks if you serialise the package first before use. On inspection I cannot initially see what is going wrong. The code seems to be successfully recreating the new classloader and re-writing all invokers, yet it still fails :(

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:52:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 13:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1097) Cleaning
 JBM Tables During Startup
In-Reply-To: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1436429.1191865923904.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1097?page=comments#action_12381031 ] 
            
Tim Fox commented on JBMESSAGING-1097:
--------------------------------------

"because the customer insists" is not a good enough reason for implementing this.

> Cleaning JBM Tables During Startup
> ----------------------------------
>
>                 Key: JBMESSAGING-1097
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.GA
>         Environment: JBossAS-4.2.0-GA
> JBossMessaging-1.4.0-GA
>            Reporter: Tyronne Wickramarathne
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:23:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 8 Oct 2007 14:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1255) add alternating
 coloured rows
 for rule analysis reporting and allow for user provided css
In-Reply-To: <17212584.1191772568224.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2018156.1191867783356.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1255?page=all ]

Fernando Meyer closed JBRULES-1255.
-----------------------------------

    Resolution: Done

> add alternating coloured rows for rule analysis reporting and allow for user provided css
> -----------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1255
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1255
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> Mark the rows in the table alternate, use a nice software light pastel colour - like green or prink. Use a CSS to declare style so users can provide alternative css.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:29:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 8 Oct 2007 14:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-476) Hotswap on JBoss AS
Message-ID: <32821412.1191868143225.JavaMail.jira@cloud.prod.atl2.jboss.com>

Hotswap on JBoss AS
-------------------

                 Key: JBAOP-476
                 URL: http://jira.jboss.com/jira/browse/JBAOP-476
             Project: JBoss AOP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Flavia Rainone
            Priority: Optional


Add support to hotswap on JBoss AS.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:33:05 2007
From: jira-events at lists.jboss.org (Philippe Ombredanne (JIRA))
Date: Mon, 8 Oct 2007 14:33:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
In-Reply-To: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14785177.1191868385544.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1253?page=all ]

Philippe Ombredanne resolved JBRULES-1253.
------------------------------------------

    Resolution: Done

Fixed in rev 15659

> drools-examples-drl  does not work under Java 6 as-is
> -----------------------------------------------------
>
>                 Key: JBRULES-1253
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2.2, at least XP (possibly others)
>            Reporter: Justin Wick
>         Assigned To: Philippe Ombredanne
>            Priority: Optional
>             Fix For: 4.0.2
>
>
> The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:56:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 8 Oct 2007 14:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-477)
 javassist.NotFoundException on Singleton Undeployment
Message-ID: <22512285.1191869763203.JavaMail.jira@cloud.prod.atl2.jboss.com>

javassist.NotFoundException on Singleton Undeployment
-----------------------------------------------------

                 Key: JBAOP-477
                 URL: http://jira.jboss.com/jira/browse/JBAOP-477
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 1.5.5.GA
            Reporter: Flavia Rainone


JBoss AOP is getting a javassist.NotFoundException on undeployment of ha-singleton components.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 15:49:14 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 15:49:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-82) MappingContext
 needs usage of MappingResult to obtain the mapped object
Message-ID: <6173441.1191872954438.JavaMail.jira@cloud.prod.atl2.jboss.com>

MappingContext needs usage of MappingResult to obtain the mapped object
-----------------------------------------------------------------------

                 Key: SECURITY-82
                 URL: http://jira.jboss.com/jira/browse/SECURITY-82
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: JBossSX, Security SPI
    Affects Versions: 2.0.1-BETA1
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-BETA2


Currently the api in MappingContext

performMapping(Map contextMap, T mappedObject)

will not work for Principal objects etc.

Introduce a MappingResult class in the MappingContext as a holder for the mapped object.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 15:59:14 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 8 Oct 2007 15:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28202815.1191873554610.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12381062 ] 
            
Ron Sigal commented on JBAS-4704:
---------------------------------

>From Dimitris:  I don't personally know of a support case around this issue.

>From Carlo:  The issue pop-ed in directly from Jira. I can't find any related support cases or forum posts.

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 16:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-82) MappingContext
 needs usage of MappingResult to obtain the mapped object
In-Reply-To: <6173441.1191872954438.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3624985.1191874023661.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-82?page=all ]

Anil Saldhana closed SECURITY-82.
---------------------------------

    Resolution: Done

> MappingContext needs usage of MappingResult to obtain the mapped object
> -----------------------------------------------------------------------
>
>                 Key: SECURITY-82
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-82
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.1-BETA1
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-BETA2
>
>
> Currently the api in MappingContext
> performMapping(Map contextMap, T mappedObject)
> will not work for Principal objects etc.
> Introduce a MappingResult class in the MappingContext as a holder for the mapped object.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 16:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-28) JACC:
 <role-name>*</role-name>
 in web.xml should allow configurable authorization bypass
In-Reply-To: <7468972.1172167373750.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11810913.1191874023977.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-28?page=all ]

Anil Saldhana updated SECURITY-28:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-BETA2)

> JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass
> ----------------------------------------------------------------------------------------
>
>                 Key: SECURITY-28
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-28
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> JBAS-1824

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 16:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-81) Identity Trust
 context should handle security domain also
In-Reply-To: <17880822.1191606363435.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30762753.1191874023455.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-81?page=all ]

Anil Saldhana closed SECURITY-81.
---------------------------------

    Resolution: Done

> Identity Trust context should handle security domain also
> ---------------------------------------------------------
>
>                 Key: SECURITY-81
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-81
>             Project: JBoss Security and Identity Management
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.1-BETA1
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-BETA2
>
>
> ITC can handle a security context that belongs to a different security domain.
> Hence ITC needs to know the sec domain for the Identity Trust Manager.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:52:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 8 Oct 2007 16:52:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3196513.1191876724630.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-687?page=comments#action_12381081 ] 
            
Ron Sigal commented on JBREM-687:
---------------------------------

Applied changes to branch remoting_2_2_0_GA for release 2.2.2.SP2.

Note:  In addition to invokerLocator and ServerInvoker, a change is also made to org.jboss.remoting.transport.Connector.

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 17:58:03 2007
From: jira-events at lists.jboss.org (Lukasz Wiktor (JIRA))
Date: Mon, 8 Oct 2007 17:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-254)
 ClassCastException in
 org.jboss.portlet.forums.ui.PortalUtil in function getPoster
Message-ID: <28414572.1191880683450.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException in org.jboss.portlet.forums.ui.PortalUtil in function getPoster
----------------------------------------------------------------------------------

                 Key: JBFORUMS-254
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-254
             Project: JBoss Forums
          Issue Type: Bug
    Affects Versions: 1.0.0 GA
         Environment: JBoss Portal 2.6.1.GA bundled with JBoss AS 4.2.1 and  integrated with OpenLDAP
            Reporter: Lukasz Wiktor
         Assigned To: Ryszard Kozmik


In class org.jboss.portlet.forums.ui.PortalUtil in function getPoster() userId is casted to Long. That causes ClassCastException when userId is for example type of String (in LDAP).

2007-10-04 15:35:07,700 ERROR [org.jboss.portlet.forums.ui.JSFUtil] org.jboss.portlet.forums.ui.JSFUtil
java.lang.ClassCastException: java.lang.String
	at org.jboss.portlet.forums.ui.PortalUtil.getPoster(PortalUtil.java:467)
             ...

It prevents from e.g. creating new topic.

See my posts on the forum. I have proposed the solution.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 20:24:12 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 20:24:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1257) Add Banking
 Example from John Dunning
In-Reply-To: <21119646.1191815943276.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15577804.1191889452673.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1257?page=all ]

Mark Proctor closed JBRULES-1257.
---------------------------------

    Resolution: Done

> Add Banking Example from John Dunning
> -------------------------------------
>
>                 Key: JBRULES-1257
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1257
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> John Dunny has blogged a nice banking tutorial at:
> http://web.mac.com/johndunning/Life_on_a_Laptop/Drools/Entries/2007/10/7_Banking_on_DROOLS.html
> And has kindly given us permission to add it to the manual.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 20:26:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 20:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1254)
 drools-repository/jbrms should
 not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3535916.1191889563321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=all ]

Mark Proctor updated JBRULES-1254:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

We've decided to leave this as is for 4.0.2. But we'll look to apply this after the branch is made.

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 20:48:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 8 Oct 2007 20:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1259) JBoss Drools
	4.0.2GA Release
Message-ID: <32091951.1191890883474.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Drools 4.0.2GA Release
----------------------------

                 Key: JBRULES-1259
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1259
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 21:18:15 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Mon, 8 Oct 2007 21:18:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
Message-ID: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>

Include eclipse JDT library in drools-eclipse IDE plugin
--------------------------------------------------------

                 Key: JBRULES-1260
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
    Affects Versions: 4.0.1
            Reporter: Joshua Jackson
         Assigned To: Mark Proctor
             Fix For: 4.0.2


Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:

org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
	at com.sample.DroolsTest.main(DroolsTest.java:21)
Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 21:55:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 21:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31703547.1191894903305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=all ]

Mark Proctor closed JBRULES-1260.
---------------------------------

    Fix Version/s: 4.0.3
                       (was: 4.0.2)
       Resolution: Done

It should get the JDT Compiler from Eclipse itself, I've not heard of others having this problem, you'll need to supply more details.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 21:57:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 21:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1261) Update to JDK1.5
	minimum
Message-ID: <20527685.1191895023212.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update to JDK1.5 minimum
------------------------

                 Key: JBRULES-1261
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1261
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.1.0.




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 22:01:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 22:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1261) Update to JDK1.5
	minimum
In-Reply-To: <20527685.1191895023212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31492656.1191895263498.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1261?page=all ]

Mark Proctor closed JBRULES-1261.
---------------------------------

    Resolution: Done

> Update to JDK1.5 minimum
> ------------------------
>
>                 Key: JBRULES-1261
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1261
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 22:30:03 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Mon, 8 Oct 2007 22:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13002741.1191897003327.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381109 ] 
            
Joshua Jackson commented on JBRULES-1260:
-----------------------------------------

I used eclipse 3.3 europa
- dropped in the 4.0.1 drools-eclipse plugin
- create new rules project and add the sample HelloWorld
- run the DroolsTest as java program
- and then I received that exception message

But when I inserted the eclipse jdt library that is provided by drools, it worked.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 02:44:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 9 Oct 2007 02:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-36) SASL Authentication
In-Reply-To: <20174150.1173881912358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14020830.1191912243495.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-36?page=all ]

Anil Saldhana closed SECURITY-36.
---------------------------------

    Resolution: Won't Fix

> SASL Authentication
> -------------------
>
>                 Key: SECURITY-36
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-36
>             Project: JBoss Security and Identity Management
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x
>         Environment: JBossAS: 4.0
>            Reporter: Michael Barker
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>         Attachments: sasl-cram-md5-patch.txt
>
>
> This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security.  Currently only supports CRAM-MD5.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 03:51:03 2007
From: jira-events at lists.jboss.org (M H (JIRA))
Date: Tue, 9 Oct 2007 03:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1262) DSL Parser "eval"
Message-ID: <29036708.1191916263283.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL Parser "eval"
-----------------

                 Key: JBRULES-1262
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1262
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: M H
         Assigned To: Mark Proctor


[when]of type Item=Item()
[when]- Title equals "{value}"=eval(title.isEqual("{value}")
[when]- Event equals "{value}"=eval(id.isEqual("{value}")
[then]Log : "{message}"=System.out.println("{message}");



the dslr File:

expander Test.dsl

rule "Your First Rule"
     when
            $p : of type Item
               - Title equals "test"
               - Event equals "test"
     then
           #actions
end

resolves to (could be seen in the drl viewer)

rule "Your First Rule"

       when
               $p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) )
       then
               #actions

end


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:46:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-161) Overwriting a node in
 the source yields an out-of-sync diagram
In-Reply-To: <28293293.1189441931051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25672452.1191919563426.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-161?page=all ]

Koen Aers updated GPD-161:
--------------------------

    Component/s: jpdl

> Overwriting a node in the source yields an out-of-sync diagram
> --------------------------------------------------------------
>
>                 Key: GPD-161
>                 URL: http://jira.jboss.com/jira/browse/GPD-161
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> 3.1.0cr1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>         Attachments: cheat.txt, processdefinition.xml, websale.par
>
>
> I edited the source xml by pasting in the Decision Node from the cheat.txt (attached) over the "Evaluate web order" found in the example websale process.  When I switched back to visual mode, I found an unattached Decision Node with no name and the "Evaluate web order" remained as before.
> I'll attach the before and after JPDL as well as the substitution text after I open this bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:48:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-162) Deploying a process
 does not pull in necessary Java classes
In-Reply-To: <31205902.1189443251838.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29055941.1191919683400.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-162?page=all ]

Koen Aers updated GPD-162:
--------------------------

    Component/s: jpdl

> Deploying a process does not pull in necessary Java classes
> -----------------------------------------------------------
>
>                 Key: GPD-162
>                 URL: http://jira.jboss.com/jira/browse/GPD-162
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> GPD 3.1.0.CR1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>         Attachments: websale.par
>
>
> When I try to deploy a process from the GPD, the class files referenced in the definition do not come across properly.
> 1) Modified an existing process (as per GPD 161).
> 2) Save the process. (.par will be attached)
> 3) Use the Deployment tab to deploy the updated process.
> 4) Execute the process and you get the following error:
> In the web page:
> Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown.
> On the console:
> 12:48:35,403 ERROR [Delegation] couldn't instantiate delegation class 'org.jbpm.websale.DeciderHandler'
> java.lang.NullPointerException
>         at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105)
>         at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:48)
>         at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:163)
>         at org.jbpm.instantiation.Delegation$$FastClassByCGLIB$$6bae1598.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.instantiation.Delegation$$EnhancerByCGLIB$$a8c02805.instantiate(<generated>)
>         at org.jbpm.graph.node.Decision.execute(Decision.java:87)
>         at org.jbpm.graph.def.Node.enter(Node.java:318)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.enter(<generated>)
>         at org.jbpm.graph.def.Transition.take(Transition.java:151)
>         at org.jbpm.graph.def.Node.leave(Node.java:393)
>         at org.jbpm.graph.node.StartState.leave(StartState.java:70)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.leave(<generated>)
>         at org.jbpm.graph.exe.Token.signal(Token.java:194)
>         at org.jbpm.graph.exe.Token.signal(Token.java:139)
>         at org.jbpm.graph.exe.Token$$FastClassByCGLIB$$74df1c6e.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5a16e027.signal(<generated>)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:476)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:390)
>         at org.jbpm.jsf.core.action.CompleteTaskActionListener.handleAction(CompleteTaskActionListener.java:47)
>         at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82)
>         at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
>         at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758)
>         at javax.faces.component.UICommand.broadcast(UICommand.java:368)
>         at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.broadcast(UITaskFormButtonBase.java:56)
>         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
>         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
>         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
>         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
>         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
>         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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:48:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-154) process image rendered
 incorrectly for large process definition
In-Reply-To: <2916967.1186754521287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22943779.1191919683579.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-154?page=all ]

Koen Aers updated GPD-154:
--------------------------

    Component/s: jpdl

> process image rendered incorrectly for large process definition
> ---------------------------------------------------------------
>
>                 Key: GPD-154
>                 URL: http://jira.jboss.com/jira/browse/GPD-154
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: mac osx,  tomcat 5.0.28
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> Hi,
> then I create a large process, and extend to the left beyond the original boundary, by placing and element in the designer and dragging, so scrollbars appear, the image when rendered in the console is offset incorrectly while on any given node,
> cheers
> Ross

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:48:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-170) misspelling: Assignmnet
In-Reply-To: <814774.1190993382986.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1022536.1191919683712.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-170?page=all ]

Koen Aers updated GPD-170:
--------------------------

    Component/s: jpdl

> misspelling: Assignmnet
> -----------------------
>
>                 Key: GPD-170
>                 URL: http://jira.jboss.com/jira/browse/GPD-170
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Chris Whalen
>         Assigned To: Koen Aers
>
> "Assignment" misspelled on task and swimlane configuration tabs.
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/TaskConfigurationComposite.java   and
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/SwimlaneConfigurationComposite.java

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:53 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 04:50:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1060)
 getInvokedBusinessInterface doesn't return correct interface
Message-ID: <22610729.1191919853782.JavaMail.jira@cloud.prod.atl2.jboss.com>

getInvokedBusinessInterface doesn't return correct interface
------------------------------------------------------------

                 Key: EJBTHREE-1060
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf
         Assigned To: Andrew Rubinger


When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface.

@Stateless
@Remote({Remote1.class, Remote2.class})

interface Remote1 extends CommonRemote

interface Remote2 extends CommonRemote

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:54 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:50:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-168) feature not recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33400339.1191919854215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-168?page=all ]

Koen Aers updated GPD-168:
--------------------------

    Component/s: jpdl

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:55 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:50:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23279965.1191919855121.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

Koen Aers updated GPD-169:
--------------------------

    Component/s: jpdl

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:55 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 04:50:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1060)
 getInvokedBusinessInterface doesn't return correct interface
In-Reply-To: <22610729.1191919853782.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24237381.1191919855520.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1060?page=comments#action_12381130 ] 
            
Carlo de Wolf commented on EJBTHREE-1060:
-----------------------------------------

The invoked interface can be inferred when enc setup is done:

@EJB Remote1 bean;

or

<ejb-ref>
  <remote>Remote1</remote>
</ejb-ref>

> getInvokedBusinessInterface doesn't return correct interface
> ------------------------------------------------------------
>
>                 Key: EJBTHREE-1060
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>
> When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface.
> @Stateless
> @Remote({Remote1.class, Remote2.class})
> interface Remote1 extends CommonRemote
> interface Remote2 extends CommonRemote

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:18:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 9 Oct 2007 05:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
Message-ID: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>

InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
----------------------------------------------------------------------------------

                 Key: JBAS-4805
                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: EJB3
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Galder Zamarreno
         Assigned To: Carlo de Wolf
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA


org.jboss.ejb3.InitialContextFactory.getHAContext() contains:

env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);

The code should not have hardcoded localhost because as soon as someone binds JBoss 
to something different, a localhost lookup will fail.

This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:24:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 05:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17284430.1191921843385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]

Dimitris Andreadis updated JBAS-4805:
-------------------------------------

    Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
                       (was: JBossAS-4.2.2.GA)

Don't set the fix versions!

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:26:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 9 Oct 2007 05:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29505110.1191921963278.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381139 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

Ok, ok, ok... :)

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:46:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 05:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1735) Add metadata to
 include portlet's icons
Message-ID: <4578399.1191923163632.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add metadata to include portlet's icons
---------------------------------------

                 Key: JBPORTAL-1735
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1735
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Thomas Heute
             Fix For: 2.6.3 Final


The Portlet spec doesn't define metadata to specify an icon for a portlet.
We could add this in our vendor specific jboss-portlet.xml descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:54:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 05:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-670) PreDestroy called
 multiple times
In-Reply-To: <14081580.1154512271311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11810544.1191923643943.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-670?page=all ]

Carlo de Wolf updated EJBTHREE-670:
-----------------------------------

    Affects Version/s: EJB 3.0 RC9 - Patch 1

> PreDestroy called multiple times
> --------------------------------
>
>                 Key: EJBTHREE-670
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-670
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD, AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: EJB 3.0 RC9 - FD
>
>
> The PreDestroy callback is called multiple times.
> Once from the container and once from the pool.
> IMHO only the pool should call PreDestroy. 
> Other callbacks are already handled by the pool.
> Unit test is in regression/ejbthree...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:03:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1735) Add metadata to
 include portlet's icons
In-Reply-To: <4578399.1191923163632.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29170130.1191924183226.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1735?page=all ]

Thomas Heute resolved JBPORTAL-1735.
------------------------------------

    Resolution: Done

> Add metadata to include portlet's icons
> ---------------------------------------
>
>                 Key: JBPORTAL-1735
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1735
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> The Portlet spec doesn't define metadata to specify an icon for a portlet.
> We could add this in our vendor specific jboss-portlet.xml descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:14:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1597) i18n display
 name for portlet instances
In-Reply-To: <18247414.1184788607107.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2464530.1191924843392.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1597?page=all ]

Thomas Heute updated JBPORTAL-1597:
-----------------------------------

    Description:     (was: This should be done using declared properties having a key such as $PREFIX.$LOCALE_ID where prefix needs to be determined and locale id is like 'fr_FR'. Also I am worried that getting a cascaded value would be difficult programatically.
)

> i18n display name for portlet instances
> ---------------------------------------
>
>                 Key: JBPORTAL-1597
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1597
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:16:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1736) Site structure
	i18n
Message-ID: <11410482.1191924963437.JavaMail.jira@cloud.prod.atl2.jboss.com>

Site structure i18n
-------------------

                 Key: JBPORTAL-1736
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1736
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final


Portals, pages and windows (portal objects) should be i18nable. (So far only pages are, and not in a good manner)


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:18:18 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:18:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1737) Themes should be
 able to display text with the correct locale
Message-ID: <16743422.1191925098787.JavaMail.jira@cloud.prod.atl2.jboss.com>

Themes should be able to display text with the correct locale
-------------------------------------------------------------

                 Key: JBPORTAL-1737
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1737
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core, Portal Theme
            Reporter: Thomas Heute
         Assigned To: Thomas Heute
             Fix For: 2.6.3 Final


Not sure what's the current state 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

        


From jira-events at lists.jboss.org  Tue Oct  9 07:04:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 07:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1078) TCK strict
	behavior
In-Reply-To: <14693809.1190323871017.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18092347.1191927843345.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1078?page=comments#action_12381148 ] 
            
Tim Fox commented on JBMESSAGING-1078:
--------------------------------------

I have extended this by allowing strictTck to be specified on the server peer and as a system property.

System property if true overrides server peer if true overrides connection factory.

> TCK strict behavior
> -------------------
>
>                 Key: JBMESSAGING-1078
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1078
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Clebert Suconic
>         Assigned To: Andy Taylor
>             Fix For: 1.4.0.GA
>
>         Attachments: testcase.patch
>
>
> By TCK Tests, we should set the JMSDestination on foreign messages, but some providers don't play well with that. (ActiveMQ for instance)
> So, we will create a setting for TCK STrict behavior, for things like setting the destination on Foreign message.
> This will be a setting on ServerPeer or on the ConnectionFactory.
> (I"m attaching a patch for a failing test because 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

        


From jira-events at lists.jboss.org  Tue Oct  9 07:32:03 2007
From: jira-events at lists.jboss.org (David Schlechtweg (JIRA))
Date: Tue, 9 Oct 2007 07:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1738) can not access a
 member of
 class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag
Message-ID: <20884325.1191929523783.JavaMail.jira@cloud.prod.atl2.jboss.com>

can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag
-------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1738
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1738
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Portlet
    Affects Versions: 2.6.2 Final
            Reporter: David Schlechtweg
         Assigned To: Julien Viet


Hi, 
 
i get a IllegalAccessException when i use a jsp tag in freemarker: 
 
<#assign portlet=JspTaglibs["http://java.sun.com/portlet"]>  
<#import "/spring.ftl" as spring /> 
<@portlet.actionURL var="postURL"> 
<@portlet.param name="action" value="newQuery" /> 
</@portlet.actionURL> 
 
I use freemarker 2.3.10 in jboss-portal-2.6.2.GA 
 
java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public" 
The problematic instruction: 
---------- 
==> user-directive portlet.actionURL [on line 3, column 1 in template/search/simple/view.ftl] 
---------- 
 
Java backtrace for programmers: 
---------- 
freemarker.template.TemplateModelException: java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public" 
at freemarker.ext.jsp.TagTransformModel.getWriter(TagTransformModel.java:177) 
at freemarker.core.Environment.visit(Environment.java:220) 
at freemarker.core.UnifiedCall.accept(UnifiedCall.java:116) 
at freemarker.core.Environment.visit(Environment.java:196) 
at freemarker.core.MixedContent.accept(MixedContent.java:92) 
at freemarker.core.Environment.visit(Environment.java:196) 
at freemarker.core.Environment.process(Environment.java:176) 
at freemarker.template.Template.process(Template.java:232) 
at org.springframework.web.servlet.view.freemarker.FreeMarkerView.processTemplate(FreeMarkerView.java:344) 
 
any ideas? 

My hunch is that the class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag is not public, and you're trying to invoke a method on it that though itself is public, it is not declared in any public superclass of GenerateURLTag, or public interface that GenerateURLTag implements.  

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 08:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
Message-ID: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
-----------------------------------------------------------------------------------------------------

                 Key: JBAS-4806
                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: IIOP service
            Reporter: Dimitris Andreadis
         Assigned To: Francisco Reverbel
            Priority: Blocker
             Fix For: JBossAS-4.2.2.GA


I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
string has not been updated, so the jacorb library will still identify itself
as "JacORB 2.3.0 (JBoss patch 4)". See

http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch

While this is a minor thing, it may cause confusion as the version string
is printed out when JacORB is used in a verbose logging level. In order to
avoid support troubles, you guys may want to fix the patch number in the
version string before AS 4.2.2 goes out. *If* you do this, then update also
the patch number in the README file, which is at patch 3:

http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)

Regards,

Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 08:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29957118.1191932283652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4806?page=all ]

Dimitris Andreadis reassigned JBAS-4806:
----------------------------------------

    Assignee: Patrick Macdonald  (was: Francisco Reverbel)

Patrick, who can take up this task, it's relatively urgent.

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Patrick Macdonald
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 08:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4754) Do a full CTS1.4 run
 to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20584642.1191932283832.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4754?page=all ]

Dimitris Andreadis updated JBAS-4754:
-------------------------------------

    Priority: Blocker  (was: Critical)

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:24:03 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 9 Oct 2007 08:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7622546.1191932643243.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-570?page=comments#action_12381157 ] 
            
Vladimir Blagojevic commented on JGRP-570:
------------------------------------------

The best way to rename leftover short lifespan thread names is to use java.util.concurrent.ThreadFactory. We keep ThreadFactory in a well known place (ProtocolStack?) and then anyone who needs a Thread can create it from this factory. When ThreadNamingPattern is sent up the stack it is applied to this ThreadFactory. No need to chase individual threads and rename threads one by one.

Consider moving to 2.7.

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:24:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 09:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
In-Reply-To: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9601184.1191936243281.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1090?page=all ]

Tim Fox updated JBMESSAGING-1090:
---------------------------------

    Issue Type: Feature Request  (was: Bug)
      Priority: Minor  (was: Major)

> Add appropriate Exception handling when hitting MaxSize
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1090
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Jay Howell
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> When using MaxSize for a queue and topic the following behaviors exist
> Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.
> Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.
> What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.
> I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  
> We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  
> Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Tue, 9 Oct 2007 09:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1244) Ruleflows
 should have a package name
In-Reply-To: <20387486.1191370683368.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16372596.1191937683375.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1244?page=comments#action_12381169 ] 
            
Mark Proctor commented on JBRULES-1244:
---------------------------------------

All existing ruleflows will need to have their package name added, or it will fail to load. This should be a standard property, much like how the ruleflow name is added.

> Ruleflows should have a package name
> ------------------------------------
>
>                 Key: JBRULES-1244
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1244
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rule Flow
>            Reporter: Kris Verlaenen
>         Assigned To: Kris Verlaenen
>             Fix For: 4.0.2
>
>
> Ruleflows should be added as part of their own package.
> This allows
>  - adding ruleflows before adding rules
>  - adding only ruleflows to a package

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:52:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 09:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-3441) Request to include
 log4j version 1.2.13 in next JBoss AS release
In-Reply-To: <22073956.1154041931506.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27069502.1191937923301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3441?page=all ]

Dimitris Andreadis closed JBAS-3441.
------------------------------------

    Resolution: Out of Date
      Assignee: Dimitris Andreadis  (was: Scott M Stark)

We have already upgraded 4.2.x and 5.x to log4j 1.2.14, and there is no intention of another 4.0.x version, so this issue is out-of-date.

> Request to include log4j version 1.2.13 in next JBoss AS release
> ----------------------------------------------------------------
>
>                 Key: JBAS-3441
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3441
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: All OS's.
>            Reporter: Khiem Tang
>         Assigned To: Dimitris Andreadis
>
> We have one component that depends on log4j-1.2.13 but the one that ships with JBoss is older. We currently use this log4j version in our JBoss stack and it seems to work fine. It would help us if JBoss put the same version (1.2.13) in the packages.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 09:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2231194.1191938043559.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4806?page=all ]

Dimitris Andreadis reassigned JBAS-4806:
----------------------------------------

    Assignee: Deepak Bhole  (was: Patrick Macdonald)

Deepak, can you look at this task?

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Deepak Bhole
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:03:04 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 9 Oct 2007 10:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-168) feature not
	recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29957323.1191938584394.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-168?page=comments#action_12381174 ] 
            
Ronald van Kuijk commented on GPD-168:
--------------------------------------

I have no problem here... did you do a "eclipse.exe -clean" ? 

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:15:03 2007
From: jira-events at lists.jboss.org (Joachim Neubert (JIRA))
Date: Tue, 9 Oct 2007 10:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-168) feature not
	recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22451414.1191939303311.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-168?page=comments#action_12381177 ] 
            
Joachim Neubert commented on GPD-168:
-------------------------------------

I think I didn't. In the meantime my configuration changed, and now the version delivered with JBoss Tools 2.0 beta4 is up and running.

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:17:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 10:17:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1061) Look into
 StatefulUnitTestCase, determine purpose
Message-ID: <7131874.1191939425385.JavaMail.jira@cloud.prod.atl2.jboss.com>

Look into StatefulUnitTestCase, determine purpose
-------------------------------------------------

                 Key: EJBTHREE-1061
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1061
             Project: EJB 3.0
          Issue Type: Task
    Affects Versions: HEAD
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


Ensure the 7 tests in StatefulUnitTestCase are valid, testing for their intentions, and report any inconsistancies to Brian.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:57:03 2007
From: jira-events at lists.jboss.org (Steve Miner (JIRA))
Date: Tue, 9 Oct 2007 10:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1152) my unit tests
 are hanging with drools 4.0.1
In-Reply-To: <1213410.1188511518355.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19443798.1191941823467.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1152?page=comments#action_12381190 ] 
            
Steve Miner commented on JBRULES-1152:
--------------------------------------

I confirmed that Drools 4.0.2 fixes my problem.  Also, my original unit tests now work again as they did with 4.0.

> my unit tests are hanging with drools 4.0.1
> -------------------------------------------
>
>                 Key: JBRULES-1152
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1152
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>         Environment: Java 1.5, Mac OX X 10.4.10, Drools 4.0.1
>            Reporter: Steve Miner
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>         Attachments: drools1152-v2.zip, drools1152.zip
>
>
> Sorry, I don't have very specific information.  Some of my project's unit tests are hanging with drools 4.0.1.  No error, just not completing.  I tried to debug a bit but could not figure it out.  Consider this an early warning until I can gather more info.
> Everything worked fine with 4.0 so I went back to that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 11:16:04 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 9 Oct 2007 11:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1256) publish source
 jars with maven
In-Reply-To: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18948292.1191942964465.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1256?page=all ]

Fernando Meyer resolved JBRULES-1256.
-------------------------------------

    Resolution: Done

> publish source jars with maven
> ------------------------------
>
>                 Key: JBRULES-1256
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 11:18:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 9 Oct 2007 11:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1259) JBoss Drools
	4.0.2GA Release
In-Reply-To: <32091951.1191890883474.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18993207.1191943083314.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1259?page=all ]

Fernando Meyer resolved JBRULES-1259.
-------------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done

> JBoss Drools 4.0.2GA Release
> ----------------------------
>
>                 Key: JBRULES-1259
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1259
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:13:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 9 Oct 2007 12:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1152) my unit tests are
 hanging with drools 4.0.1
In-Reply-To: <1213410.1188511518355.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11352825.1191946383908.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1152?page=all ]

Edson Tirelli closed JBRULES-1152.
----------------------------------


Thanks for the feedback.

> my unit tests are hanging with drools 4.0.1
> -------------------------------------------
>
>                 Key: JBRULES-1152
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1152
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>         Environment: Java 1.5, Mac OX X 10.4.10, Drools 4.0.1
>            Reporter: Steve Miner
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>         Attachments: drools1152-v2.zip, drools1152.zip
>
>
> Sorry, I don't have very specific information.  Some of my project's unit tests are hanging with drools 4.0.1.  No error, just not completing.  I tried to debug a bit but could not figure it out.  Consider this an early warning until I can gather more info.
> Everything worked fine with 4.0 so I went back to that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:31:20 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 12:31:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
Message-ID: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>

Potential deadlock in shutting down server
------------------------------------------

                 Key: JBMESSAGING-1099
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:39:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 9 Oct 2007 12:39:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9365565.1191947944280.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Anil Saldhana updated JBMESSAGING-1099:
---------------------------------------

    Priority: Critical  (was: Major)

I have to make this issue "Critical" because I have seen the case when JMS destination authorization fails, the server just hangs.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:51:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 12:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28917374.1191948663447.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12381223 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

If you can replicate this, please add instructions to this task.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1034) Port
 ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to
 Branch_4_2
In-Reply-To: <22376933.1187730452121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13780659.1191953403574.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1034?page=all ]

Carlo de Wolf updated EJBTHREE-1034:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2
> ------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1034
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1034
>             Project: EJB 3.0
>          Issue Type: Patch
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Frank Langelage
>             Fix For: Branch_4_2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Port the changes made on ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java in Head to Branch 4.2.
> Using an ear with seperated session and entity beans (different ejb-modules) I got the exception "There is no default persistence nit in this deployment." when using "@PersistenceContext private EntityManager entityManager;" in my Session Bean.
> Using the head version of the source file within my 4.2.2.GA cvs checkout the problem went away.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1034) Port
 ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to
 Branch_4_2
In-Reply-To: <22376933.1187730452121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4664691.1191953403848.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1034?page=all ]

Carlo de Wolf updated EJBTHREE-1034:
------------------------------------

     Original Estimate:     (was: 1 hour)
    Remaining Estimate:     (was: 1 hour)
            Complexity:   (was: Low)

> Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2
> ------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1034
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1034
>             Project: EJB 3.0
>          Issue Type: Patch
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Frank Langelage
>             Fix For: Branch_4_2
>
>
> Port the changes made on ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java in Head to Branch 4.2.
> Using an ear with seperated session and entity beans (different ejb-modules) I got the exception "There is no default persistence nit in this deployment." when using "@PersistenceContext private EntityManager entityManager;" in my Session Bean.
> Using the head version of the source file within my 4.2.2.GA cvs checkout the problem went away.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:16:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 14:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1100) Non durable
 topic
 subscribers with noLocal=true  result in message build up on server
Message-ID: <8358901.1191953763435.JavaMail.jira@cloud.prod.atl2.jboss.com>

Non durable topic subscribers with noLocal=true  result in message build up on server
-------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1100
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1100
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


If you create a non durable topic subscription with noLocal = true, then send a lot of local messages. They build in the subscription queue on the server.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:16:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
Message-ID: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>

Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
----------------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1062
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


The following doesn't work:

@Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}

interface ExpectedLocalInterface {}

class SuperBean implements OtherInterface {}

interface OtherInterface {}

Based on the spec ExpectedLocalInterface is expected to become the local business interface.

EJB 3 4.6.6:
If bean class implements a single interface, that interface is assumed to be the busi-
ness interface of the bean. This business interface will be a local interface unless the
interface is designated as a remote business interface by use of the Remote annota-
tion on the bean class or interface or by means of the deployment descriptor.


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:18:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1061) Look into
 StatefulUnitTestCase, determine purpose
In-Reply-To: <7131874.1191939425385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26175540.1191953883419.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1061?page=all ]

Carlo de Wolf updated EJBTHREE-1061:
------------------------------------

    Affects Version/s:     (was: HEAD)

> Look into StatefulUnitTestCase, determine purpose
> -------------------------------------------------
>
>                 Key: EJBTHREE-1061
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1061
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Ensure the 7 tests in StatefulUnitTestCase are valid, testing for their intentions, and report any inconsistancies to Brian.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:35:07 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 14:35:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1100) Non durable
 topic
 subscribers with noLocal=true  result in message build up on server
In-Reply-To: <8358901.1191953763435.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10899956.1191954907149.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1100?page=all ]

Tim Fox closed JBMESSAGING-1100.
--------------------------------

    Resolution: Done

> Non durable topic subscribers with noLocal=true  result in message build up on server
> -------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1100
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1100
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> If you create a non durable topic subscription with noLocal = true, then send a lot of local messages. They build in the subscription queue on the server.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:52:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 9 Oct 2007 14:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1033) Add EJB2.x JMX
 metrics to EJB3
In-Reply-To: <19347205.1187704052441.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4022292.1191955923379.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1033?page=all ]

William DeCoste resolved EJBTHREE-1033.
---------------------------------------

    Resolution: Done

> Add EJB2.x JMX metrics to EJB3
> ------------------------------
>
>                 Key: EJBTHREE-1033
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1033
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: EJB 3.0 RC9 - Patch 1
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 5.0.0.Beta3
>
>
> Stateless: AvailableCount, MaxSize, CurrentSize, CreateCount, RemoveCount
> Stateful: CacheSize, PassivatedCount, CreateCount, RemoveCount, AvailableSize, CurrentSize, MaxSize
> MDB: MinPoolSize, MaxPoolSize, MaxMessages, KeepAliveMillis

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:06:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes for Anil
Message-ID: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure EJBSpecUnitTestCase Passes for Anil
------------------------------------------

                 Key: EJBTHREE-1063
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
             Project: EJB 3.0
          Issue Type: Task
    Affects Versions: HEAD
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:06:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15538771.1191960365795.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=all ]

Andrew Rubinger updated EJBTHREE-1063:
--------------------------------------

    Summary: Ensure EJBSpecUnitTestCase Passes  (was: Ensure EJBSpecUnitTestCase Passes for Anil)

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:08:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:08:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23116809.1191960485547.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=comments#action_12381263 ] 
            
Andrew Rubinger commented on EJBTHREE-1063:
-------------------------------------------

Prioritize successful deployment of test case archives

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:16:07 2007
From: jira-events at lists.jboss.org (Deepak Bhole (JIRA))
Date: Tue, 9 Oct 2007 16:16:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8847648.1191960967212.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4806?page=all ]

Deepak Bhole resolved JBAS-4806.
--------------------------------

    Resolution: Done

New jacorb has been uploaded to repository. There were differences in the following classes:

org/jacorb/idl/IdlSymbol.class
org/jacorb/idl/parser.class
org/jacorb/orb/giop/CodeSet.class
org/jacorb/orb/ORB.class
org/jacorb/orb/portableInterceptor/ORBInitInfoImpl.class
org/jacorb/util/BuildVersion.class
org/jacorb/util/Version.class

jcf-dump shows that all differences are either related to the version string, or the build time, both of which are acceptable.

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Deepak Bhole
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:26:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23523610.1191961563894.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Andrew Rubinger reopened EJBTHREE-785:
--------------------------------------

             
After reinterpretation on forum, going to remove from tests the bearing of interface hierarchy, and instead focus on the following construct:

@Remote
public interface MyBusiness{}

public MySuper implements MyBusiness{}

@Stateless
public class MyBusinessBean extends MySuper{}





> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 17:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 17:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13475808.1191963663621.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4806?page=comments#action_12381280 ] 
            
Dimitris Andreadis commented on JBAS-4806:
------------------------------------------

Thanks!

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Deepak Bhole
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 17:04:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 17:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4657) Upgrade JBossWeb
 to 2.1.0.CR4 (from 2.0.1.CR7)
In-Reply-To: <614928.1188830958251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14427164.1191963843380.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4657?page=comments#action_12381281 ] 
            
Dimitris Andreadis commented on JBAS-4657:
------------------------------------------

Using 2.1.0.CR6

> Upgrade JBossWeb to 2.1.0.CR4 (from 2.0.1.CR7)
> ----------------------------------------------
>
>                 Key: JBAS-4657
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4657
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>            Reporter: Dimitris Andreadis
>         Assigned To: Remy Maucherat
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Component upgrades need to be tracked in JIRA.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 17:11:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 17:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4716) Update common-core to
	2.2.2.GA
In-Reply-To: <9279917.1189681040331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3819762.1191964263468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4716?page=all ]

Dimitris Andreadis closed JBAS-4716.
------------------------------------

    Resolution: Done

Done

> Update common-core to 2.2.2.GA
> ------------------------------
>
>                 Key: JBAS-4716
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4716
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Common-core has fixes we need. Since further fixes are possible maybe move to a 2.2.2-snapshot release first.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:33:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-817) Release 2.2.2.SP2
Message-ID: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>

Release 2.2.2.SP2
-----------------

                 Key: JBREM-817
                 URL: http://jira.jboss.com/jira/browse/JBREM-817
             Project: JBoss Remoting
          Issue Type: Release
      Security Level: Public (Everyone can see)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-811) Privileged Block
 to create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5987584.1191969543594.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-811?page=comments#action_12381294 ] 
            
Ron Sigal commented on JBREM-811:
---------------------------------

Fix applied to branch remoting_2_2_0_GA for release 2.2.2.SP2.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA, 2.4.0.Beta1 (Pinto)
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.2.2.GA_CP01, 2.2.2.SP2, 2.4.0.Beta1 (Pinto)
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-817) Release 2.2.2.SP2
In-Reply-To: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32006576.1191969543360.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-817?page=all ]

Ron Sigal updated JBREM-817:
----------------------------

        Fix Version/s: 2.2.2.SP2
    Affects Version/s: 2.2.2.SP2

> Release 2.2.2.SP2
> -----------------
>
>                 Key: JBREM-817
>                 URL: http://jira.jboss.com/jira/browse/JBREM-817
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:41:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13059570.1191969663380.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381296 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Fix applied to branch remoting_2_2_0_GA for release 2.2.2.SP2.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 19:46:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Tue, 9 Oct 2007 19:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1739) Replace use to
 QName constuctor to use of QName.valueOf where appropriate.
Message-ID: <25711751.1191973563369.JavaMail.jira@cloud.prod.atl2.jboss.com>

Replace use to QName constuctor to use of QName.valueOf where appropriate.
--------------------------------------------------------------------------

                 Key: JBPORTAL-1739
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1739
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core, Portal WSRP
    Affects Versions: 2.6.3 Final, 2.8 Final
            Reporter: Chris Laprun
         Assigned To: Chris Laprun
            Priority: Minor
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 21:36:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Tue, 9 Oct 2007 21:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-453)
 maven-jbossaop-plugin requires
 artifact maven-jbossaop-plugin on compile classpath
In-Reply-To: <31000254.1186523875263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20921485.1191980163557.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-453?page=comments#action_12381313 ] 
            
Jason T. Greene commented on JBAOP-453:
---------------------------------------

This plugin _MUST_ use  the projects dependencies.  Otherwise how can AOP process all known class files?

Consider the simple scenario of a project class inheriting a class in a dependent library. Since the classpath only contains the output directory, it will not be loaded, and thus aopc will fail. If you define all of this in the plugin config, then will end up duplicating every dependency in your project twice.

> maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath
> ----------------------------------------------------------------------------------
>
>                 Key: JBAOP-453
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-453
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: maven 2
>            Reporter: Anders Andersen
>         Assigned To: Stale Pedersen
>
> In order to use the plugin I have to add the following dependencies to the client artifact dependency list.
>     <dependency>
>       <groupId>org.jboss.maven.plugins</groupId>
>       <artifactId>maven-jbossaop-plugin</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-aop</artifactId>
>       <version>2.0.0.alpha2</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-common</artifactId>
>       <version>4.0.2</version>
>     </dependency>
>     <dependency>
>       <groupId>concurrent</groupId>
>       <artifactId>concurrent</artifactId>
>       <version>1.3.4</version>
>     </dependency>
> This is relative wrong, because all maven internal artifacts ends up being nested dependent om the runtime artifact.
> See lists below.
> I think the statement
>       cl.addArguments(new String[] { "-cp", createClassPathList(project.getArtifacts())});
> is wrong.
> I tried to include only project.getPluginArtifacts(), but it gave me a NPE
> So I am not 100% sure what the code solution should be
> but it is not good to having maven artifacts in the resulting dependency list of the client-artifact
> list: (resulting depenency list)
> The ** marked should not be there
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.jar
> /Users/aka/.m2/repository/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-opends/2.6.1-SNAPSHOT/portal-test-opends-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/isorelax/isorelax/20020414/isorelax-20020414.jar
> /Users/aka/.m2/repository/jgroups/jgroups-all/2.2.7/jgroups-all-2.2.7.jar
> /Users/aka/.m2/repository/jboss/jboss-common/4.0.2/jboss-common-4.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-xml-binding/5.0.0.Alpha/jboss-xml-binding-5.0.0.Alpha.jar
> /Users/aka/.m2/repository/jboss/jboss-cache/1.2.2/jboss-cache-1.2.2.jar
> /Users/aka/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar
> /Users/aka/.m2/repository/jboss/jboss-j2se/200504122039/jboss-j2se-200504122039.jar
> /Users/aka/.m2/repository/jboss/jbossha/4.0.2/jbossha-4.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-minimal/4.0.2/jboss-minimal-4.0.2.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-common-client/4.0.4.GA/jboss-common-client-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server/2.6.1-SNAPSHOT/portal-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-saaj/4.0.4.GA/jboss-saaj-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-system/4.0.4.GA/jboss-system-4.0.4.GA.jar
> /Users/aka/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar
> /Users/aka/.m2/repository/org/jboss/portal/core/portal-core/2.6.1-SNAPSHOT/portal-core-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/javassist/3.4.ga/javassist-3.4.ga.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test/2.6.1-SNAPSHOT/portal-test-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/format/portal-format/2.6.1-SNAPSHOT/portal-format-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.jar
> /Users/aka/.m2/repository/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar
> /Users/aka/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> /Users/aka/.m2/repository/jboss/jboss-system/4.0.2/jboss-system-4.0.2.jar
> /Users/aka/.m2/repository/javax/mail/mail/1.4/mail-1.4.jar
> /Users/aka/.m2/repository/hibernate/hibernate/3.2.0/hibernate-3.2.0.jar
> /Users/aka/.m2/repository/jboss/jboss-j2ee/4.0.4.GA/jboss-j2ee-4.0.4.GA.jar
> /Users/aka/.m2/repository/jaxen/jaxen/1.0-FCS/jaxen-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server-test-framework/2.6.1-SNAPSHOT/portal-server-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-project/2.0.2/maven-project-2.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-microcontainer/4.0.4.GA/jboss-microcontainer-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common/2.6.1-SNAPSHOT/portal-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/selenium/selenium-java-client-driver/0.0/selenium-java-client-driver-0.0.jar
> /Users/aka/.m2/repository/javax/portlet/portlet-api/1.0/portlet-api-1.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/theme/portal-theme/2.6.1-SNAPSHOT/portal-theme-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.jar
> /Users/aka/.m2/repository/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss/4.0.4.GA/jboss-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
> /Users/aka/.m2/repository/wsdl4j/wsdl4j/1.5.1/wsdl4j-1.5.1.jar
> /Users/aka/.m2/repository/concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/jboss/jboss-backport-concurrent/2.1.0.GA/jboss-backport-concurrent-2.1.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jbosssx/4.0.4.GA/jbosssx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> /Users/aka/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> /Users/aka/.m2/repository/trove/trove/1.1-beta-5/trove-1.1-beta-5.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/2.0.0.alpha2/jboss-aop-2.0.0.alpha2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-model/2.0.2/maven-model-2.0.2.jar
> /Users/aka/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar
> /Users/aka/.m2/repository/log4j/log4j/1.2.8/log4j-1.2.8.jar
> /Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet/2.6.1-SNAPSHOT/portal-portlet-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/jboss-aspect-library/1.5/jboss-aspect-library-1.5.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-server/portal-portlet-server/2.6.1-SNAPSHOT/portal-portlet-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jmx/4.0.4.GA/jboss-jmx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-impl/1.1.1/myfaces-impl-1.1.1.jar
> /Users/aka/.m2/repository/org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/jboss-aop/1.5.0.GA/jboss-aop-1.5.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common-junit/2.6.1-SNAPSHOT/portal-common-junit-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-profile/2.0.2/maven-profile-2.0.2.jar
> /Users/aka/.m2/repository/org/visigoths/freemaker/freemarker/2.3.9/freemarker-2.3.9.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-agent/2.6.1-SNAPSHOT/portal-test-agent-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-dependency/4.0.4.GA/jboss-dependency-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-federation/portal-portlet-federation/2.6.1-SNAPSHOT/portal-portlet-federation-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/msv/msv/20020414/msv-20020414.jar
> /Users/aka/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
> /Users/aka/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
> /Users/aka/.m2/repository/slide/webdavlib/2.0/webdavlib-2.0.jar
> **/Users/aka/.m2/repository/org/jboss/maven/plugins/maven-jbossaop-plugin/1.0-SNAPSHOT/maven-jbossaop-plugin-1.0-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/web/portal-web/2.6.1-SNAPSHOT/portal-web-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-api/1.1.1/myfaces-api-1.1.1.jar
> /Users/aka/.m2/repository/org/jboss/portal/wsrp/portal-wsrp-gen/2.6.1-SNAPSHOT/portal-wsrp-gen-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/jems/portal-jems/2.6.1-SNAPSHOT/portal-jems-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/registration/portal-registration/2.6.1-SNAPSHOT/portal-registration-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jaxrpc/4.0.4.GA/jboss-jaxrpc-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/security/portal-security/2.6.1-SNAPSHOT/portal-security-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/api/portal-api/2.6.1-SNAPSHOT/portal-api-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar
> /Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> /Users/aka/.m2/repository/dom4j/dom4j/1.4/dom4j-1.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/identity/portal-identity/2.6.1-SNAPSHOT/portal-identity-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/explode-common/2.6.1-SNAPSHOT/explode-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet-test-framework/2.6.1-SNAPSHOT/portal-portlet-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.2/plexus-utils-1.4.2.jar
> /Users/aka/.m2/repository/jboss/jnpserver/3.2.3/jnpserver-3.2.3.jar
> /Users/aka/.m2/repository/opends/opends/0.0/opends-0.0.jar

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 21:59:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Tue, 9 Oct 2007 21:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1254)
 drools-repository/jbrms
 should not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28058368.1191981543284.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=comments#action_12381315 ] 
            
Michael Neale commented on JBRULES-1254:
----------------------------------------

What geoffrey says makes sense. but 99% of the time they will use the war as a "self contained" unit anyway. 

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 22:56:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 22:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-817) Release 2.2.2.SP2
In-Reply-To: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8292922.1191984963265.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-817?page=comments#action_12381318 ] 
            
Ron Sigal commented on JBREM-817:
---------------------------------

A 2.2.2.SP2 directory has been created in the repository, with a jboss-remoting.jar built with jdk 1.4.

> Release 2.2.2.SP2
> -----------------
>
>                 Key: JBREM-817
>                 URL: http://jira.jboss.com/jira/browse/JBREM-817
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.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

        


From jira-events at lists.jboss.org  Tue Oct  9 22:58:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 22:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21211517.1191985083220.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381319 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

The default behavior remains the same.  To get the new behavior, the server should be configured with the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.RETURN_EXCEPTION (actual value "return-exception")  set to true.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 23:08:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 23:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4714) Upgrade
 JBossRemoting to 2.2.2.SP1 (from 2.2.0.GA)
In-Reply-To: <17799303.1189663991032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13703743.1191985683485.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4714?page=all ]

Ron Sigal reopened JBAS-4714:
-----------------------------

             
Remoting 2.2.2.SP2 is now available.  It includes fixes for the following:

JBREM-687: allow binding to 0.0.0.0	 
JBREM-811: Privileged Block to create Class Loader 	 
JBREM-813: ServletServerInvoker should return an exception instead of just an error message

> Upgrade JBossRemoting to 2.2.2.SP1 (from 2.2.0.GA)
> --------------------------------------------------
>
>                 Key: JBAS-4714
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4714
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The upgrade from Remoting 2.2.0.GA to 2.2.2.GA is occasioned largely by a set of features and fixes for JBossMessaging 1.4. 
> The further upgrade to 2.2.2.SP1 consists of fixes for JBREM-653 and JBREM-750.  The fix for JBREM-750 was supposed to go into 2.2.2.GA but was overlooked.  The fix for JBREM-653 is needed for ESB 4.2.1.
> These fixes have been applied to the remoting_2_2_0_GA branch from which 2.2.2.GA was released.  As soon as the related unit tests pass on cruisecontrol, the branch will be tagged remoting_2_2_2_SP1.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 01:02:12 2007
From: jira-events at lists.jboss.org (Peter Lynch (JIRA))
Date: Wed, 10 Oct 2007 01:02:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12029956.1191992532506.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381325 ] 
            
Peter Lynch commented on JBRULES-1260:
--------------------------------------

I can confirm this happened for me as well with the same setup.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 01:14:03 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Wed, 10 Oct 2007 01:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19845735.1191993243344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=all ]

Joshua Jackson reopened JBRULES-1260:
-------------------------------------

             
Can we please re-test this again as another user has confirmed that this also happens to him.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 02:03:04 2007
From: jira-events at lists.jboss.org (Roland Bali (JIRA))
Date: Wed, 10 Oct 2007 02:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4491) Server startup
 failure with JDK 1.6
In-Reply-To: <30746220.1182198611683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20003992.1191996184791.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12381328 ] 
            
Roland Bali commented on JBAS-4491:
-----------------------------------

This might be obvious since it seems to be a 1.6 bug but the error persists on JDK 1.6.0_03-b05 in Windows.

> Server startup failure with JDK 1.6
> -----------------------------------
>
>                 Key: JBAS-4491
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4491
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: Windows
>            Reporter: Greg Zoller
>         Attachments: Signature.java
>
>
> An out-of-the-box installation of JBoss 5.0.0 Beta2 running with JDK 1.6 produces the following exception upon startup.  Not sure the whys or wherefores but am pretty sure its not a good thing.
> 13:24:13,467 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
> 13:24:13,467 INFO  [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017)
> 13:24:13,467 INFO  [ServerImpl] Home Dir: C:\Program Files\jboss-5.0.0.Beta2
> 13:24:13,467 INFO  [ServerImpl] Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/
> 13:24:13,467 INFO  [ServerImpl] Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/lib/
> 13:24:13,467 INFO  [ServerImpl] Patch URL: null
> 13:24:13,467 INFO  [ServerImpl] Server Name: default
> 13:24:13,467 INFO  [ServerImpl] Server Home Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:13,467 INFO  [ServerImpl] Server Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/
> 13:24:13,467 INFO  [ServerImpl] Server Data Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\data
> 13:24:13,467 INFO  [ServerImpl] Server Temp Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\tmp
> 13:24:13,467 INFO  [ServerImpl] Server Config URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/
> 13:24:13,467 INFO  [ServerImpl] Server Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/lib/
> 13:24:13,467 INFO  [ServerImpl] Root Deployment Filename: jboss-service.xml
> 13:24:13,499 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml
> 13:24:14,831 INFO  [ProfileImpl] Using profile root:C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:15,913 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter state=Described
> java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125)
> 	at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292)
> 	at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138)
> 	at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280)
> 	at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
> 	at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
> 	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
> 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
> 	at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBootstrap.java:295)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:222)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at java.net.URLClassLoader$1.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170)
> 	... 35 more
> 13:24:16,258 INFO  [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
> 13:24:16,305 INFO  [JMXKernel] Legacy JMX core initialized
> Failed to boot JBoss:
> java.lang.RuntimeException: Exception during Bootstrap
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
> VFSBootstrapScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeployerScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeploymentScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> *** CONTEXTS IN ERROR: Name -> Error
> DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileServiceBootstrap.java:389)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	... 5 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 02:28:03 2007
From: jira-events at lists.jboss.org (Tuomas Kiviaho (JIRA))
Date: Wed, 10 Oct 2007 02:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1263) Mark
 xml-apis/xercesImpl as
 optional dependencies in drools-compiler pom.xml
Message-ID: <31321311.1191997683967.JavaMail.jira@cloud.prod.atl2.jboss.com>

Mark xml-apis/xercesImpl as optional dependencies in drools-compiler pom.xml
----------------------------------------------------------------------------

                 Key: JBRULES-1263
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1263
             Project: JBoss Drools
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Tuomas Kiviaho
         Assigned To: Mark Proctor


As commented in JBRULES-992 jdk provides xml-apis already so the declaration could be marked as optional or dropped completely. Marking of xercesImpl as optional requires compile time dependency check. Dropping it completely requires also verification that it isn't used anywhere at runtime.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:02:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 04:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1073) JMS messages
 are not taken from the queue after database connection recovery
In-Reply-To: <22436968.1190115251065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9566890.1192003323317.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1073?page=all ]

Tim Fox closed JBMESSAGING-1073.
--------------------------------

    Resolution: Cannot Reproduce Bug

User cannot reproduce with 1.4.0.GA

> JMS messages are not taken from the queue after database connection recovery
> ----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1073
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1073
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.3.0.GA
>         Environment: JBoss.4.2.1 JBossMessaging 1.3GA Oracle 10g database jdk 1.5 on solaris intel
>            Reporter: Evgueni Smoliar
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> We have  2 jboss server running in the cluster. Messaging is also configured with clustered queues. 
> At one moment we had a database crash. Database was recovered in 5 minutes and connections from jboss were reestablished . All applications works OK, new messages processed correctly. The problem is with the messages processed during the crash time. JMS could not commit them and couldn't rollback at the time. After reestablishing of the connection this messages are not redelivered anymore. 
> The only way to get those message delivered is to restart jboss servers. 
> This is strange problem which we never experienced with old jboss-jms implementation.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:38:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 10 Oct 2007 04:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29327421.1192005483526.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Carlo de Wolf updated EJBTHREE-1062:
------------------------------------

    Priority: Critical  (was: Major)

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>            Priority: Critical
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:40:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 10 Oct 2007 04:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12312897.1192005603702.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Carlo de Wolf reassigned EJBTHREE-1062:
---------------------------------------

    Assignee: Andrew Rubinger

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:40:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 10 Oct 2007 04:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32689183.1192005603888.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Carlo de Wolf updated EJBTHREE-1062:
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 05:41:05 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 05:41:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1740) cms admin
 portlet checks for hardcoded role named 'admin'
Message-ID: <26476529.1192009265578.JavaMail.jira@cloud.prod.atl2.jboss.com>

cms admin portlet checks for hardcoded role named 'admin'
---------------------------------------------------------

                 Key: JBPORTAL-1740
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1740
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final
            Reporter: Tobias Roth
         Assigned To: Sohil Shah


See also http://jira.jboss.com/jira/browse/JBPORTAL-1646

I found another hardcoded use of 'admin'. The effect of having this is that even with the change I described above, permissions of cms nodes cannot be changed by users that are not in role called 'admin'.

Why does the security console need to have separate access rights? Aren't the access rights for the CMS admin console enough?



In core-cms/src/main/org/jboss/portal/core/cms/ui/admin/CMSAdminPortlet.java:

   private boolean isSecurityConsoleAccessible(PortletRequest portletRequest)
   {
      try
      {
         boolean isAccessible = false;

         if (portletRequest.getUserPrincipal() != null)
         {
            User user = this.userModule.findUserByUserName(portletRequest.getUserPrincipal().getName());
            Set roles = this.membershipModule.getRoles(user);
            if (roles != null)
            {
               for (Iterator itr = roles.iterator(); itr.hasNext();)
               {
                  Role role = (Role)itr.next();
                  if (role.getName().equalsIgnoreCase("admin"))
                  {
                     isAccessible = true;
                     break;
                  }
               }
            }
         }

         return isAccessible;
      }
      catch (Exception e)
      {
         return false;
      }
   }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 05:45:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 05:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17984461.1192009503474.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_12381366 ] 
            
Tobias Roth commented on JBPORTAL-1733:
---------------------------------------

I just created JBPORTAL-1740. Sorry, didn't see this one.

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 05:47:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 05:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1740) cms admin
 portlet checks for hardcoded role named 'admin'
In-Reply-To: <26476529.1192009265578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33063901.1192009623838.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1740?page=comments#action_12381368 ] 
            
Tobias Roth commented on JBPORTAL-1740:
---------------------------------------

Sorry, this is a duplicate for JBPORTAL-1733. I have more info in here though.

> cms admin portlet checks for hardcoded role named 'admin'
> ---------------------------------------------------------
>
>                 Key: JBPORTAL-1740
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1740
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>
> See also http://jira.jboss.com/jira/browse/JBPORTAL-1646
> I found another hardcoded use of 'admin'. The effect of having this is that even with the change I described above, permissions of cms nodes cannot be changed by users that are not in role called 'admin'.
> Why does the security console need to have separate access rights? Aren't the access rights for the CMS admin console enough?
> In core-cms/src/main/org/jboss/portal/core/cms/ui/admin/CMSAdminPortlet.java:
>    private boolean isSecurityConsoleAccessible(PortletRequest portletRequest)
>    {
>       try
>       {
>          boolean isAccessible = false;
>          if (portletRequest.getUserPrincipal() != null)
>          {
>             User user = this.userModule.findUserByUserName(portletRequest.getUserPrincipal().getName());
>             Set roles = this.membershipModule.getRoles(user);
>             if (roles != null)
>             {
>                for (Iterator itr = roles.iterator(); itr.hasNext();)
>                {
>                   Role role = (Role)itr.next();
>                   if (role.getName().equalsIgnoreCase("admin"))
>                   {
>                      isAccessible = true;
>                      break;
>                   }
>                }
>             }
>          }
>          return isAccessible;
>       }
>       catch (Exception e)
>       {
>          return false;
>       }
>    }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:00:03 2007
From: jira-events at lists.jboss.org (Alexandre Gattiker (JIRA))
Date: Wed, 10 Oct 2007 06:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
Message-ID: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
------------------------------------------------------------------

                 Key: JBRULES-1264
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Alexandre Gattiker
         Assigned To: Mark Proctor


Removing one of the three rules magically solves the problem.


java.lang.NullPointerException
	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
	at com.sample.DroolsTest.main(DroolsTest.java:21)




package com.sample;

import java.io.InputStreamReader;
import java.io.Reader;

import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;

public class DroolsTest
{

    public static final void main(String[] args)
    {
        try
        {
            RuleBase ruleBase = readRule();
            WorkingMemory workingMemory = ruleBase.newStatefulSession();
            workingMemory.insert(new Attribute());
            workingMemory.insert(new Message());
            workingMemory.fireAllRules();
        }
        catch (Throwable t)
        {
            t.printStackTrace();
        }
    }

    private static RuleBase readRule() throws Exception
    {
        Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
        PackageBuilder builder = new PackageBuilder();
        builder.addPackageFromDrl(source);
        Package pkg = builder.getPackage();
        RuleBase ruleBase = RuleBaseFactory.newRuleBase();
        ruleBase.addPackage(pkg);
        return ruleBase;
    }

    public static class Message
    {
        //empty
    }

    public static class Attribute
    {

        public Integer getValue()
        {
            return null;
        }

    }

}


package com.sample
 
import com.sample.DroolsTest.Message;
import com.sample.DroolsTest.Attribute;
 
rule "rule_1"
	
	when
		Message()
		Attribute(value == 1)
	then
		System.err.println("case 1");
end

rule "rule_2"
	
	when
		Message()
		Attribute(value == 2)
	then
		System.err.println("case 2");
end


rule "rule_3"
	
	when
		Message()
		$a:Attribute(value == 3)
	then
		System.err.println("case 3");
end


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:53:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Wed, 10 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1741) PortalURL
 security not honoured
Message-ID: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>

PortalURL security not honoured
-------------------------------

                 Key: JBPORTAL-1741
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core
    Affects Versions: 2.6.2 Final, 2.6.1 Final, 2.6 Final, 2.6.3 Final
            Reporter: Julien Viet
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final
         Attachments: PortalURLSecurity.zip

PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:53:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Wed, 10 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18667168.1192013583422.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Julien Viet updated JBPORTAL-1741:
----------------------------------

    Attachment: PortalURLSecurity.zip

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:55:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 06:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27991976.1192013703290.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Thomas Heute reassigned JBPORTAL-1741:
--------------------------------------

    Assignee: Thomas Heute  (was: Julien Viet)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:57:19 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Wed, 10 Oct 2007 06:57:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7278496.1192013839923.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Julien Viet updated JBPORTAL-1741:
----------------------------------

    Priority: Critical  (was: Major)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Thomas Heute
>            Priority: Critical
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:05:13 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 10 Oct 2007 07:05:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4714) Upgrade
 JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)
In-Reply-To: <17799303.1189663991032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22772019.1192014313382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4714?page=all ]

Dimitris Andreadis updated JBAS-4714:
-------------------------------------

    Summary: Upgrade JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)  (was: Upgrade JBossRemoting to 2.2.2.SP1 (from 2.2.0.GA))

> Upgrade JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)
> --------------------------------------------------
>
>                 Key: JBAS-4714
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4714
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The upgrade from Remoting 2.2.0.GA to 2.2.2.GA is occasioned largely by a set of features and fixes for JBossMessaging 1.4. 
> The further upgrade to 2.2.2.SP1 consists of fixes for JBREM-653 and JBREM-750.  The fix for JBREM-750 was supposed to go into 2.2.2.GA but was overlooked.  The fix for JBREM-653 is needed for ESB 4.2.1.
> These fixes have been applied to the remoting_2_2_0_GA branch from which 2.2.2.GA was released.  As soon as the related unit tests pass on cruisecontrol, the branch will be tagged remoting_2_2_2_SP1.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:07:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 07:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1646) portal-cms
 depends on existence of user 'admin'
In-Reply-To: <23503800.1187790682411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32935949.1192014423344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1646?page=all ]

Thomas Heute updated JBPORTAL-1646:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> portal-cms depends on existence of user 'admin'
> -----------------------------------------------
>
>                 Key: JBPORTAL-1646
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1646
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> cms/src/main/org/jboss/portal/cms/impl/jcr/JCRCMS.java has the user 'admin' hardcoded:
>    /** Loads content from sar and adds it to the repo. */
>    public void createContent() throws Exception
>    {
>       log.info("Creating default CMS content.");
>       
>       // Get the content
>       URL root = Thread.currentThread().getContextClassLoader().getResource(defaultContentLocation);
>       
>       //make the user executing these to create the default content, an 'Admin' user
>       //without this, the fine grained security won't allow the creation
>       UserModule userModule = getUserModule();
>       if(userModule != null)
>       {
> 	      org.hibernate.Session session = org.jboss.portal.cms.hibernate.state.Tools.getOpenSession();
> 	      org.hibernate.Transaction tx = session.beginTransaction();
> 	      User user = userModule.findUserByUserName("admin"); // HERE
> 	      if(user!=null)
> 	      {
> 	    	  JCRCMS.getUserInfo().set(user);
> 	      }
> 	      tx.rollback();
> 	      org.jboss.portal.cms.hibernate.state.Tools.closeSession(session);
>       }	
> If it doesn't exist (for example because LDAP is being used), portal-cms cannopt be deployed, and several database tables are not created. If 'admin' is changed to an existing user, everything works fine.
> There is another reference to 'admin' in cms/src/main/org/jboss/portal/cms/impl/jcr/command/ACLEnforcer.java, but leaving this as it is doesn't seem to have any negative effect.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:11:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1646) portal-cms
 depends on existence of user 'admin'
In-Reply-To: <23503800.1187790682411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4513258.1192014663344.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1646?page=comments#action_12381377 ] 
            
Tobias Roth commented on JBPORTAL-1646:
---------------------------------------

This is not the same as 1733 and 1740. This issue is unique, while 1733 and 1740 are the same.

> portal-cms depends on existence of user 'admin'
> -----------------------------------------------
>
>                 Key: JBPORTAL-1646
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1646
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> cms/src/main/org/jboss/portal/cms/impl/jcr/JCRCMS.java has the user 'admin' hardcoded:
>    /** Loads content from sar and adds it to the repo. */
>    public void createContent() throws Exception
>    {
>       log.info("Creating default CMS content.");
>       
>       // Get the content
>       URL root = Thread.currentThread().getContextClassLoader().getResource(defaultContentLocation);
>       
>       //make the user executing these to create the default content, an 'Admin' user
>       //without this, the fine grained security won't allow the creation
>       UserModule userModule = getUserModule();
>       if(userModule != null)
>       {
> 	      org.hibernate.Session session = org.jboss.portal.cms.hibernate.state.Tools.getOpenSession();
> 	      org.hibernate.Transaction tx = session.beginTransaction();
> 	      User user = userModule.findUserByUserName("admin"); // HERE
> 	      if(user!=null)
> 	      {
> 	    	  JCRCMS.getUserInfo().set(user);
> 	      }
> 	      tx.rollback();
> 	      org.jboss.portal.cms.hibernate.state.Tools.closeSession(session);
>       }	
> If it doesn't exist (for example because LDAP is being used), portal-cms cannopt be deployed, and several database tables are not created. If 'admin' is changed to an existing user, everything works fine.
> There is another reference to 'admin' in cms/src/main/org/jboss/portal/cms/impl/jcr/command/ACLEnforcer.java, but leaving this as it is doesn't seem to have any negative effect.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:11:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <569225.1192014663539.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_12381378 ] 
            
Tobias Roth commented on JBPORTAL-1733:
---------------------------------------

This is not the same as 1647. This issue is the same as 1740.

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:31:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 07:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1454) Redo the CMS
 Action Menu for the CMS Admin tool
In-Reply-To: <5514709.1179756952366.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18161337.1192015863558.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1454?page=all ]

Thomas Heute resolved JBPORTAL-1454.
------------------------------------

    Resolution: Out of Date

> Redo the CMS Action Menu for the CMS Admin tool
> -----------------------------------------------
>
>                 Key: JBPORTAL-1454
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1454
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.CR2
>            Reporter: Sohil Shah
>         Assigned To: Sohil Shah
>             Fix For: 2.8 Final
>
>
> The select Action drop down has a small triangle to the left of it, along with all of the items in the drop down. These should be removed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:35:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 07:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1646) portal-cms
 depends on existence of user 'admin'
In-Reply-To: <23503800.1187790682411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8092840.1192016103302.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1646?page=comments#action_12381381 ] 
            
Thomas Heute commented on JBPORTAL-1646:
----------------------------------------

Oups sorrry clicked too fast

> portal-cms depends on existence of user 'admin'
> -----------------------------------------------
>
>                 Key: JBPORTAL-1646
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1646
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> cms/src/main/org/jboss/portal/cms/impl/jcr/JCRCMS.java has the user 'admin' hardcoded:
>    /** Loads content from sar and adds it to the repo. */
>    public void createContent() throws Exception
>    {
>       log.info("Creating default CMS content.");
>       
>       // Get the content
>       URL root = Thread.currentThread().getContextClassLoader().getResource(defaultContentLocation);
>       
>       //make the user executing these to create the default content, an 'Admin' user
>       //without this, the fine grained security won't allow the creation
>       UserModule userModule = getUserModule();
>       if(userModule != null)
>       {
> 	      org.hibernate.Session session = org.jboss.portal.cms.hibernate.state.Tools.getOpenSession();
> 	      org.hibernate.Transaction tx = session.beginTransaction();
> 	      User user = userModule.findUserByUserName("admin"); // HERE
> 	      if(user!=null)
> 	      {
> 	    	  JCRCMS.getUserInfo().set(user);
> 	      }
> 	      tx.rollback();
> 	      org.jboss.portal.cms.hibernate.state.Tools.closeSession(session);
>       }	
> If it doesn't exist (for example because LDAP is being used), portal-cms cannopt be deployed, and several database tables are not created. If 'admin' is changed to an existing user, everything works fine.
> There is another reference to 'admin' in cms/src/main/org/jboss/portal/cms/impl/jcr/command/ACLEnforcer.java, but leaving this as it is doesn't seem to have any negative effect.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:23:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 08:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1265) literal/formula
 could be clearer in guided editor RHS
Message-ID: <29918365.1192018983205.JavaMail.jira@cloud.prod.atl2.jboss.com>

literal/formula could be clearer in guided editor RHS
-----------------------------------------------------

                 Key: JBRULES-1265
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1265
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:31:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1265) literal/formula
 could be clearer in guided editor RHS
In-Reply-To: <29918365.1192018983205.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19853589.1192019463466.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1265?page=all ]

Michael Neale closed JBRULES-1265.
----------------------------------

    Resolution: Done

> literal/formula could be clearer in guided editor RHS
> -----------------------------------------------------
>
>                 Key: JBRULES-1265
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1265
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:33:18 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 08:33:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2964703.1192019598156.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381390 ] 
            
Mark Proctor commented on JBRULES-1260:
---------------------------------------

Are you using Eclipse3.2?

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:33:18 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 08:33:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18574449.1192019598577.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381391 ] 
            
Mark Proctor commented on JBRULES-1260:
---------------------------------------

The  plugin  does  not work with Eclipse3.3.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 08:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1263) Mark
 xml-apis/xercesImpl as
 optional dependencies in drools-compiler pom.xml
In-Reply-To: <31321311.1191997683967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16018730.1192019703929.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1263?page=all ]

Mark Proctor closed JBRULES-1263.
---------------------------------

    Resolution: Out of Date

I'm not changing this  now for the  4.0.x series, but  I've dropped  it already  for 4.1.0.

> Mark xml-apis/xercesImpl as optional dependencies in drools-compiler pom.xml
> ----------------------------------------------------------------------------
>
>                 Key: JBRULES-1263
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1263
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Tuomas Kiviaho
>         Assigned To: Mark Proctor
>
> As commented in JBRULES-992 jdk provides xml-apis already so the declaration could be marked as optional or dropped completely. Marking of xercesImpl as optional requires compile time dependency check. Dropping it completely requires also verification that it isn't used anywhere at runtime.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 09:05:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 10 Oct 2007 09:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4807) Cannot redeploy
 webapp after deploy failure
Message-ID: <27444204.1192021503535.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot redeploy webapp after deploy failure
-------------------------------------------

                 Key: JBAS-4807
                 URL: http://jira.jboss.com/jira/browse/JBAS-4807
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Deployment services
            Reporter: Thomas Diesler
         Assigned To: Dimitris Andreadis
             Fix For:  JBossAS-5.0.0.Beta3


If a webapp cannot be deployed due to some deployment problem, this webapp is not taken down properly.
A subsequent deployment of the webapp fails

14:55:03,570 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war state=PostClassLoader mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war
        at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175)
        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
        at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)

Caused by: org.jboss.ws.WSException: Cannot find port in wsdl: {http://ws.com/}ProviderPort
        at org.jboss.ws.metadata.builder.MetaDataBuilder.replaceAddressLocation(MetaDataBuilder.java:338)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSProviderMetaDataBuilder.buildProviderMetaData(JAXWSProviderMetaDataBuilder.java:147)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:55)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
        at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
        at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
        at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)

14:55:03,744 WARN  [MainDeployer] undeploy 'file:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war' : package not deployed
14:55:03,770 WARN  [MainDeployer] undeploy 'file:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war' : package not deployed
14:55:10,884 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war is already installed.






-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 09:32:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 09:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7908950.1192023123258.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Thomas Heute resolved JBPORTAL-1741.
------------------------------------

    Resolution: Done
      Assignee: Julien Viet  (was: Thomas Heute)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>            Priority: Critical
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 09:38:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 09:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
Message-ID: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix tutorial for 2.1.0 series
-----------------------------

                 Key: JBCACHE-1195
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.GA


As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.

Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Wed Oct 10 10:35:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 10 Oct 2007 10:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1061) Look into
 StatefulUnitTestCase, determine purpose
In-Reply-To: <7131874.1191939425385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11920156.1192026903392.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1061?page=comments#action_12381427 ] 
            
Brian Stansberry commented on EJBTHREE-1061:
--------------------------------------------

This is the test in the org.jboss.ejb3.test.cache.unit package.  There are SFSBs tests in org.jboss.ejb3.test.stateful and org.jboss.ejb3.test.clusteredsession that may cover the same stuff.

> Look into StatefulUnitTestCase, determine purpose
> -------------------------------------------------
>
>                 Key: EJBTHREE-1061
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1061
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Ensure the 7 tests in StatefulUnitTestCase are valid, testing for their intentions, and report any inconsistancies to Brian.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 10:43:04 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 10:43:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1266) Composite facts
 types (OR, AND) not rendering correctly
Message-ID: <7101908.1192027384751.JavaMail.jira@cloud.prod.atl2.jboss.com>

Composite facts types (OR, AND) not rendering correctly
-------------------------------------------------------

                 Key: JBRULES-1266
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1266
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.0.3, 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 10:51:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1266) Composite facts
 types (OR, AND) not rendering correctly
In-Reply-To: <7101908.1192027384751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21968329.1192027863430.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1266?page=all ]

Michael Neale closed JBRULES-1266.
----------------------------------

    Resolution: Done

> Composite facts types (OR, AND) not rendering correctly
> -------------------------------------------------------
>
>                 Key: JBRULES-1266
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1266
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:12:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 11:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-999) Bridge
 startup should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <264541.1192029123459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=all ]

Tim Fox reopened JBMESSAGING-999:
---------------------------------

      Assignee: Tim Fox  (was: Sergey Koshcheyev)
             

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:12:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 11:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-999) Bridge startup
 should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10977953.1192029123596.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=all ]

Tim Fox updated JBMESSAGING-999:
--------------------------------

        Fix Version/s: 1.4.0.SP1
                           (was: 1.4.0.CR1)
    Affects Version/s: 1.4.0.GA

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:13:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 11:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-999) Bridge
 startup should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14295712.1192029184233.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=comments#action_12381446 ] 
            
Tim Fox commented on JBMESSAGING-999:
-------------------------------------

I've re-opened this since it seems the task wasn't completed properly.

Although retry logic was added on the Bridge class itself.

It would still fail since the destination lookups are made from the BridgeService class before the Bridge is instantiated.

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:19:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 10 Oct 2007 11:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4808) MBean Service to bind
 DistributedTimeCachePolicy to JNDI under java:
Message-ID: <5576125.1192029543311.JavaMail.jira@cloud.prod.atl2.jboss.com>

MBean Service to bind DistributedTimeCachePolicy to JNDI under java:
--------------------------------------------------------------------

                 Key: JBAS-4808
                 URL: http://jira.jboss.com/jira/browse/JBAS-4808
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Security
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Anil Saldhana
         Assigned To: Stefan Guilhen
             Fix For: JBossAS-4.2.3.GA


We have many requests for clustering of the authentication cache in the JBoss security managers.

We need a MBean service that can be configured (on demand by user)  which will bind the DistributedTimedCachePolicy in JNDI under java: context

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:27:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 11:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10859935.1192030023370.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=comments#action_12381448 ] 
            
Mark Proctor commented on JBRULES-1264:
---------------------------------------

ok I've confirmed this and its a valid bug :(
The isNull checks that where placed in a while ago are on the evaluators, but not on the indexing code - this code is only breaks with the index stuff.

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:39:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 10 Oct 2007 11:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-111) unmarshalling Map with
 XmlJavaTypeAdapter
Message-ID: <25538122.1192030743263.JavaMail.jira@cloud.prod.atl2.jboss.com>

unmarshalling Map with XmlJavaTypeAdapter
-----------------------------------------

                 Key: JBXB-111
                 URL: http://jira.jboss.com/jira/browse/JBXB-111
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Bug
    Affects Versions: JBossXB-2.0.0.CR4
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-2.0.0.CR5


The use-case was taken from http://java.sun.com/javaee/5/docs/api/javax/xml/bind/annotation/adapters/XmlAdapter.html but simplified in the test case

package org.jboss.test.xb.builder.object.element.javatypeadapter.test;
public class JavaTypeAdapterUnitTestCase extends AbstractBuilderTest


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:39:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 10 Oct 2007 11:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-111) unmarshalling Map with
 XmlJavaTypeAdapter
In-Reply-To: <25538122.1192030743263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3050046.1192030743371.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-111?page=all ]

Alexey Loubyansky closed JBXB-111.
----------------------------------

    Resolution: Done

Fixed.

> unmarshalling Map with XmlJavaTypeAdapter
> -----------------------------------------
>
>                 Key: JBXB-111
>                 URL: http://jira.jboss.com/jira/browse/JBXB-111
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> The use-case was taken from http://java.sun.com/javaee/5/docs/api/javax/xml/bind/annotation/adapters/XmlAdapter.html but simplified in the test case
> package org.jboss.test.xb.builder.object.element.javatypeadapter.test;
> public class JavaTypeAdapterUnitTestCase extends AbstractBuilderTest

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:42:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1182) JMX wrappers log
 WARN messages on calling getter for deprecated attributes
In-Reply-To: <18370997.1189447451670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25550239.1192030923386.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1182?page=all ]

Manik Surtani reopened JBCACHE-1182:
------------------------------------

             

> JMX wrappers log WARN messages on calling getter for deprecated attributes
> --------------------------------------------------------------------------
>
>                 Key: JBCACHE-1182
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1182
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA
>
>
> Logged after viewing a cache mbean in AS's jmx-console:
> 12:55:33,437 WARN  [CacheJmxWrapper] MBean attribute 'CacheLoaderConfiguration'
> is deprecated; use 'CacheLoaderConfig'
> 12:55:34,046 WARN  [CacheJmxWrapper] MBean attribute 'UseInterceptorMbeans' is d
> eprecated; use 'ExposeManagementStatistics'
> These should only be logged for the setter; the setter is what implies conscious usage of the outdated API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:42:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1182) JMX wrappers log
 WARN messages on calling getter for deprecated attributes
In-Reply-To: <18370997.1189447451670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29023216.1192030923580.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1182?page=all ]

Manik Surtani resolved JBCACHE-1182.
------------------------------------

    Resolution: Done

> JMX wrappers log WARN messages on calling getter for deprecated attributes
> --------------------------------------------------------------------------
>
>                 Key: JBCACHE-1182
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1182
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA
>
>
> Logged after viewing a cache mbean in AS's jmx-console:
> 12:55:33,437 WARN  [CacheJmxWrapper] MBean attribute 'CacheLoaderConfiguration'
> is deprecated; use 'CacheLoaderConfig'
> 12:55:34,046 WARN  [CacheJmxWrapper] MBean attribute 'UseInterceptorMbeans' is d
> eprecated; use 'ExposeManagementStatistics'
> These should only be logged for the setter; the setter is what implies conscious usage of the outdated API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1099) JDBCCacheLoader
 does not deal with Schema names?
In-Reply-To: <26867781.1181298011551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10082268.1192031062098.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1099?page=all ]

Manik Surtani reopened JBCACHE-1099:
------------------------------------

             

> JDBCCacheLoader does not deal with Schema names?
> ------------------------------------------------
>
>                 Key: JBCACHE-1099
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1099
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR2
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA
>
>
> Should be able to take in a schema name property and prepend this to table names when generating SQL.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1766228.1192031062230.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani reopened JBCACHE-1167:
------------------------------------

             

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4, 2.0.0.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP5, 2.1.0.GA
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1172)
 CacheLoaderInterceptor
 doesn't load data for Node.getKeys() or Node.getData()
In-Reply-To: <12017577.1188097518214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24501869.1192031062358.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1172?page=all ]

Manik Surtani reopened JBCACHE-1172:
------------------------------------

             

> CacheLoaderInterceptor doesn't load data for Node.getKeys() or Node.getData()
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1172
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1172
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> CacheLoaderInterceptor.mustLoad always returns false if there is no data key associated with the MethodCall.  Effect is calls for CacheImpl._getKeys  and _getData don't trigger a load from the cache loader.
> Added tests testKeyKeys() and testGetData() to CacheLoaderTestsBase to show the issue.
> Solution is to add a boolean 'allKeys' variable to CacheLoaderInterceptor.invoke.  Set it to true if the MethodCall is _getKeys or _getData.  Pass the value through to mustLoad, and if true load the data if Node.isDataLoaded returns false.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1175)
	Option.forceCall(A)sync
In-Reply-To: <31286648.1188585138477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17847357.1192031069668.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=all ]

Manik Surtani reopened JBCACHE-1175:
------------------------------------

             

> Option.forceCall(A)sync
> -----------------------
>
>                 Key: JBCACHE-1175
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Add an option to allow an individual call to go async/sync when the cache overall is configured for the opposite.
> This would only be relevant to calls not running in a tx; transactional replication would use the standard semantic configured for the cache.
> Use case for this is Hibernate timestamp region replication, which needs to go async, while all other Hibernate 2nd level cache traffic goes sync.  A good region-based cache impl would solve the problem as well, but that will surely take quite a while to implement a while while doing it via an Option looks quite trivial.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:29 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:29 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1178) Option to set
	lock timeout
In-Reply-To: <14176892.1189113131136.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31319067.1192031069816.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1178?page=all ]

Manik Surtani reopened JBCACHE-1178:
------------------------------------

             

> Option to set lock timeout
> --------------------------
>
>                 Key: JBCACHE-1178
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1178
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Allow override of the standard lock timeout on a per-invocation basis.
> For background on the specific use case that needs this, see http://lists.jboss.org/pipermail/hibernate-dev/2007-September/002669.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:29 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:29 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1180)
 CacheImpl.toString() prints cache details
In-Reply-To: <29419991.1189446491112.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22693300.1192031069946.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1180?page=all ]

Manik Surtani reopened JBCACHE-1180:
------------------------------------

             

> CacheImpl.toString() prints cache details
> -----------------------------------------
>
>                 Key: JBCACHE-1180
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1180
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Calls CacheImpl.toString(true), thus printing the entire tree.
> In 1.x the equivalent impl was to call toString(false).
> This shows up in the JMX console, which calls toString() on attribute values.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:30 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1181) CacheJmxWrappers
 exposes details as JMX attributes, not operations
In-Reply-To: <24706943.1189446862714.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31932402.1192031070078.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1181?page=all ]

Manik Surtani reopened JBCACHE-1181:
------------------------------------

             

> CacheJmxWrappers exposes details as JMX attributes, not operations
> ------------------------------------------------------------------
>
>                 Key: JBCACHE-1181
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1181
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> getConfigurationAsString();
> getConfigurationAsHtmlString();
> getCacheDetails();
> getCacheDetailsAsHtml();
> getLockInfo();
> getLockInfoAsHtml();
> All are too verbose for exposure as MBean attributes in the JMX console.  They need to be converted into operations so users will have to specifically invoke them.
> A better API would be:
> printConfigurationAsString();
> printConfigurationAsHtmlString();
> printCacheDetails();
> printCacheDetailsAsHtml();
> printLockInfo();
> printLockInfoAsHtml();

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1172)
 CacheLoaderInterceptor
 doesn't load data for Node.getKeys() or Node.getData()
In-Reply-To: <12017577.1188097518214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12999032.1192031283593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1172?page=all ]

Manik Surtani resolved JBCACHE-1172.
------------------------------------

    Resolution: Done

> CacheLoaderInterceptor doesn't load data for Node.getKeys() or Node.getData()
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1172
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1172
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> CacheLoaderInterceptor.mustLoad always returns false if there is no data key associated with the MethodCall.  Effect is calls for CacheImpl._getKeys  and _getData don't trigger a load from the cache loader.
> Added tests testKeyKeys() and testGetData() to CacheLoaderTestsBase to show the issue.
> Solution is to add a boolean 'allKeys' variable to CacheLoaderInterceptor.invoke.  Set it to true if the MethodCall is _getKeys or _getData.  Pass the value through to mustLoad, and if true load the data if Node.isDataLoaded returns false.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1175)
	Option.forceCall(A)sync
In-Reply-To: <31286648.1188585138477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10397571.1192031283702.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=all ]

Manik Surtani resolved JBCACHE-1175.
------------------------------------

    Resolution: Done

> Option.forceCall(A)sync
> -----------------------
>
>                 Key: JBCACHE-1175
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Add an option to allow an individual call to go async/sync when the cache overall is configured for the opposite.
> This would only be relevant to calls not running in a tx; transactional replication would use the standard semantic configured for the cache.
> Use case for this is Hibernate timestamp region replication, which needs to go async, while all other Hibernate 2nd level cache traffic goes sync.  A good region-based cache impl would solve the problem as well, but that will surely take quite a while to implement a while while doing it via an Option looks quite trivial.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1178) Option to set
	lock timeout
In-Reply-To: <14176892.1189113131136.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5857463.1192031283829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1178?page=all ]

Manik Surtani resolved JBCACHE-1178.
------------------------------------

    Resolution: Done

> Option to set lock timeout
> --------------------------
>
>                 Key: JBCACHE-1178
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1178
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Allow override of the standard lock timeout on a per-invocation basis.
> For background on the specific use case that needs this, see http://lists.jboss.org/pipermail/hibernate-dev/2007-September/002669.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1180)
 CacheImpl.toString() prints cache details
In-Reply-To: <29419991.1189446491112.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25717944.1192031283956.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1180?page=all ]

Manik Surtani resolved JBCACHE-1180.
------------------------------------

    Resolution: Done

> CacheImpl.toString() prints cache details
> -----------------------------------------
>
>                 Key: JBCACHE-1180
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1180
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Calls CacheImpl.toString(true), thus printing the entire tree.
> In 1.x the equivalent impl was to call toString(false).
> This shows up in the JMX console, which calls toString() on attribute values.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1181) CacheJmxWrappers
 exposes details as JMX attributes, not operations
In-Reply-To: <24706943.1189446862714.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19846020.1192031284097.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1181?page=all ]

Manik Surtani resolved JBCACHE-1181.
------------------------------------

    Resolution: Done

> CacheJmxWrappers exposes details as JMX attributes, not operations
> ------------------------------------------------------------------
>
>                 Key: JBCACHE-1181
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1181
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> getConfigurationAsString();
> getConfigurationAsHtmlString();
> getCacheDetails();
> getCacheDetailsAsHtml();
> getLockInfo();
> getLockInfoAsHtml();
> All are too verbose for exposure as MBean attributes in the JMX console.  They need to be converted into operations so users will have to specifically invoke them.
> A better API would be:
> printConfigurationAsString();
> printConfigurationAsHtmlString();
> printCacheDetails();
> printCacheDetailsAsHtml();
> printLockInfo();
> printLockInfoAsHtml();

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:50:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1099) JDBCCacheLoader
 does not deal with Schema names?
In-Reply-To: <26867781.1181298011551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16170795.1192031403343.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1099?page=all ]

Manik Surtani resolved JBCACHE-1099.
------------------------------------

    Resolution: Done

> JDBCCacheLoader does not deal with Schema names?
> ------------------------------------------------
>
>                 Key: JBCACHE-1099
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1099
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR2
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA
>
>
> Should be able to take in a schema name property and prepend this to table names when generating SQL.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:50:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11781404.1192031403472.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani resolved JBCACHE-1167.
------------------------------------

    Resolution: Done

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4, 2.0.0.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1186)
 ClusteredCacheLoader to wait
 for first positive result rather than all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13928273.1192031644540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani updated JBCACHE-1186:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> ClusteredCacheLoader to wait for first positive result rather than all results
> ------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1155) Invalidation with
 optimistic versioning could cause cache to write stale data
In-Reply-To: <16391432.1185540287029.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17625630.1192031644447.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1155?page=all ]

Manik Surtani updated JBCACHE-1155:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Invalidation with optimistic versioning could cause cache to write stale data
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1155
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1155
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> The root of the problem is that invalidation evicts remote nodes which may mean that remote nodes are removed completely, losing all historic versioning data
> 1) Svr 1 generates state for node (data version 1)
> 2) Svr 2 generates newer state for same node (data version 2)
> 3) Svr 2 commits (data version 2), invalidates state on cache 1
> 4) Svr 1 commits, and this is allowed to proceed since it seems cache 1 created this data new, and it does not exist in cache 1.
> 5) Svr 1 will attempt to invalidate this remotely, but this will fail - but it will still be applied locally.
> 6) Inconsistency!!!
> Solution: Invalidation not to remove nodes, but evict nodes as though they had children (remove data maps and set dataInitialised to false), and (if optimistic) attach the version of the invalidation to the node.
> Eviction to have, in addition to maxTTL, a minTTL as well so that nodes spend at least a certain amount of time in the cache even if scheduled for eviction since even if we have the above eviction may come along and remove the node altogether.
> MinTTL to be configured to be greater than the max length of transactions.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-910)
 TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
In-Reply-To: <7891202.1166570293319.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13108693.1192031644834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-910?page=all ]

Manik Surtani updated JBCACHE-910:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
> -----------------------------------------------------
>
>                 Key: JBCACHE-910
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-910
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.ALPHA2
>            Reporter: Elias Ross
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> This method is called by the region manager.
> There's a bunch of Voodoo taking place here, legacy bits mixed with some newer stuff.
> One thing that strikes me as wrong already is this code:
> child = factory.createDataNode(type, name,
>                        subtree.getFqnChild(i + 1),
>                        parent, lock_table, coordinator, null, this.rootSpi);
> For some reason, it is passing the lock_table into the Node as the data to initialize the node with.
> Somehow I think the right way to fix this would be to do a Cache.addChild(Fqn) call in RegionManager and remove this method.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-549) Override GET_ALL
 and timeout for synchronous requests
Message-ID: <24057695.1192031645279.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-549?page=all ]

Manik Surtani updated JBCACHE-549:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Override GET_ALL and timeout for synchronous requests
> -----------------------------------------------------
>
>                 Key: JBCACHE-549
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-549
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4beta, 1.3.0.GA, 1.2.4, 1.2.4SP1, 1.2.4SP2
>            Reporter: Bela Ban
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Currently, when executing a *synchronous* method call across a cluster, the caller has to wait until all recipients send the reply, so the default mode is always GroupRequest.GET_ALL. However, we should provide more options (possibly in an Option), e.g.
> - GET_ALL
> - GET_FIRST
> - GET_N (where N < number of recipients)
> - GET_MAJORITY
> We may also want to be able to set the timeout for the call in an Options parameter, and combine this with the mode.
> So Options (used e.g. by put(), remove() etc) should have additional parameters, and *use* them in the relevant interceptors

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1144) Update build
 system to use Maven2 rather than Ant
In-Reply-To: <7905246.1184844227204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5986443.1192031645352.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1144?page=all ]

Manik Surtani updated JBCACHE-1144:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Update build system to use Maven2 rather than Ant
> -------------------------------------------------
>
>                 Key: JBCACHE-1144
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1144
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1180)
 CacheImpl.toString() prints cache details
In-Reply-To: <29419991.1189446491112.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17456119.1192031645471.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1180?page=all ]

Manik Surtani updated JBCACHE-1180:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> CacheImpl.toString() prints cache details
> -----------------------------------------
>
>                 Key: JBCACHE-1180
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1180
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Calls CacheImpl.toString(true), thus printing the entire tree.
> In 1.x the equivalent impl was to call toString(false).
> This shows up in the JMX console, which calls toString() on attribute values.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-957) Allow per-node
 configuration of LockParentForChildInsertRemove
In-Reply-To: <27480287.1170109978549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20273398.1192031645654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-957?page=all ]

Manik Surtani updated JBCACHE-957:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Allow per-node configuration of LockParentForChildInsertRemove
> --------------------------------------------------------------
>
>                 Key: JBCACHE-957
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-957
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>         Attachments: lock.diff
>
>
> Use the new LockParentForChildInsertRemove as a global default that sets a per-node behavior.  Expose an API in Node (not NodeSPI) that allows the application to change the behavior for an individual node.
> Use case: session replication, which stores data in a structure like this:
> /SESSION/webapp/session1/.../...
> /SESSION/webapp/session2/.../...
> The session managment layer wants the greater correctness that comes with enforcing LockParentForChildInsertRemove="true" with the sessionX node and below.  But requiring a WL on /SESSION/webapp before any session could be added or removed will greatly disrupt session creation and expiration.  This feature allows the best of both worlds, by allowing the application to set LockParentForChildInsertRemove="false" on /SESSION and /SESSION/webapp.
> This is a simple alternative to lock striping in the node's children map.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1127) Switch to
	jboss-javaee.jar
In-Reply-To: <27724535.1184097873268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3479932.1192031645792.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1127?page=all ]

Manik Surtani updated JBCACHE-1127:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Switch to jboss-javaee.jar
> --------------------------
>
>                 Key: JBCACHE-1127
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1127
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Carlo de Wolf has pulled the JEE APIs out of the AS codebase and into a separate project that produces a jboss-javaee.jar.  Right now it's only produced a snapshot, but once it produces a GA release JBC should switch to it from jboss-j2ee.jar.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1146) Parameterise
 tests for various permutations
In-Reply-To: <6430365.1184844227374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11016179.1192031645948.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1146?page=all ]

Manik Surtani updated JBCACHE-1146:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Parameterise tests for various permutations
> -------------------------------------------
>
>                 Key: JBCACHE-1146
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1146
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1182) JMX wrappers log
 WARN messages on calling getter for deprecated attributes
In-Reply-To: <18370997.1189447451670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20231992.1192031646062.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1182?page=all ]

Manik Surtani updated JBCACHE-1182:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> JMX wrappers log WARN messages on calling getter for deprecated attributes
> --------------------------------------------------------------------------
>
>                 Key: JBCACHE-1182
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1182
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Logged after viewing a cache mbean in AS's jmx-console:
> 12:55:33,437 WARN  [CacheJmxWrapper] MBean attribute 'CacheLoaderConfiguration'
> is deprecated; use 'CacheLoaderConfig'
> 12:55:34,046 WARN  [CacheJmxWrapper] MBean attribute 'UseInterceptorMbeans' is d
> eprecated; use 'ExposeManagementStatistics'
> These should only be logged for the setter; the setter is what implies conscious usage of the outdated API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1193) Tests should not
 call Transaction.commit/rollback()
In-Reply-To: <5880125.1191386163241.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15566822.1192031646190.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1193?page=all ]

Manik Surtani updated JBCACHE-1193:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Tests should not call Transaction.commit/rollback()
> ---------------------------------------------------
>
>                 Key: JBCACHE-1193
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1193
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Jason T. Greene
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> The JTA spec says that the thread association of a transaction can only be controlled by TransactionManager. The reason is that a Transaction can be bound to multple threads. In order to be compliant, and work with JBoss JTA, we need to ensure that all operations go through TransactionManager

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3105002.1192031646299.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani updated JBCACHE-1167:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1
                       (was: 1.4.1.SP5)

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5, 2.1.0.BETA1
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1171) Make constructor
 Fqn(List<E> names, boolean safe) public
In-Reply-To: <4725833.1187979928897.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31603394.1192031646422.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1171?page=all ]

Manik Surtani updated JBCACHE-1171:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Make constructor Fqn(List<E> names, boolean safe) public
> --------------------------------------------------------
>
>                 Key: JBCACHE-1171
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1171
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.BETA1, 2.1.0.GA
>
>
> This constructor saves the cost of making a defensive copy of the passed in List.  I've got some code that necessarily creates an ArrayList to pass to the Fqn c'tor, but there's no need to copy it; I hold no ref to the List.  Being able to use this c'tor would be a minor optimization.  I don't see any reason not to expose it as public; the javadoc for the constructor is clear about the proper usage.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1181) CacheJmxWrappers
 exposes details as JMX attributes, not operations
In-Reply-To: <24706943.1189446862714.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19007762.1192031646546.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1181?page=all ]

Manik Surtani updated JBCACHE-1181:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> CacheJmxWrappers exposes details as JMX attributes, not operations
> ------------------------------------------------------------------
>
>                 Key: JBCACHE-1181
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1181
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> getConfigurationAsString();
> getConfigurationAsHtmlString();
> getCacheDetails();
> getCacheDetailsAsHtml();
> getLockInfo();
> getLockInfoAsHtml();
> All are too verbose for exposure as MBean attributes in the JMX console.  They need to be converted into operations so users will have to specifically invoke them.
> A better API would be:
> printConfigurationAsString();
> printConfigurationAsHtmlString();
> printCacheDetails();
> printCacheDetailsAsHtml();
> printLockInfo();
> printLockInfoAsHtml();

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1178) Option to set
	lock timeout
In-Reply-To: <14176892.1189113131136.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23719913.1192031646680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1178?page=all ]

Manik Surtani updated JBCACHE-1178:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Option to set lock timeout
> --------------------------
>
>                 Key: JBCACHE-1178
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1178
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Allow override of the standard lock timeout on a per-invocation basis.
> For background on the specific use case that needs this, see http://lists.jboss.org/pipermail/hibernate-dev/2007-September/002669.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1175)
	Option.forceCall(A)sync
In-Reply-To: <31286648.1188585138477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28859184.1192031646800.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=all ]

Manik Surtani updated JBCACHE-1175:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Option.forceCall(A)sync
> -----------------------
>
>                 Key: JBCACHE-1175
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Add an option to allow an individual call to go async/sync when the cache overall is configured for the opposite.
> This would only be relevant to calls not running in a tx; transactional replication would use the standard semantic configured for the cache.
> Use case for this is Hibernate timestamp region replication, which needs to go async, while all other Hibernate 2nd level cache traffic goes sync.  A good region-based cache impl would solve the problem as well, but that will surely take quite a while to implement a while while doing it via an Option looks quite trivial.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1179) Blocking access
 to cache based
 on CacheStatus broken around channel connect/disconnect
In-Reply-To: <22553328.1189435151214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31035120.1192031647237.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1179?page=all ]

Manik Surtani updated JBCACHE-1179:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Blocking access to cache based on CacheStatus broken around channel connect/disconnect
> --------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1179
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1179
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> CacheImpl.invokeMethod will throw an ISE if CacheStatus != STARTED.  Problem is the channel is connected during CacheStatus.STARTING and CacheStatus.STOPPING. As long as the channel is connected you get exceptions during replication for as shown in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118013.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1142) Update JBoss
 Cache source code infrastructure
In-Reply-To: <31605360.1184844107046.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20649964.1192031647330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1142?page=all ]

Manik Surtani updated JBCACHE-1142:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Update JBoss Cache source code infrastructure
> ---------------------------------------------
>
>                 Key: JBCACHE-1142
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1142
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1145) Update test suite
 to use TestNG
In-Reply-To: <32594581.1184844227288.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26851459.1192031647474.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1145?page=all ]

Manik Surtani updated JBCACHE-1145:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Update test suite to use TestNG
> -------------------------------
>
>                 Key: JBCACHE-1145
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1145
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1099) JDBCCacheLoader
 does not deal with Schema names?
In-Reply-To: <26867781.1181298011551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32115359.1192031647600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1099?page=all ]

Manik Surtani updated JBCACHE-1099:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> JDBCCacheLoader does not deal with Schema names?
> ------------------------------------------------
>
>                 Key: JBCACHE-1099
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1099
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR2
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Should be able to take in a schema name property and prepend this to table names when generating SQL.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1189) Implement JGroups
 Connect + State Transfer in JBC
In-Reply-To: <18329595.1190729863300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6043652.1192031647713.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1189?page=all ]

Manik Surtani updated JBCACHE-1189:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Implement JGroups Connect + State Transfer in JBC
> -------------------------------------------------
>
>                 Key: JBCACHE-1189
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1189
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1172)
 CacheLoaderInterceptor doesn't
 load data for Node.getKeys() or Node.getData()
In-Reply-To: <12017577.1188097518214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19020267.1192031647834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1172?page=all ]

Manik Surtani updated JBCACHE-1172:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> CacheLoaderInterceptor doesn't load data for Node.getKeys() or Node.getData()
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1172
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1172
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> CacheLoaderInterceptor.mustLoad always returns false if there is no data key associated with the MethodCall.  Effect is calls for CacheImpl._getKeys  and _getData don't trigger a load from the cache loader.
> Added tests testKeyKeys() and testGetData() to CacheLoaderTestsBase to show the issue.
> Solution is to add a boolean 'allKeys' variable to CacheLoaderInterceptor.invoke.  Set it to true if the MethodCall is _getKeys or _getData.  Pass the value through to mustLoad, and if true load the data if Node.isDataLoaded returns false.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-407) Write locks not
 acquired on newly created empty nodes
Message-ID: <1171809.1192031647974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-407?page=all ]

Manik Surtani updated JBCACHE-407:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Write locks not acquired on newly created empty nodes
> -----------------------------------------------------
>
>                 Key: JBCACHE-407
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-407
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.GA, 1.4.0.GA, 1.3.0.GA, 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> When an empty node is created during a put (e.g node "/a" created as a result of a cache.put("/a/1", "key", "value"); call), only a read lock is acquired on the empty node. If the node is created as part of a transaction, the following failure can occur:
> 2 threads, empty cache, READ_COMMITTED
> 1) T1 starts a tx
> 2) T1 invokes cache.put("/a/1", "key", "value1");
> 3) T2 invokes cache.put("/a/2", "key", "value2");
> 4) T1's transaction rolls back
> 5) T2 invokes cache.get("/a/2", "key");  Should get "value2", will get null because the tx rollback will remove node /a and thus /a/2 as well.
> This IMO breaks READ_COMMITTED semantics, as T2 is able to "read" /a (in the sense of seeing it exists and thus can have children appended to it) before the tx that created /a is committed.
> New unit test IsolationLevelReadCommittedTest.testNodeCreationRollback() demonstrates the issue.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1143) Migrate
 repository from CVS to SVN
In-Reply-To: <5716848.1184844227121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26322561.1192031648072.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1143?page=all ]

Manik Surtani updated JBCACHE-1143:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Migrate repository from CVS to SVN
> ----------------------------------
>
>                 Key: JBCACHE-1143
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1143
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1147) Document changes
In-Reply-To: <11638383.1184844347023.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21918357.1192031648147.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1147?page=all ]

Manik Surtani updated JBCACHE-1147:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Document changes
> ----------------
>
>                 Key: JBCACHE-1147
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1147
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1173)
 o.j.c.u.ThreadGate does not implement timeouts properly
In-Reply-To: <17723921.1188172829784.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5679970.1192031648283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1173?page=all ]

Manik Surtani updated JBCACHE-1173:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> o.j.c.u.ThreadGate does not implement timeouts properly
> -------------------------------------------------------
>
>                 Key: JBCACHE-1173
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1173
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Jason T. Greene
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> The primary side-effect of this problem is that the state transfer will block forever waiting for an unblock event.
> This should be rewritten to use j.u.c Condition instead of object.wait()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-751)
 ignoreModifications cache
 loader flag to be extended to all cache loaders, not just ones configured
 in a chaining cache loader
In-Reply-To: <26415084.1156852159852.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22429299.1192031648373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-751?page=all ]

Manik Surtani updated JBCACHE-751:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> ignoreModifications cache loader flag to be extended to all cache loaders, not just ones configured in a chaining cache loader
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-751
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-751
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 1.4.0.GA, 1.3.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6117827.1192031648505.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani updated JBCACHE-1167:
-----------------------------------

    Fix Version/s: 1.4.1.SP5

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5, 2.1.0.BETA1
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:40:14 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Wed, 10 Oct 2007 12:40:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4809) JCA deployer and
 metadata
 incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
Message-ID: <29252975.1192034414855.JavaMail.jira@cloud.prod.atl2.jboss.com>

JCA deployer and metadata incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
---------------------------------------------------------------------------------------------------

                 Key: JBAS-4809
                 URL: http://jira.jboss.com/jira/browse/JBAS-4809
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JCA service
            Reporter: Weston Price
         Assigned To: Weston Price
             Fix For:  JBossAS-5.0.0.Beta3


The ManagedConnectionEmptyContentAdapter did not correctly unmarshall XA based deployments. As a result, non datasource XA deployments (most notably JmsXA) are being incorrectly identified with local tx support and causing failures.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:55:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-315) Break locks for
	state transfer
Message-ID: <26741109.1192035306341.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-315?page=all ]

Manik Surtani updated JBCACHE-315:
----------------------------------

    Fix Version/s: 2.1.0.CR1

> Break locks for state transfer
> ------------------------------
>
>                 Key: JBCACHE-315
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-315
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> State transfer needs to acquire a lock on the root to make sure all existing TXs have been completed. However, when a TX takes more time than the lock acquisition timeout, state transfer will fail.
> Therefore, we need to forcefully acquire the locks for the state transfer by force-releasing the existing locks, and rolling back all TXs that held those locks.
> This will ensure that state transfer always succeeds, at the expense of some rolled back TXs.
> We need to investigate how this works with optimistic locking

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:55:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26678854.1192035306500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=all ]

Manik Surtani updated JBCACHE-1192:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication, Eviction
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 1.4.1.SP6, 2.1.0.CR1
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:55:06 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 12:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13564537.1192035306661.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=comments#action_12381479 ] 
            
Mark Proctor commented on JBRULES-1264:
---------------------------------------

To summarise this is a bug on CompositeObjectSink - which is only used when you have 3+ == constraints on the same field, the 3 value can be overriden by the threshold configuration value. The indexing for CompositeObjectSink is not able to handle null values. The work around for this at the moment is to set alphaNodeHashingThreshold to 0.

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:16 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1156) Configuration
	profiles
In-Reply-To: <12193835.1185540767196.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7925630.1192035436281.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1156?page=all ]

Manik Surtani updated JBCACHE-1156:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Configuration profiles
> ----------------------
>
>                 Key: JBCACHE-1156
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1156
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Requested by both AS clustering and Hibernate.
> The ability to use a specialised ConfigurationFactory that gives you a pre-configured cache for specific purposes.  E.g., CacheFactory.getAsyncReplicatedCache("myJGroupsMuxStackName")
> To be done as a subclass of DefaultCacheFactory (ProfileCacheFactory?)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:16 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5916860.1192035436438.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=all ]

Manik Surtani updated JBCACHE-1009:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:16 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 12:57:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17949382.1192035436617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Workaround Description: 
Set alphaNodeHashingThreshold to 0.


> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:18 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1153) Introduce a
 concept of structural nodes
In-Reply-To: <6252571.1185539387065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30777113.1192035438828.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1153?page=all ]

Manik Surtani updated JBCACHE-1153:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Introduce a concept of structural nodes
> ---------------------------------------
>
>                 Key: JBCACHE-1153
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1153
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Structural nodes should not be taken into consideration when processing regions for eviction.
> Typically are nodes that do not contain data (and are not intended to contain data), but are used to build tree structure.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:18 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1170) Partial state
 transfer fails when multiple regions present
In-Reply-To: <5358429.1187970318264.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28623580.1192035438965.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1170?page=all ]

Manik Surtani updated JBCACHE-1170:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Partial state transfer fails when multiple regions present
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1170
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.  
> Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase.  Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call.  Using region /JSESSION/localhost/http-field
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
> The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped", or perhaps nothing at all.
> Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal.  Two problems:
> 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
> 2) Need to ensure that the right Fqn gets written.  In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything.  If not, just cleaning up the ThreadLocal should work.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:19 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1154) Introduce ability
 to mark
 nodes as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11449903.1192035439131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Manik Surtani updated JBCACHE-1154:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-704) Externalise the TM
 used in the test suite so the TM can be injected when running tests.
In-Reply-To: <32285530.1153238351263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16436126.1192035543330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-704?page=all ]

Manik Surtani updated JBCACHE-704:
----------------------------------

    Fix Version/s: 2.1.0.CR1
         Assignee: Jason T. Greene  (was: Manik Surtani)

> Externalise the TM used in the test suite so the TM can be injected when running tests.
> ---------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-704
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-704
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Allows for QA to certify JBC on other TMs like JBossTS and JBossTM.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
In-Reply-To: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22245245.1192035543397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1195?page=all ]

Manik Surtani updated JBCACHE-1195:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Fix tutorial for 2.1.0 series
> -----------------------------
>
>                 Key: JBCACHE-1195
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.
> Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1176) Bad performance
 when deleting a large tree from JDBCCacheLoader
In-Reply-To: <22599873.1188997871354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20652388.1192035543620.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1176?page=all ]

Manik Surtani updated JBCACHE-1176:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Bad performance when deleting a large tree from JDBCCacheLoader 
> ----------------------------------------------------------------
>
>                 Key: JBCACHE-1176
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1176
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR1
>            Reporter: gmeroz
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> When using JDBCCacheLaoder and trying to delete the hole tree:
> using: cache.getCache().removeNode(Fqn.ROOT)
> it takes a long time which may cause transaction timeouts when running on application server.
> it seems that each node is deleted seperately instead of using one sql command.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-295) Add unit tests for
 ReplicationQueue
Message-ID: <15063994.1192035543759.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-295?page=all ]

Manik Surtani updated JBCACHE-295:
----------------------------------

    Fix Version/s: 2.1.0.CR1

> Add unit tests for ReplicationQueue
> -----------------------------------
>
>                 Key: JBCACHE-295
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-295
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:01:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 13:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1837352.1192035663494.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Workaround Description: 
Set alphaNodeHashingThreshold to really large number like 99999.


  was:
Set alphaNodeHashingThreshold to 0.



> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:03:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 10 Oct 2007 13:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1196) Option
 cacheModeLocal value gets changed during PESSIMISTIC calls
Message-ID: <18616605.1192035783594.JavaMail.jira@cloud.prod.atl2.jboss.com>

Option cacheModeLocal value gets changed during PESSIMISTIC calls
-----------------------------------------------------------------

                 Key: JBCACHE-1196
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1196
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Replication
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: 2.1.0.CR1


In org.jboss.cache.options.ForceCacheModeTest I unthinkingly used the same instance of an Option for two invocations. Option.cacheModeLocal meant to be true.  Found that with PESSIMISTIC locking enabled, cacheModeLocal would be set to false when the first request returned.  This led to intermittent failures in the tests, as the initial state of the system was not as expected.

Need to determine why the Option value is being changed.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:05:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 13:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27095792.1192035903316.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=comments#action_12381484 ] 
            
Mark Proctor commented on JBRULES-1264:
---------------------------------------

sorry 0 does not disable, so you have to set the threashold to a value greater than ever will be met, like 99999.

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:33:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Wed, 10 Oct 2007 13:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-478) ClassCastException on
 AnnotatedParameterAdviceInfo
Message-ID: <24439266.1192037583244.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException on AnnotatedParameterAdviceInfo
--------------------------------------------------

                 Key: JBAOP-478
                 URL: http://jira.jboss.com/jira/browse/JBAOP-478
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Flavia Rainone
         Assigned To: Flavia Rainone


This is what happens when line 464 of AnnotatedAdviceInfo is executed with a method that returns a parameterized type:
java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl
        at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$SingleParameterType.internalValidate(AnnotatedParameterAdviceInfo.java:464)
        at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$ParameterAnnotationType.validate(AnnotatedParameterAdviceInfo.java:374)
        at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo.matches(AnnotatedParameterAdviceInfo.java:124)
        at org.jboss.aop.advice.annotation.AdviceMethodFactory.bestValidAdvice(AdviceMethodFactory.java:412)
        at org.jboss.aop.advice.annotation.AdviceMethodFactory.findAdviceMethod(AdviceMethodFactory.java:291)
        at org.jboss.aop.instrument.JoinPointGenerator$AdviceSetups.<init>(JoinPointGenerator.java:1532)
        at org.jboss.aop.instrument.JoinPointGenerator.initialiseAdviceInfosAndAddFields(JoinPointGenerator.java:550)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:399)
        at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
        at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1630)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1626)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
        at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1017)
        at org.jboss.test.aop.annotatedAdviceParams.ReturnInvalidPOJO$ReturnInvalidPOJOAdvisor.methodGenericsAfter54841465230530634828(ReturnInvalidPOJO$Retu
rnInvalidPOJOAdvisor.java)

This task includes a check on the code to see if the error is repeated in other code lines.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:24:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 10 Oct 2007 14:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1267) Allow predicates
 to be nested inside a field constraint
Message-ID: <3975385.1192040643293.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow predicates to be nested inside a field constraint
-------------------------------------------------------

                 Key: JBRULES-1267
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1267
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.1.0


Allow predicates to be nested inside a field constraint

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:26:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 10 Oct 2007 14:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1267) Allow predicates
 to be nested inside a field constraint
In-Reply-To: <3975385.1192040643293.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32736151.1192040763305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1267?page=all ]

Edson Tirelli closed JBRULES-1267.
----------------------------------

    Resolution: Done

Predicates now can be used as restrictions.

> Allow predicates to be nested inside a field constraint
> -------------------------------------------------------
>
>                 Key: JBRULES-1267
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1267
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.1.0
>
>
> Allow predicates to be nested inside a field constraint

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:26:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 10 Oct 2007 14:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1064) review and
 update assigned JIRA tasks
Message-ID: <18446539.1192040763458.JavaMail.jira@cloud.prod.atl2.jboss.com>

review and update assigned JIRA tasks
-------------------------------------

                 Key: EJBTHREE-1064
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1064
             Project: EJB 3.0
          Issue Type: Task
            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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:54:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 10 Oct 2007 14:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1065) Integrate EJB3
 Tutorials Tests with build-test.xml
Message-ID: <30526178.1192042443286.JavaMail.jira@cloud.prod.atl2.jboss.com>

Integrate EJB3 Tutorials Tests with build-test.xml
--------------------------------------------------

                 Key: EJBTHREE-1065
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1065
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger


Will require obtaining the relevant Ant tasks from the tutorials build, merging into ejb3 build-test.xml.  JVM Argument will need to be passed into the target to specify JBOSS_HOME and TUTORIALS_HOME.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 15:05:03 2007
From: jira-events at lists.jboss.org (Kurt Stam (JIRA))
Date: Wed, 10 Oct 2007 15:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4810) mail-ra.rar make SSL
	configurable
Message-ID: <18464142.1192043103930.JavaMail.jira@cloud.prod.atl2.jboss.com>

mail-ra.rar make SSL configurable
---------------------------------

                 Key: JBAS-4810
                 URL: http://jira.jboss.com/jira/browse/JBAS-4810
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: JCA service
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Kurt Stam
         Assigned To: Weston Price
         Attachments: mail-ra-patch.txt

We are using it in JBossESB now, but in my (test) case I did not want SSL with my IMAP
connection, so I'm suggesting to make this setting configurable in the 

connector/src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java

-      sessionProps.setProperty("mail.imap.starttls.enable", "true");
+      sessionProps.setProperty("mail.imap.starttls.enable", starttls + "");

I have attached the patch.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 15:05:04 2007
From: jira-events at lists.jboss.org (Kurt Stam (JIRA))
Date: Wed, 10 Oct 2007 15:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4810) mail-ra.rar make SSL
	configurable
In-Reply-To: <18464142.1192043103930.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25188831.1192043104321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4810?page=all ]

Kurt Stam updated JBAS-4810:
----------------------------

    Attachment: mail-ra-patch.txt

> mail-ra.rar make SSL configurable
> ---------------------------------
>
>                 Key: JBAS-4810
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4810
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Kurt Stam
>         Assigned To: Weston Price
>         Attachments: mail-ra-patch.txt
>
>
> We are using it in JBossESB now, but in my (test) case I did not want SSL with my IMAP
> connection, so I'm suggesting to make this setting configurable in the 
> connector/src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java
> -      sessionProps.setProperty("mail.imap.starttls.enable", "true");
> +      sessionProps.setProperty("mail.imap.starttls.enable", starttls + "");
> I have attached the patch.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 16:22:04 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?C=C3=A9lio_=28JIRA=29?=)
Date: Wed, 10 Oct 2007 16:22:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1049) wrong
 insert/delete order when updating record-set
In-Reply-To: <3396984.1189729150976.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16874992.1192047724393.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1049?page=comments#action_12381527 ] 
            
C?lio commented on EJBTHREE-1049:
---------------------------------

I'm having the same problem.

> wrong insert/delete order when updating record-set
> --------------------------------------------------
>
>                 Key: EJBTHREE-1049
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1049
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>         Environment: jboss-4.2.1.GA , Fedora 6 
>            Reporter: Imran Pariyani
>
> Overview: I have a record with a OneToMany association. From this associated record-set a record is removed and added again, both records identified with the same key. When doing a merge, I get a Unique constraint violation, because EJB first tries to insert the new record. It should first delete the old record, and after this insert the new record, avoiding the unique constraint violation.
> Detailed description: I have the following entities: Location and LocationI18n. 
>  Location has onetomany mapping with locationi18n as follows 
> @OneToMany(cascade = CascadeType.ALL, mappedBy = "location", fetch = FetchType.EAGER)
> private List<LocationI18n> translations;
> And the mapping in the locationi18n is :
> @ManyToOne(cascade = {CascadeType.MERGE, CascadeType.PERSIST },fetch = FetchType.LAZY, optional = false)
> @JoinColumn(name = "loc_id", referencedColumnName = "id", nullable = false, columnDefinition = "loc_id INT NOT NULL")
>     private Location location;
> In the locationI18n table i have a unique key UNIQUE KEY (language, loc_id), 
> So now if i get a location and inside the location i have the collection of locationi18n .. if from that collection i remove one object with language lets say 'EN' and insert a new locationi18n object with the same language 'EN' then it first inserts the new record and then delets the records which has been removed from the collection
> Below is the stack trace:
> 2007-09-07 02:17:24,847 DEBUG [org.hibernate.SQL] insert into location_i18n (loc_id, language, date_created, date_updated, province, city, worldregion, region, subregion, quarter) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.IntegerType] binding '1' to parameter: 1
> 2007-09-07 02:17:24,848 DEBUG [org.hibernate.type.EnumType] Binding 'EN' to parameter: 2
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.TimestampType] binding '2007-09-07 02:17:24' to parameter: 3
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.TimestampType] binding '2007-09-07 02:17:24' to parameter: 4
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.StringType] binding null to parameter: 5
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.StringType] binding null to parameter: 6
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding null to parameter: 7
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding 'afsdfa' to parameter: 8
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding null to parameter: 9
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding null to parameter: 10
> 2007-09-07 02:17:24,873 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1062, SQLState: 23000
> 2007-09-07 02:17:24,874 ERROR [org.hibernate.util.JDBCExceptionReporter] Duplicate entry 'EN-1' for key 2
> 2007-09-07 02:17:24,874 ERROR [STDERR] javax.persistence.EntityExistsException: org.hibernate.exception.ConstraintViolationException: could not insert: [com.triple.LocationI18n]
> 2007-09-07 02:17:24,874 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:604)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:236)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at org.jboss.ejb3.entity.TransactionScopedEntityManager.merge(TransactionScopedEntityManager.java:188)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at com.triple.LocationBean.updateLocation(LocationBean.java:83)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 2007-09-07 02:17:24,875 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
> Test case of the same is present at 
> http://opensource.atlassian.com/projects/hibernate/secure/attachment/13468/test-pro.tar.gz

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 10 16:45:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 16:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3515440.1192049103315.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Attachment: JBRULES-1264.patch

this patch is applied to trunk and needs to be applied to 4.0.x and 4.1.x

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>         Attachments: JBRULES-1264.patch
>
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 17:20:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 10 Oct 2007 17:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-677) Compression
 marshalling fails intermittently.
In-Reply-To: <29287238.1169255872708.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24377757.1192051203286.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-677?page=comments#action_12381543 ] 
            
Ron Sigal commented on JBREM-677:
---------------------------------

Another forum reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119309

> Compression marshalling fails intermittently.
> ---------------------------------------------
>
>                 Key: JBREM-677
>                 URL: http://jira.jboss.com/jira/browse/JBREM-677
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> When used with EJB's, CompressingUnMarshaller intermittently throws java.io.IOException: Not in GZIP format.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 21:25:03 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Wed, 10 Oct 2007 21:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23270601.1192065903613.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381567 ] 
            
Joshua Jackson commented on JBRULES-1260:
-----------------------------------------

Yes exactly. We're using eclipse 3.3 europa
But if we insert the The Eclipse JDT Core jar into the drools plugin folder it will work

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 21:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 21:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21512205.1192066503597.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381568 ] 
            
Mark Proctor commented on JBRULES-1260:
---------------------------------------

If we added the jar it would then be redundant for the Eclipse 3.2 and besides more than that is broken. 4.0.x will not be adding support for Eclipse 3.3. If want to use Eclipse 3.3 you can work of trunk snapshots which have already been upgraded for jdk1.5 and Eclipse 3.3. However bear in mind that trunk is our R&D area.
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/



> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 21:37:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 21:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18072917.1192066623271.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=all ]

Mark Proctor closed JBRULES-1260.
---------------------------------

    Resolution: Rejected

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 23:59:03 2007
From: jira-events at lists.jboss.org (Travis Brown (JIRA))
Date: Wed, 10 Oct 2007 23:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
Message-ID: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failure to deserialize BytesMessage contents
--------------------------------------------

                 Key: JBMESSAGING-1101
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
            Reporter: Travis Brown
         Assigned To: Tim Fox


BytesMessage consumers often receive the following error:

Client side:
2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
java.io.EOFException
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)

Server side:
2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
java.lang.RuntimeException: Unknown type: 76
        at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
        at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
        at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
        at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
        at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
        at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
        at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
        at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.remoting.Client.invokeOneway(Client.java:598)
        at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
        at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
        at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
        at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
        at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
        at org.jgroups.JChannel.up(JChannel.java:1102)
        at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
        at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FC.up(FC.java:422)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
        at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FD.up(FD.java:300)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.Discovery.up(Discovery.java:225)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
        at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
        at org.jgroups.protocols.TP.access$400(TP.java:45)
        at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
        at java.lang.Thread.run(Thread.java:595)


In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)

I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.


This fix resolves the issue in our environment:

diff -r org/jboss/jms/message/JBossBytesMessage.java
592c592
<       return (byte[])getPayload();
---
>       return (byte[])getBytesMessagePayload();

diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
281a282,303
> 	public synchronized Object getBytesMessagePayload()
> 	{
> 		if (payload != null)
> 		{
> 			return payload;
> 		}
> 		else if (payloadAsByteArray != null)
> 		{
> 			payload = payloadAsByteArray;
> 			payloadAsByteArray = null;
>   	  return payload;
> 		}
> 		else
> 		{
> 			return null;
> 		}
> 	}
> 




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 00:47:15 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 00:47:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-811) Privileged Block
 to create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17867615.1192078035029.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-811?page=comments#action_12381575 ] 
            
Ron Sigal commented on JBREM-811:
---------------------------------

Fix applied to branch remoting_2_x for release 2.4.0.Beta1.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1935471.1192079583564.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381579 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Fix applied to branch remoting_2_x for release 2.2.2.SP2.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:18:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-818) Release 2.2.2.GA_CP01
Message-ID: <12204903.1192079883249.JavaMail.jira@cloud.prod.atl2.jboss.com>

Release 2.2.2.GA_CP01
---------------------

                 Key: JBREM-818
                 URL: http://jira.jboss.com/jira/browse/JBREM-818
             Project: JBoss Remoting
          Issue Type: Release
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA_CP01
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.2.2.GA_CP01




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:27:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-811) Privileged Block
 to create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15113156.1192080423481.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-811?page=comments#action_12381580 ] 
            
Ron Sigal commented on JBREM-811:
---------------------------------

Fix applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:27:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12283490.1192080423675.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal updated JBREM-811:
----------------------------

    Assignee: Ron Sigal  (was: Trustin Lee)

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:27:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18526438.1192080423877.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal closed JBREM-811.
---------------------------

    Resolution: Done

Fix has now been applied to all relevant branches.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11905630.1192084743382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal updated JBREM-687:
----------------------------

    Fix Version/s:     (was: 2.2.2.GA_CP01)

Removed from fix version 2.2.2.GA_CP01:

When I asked about the related issue JBAS-4704 "The port for the InvokerLayer (ejb3-deployer) listens only to one interface (address)", got the following responses:

>From Dimitris: I don't personally know of a support case around this issue.

>From Carlo: The issue pop-ed in directly from Jira. I can't find any related support cases or forum posts.

Therefore, will not include fix in 2.2.2.GA_CP01 unless the problem arises in a support case.

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1805202.1192084743563.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal closed JBREM-687.
---------------------------

    Resolution: Done

Fix has been applied to all appropriate branches.

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP2, 2.4.0.Beta1 (Pinto)
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:44:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-814) Logger in
 HTTPClientInvoker should be static (CLONE of JBREM-750)
In-Reply-To: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24631782.1192085043251.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-814?page=all ]

Ron Sigal closed JBREM-814.
---------------------------

    Resolution: Done

Fix has been applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> Logger in HTTPClientInvoker should be static (CLONE of JBREM-750)
> -----------------------------------------------------------------
>
>                 Key: JBREM-814
>                 URL: http://jira.jboss.com/jira/browse/JBREM-814
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:50:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
In-Reply-To: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8587967.1192085403312.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-815?page=all ]

Ron Sigal closed JBREM-815.
---------------------------

    Resolution: Done

Fix applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> allow user to set content-type for http responses (CLONE of JBREM-653)
> ----------------------------------------------------------------------
>
>                 Key: JBREM-815
>                 URL: http://jira.jboss.com/jira/browse/JBREM-815
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
> Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:52:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30205180.1192085523344.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381593 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

There is a unit test, org.jboss.test.remoting.transport.servlet.ServletInvokerExceptionTestClient, which must be run manually; i.e., a servlet container must be started first.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:52:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19707803.1192085523460.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381594 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Fix applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:54:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28156533.1192085643238.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-813?page=all ]

Ron Sigal closed JBREM-813.
---------------------------

    Resolution: Done

Fix has been applied to all appropriate branches.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:10:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:10:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1268)
 Activation.remove() is removing the WRONG activation
Message-ID: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>

Activation.remove() is removing the WRONG activation
----------------------------------------------------

                 Key: JBRULES-1268
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Reteoo
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Mark Proctor
             Fix For: 4.1.0


Check out FIXME_testActivationCancellation in MiscTest.java.

It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.

The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().

This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 



-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:10:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:10:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1268)
 Activation.remove() is removing the WRONG activation
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14400900.1192086614664.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Michael Neale updated JBRULES-1268:
-----------------------------------

    Priority: Critical  (was: Major)

> Activation.remove() is removing the WRONG activation
> ----------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:17:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10033724.1192087023378.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Michael Neale updated JBRULES-1268:
-----------------------------------

    Summary: Activation.remove() is removing the WRONG activation when used in events  (was: Activation.remove() is removing the WRONG activation)

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:47:05 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:47:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1269) Import DRL to
 update existing assets
Message-ID: <27053219.1192088825786.JavaMail.jira@cloud.prod.atl2.jboss.com>

Import DRL to update existing assets
------------------------------------

                 Key: JBRULES-1269
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1269
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:54:18 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 11 Oct 2007 03:54:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
Message-ID: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>

Integrate the JBossWS core testsuite in the release QA
------------------------------------------------------

                 Key: JBAS-4811
                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For: JBossAS-4.2.2.GA


Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.

The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:56:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 11 Oct 2007 03:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31721949.1192089363242.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Thomas Heute updated JBPORTAL-1741:
-----------------------------------

    Affects Version/s:     (was: 2.6.3 Final)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>            Priority: Critical
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:01:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 04:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1269) Import DRL to
 update existing assets
In-Reply-To: <27053219.1192088825786.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7992943.1192089663273.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1269?page=all ]

Michael Neale closed JBRULES-1269.
----------------------------------

    Resolution: Done

> Import DRL to update existing assets
> ------------------------------------
>
>                 Key: JBRULES-1269
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1269
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:06:03 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Thu, 11 Oct 2007 04:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1069) Include common-io
 and common-fileupload in the ear configuration
In-Reply-To: <22824913.1191835149906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10202963.1192089963507.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1069?page=comments#action_12381610 ] 
            
Tom Baeyens commented on JBPM-1069:
-----------------------------------

could you explain this a bit more ?  why are these libraries needed ?

> Include common-io and common-fileupload in the ear configuration
> ----------------------------------------------------------------
>
>                 Key: JBPM-1069
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1069
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>            Reporter: Fady Matar
>         Assigned To: Tom Baeyens
>            Priority: Trivial
>             Fix For: jBPM 3.3
>
>
> Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file)
> The ear files can be appended to the JBoss AS configuration or can be packaged within the ear

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:16:41 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Thu, 11 Oct 2007 04:16:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1069) Include common-io
 and common-fileupload in the ear configuration
In-Reply-To: <22824913.1191835149906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21105425.1192090601488.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1069?page=comments#action_12381613 ] 
            
Fady Matar commented on JBPM-1069:
----------------------------------

Those libraries are needed to handle the file upload mechanism. In previous releases of JBoss they were included with the Tomcat libraries, apparently they're being used in the deployment target. Whenever I deploy the application the exception stack trace indicates that they're missing. They could be bundled either in the application or added to the classpath libraries of JBoss (The workaround I have used)

> Include common-io and common-fileupload in the ear configuration
> ----------------------------------------------------------------
>
>                 Key: JBPM-1069
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1069
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>            Reporter: Fady Matar
>         Assigned To: Tom Baeyens
>            Priority: Trivial
>             Fix For: jBPM 3.3
>
>
> Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file)
> The ear files can be appended to the JBoss AS configuration or can be packaged within the ear

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:33:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 11 Oct 2007 04:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21293095.1192091583924.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Andrew Rubinger resolved EJBTHREE-785.
--------------------------------------

    Resolution: Done

Fixes to unit tests confirmed resolved

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 05:31:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 11 Oct 2007 05:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11005646.1192095063668.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]

Carlo de Wolf reassigned JBAS-4805:
-----------------------------------

    Assignee: William DeCoste  (was: Carlo de Wolf)

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 06:07:04 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Thu, 11 Oct 2007 06:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
Message-ID: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>

Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
------------------------------------------------------------------------------

                 Key: JBAS-4812
                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.0.GA
            Reporter: Dominik Pospisil
         Assigned To: Brian Stansberry
         Attachments: ejb3-buddy.tgz

Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 06:07:06 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Thu, 11 Oct 2007 06:07:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16803037.1192097226826.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4812?page=all ]

Dominik Pospisil updated JBAS-4812:
-----------------------------------

    Attachment: ejb3-buddy.tgz

Test logs.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 08:52:22 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 11 Oct 2007 08:52:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1196) Option
 cacheModeLocal value gets changed during PESSIMISTIC calls
In-Reply-To: <18616605.1192035783594.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2366316.1192107142477.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1196?page=all ]

Brian Stansberry closed JBCACHE-1196.
-------------------------------------

    Fix Version/s:     (was: 2.1.0.CR1)
       Resolution: Won't Fix

A caller should not attempt to reuse an instance of Option. Once you pass it to the cache, it belongs to the cache.

> Option cacheModeLocal value gets changed during PESSIMISTIC calls
> -----------------------------------------------------------------
>
>                 Key: JBCACHE-1196
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1196
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>
> In org.jboss.cache.options.ForceCacheModeTest I unthinkingly used the same instance of an Option for two invocations. Option.cacheModeLocal meant to be true.  Found that with PESSIMISTIC locking enabled, cacheModeLocal would be set to false when the first request returned.  This led to intermittent failures in the tests, as the initial state of the system was not as expected.
> Need to determine why the Option value is being changed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:00:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 11 Oct 2007 09:00:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
Message-ID: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>

Business interfaces defined in the descriptor are ignored
---------------------------------------------------------

                 Key: EJBTHREE-1066
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:09:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 11 Oct 2007 09:09:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4609) Original
 SevletResponse or
 wrapped original ServletResponse not passed to RequestDispatcher in
 violation of SRV.8.2 and SRV.14.2.5.1
In-Reply-To: <14152110.1187166841533.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12704092.1192108144015.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4609?page=all ]

Thomas Heute resolved JBAS-4609.
--------------------------------

    Resolution: Done

This is not a JBoss AS bug.

jboss-web got more strict regarding to the servlet spec, and does what it says.

If you want to have something a bit more loose, start JBoss AS with:
-Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=false

And it won't check for this, so you can use frameworks that are not strictly following the spec.

> Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4609
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4609
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: RHeL
>            Reporter: stefan lotties
>
> Sometimes in the log the following stacktrace appears while someone is surfing in an application:
> 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
> b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
> javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
> ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
>         at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
> a:1018)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
>         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
>         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
> r.java:237)
>         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
> java:300)
>         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
>         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>         at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
> ava:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
> 469)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
> java:316)
>         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
> 44)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
> 156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
> va:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595) 
> I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:48:21 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 09:48:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16229816.1192110501420.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381679 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

This can easily be reproduced by having a Resource injected that 
it's only deployed in one of the nodes, for example, an HA Singleton 
MBean like JBoss MQ in a clustered environment.  

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:52:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Thu, 11 Oct 2007 09:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-422) Retro-woven
 Class.getTypeParameters() method returns zero-length array
Message-ID: <25067970.1192110723740.JavaMail.jira@cloud.prod.atl2.jboss.com>

Retro-woven Class.getTypeParameters() method returns zero-length array
----------------------------------------------------------------------

                 Key: JBBUILD-422
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-422
             Project: JBoss Build System
          Issue Type: Bug
          Components: JBossRetro
    Affects Versions: JBossRetro-1.1.2.GA
            Reporter: Flavia Rainone


The method Class.getTypeParameters returns a zero length array when called on java.util.List.class.

Probably the same occurs with all other Java API classes that have been parameterized as of jdk1.5.

Not sure whether the problem occurs with a parameterized class that has been retro-woven, though (maybe the bug happens only with non-retrowoven classes)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 10:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 11 Oct 2007 10:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4609) Original
 SevletResponse or
 wrapped original ServletResponse not passed to RequestDispatcher in
 violation of SRV.8.2 and SRV.14.2.5.1
In-Reply-To: <14152110.1187166841533.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22759730.1192111263285.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4609?page=all ]

Dimitris Andreadis reopened JBAS-4609:
--------------------------------------

             

> Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4609
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4609
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: RHeL
>            Reporter: stefan lotties
>
> Sometimes in the log the following stacktrace appears while someone is surfing in an application:
> 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
> b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
> javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
> ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
>         at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
> a:1018)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
>         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
>         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
> r.java:237)
>         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
> java:300)
>         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
>         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>         at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
> ava:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
> 469)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
> java:316)
>         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
> 44)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
> 156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
> va:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595) 
> I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 10:03:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 11 Oct 2007 10:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4609) Original
 SevletResponse or wrapped
 original ServletResponse not passed to RequestDispatcher in violation of
 SRV.8.2 and SRV.14.2.5.1
In-Reply-To: <14152110.1187166841533.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24010254.1192111383255.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4609?page=all ]

Dimitris Andreadis closed JBAS-4609.
------------------------------------

    Resolution: Rejected

Thomas, when you close issues like this, please use a different resolution (like rejected, etc.)

> Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4609
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4609
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: RHeL
>            Reporter: stefan lotties
>
> Sometimes in the log the following stacktrace appears while someone is surfing in an application:
> 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
> b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
> javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
> ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
>         at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
> a:1018)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
>         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
>         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
> r.java:237)
>         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
> java:300)
>         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
>         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>         at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
> ava:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
> 469)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
> java:316)
>         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
> 44)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
> 156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
> va:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595) 
> I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 10:06:05 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?C=EF=BF=A9dric_Chantepie_=28JIRA=29?=)
Date: Thu, 11 Oct 2007 10:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4813) EAR with WAR
 classloading isolation & commons-httpclient
Message-ID: <29000557.1192111565670.JavaMail.jira@cloud.prod.atl2.jboss.com>

EAR with WAR classloading isolation & commons-httpclient
--------------------------------------------------------

                 Key: JBAS-4813
                 URL: http://jira.jboss.com/jira/browse/JBAS-4813
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: ClassLoading, Web (Tomcat) service
    Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1
         Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
jrockit-R26.4.0-jdk1.5.0_06
            Reporter: C?dric Chantepie
         Assigned To: Scott M Stark
            Priority: Blocker


We have an EAR including 4 modules :
- an ejb .jar,
- persistence .har
- 2 webapps.

3 modules -- the ejb .jar and the 2 webapps,  depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.

== META-INF/jboss-app.xml ==
<!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
         "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">

<jboss-app>
  <loader-repository>my.package:loader=My.ear
    <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
  </loader-repository>
  <jmx-name>my.package:module=My.ear</jmx-name>
  <module>
    <har>MyPersistence.har</har>
  </module>
</jboss-app>

Then I've added Class-Path attribute in ejb .jar manifest.

== ejb.jar | META-INF/MANIFEST.MF ==

Manifest-Version: 1.0
Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
 ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
 ucene-analyzers-2.0.0.jar

(Line breaks there are as in MANIFEST.MF when I extract it from the jar.)

I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.

== webapp1.war | META-INF/MANIFEST.MF ==

Manifest-Version: 1.0
Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
 b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
 ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
 .jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
 ailer.jar lib/commons-httpclient-3.1.jar

== webapp2.war | META-INF/MANIFEST.MF ==

Manifest-Version: 1.0
Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
 b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
 2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
 jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
 APSHOT.jar lib/commons-httpclient-3.1.jar

And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".

== webapp1.war | WEB-INF/MANIFEST.MF ==

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE jboss-web
  PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
  "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">

<jboss-web>
  <context-root>/BO</context-root>
  <virtual-host>www.my-vhost.com</virtual-host>

  <class-loading java2ClassLoadingCompliance="false">
    <loader-repository>my.package:loader=My.ear
        <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
    </loader-repository>
  </class-loading>
</jboss-web>

== webapp2.war | WEB-INF/MANIFEST.MF ==

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE jboss-web
  PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
  "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">

<jboss-web>
  <context-root>/</context-root>
  <virtual-host>www.my-vhost.com</virtual-host>

  <class-loading java2ClassLoadingCompliance="false">
    <loader-repository>my.package:loader=My.ear
        <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
    </loader-repository>
  </class-loading>
</jboss-web>

Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.

The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one. 

If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.

I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.

2 of these test server have the same linux version (kernel), excepted SMP support.

Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.

So please if you can give some useful information.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 11 10:40:06 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 10:40:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4813) EAR with WAR
 classloading isolation & commons-httpclient
In-Reply-To: <29000557.1192111565670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8350158.1192113606802.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4813?page=all ]

Adrian Brock updated JBAS-4813:
-------------------------------

    Component/s:     (was: ClassLoading)
       Assignee: Remy Maucherat  (was: Scott M Stark)
       Priority: Major  (was: Blocker)

You'll get a faster response if you attach an example deployment reproducing the problem.

NOTE: The jboss-web.xml classloading configuration is largely ignored in 4.0.5
(since it uses the Tomcat classloader) unless you changed the jboss-web service config 
to use the jboss classloader.

Assigned to Remy since if there is an issue it is likely within the Tomcat classloader not JBoss
(e.g. Tomcat automatically ignores a lot of apache commons classes in the war?)

> EAR with WAR classloading isolation & commons-httpclient
> --------------------------------------------------------
>
>                 Key: JBAS-4813
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4813
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.5.GA
>         Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
> jrockit-R26.4.0-jdk1.5.0_06
>            Reporter: C?dric Chantepie
>         Assigned To: Remy Maucherat
>
> We have an EAR including 4 modules :
> - an ejb .jar,
> - persistence .har
> - 2 webapps.
> 3 modules -- the ejb .jar and the 2 webapps,  depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.
> == META-INF/jboss-app.xml ==
> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
>          "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
> <jboss-app>
>   <loader-repository>my.package:loader=My.ear
>     <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>   </loader-repository>
>   <jmx-name>my.package:module=My.ear</jmx-name>
>   <module>
>     <har>MyPersistence.har</har>
>   </module>
> </jboss-app>
> Then I've added Class-Path attribute in ejb .jar manifest.
> == ejb.jar | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
>  ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
>  ucene-analyzers-2.0.0.jar
> (Line breaks there are as in MANIFEST.MF when I extract it from the jar.)
> I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.
> == webapp1.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
>  ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
>  .jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
>  ailer.jar lib/commons-httpclient-3.1.jar
> == webapp2.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
>  2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
>  jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
>  APSHOT.jar lib/commons-httpclient-3.1.jar
> And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".
> == webapp1.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/BO</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> == webapp2.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.
> The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one. 
> If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.
> I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.
> 2 of these test server have the same linux version (kernel), excepted SMP support.
> Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.
> So please if you can give some useful information.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 11 10:50:13 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?C=EF=BF=A9dric_Chantepie_=28JIRA=29?=)
Date: Thu, 11 Oct 2007 10:50:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4813) EAR with WAR
 classloading isolation & commons-httpclient
In-Reply-To: <29000557.1192111565670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15794159.1192114213696.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4813?page=comments#action_12381705 ] 
            
C?dric Chantepie commented on JBAS-4813:
----------------------------------------

I know that jboss-web are ignored, I have let them because maven generate them. 

As I've said the configuration for classloading is in jboss-app.xml, I think this is ok ?

> EAR with WAR classloading isolation & commons-httpclient
> --------------------------------------------------------
>
>                 Key: JBAS-4813
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4813
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.5.GA
>         Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
> jrockit-R26.4.0-jdk1.5.0_06
>            Reporter: C?dric Chantepie
>         Assigned To: Remy Maucherat
>
> We have an EAR including 4 modules :
> - an ejb .jar,
> - persistence .har
> - 2 webapps.
> 3 modules -- the ejb .jar and the 2 webapps,  depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.
> == META-INF/jboss-app.xml ==
> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
>          "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
> <jboss-app>
>   <loader-repository>my.package:loader=My.ear
>     <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>   </loader-repository>
>   <jmx-name>my.package:module=My.ear</jmx-name>
>   <module>
>     <har>MyPersistence.har</har>
>   </module>
> </jboss-app>
> Then I've added Class-Path attribute in ejb .jar manifest.
> == ejb.jar | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
>  ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
>  ucene-analyzers-2.0.0.jar
> (Line breaks there are as in MANIFEST.MF when I extract it from the jar.)
> I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.
> == webapp1.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
>  ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
>  .jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
>  ailer.jar lib/commons-httpclient-3.1.jar
> == webapp2.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
>  2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
>  jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
>  APSHOT.jar lib/commons-httpclient-3.1.jar
> And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".
> == webapp1.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/BO</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> == webapp2.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.
> The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one. 
> If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.
> I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.
> 2 of these test server have the same linux version (kernel), excepted SMP support.
> Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.
> So please if you can give some useful information.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 11 12:12:05 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Thu, 11 Oct 2007 12:12:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <13496434.1192119125187.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil updated JBMESSAGING-381:
------------------------------------

    Attachment: patch-JBMESSAGING-381.txt

tentative patch.

corresponding test case is:
export TARGET_CLASS=org.jboss.test.messaging.jms.PersistenceTest
export TARGET_TEST=testQueueWithDisabledPersistence

test case is:
* deploy a queue with disabled persistence
* send a few messages with DeliveryMode.PERSISTENT
* restart the server
* redeploy the same queue
* check that the queue is empty

(the opposing test is PersistenceTest.testQueuePersistence() which checks
that the messages are still in the queue after restart)

- Persistent is true by default for destinations.
- It can be set only before the destination is started (at deployment time)
- a "not persistent" destination corresponds to a MessagingQueue w/o a 
  PersistenceManager and flagged as non recoverable

I did not check passing null as a PersistenceManager in ChannelSupport is acceptable... it may generate unexpected NPE...

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:30:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 12:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25087275.1192120203552.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381769 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

This issue has a secondary side effect where SessionContext.lookup() calls within 
the bean that had the Resource injected also throws a javax.naming.CommunicationException.

InitialContextFactory.getHAContext():

Hashtable env = ctx.getEnvironment(); // this is the Container's getEnc();
...
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());

This call changes the EJB container's Context.PROVIDER_URL, so SessionContext.lookup 
calls after this are gonna try to go localhost first. If they fail, they'll try do a new InitIalContext() 
which will probably succeed (it did in my tests)

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:32:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4517) Remove the old
 JMSContainerInvoker and ServerSessionPool
In-Reply-To: <17973789.1183572230984.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13486272.1192120323241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4517?page=all ]

Adrian Brock updated JBAS-4517:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120986

This has been mostly done, with some minor tidyup issues on the attached forum thread.

> Remove the old JMSContainerInvoker and ServerSessionPool
> --------------------------------------------------------
>
>                 Key: JBAS-4517
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4517
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The old EJB2.0 JMSContainerInvoker and supporting classes needs removing from the server module.
> With one exception (start/stopDelivery) all the features (+many others) are now supported in the jca inbound jms rar.
> This will remove a dependency on the XIDFactory from the old transaction project which shouldn't even be there.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:34:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4518) EJB3 should not have
 a dependency on the XID factory
In-Reply-To: <18371485.1183572351190.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21805479.1192120443384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4518?page=all ]

Adrian Brock closed JBAS-4518.
------------------------------

    Resolution: Done
      Assignee: Adrian Brock  (was: Carlo de Wolf)

This legacy class has been removed along with referenecs in the configuration.

> EJB3 should not have a dependency on the XID factory
> ----------------------------------------------------
>
>                 Key: JBAS-4518
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4518
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The EJB3 dependency on the XIDFactory should not be there.
> EJB3 should be using the JCA inbound resource adapter.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:07 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4518) EJB3 should not
 have a dependency on the XID factory
In-Reply-To: <18371485.1183572351190.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22451009.1192120567912.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4518?page=all ]

Adrian Brock reopened JBAS-4518:
--------------------------------

             

> EJB3 should not have a dependency on the XID factory
> ----------------------------------------------------
>
>                 Key: JBAS-4518
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4518
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The EJB3 dependency on the XIDFactory should not be there.
> EJB3 should be using the JCA inbound resource adapter.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:08 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4518) EJB3 should not have
 a dependency on the XID factory
In-Reply-To: <18371485.1183572351190.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3514502.1192120568074.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4518?page=all ]

Adrian Brock closed JBAS-4518.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> EJB3 should not have a dependency on the XID factory
> ----------------------------------------------------
>
>                 Key: JBAS-4518
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4518
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The EJB3 dependency on the XIDFactory should not be there.
> EJB3 should be using the JCA inbound resource adapter.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:08 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4519) The IIOP dependency
 on the old transaction needs removing
In-Reply-To: <2125312.1183572351674.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8261403.1192120568556.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4519?page=all ]

Adrian Brock reopened JBAS-4519:
--------------------------------

             

> The IIOP dependency on the old transaction needs removing
> ---------------------------------------------------------
>
>                 Key: JBAS-4519
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4519
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Adrian Brock
>         Assigned To: Francisco Reverbel
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:08 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4519) The IIOP dependency
 on the old transaction needs removing
In-Reply-To: <2125312.1183572351674.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7349141.1192120568784.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4519?page=all ]

Adrian Brock closed JBAS-4519.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> The IIOP dependency on the old transaction needs removing
> ---------------------------------------------------------
>
>                 Key: JBAS-4519
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4519
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Adrian Brock
>         Assigned To: Francisco Reverbel
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:09 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4520) Remove testsuite
 dependency on old transaction manager
In-Reply-To: <10023540.1183572471230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10231135.1192120569156.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4520?page=all ]

Adrian Brock reopened JBAS-4520:
--------------------------------

             

> Remove testsuite dependency on old transaction manager
> ------------------------------------------------------
>
>                 Key: JBAS-4520
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4520
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The parts of the testsuite that depend upon the old transaction manager need removing.
> They should either be replaced with JBossTM as an in-memory transaction manager (this could be done
> by changing the TransactionManagerLocator in the jboss-integration project)
> or the tests need moving to run inside the appserver.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:09 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4520) Remove testsuite
 dependency on old transaction manager
In-Reply-To: <10023540.1183572471230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7670394.1192120569380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4520?page=all ]

Adrian Brock closed JBAS-4520.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> Remove testsuite dependency on old transaction manager
> ------------------------------------------------------
>
>                 Key: JBAS-4520
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4520
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The parts of the testsuite that depend upon the old transaction manager need removing.
> They should either be replaced with JBossTM as an in-memory transaction manager (this could be done
> by changing the TransactionManagerLocator in the jboss-integration project)
> or the tests need moving to run inside the appserver.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:09 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4517) Remove the old
 JMSContainerInvoker and ServerSessionPool
In-Reply-To: <17973789.1183572230984.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2698131.1192120569628.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4517?page=all ]

Adrian Brock closed JBAS-4517.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> Remove the old JMSContainerInvoker and ServerSessionPool
> --------------------------------------------------------
>
>                 Key: JBAS-4517
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4517
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The old EJB2.0 JMSContainerInvoker and supporting classes needs removing from the server module.
> With one exception (start/stopDelivery) all the features (+many others) are now supported in the jca inbound jms rar.
> This will remove a dependency on the XIDFactory from the old transaction project which shouldn't even be there.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:38:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4516) The transaction
 project needs moving out jboss-head since it is obsolete
In-Reply-To: <27290032.1183572051138.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20354746.1192120683637.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4516?page=all ]

Adrian Brock closed JBAS-4516.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

The old transaction manager is now gone from head.

> The transaction project needs moving out jboss-head since it is obsolete
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4516
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4516
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The transaction project in jboss-head is obsolete now that it uses JBossTM.
> The subtasks of this task describe what needs doing to complete that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:40:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Thu, 11 Oct 2007 12:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as that is being removed
 from JBAS code
Message-ID: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
---------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1102
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: 1.4.0.GA
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:53:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Thu, 11 Oct 2007 12:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as
 that is being removed from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19145027.1192121583415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Clebert Suconic closed JBMESSAGING-1102.
----------------------------------------

    Resolution: Done

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:04:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Thu, 11 Oct 2007 13:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-478) ClassCastException on
 AnnotatedParameterAdviceInfo
In-Reply-To: <24439266.1192037583244.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23618154.1192122243295.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-478?page=all ]

Flavia Rainone closed JBAOP-478.
--------------------------------

    Resolution: Done

> ClassCastException on AnnotatedParameterAdviceInfo
> --------------------------------------------------
>
>                 Key: JBAOP-478
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-478
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>
> This is what happens when line 464 of AnnotatedAdviceInfo is executed with a method that returns a parameterized type:
> java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl
>         at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$SingleParameterType.internalValidate(AnnotatedParameterAdviceInfo.java:464)
>         at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$ParameterAnnotationType.validate(AnnotatedParameterAdviceInfo.java:374)
>         at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo.matches(AnnotatedParameterAdviceInfo.java:124)
>         at org.jboss.aop.advice.annotation.AdviceMethodFactory.bestValidAdvice(AdviceMethodFactory.java:412)
>         at org.jboss.aop.advice.annotation.AdviceMethodFactory.findAdviceMethod(AdviceMethodFactory.java:291)
>         at org.jboss.aop.instrument.JoinPointGenerator$AdviceSetups.<init>(JoinPointGenerator.java:1532)
>         at org.jboss.aop.instrument.JoinPointGenerator.initialiseAdviceInfosAndAddFields(JoinPointGenerator.java:550)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:399)
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
>         at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1630)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1626)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
>         at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1017)
>         at org.jboss.test.aop.annotatedAdviceParams.ReturnInvalidPOJO$ReturnInvalidPOJOAdvisor.methodGenericsAfter54841465230530634828(ReturnInvalidPOJO$Retu
> rnInvalidPOJOAdvisor.java)
> This task includes a check on the code to see if the error is repeated in other code lines.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:22:03 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 11 Oct 2007 13:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4814) Refactor the
 conf/jboss-service.xml services
Message-ID: <10029170.1192123323246.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor the conf/jboss-service.xml services
--------------------------------------------

                 Key: JBAS-4814
                 URL: http://jira.jboss.com/jira/browse/JBAS-4814
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Scott M Stark
         Assigned To: Scott M Stark
             Fix For: JBossAS-5.0.0.CR1


The legacy/conf/jboss-service.xml needs to be stripped down, possibly removed as there are too many non-core services in this currently.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:50:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 13:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4815)
 UnifiedInvokerProxyHA - Client
 instance check and assignment should be atomic
Message-ID: <15370726.1192125004025.JavaMail.jira@cloud.prod.atl2.jboss.com>

UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
-----------------------------------------------------------------------------

                 Key: JBAS-4815
                 URL: http://jira.jboss.com/jira/browse/JBAS-4815
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering, Remoting
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Galder Zamarreno
         Assigned To: Galder Zamarreno


I have realised that UnifiedInvokerProxy/UnifiedInvokerProxyHA maintain a instance reference to 
the InvokerLocator/Client instances to a specific invocation is using. That is, when a new target is 
chosen, the unified proxy updates its Client and corresponding InvokerLocator instances (if they've 
changed), and uses the Cient instance variable to make the call. As far as I can see there's no 
synchronisation in the usage/assignment of Client or InvokerLocator. Proxies are meant to be thread 
safe which means that multiple client app threads could be using the same proxy without any problems. 
I can see all this going wrong the moment someone uses client proxies this way in a clustered 
environment with round robin load balance policy. We've got no guarantee that round robin will work 
correctly in these situations.

Several solutions have been discussed in 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:52:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 13:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4816) FirstAvailable -
 access and update of electedTarget is not atomic
Message-ID: <9108020.1192125123233.JavaMail.jira@cloud.prod.atl2.jboss.com>

FirstAvailable - access and update of electedTarget is not atomic
-----------------------------------------------------------------

                 Key: JBAS-4816
                 URL: http://jira.jboss.com/jira/browse/JBAS-4816
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Galder Zamarreno
         Assigned To: Galder Zamarreno
            Priority: Trivial


Looking at FirstAvailable load balance policy, electedTarget access/update is not synchronised, 
however, the chances of having some issues are very small. First, the proxy needs to be shared 
by various threads before the electedTarget has been set, but as electedTarget already elected 
randomly, the secondary effects of this lack of safety are none.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 16:44:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 11 Oct 2007 16:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-83) Maven sub-module
 jbosssx in the project
Message-ID: <28929119.1192135443570.JavaMail.jira@cloud.prod.atl2.jboss.com>

Maven sub-module jbosssx in the project
---------------------------------------

                 Key: SECURITY-83
                 URL: http://jira.jboss.com/jira/browse/SECURITY-83
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Repository
    Affects Versions: 2.0.1-BETA2
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-GA


projects/security/security-jboss-sx/trunk

needs to have two submodules
jbosssx
jbosssx-client

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 16:46:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Thu, 11 Oct 2007 16:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
Message-ID: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>

CtField.getConstantValue() for just added fileds
------------------------------------------------

                 Key: JASSIST-37
                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
             Project: Javassist
          Issue Type: Bug
         Environment: Java 5, javassist 3.4.ga
            Reporter: Vlad Skarzhevskyy
         Assigned To: Shigeru Chiba


I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = fields.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .





-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 11 Oct 2007 17:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-83) Maven sub-module
 jbosssx in the project
In-Reply-To: <28929119.1192135443570.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18928408.1192136823412.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-83?page=all ]

Anil Saldhana closed SECURITY-83.
---------------------------------

    Resolution: Done

> Maven sub-module jbosssx in the project
> ---------------------------------------
>
>                 Key: SECURITY-83
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-83
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Repository
>    Affects Versions: 2.0.1-BETA2
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-GA
>
>
> projects/security/security-jboss-sx/trunk
> needs to have two submodules
> jbosssx
> jbosssx-client

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:42:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 17:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4817)
 PreFillPoolingUnitTestCase isssues
Message-ID: <20249927.1192138923234.JavaMail.jira@cloud.prod.atl2.jboss.com>

PreFillPoolingUnitTestCase isssues
----------------------------------

                 Key: JBAS-4817
                 URL: http://jira.jboss.com/jira/browse/JBAS-4817
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JCA service
    Affects Versions: JBossAS-5.0.0.Beta2, JBossAS-5.0.0.Beta1
            Reporter: Weston Price
         Assigned To: Weston Price
             Fix For:  JBossAS-5.0.0.Beta3


There are two types of failures in the PreFillPoolingUnitTestCase. The first has to do with the new JAXB based deployment in AS5. JAXB appears to have an issue with the following type of XML booleans

<prefill>True</prefill>

JAXB incorrectly marshalls this to false while values such as

<prefill>tRue</prefill>

work. 

The other issue appears to be in timing and relation to the PoolFiller thread. 



-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:44:13 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Thu, 11 Oct 2007 17:44:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12327618.1192139053793.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Edson Tirelli reassigned JBRULES-1268:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:48:04 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Thu, 11 Oct 2007 17:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16150055.1192139284953.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=comments#action_12381830 ] 
            
Edson Tirelli commented on JBRULES-1268:
----------------------------------------

There are 2 problems. The first problem is easy to fix: an Activation that is not queued anymore, should never call dequeue on itself again. This is fixed by nulling out the queue reference in the dequeue method:

    public void dequeue() {
        if ( this.queue != null ) {
            // will only be null if the AgendaGroup is locked when the activation add was attempted
            this.queue.dequeue( this.index );
            this.queue = null;
        }
        this.activated = false;
    }

The second problem is more subtle: is it a valid use case to try to cancel (dequeue) an activation from inside a listener? I don't think we should allow this, since listeners are supposed to be read-only and not influence the rule engine execution.

Ideas?




> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 18:33:03 2007
From: jira-events at lists.jboss.org (Philippe Ombredanne (JIRA))
Date: Thu, 11 Oct 2007 18:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1270) Tool friendly
 MVEL features for MVEl 2.0
Message-ID: <5095612.1192141983349.JavaMail.jira@cloud.prod.atl2.jboss.com>

Tool friendly MVEL features for MVEl 2.0
----------------------------------------

                 Key: JBRULES-1270
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1270
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
            Reporter: Philippe Ombredanne
         Assigned To: Mark Proctor
             Fix For: FUTURE


Here are a couple request for MVEl 2.0:
- keeping something like an ast (may be with a  compile flag) that is close to the actual expression text
- producing compiled expression even of there were some errors (ie keep on trucking) (optional flag for that too)
- being able to extend the ast with completion information (ie attach completion stuffs directly as a decoration of node in the parse tree

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 19:09:03 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 11 Oct 2007 19:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4424)
 WebAuthentication:Generate a SSOID
In-Reply-To: <20618100.1179337252975.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3576019.1192144143964.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4424?page=comments#action_12381884 ] 
            
Stefan Guilhen commented on JBAS-4424:
--------------------------------------

I'm implementing the SSO functionality pretty much like the AuthenticatorBase, by delegating the SSO operations to the SingleSignOn valve. However, the methods that we must invoke (register, update, associate) are protected in the SingleSignOn class. I've started a discussion on the forums (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094309#4094309), and my first idea is to relax the SingleSignOn method's access to public in JBossWeb.

> WebAuthentication:Generate a SSOID
> ----------------------------------
>
>                 Key: JBAS-4424
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4424
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Security
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication
> The feature needs to implement the sso stuff if it is desired by the user.  At the least, ssoid needs to be generated and set on the session.
> The ssoid generation logic exists in AuthenticatorBase.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 19:53:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 19:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5467112.1192146783345.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=comments#action_12381888 ] 
            
Michael Neale commented on JBRULES-1268:
----------------------------------------

yes that is a good point. The problem is that the event listener exposes the activation item in its API, thus the remove() is there. 

AgendaFilter is really what this is for. 

I would be happy with this to throw a UnsupportedOperationException - with clear error message saying how you can't change the activation inside a event listener (and use a filter instead).

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 20:33:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 11 Oct 2007 20:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1268)
 Activation.remove() is removing
 the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15171768.1192149183322.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Mark Proctor closed JBRULES-1268.
---------------------------------

    Resolution: Done

I've set this to null the queue, so if called twice this method does nothing. I'm less worried about this as it should never be called by a user. If someone wants to update javadocs, go for it. We could update the event object not to expose the Activation, that is a possability. So it just has getRule, getFactHandle methods.

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:15:04 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4720) Ensure
 security-domain is picked up by JCA Deployer
In-Reply-To: <25591894.1189710491347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12789027.1192158904386.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4720?page=all ]

Weston Price resolved JBAS-4720.
--------------------------------

    Resolution: Done

The new deployment model correctly handles security domain deployments.

> Ensure security-domain is picked up by JCA Deployer
> ---------------------------------------------------
>
>                 Key: JBAS-4720
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4720
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Anil Saldhana
>         Assigned To: Weston Price
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Ensure that the security-domain settings are read into the metadata to be used by ConnectionManager.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:17:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4671)
 DsDataSourceTemplate needs to be completed
In-Reply-To: <29814872.1188958164434.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7707397.1192159023564.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4671?page=all ]

Weston Price reassigned JBAS-4671:
----------------------------------

    Assignee: Weston Price

> DsDataSourceTemplate needs to be completed
> ------------------------------------------
>
>                 Key: JBAS-4671
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4671
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service, Management services
>            Reporter: Scott M Stark
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The org.jboss.resource.deployers.management,DsDataSourceTemplate template implementation needs to be completed to allow the addition of datasources.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:17:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4671) DsDataSourceTemplate
 needs to be completed
In-Reply-To: <29814872.1188958164434.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26872096.1192159023888.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4671?page=all ]

Weston Price updated JBAS-4671:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120873

> DsDataSourceTemplate needs to be completed
> ------------------------------------------
>
>                 Key: JBAS-4671
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4671
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service, Management services
>            Reporter: Scott M Stark
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The org.jboss.resource.deployers.management,DsDataSourceTemplate template implementation needs to be completed to allow the addition of datasources.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:19:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4059) JBoss5 RARDeployer
 deploys RAR's twice
In-Reply-To: <15351446.1170628159545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15189924.1192159143422.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4059?page=all ]

Weston Price resolved JBAS-4059.
--------------------------------

    Resolution: Out of Date

Old issue that has been addressed by latest deployer framework.

> JBoss5 RARDeployer deploys RAR's twice
> --------------------------------------
>
>                 Key: JBAS-4059
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4059
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Weston Price
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Because of the new deployment structure in JBoss5, the RAR deployer is now deploying RAR's twice. I assume this has to do with the RARDeployer using a deprecated API of the DeploymentUnit. 
> As a result, the JMX console records deployments such as:
> # name='jboss-ha-local-jdbc.rar#jboss-ha-local-jdbc.rar',service=RARDeployment
> # name='jboss-ha-local-jdbc.rar',service=RARDeployment
> This is causing issues with programmatic deployment, as well as the new metadata repository. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:47:58 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 23:47:58 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1271) Test Manager
Message-ID: <23074427.1192160878947.JavaMail.jira@cloud.prod.atl2.jboss.com>

Test Manager
------------

                 Key: JBRULES-1271
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1271
             Project: JBoss Drools
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: drools-brms
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:47:59 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 23:47:59 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1121) Operator field and
 the fact's variable field required in the "then" part of the rule
In-Reply-To: <26598244.1187937569373.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14621178.1192160879140.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1121?page=all ]

Michael Neale closed JBRULES-1121.
----------------------------------

    Fix Version/s: 4.1.0
                       (was: FUTURE)
       Resolution: Done

I have changed the behaviour of this a bit - should be clearer in future how to do this.

> Operator field and the fact's variable field required in the "then" part of the rule
> ------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1121
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1121
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE, drools-brms
>    Affects Versions:  4.0.0.GA
>         Environment: drools-jbrms stand alone and Eclipse drools-4.0.0 
>            Reporter: sreeni sabapathy
>         Assigned To: Michael Neale
>            Priority: Minor
>             Fix For: 4.1.0
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> In the drools-jbrms standalone and even in the eclipse plugin version of "New guided drl file"
> the "then" part of the rule has the limitation of assigning the fixed value to the fact's variable.
> But in many condition the the value of the variable depends upon the value of another variable.
> I have taken  a simple example for explanation.
> For calcluating simple interest
> SI = P*T*R/100
> Now in the rule file if the 
> "when" condition as the check of " Calcluation type (simple ineterst or compound interest)"
> "then" part having SI, 
> At the present drool-jbrms definition the 
> "then" part has SI = text field.
> But my requirement is to look up the class variable "principle", "Time" and the "Rate" and then calculate, not just 
> assign some fixed values.
> In a simple sentence I would appreciate if the drools- jbrms has the options related to  "when" in the "then" part of the rule also.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:47:59 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 23:47:59 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1271) Test Manager
In-Reply-To: <23074427.1192160878947.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28592259.1192160879411.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1271?page=all ]

Michael Neale updated JBRULES-1271:
-----------------------------------

      Component/s: drools-brms
    Fix Version/s: FUTURE
      Description: General JIRA for test manager features.

> Test Manager
> ------------
>
>                 Key: JBRULES-1271
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1271
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>
> General JIRA for test manager features.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:02:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
Message-ID: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
---------------------------------------------------------------

                 Key: JBAS-4818
                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:04:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15613208.1192161843236.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith updated JBAS-4818:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

Chapter 1 is Attached.

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:06:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
Message-ID: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - TRACKER
-----------------------------------------

                 Key: JBAS-4819
                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Directory Structure
Message-ID: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 2 -  Directory Structure
------------------------------------------------------------------

                 Key: JBAS-4820
                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt

Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Directory Structure
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28514986.1192162263453.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Michael Smith updated JBAS-4820:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-2.odt

Chapter 2 Attached

> TECH REVIEW: Installation Guide - Chapter 2 -  Directory Structure
> ------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:13:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  The Default Server Configuration File Set
Message-ID: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 3 -  The Default Server Configuration File Set
----------------------------------------------------------------------------------------

                 Key: JBAS-4821
                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


 Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:15:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4822) TECH REVIEW:
 Installation Guide -
 Chapter 4 -  The Default Server Configuration File Set
Message-ID: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 4 -  The Default Server Configuration File Set
----------------------------------------------------------------------------------------

                 Key: JBAS-4822
                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt

Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:15:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide -
 Chapter 4 -  The Default Server Configuration File Set
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30427653.1192162503415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-4.odt

Chapter 4 Attached

> TECH REVIEW: Installation Guide - Chapter 4 -  The Default Server Configuration File Set
> ----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:17:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Starting and Stopping JBoss
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19742778.1192162623352.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 4 -  Starting and Stopping JBoss  (was: TECH REVIEW: Installation Guide - Chapter 4 -  The Default Server Configuration File Set)

> TECH REVIEW: Installation Guide - Chapter 4 -  Starting and Stopping JBoss
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:17:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  The Default Server Configuration File Set
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21949056.1192162623501.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

Michael Smith updated JBAS-4821:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-3.odt

Chapter 3 Attached

> TECH REVIEW: Installation Guide - Chapter 3 -  The Default Server Configuration File Set
> ----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:28:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4823) TECH REVIEW: Getting
 Started Guide - TRACKER
Message-ID: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - TRACKER
--------------------------------------------

                 Key: JBAS-4823
                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:34 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4824) TECH REVIEW: Getting
 Started Guide - Appendix A. Further Information Sources
Message-ID: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
----------------------------------------------------------------------------

                 Key: JBAS-4824
                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:34 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - Getting Started
Message-ID: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started
----------------------------------------------------------------

                 Key: JBAS-4825
                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/



-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4826) TECH REVIEW: Getting
 Started Guide - Chapter 2. The JBoss Server - A Quick Tour
Message-ID: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour
-------------------------------------------------------------------------------

                 Key: JBAS-4826
                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
Message-ID: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
------------------------------------------------------------------------------

                 Key: JBAS-4827
                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. The Duke's Bank Application
Message-ID: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 4. The Duke's Bank Application
---------------------------------------------------------------------------

                 Key: JBAS-4828
                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. J2EE Web Services
Message-ID: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 5. J2EE Web Services
-----------------------------------------------------------------

                 Key: JBAS-4829
                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. JMS and Message-Driven Beans
Message-ID: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans
----------------------------------------------------------------------------

                 Key: JBAS-4830
                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4831) TECH REVIEW: Getting
 Started Guide - Chapter 7. Container-Managed Persistence
Message-ID: <2964949.1192165535786.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
-----------------------------------------------------------------------------

                 Key: JBAS-4831
                 URL: http://jira.jboss.com/jira/browse/JBAS-4831
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4832) TECH REVIEW: Getting
 Started Guide - Chapter 8. Using other Databases
Message-ID: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
---------------------------------------------------------------------

                 Key: JBAS-4832
                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:36 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:36 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4833) TECH REVIEW: Getting
 Started Guide - Chapter 9. Using Hibernate
Message-ID: <12730012.1192165536058.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
---------------------------------------------------------------

                 Key: JBAS-4833
                 URL: http://jira.jboss.com/jira/browse/JBAS-4833
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4824) TECH REVIEW: Getting
 Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27804898.1192165623713.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Michael Smith updated JBAS-4824:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Appendix.odt

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4833) TECH REVIEW: Getting
 Started Guide - Chapter 9. Using Hibernate
In-Reply-To: <12730012.1192165536058.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21464001.1192165623842.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4833?page=all ]

Michael Smith updated JBAS-4833:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-9.odt

> TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
> ---------------------------------------------------------------
>
>                 Key: JBAS-4833
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4833
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-9.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4832) TECH REVIEW: Getting
 Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12852496.1192165624029.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4832?page=all ]

Michael Smith updated JBAS-4832:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-8.odt

> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4831) TECH REVIEW: Getting
 Started Guide - Chapter 7. Container-Managed Persistence
In-Reply-To: <2964949.1192165535786.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6612848.1192165624146.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4831?page=all ]

Michael Smith updated JBAS-4831:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-7.odt

> TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4831
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4831
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-7.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. JMS and Message-Driven Beans
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11527511.1192165624264.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Michael Smith updated JBAS-4830:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-6.odt

> TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. J2EE Web Services
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20457507.1192165624406.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Michael Smith updated JBAS-4829:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-5.odt

> TECH REVIEW: Getting Started Guide - Chapter 5. J2EE Web Services
> -----------------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. The Duke's Bank Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28879582.1192165624565.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Michael Smith updated JBAS-4828:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-4.odt

> TECH REVIEW: Getting Started Guide - Chapter 4. The Duke's Bank Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8294341.1192165624714.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Michael Smith updated JBAS-4827:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-3.odt

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started Guide - Chapter 2. The JBoss Server - A Quick Tour
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5040531.1192165624834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Michael Smith updated JBAS-4826:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-2.odt

> TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - Getting Started
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30196809.1192165624973.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

Michael Smith updated JBAS-4825:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-1.odt

> TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started
> ----------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:11:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
Message-ID: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Clustering Guide - TRACKER
---------------------------------------

                 Key: JBAS-4834
                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
Message-ID: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
--------------------------------------------------------

                 Key: JBAS-4835
                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
Message-ID: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
-----------------------------------------------------------------------

                 Key: JBAS-4836
                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
Message-ID: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
-----------------------------------------------------------------------

                 Key: JBAS-4837
                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
Message-ID: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
----------------------------------------------------------------------

                 Key: JBAS-4838
                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
Message-ID: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
------------------------------------------------------------

                 Key: JBAS-4839
                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
Message-ID: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
----------------------------------------------------------

                 Key: JBAS-4840
                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:37:18 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:37:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
Message-ID: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Chapter2 - JBossCache and JGroups Services
-------------------------------------------------------

                 Key: JBAS-4841
                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:37:18 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:37:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23378177.1192167438605.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

samson kittoli updated JBAS-4838:
---------------------------------

          Component/s: Documentation
    Affects Version/s: JBossAS-4.2.2.GA
              Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:37:18 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:37:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31680594.1192167438749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

samson kittoli updated JBAS-4837:
---------------------------------

          Component/s: Documentation
    Affects Version/s: JBossAS-4.2.2.GA
              Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:39:24 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:39:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6724946.1192167564192.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

samson kittoli updated JBAS-4836:
---------------------------------

          Component/s: Documentation
    Affects Version/s: JBossAS-4.2.2.GA
              Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:39:24 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:39:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30564211.1192167564359.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

samson kittoli updated JBAS-4835:
---------------------------------

    Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:39:24 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:39:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24988166.1192167564539.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

samson kittoli updated JBAS-4839:
---------------------------------

    Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:41:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27184631.1192167663319.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

samson kittoli updated JBAS-4835:
---------------------------------

    Attachment: JBAS-422 - Clustering -  Chapter1 - Introduction.odt

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:41:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20521541.1192167663467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

samson kittoli updated JBAS-4836:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30925513.1192167783423.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

samson kittoli updated JBAS-4837:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10974014.1192167783540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

samson kittoli updated JBAS-4838:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9016242.1192167783824.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

samson kittoli updated JBAS-4839:
---------------------------------

    Attachment: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8884290.1192167784057.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

samson kittoli updated JBAS-4840:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21640176.1192167784240.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

samson kittoli updated JBAS-4841:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:50:17 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:50:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24797602.1192168217974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

samson kittoli updated JBAS-4835:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:01:19 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 12 Oct 2007 02:01:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29152137.1192168879742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Rubinger resolved EJBTHREE-1062.
---------------------------------------

    Resolution: Done

Unit test passes, none further broken (some unit tests required alterations to their existing naming strategies as fixes for this issue created a naming conflict).

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:01:19 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:01:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24747654.1192168879989.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

samson kittoli updated JBAS-4839:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:03:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14038244.1192168983437.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

samson kittoli updated JBAS-4840:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:03:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25108525.1192168983630.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

samson kittoli updated JBAS-4841:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:05:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4842) TECH REVIEW: Server
 Configuration Guide - TRACKER
Message-ID: <22836378.1192169103482.JavaMail.jira@cloud.prod.atl2.jboss.com>

 TECH REVIEW: Server Configuration Guide - TRACKER
--------------------------------------------------

                 Key: JBAS-4842
                 URL: http://jira.jboss.com/jira/browse/JBAS-4842
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 02:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1197) Incorporate
 Spanish XML into Cache docs repo and build
Message-ID: <10175107.1192169223335.JavaMail.jira@cloud.prod.atl2.jboss.com>

Incorporate Spanish XML into Cache docs repo and build
------------------------------------------------------

                 Key: JBCACHE-1197
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1197
             Project: JBoss Cache
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Michael Smith
         Assigned To: Manik Surtani


Need to put the spanish XML file where it belongs

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
Message-ID: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
---------------------------------------------------------------------------------------------

                 Key: JBAS-4843
                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
Message-ID: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
-------------------------------------------------------------------------------

                 Key: JBAS-4844
                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4845) TECH REVIEW: Server
 Configuration
 Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
Message-ID: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
---------------------------------------------------------------------------------------------------------

                 Key: JBAS-4845
                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Messaging on JBoss
Message-ID: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Server Configuration Guide - Chapter6 - Messaging on JBoss
------------------------------------------------------------------------

                 Key: JBAS-4846
                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Transactions on JBoss
Message-ID: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Server Configuration Guide - Chapter5 - Transactions on JBoss
---------------------------------------------------------------------------

                 Key: JBAS-4847
                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Connectors on JBoss
Message-ID: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter4 - Connectors on JBoss
------------------------------------------------------------------------

                 Key: JBAS-4848
                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - Naming on JBoss
Message-ID: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Server Configuration Guide - Chapter3 - Naming on JBoss
---------------------------------------------------------------------

                 Key: JBAS-4849
                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
Message-ID: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
---------------------------------------------------------------

                 Key: JBAS-4850
                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
Message-ID: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
-----------------------------------------------------------------------------------------------

                 Key: JBAS-4851
                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5266748.1192170423487.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

samson kittoli updated JBAS-4851:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7674676.1192170423604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

samson kittoli updated JBAS-4850:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - Naming on JBoss
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28106266.1192170423718.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

samson kittoli updated JBAS-4849:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter3 - Naming on JBoss
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Connectors on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22761692.1192170423837.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli updated JBAS-4848:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter4 - Connectors on JBoss
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Transactions on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15672135.1192170423964.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

samson kittoli updated JBAS-4847:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Messaging on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3048313.1192170424104.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

samson kittoli updated JBAS-4846:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Messaging on JBoss
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration
 Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4857463.1192170424220.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

samson kittoli updated JBAS-4845:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt

> TECH REVIEW: Server Configuration Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9512597.1192170424355.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

samson kittoli updated JBAS-4844:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:29:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20888218.1192170543216.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

samson kittoli updated JBAS-4843:
---------------------------------

    Attachment: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:31:05 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Fri, 12 Oct 2007 02:31:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1627) Evaluate and
 implement missing JSR-88 functionality
Message-ID: <17756514.1192170665958.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1627?page=all ]

Max Andersen closed JBAS-1627.
------------------------------

    Resolution: Rejected

> Evaluate and implement missing JSR-88 functionality
> ---------------------------------------------------
>
>                 Key: JBAS-1627
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1627
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>    Affects Versions: JBossAS-4.0.1 Final
>         Environment: deployment module
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:31:06 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Fri, 12 Oct 2007 02:31:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-1627) Evaluate and
 implement missing JSR-88 functionality
Message-ID: <20455638.1192170666270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1627?page=all ]

Max Andersen reopened JBAS-1627:
--------------------------------

             
wrong bug ;)

> Evaluate and implement missing JSR-88 functionality
> ---------------------------------------------------
>
>                 Key: JBAS-1627
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1627
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>    Affects Versions: JBossAS-4.0.1 Final
>         Environment: deployment module
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:45:15 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 12 Oct 2007 02:45:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4822584.1192171515246.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=all ]

Andrew Rubinger reassigned EJBTHREE-1066:
-----------------------------------------

    Assignee: Andrew Rubinger

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:44:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 12 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3894053.1192175043343.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Rubinger reopened EJBTHREE-1062:
---------------------------------------

             
Should not require JNDI naming fixes.

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:44:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7250862.1192175043521.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12381960 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I verified that jbossws-2.0.1.SP2 core tests pass against Branch_4_2.

The difference between SP1 and SP2 is that SP2 does not ship with the (outdated) container integration jar jbossws-jboss42.jar, which is now part of the AS code base. i.e. jbossws-jboss42.jar is not part of jbossws.sar any more.

Do you want me to install that version. Other than that there is no change and hence there is no QA rerun required.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:46:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7793479.1192175163488.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Thomas Diesler reassigned JBAS-4811:
------------------------------------

    Assignee: Dimitris Andreadis

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:46:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27767301.1192175163646.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12381961 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

The latest test run is here

http://jbws.dyndns.org:8280/hudson/

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:54:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4852) EJB3 web service
 endpoints ignore metadata in jboss.xml
Message-ID: <16146379.1192175643414.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJB3 web service endpoints ignore metadata in jboss.xml
-------------------------------------------------------

                 Key: JBAS-4852
                 URL: http://jira.jboss.com/jira/browse/JBAS-4852
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Carlo de Wolf
             Fix For: JBossAS-4.2.2.GA


This is related to JBWS-1813

It needs to be decided whether jboss-4.2.2 can go out despite this issue.
Currently, users are forced to use annotations on the bean.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 04:00:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 12 Oct 2007 04:00:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7717327.1192176007545.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12381962 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

Sure, we should move to SP2.

How you propose to incorporate the WS tests in AS releases?

Wouldn't the easiest thing be to replicate your hudson configuration in the QA environment?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 04:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 12 Oct 2007 04:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1067) Refactor EJB 3
 onto the unified metadata
Message-ID: <16637681.1192176603400.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor EJB 3 onto the unified metadata
----------------------------------------

                 Key: EJBTHREE-1067
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1067
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Carlo de Wolf
         Assigned To: Carlo de Wolf
            Priority: Critical
             Fix For: AS 5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 04:38:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 12 Oct 2007 04:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1067) Refactor EJB 3
 onto the unified metadata
In-Reply-To: <16637681.1192176603400.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29277586.1192178283650.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1067?page=all ]

Carlo de Wolf updated EJBTHREE-1067:
------------------------------------

     Original Estimate: 1 week
    Remaining Estimate: 1 week

> Refactor EJB 3 onto the unified metadata
> ----------------------------------------
>
>                 Key: EJBTHREE-1067
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1067
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:02:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 12 Oct 2007 05:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27116.1192179723315.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=comments#action_12381964 ] 
            
Dimitris Andreadis commented on EJBTHREE-1062:
----------------------------------------------

I added a note about this problem in the 4.2.2.GA release notes.

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:16:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-171) Split the jPDL plugin
 in a Common/jPDL/BPEL plugin triad
Message-ID: <25610757.1192180563603.JavaMail.jira@cloud.prod.atl2.jboss.com>

Split the jPDL plugin in a Common/jPDL/BPEL plugin triad
--------------------------------------------------------

                 Key: GPD-171
                 URL: http://jira.jboss.com/jira/browse/GPD-171
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers


the common classes and extension points have to be included in the common plugin

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:18:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-172) Develop an extension
 example for a simple DSL in its own plugin
Message-ID: <16781370.1192180683620.JavaMail.jira@cloud.prod.atl2.jboss.com>

Develop an extension example for a simple DSL in its own plugin
---------------------------------------------------------------

                 Key: GPD-172
                 URL: http://jira.jboss.com/jira/browse/GPD-172
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:18:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:18:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-173) Develop a complete
 jPDL extension example
Message-ID: <19634315.1192180685849.JavaMail.jira@cloud.prod.atl2.jboss.com>

Develop a complete jPDL extension example
-----------------------------------------

                 Key: GPD-173
                 URL: http://jira.jboss.com/jira/browse/GPD-173
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:20:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-174) Develop a jPDL
	cheatsheet
Message-ID: <1560923.1192180803591.JavaMail.jira@cloud.prod.atl2.jboss.com>

Develop a jPDL cheatsheet
-------------------------

                 Key: GPD-174
                 URL: http://jira.jboss.com/jira/browse/GPD-174
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:40:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 05:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
Message-ID: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>

jbossxb-1.0.0.GA shows webservice regression
--------------------------------------------

                 Key: JBAS-4853
                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For: JBossAS-4.2.2.GA


This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11

org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString

junit.framework.ComparisonFailure: expected:<   > but was:<>
	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:00:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Moved: (GPD-175) jBPM Process Designer
 fails with class cast exception
Message-ID: <12168646.1192183203536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-175?page=all ]

Koen Aers moved JBIDE-523 to GPD-175:
-------------------------------------

          Project: JBoss jBPM GPD  (was: JBoss Tools)
              Key: GPD-175  (was: JBIDE-523)
      Component/s: jpdl
                       (was: jbpm)
    Fix Version/s: jBPM jPDL Designer 3.1.0.SP1
                       (was: 2.0.0.CR1)

> jBPM Process Designer fails with class cast exception
> -----------------------------------------------------
>
>                 Key: GPD-175
>                 URL: http://jira.jboss.com/jira/browse/GPD-175
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Fedora Core 6 with Sun's Java 1.5.0_12
> Lenovo ThinkPad T60
> 2GB RAM
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.0.SP1
>
>         Attachments: processdefinition.xml
>
>
> I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open:
> java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput
> 	at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source)
> 	at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
> 	at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
> 	at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> 	at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> 	at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
> 	at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
> 	at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
> 	at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
> 	at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> 	at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822)
> 	at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721)
> 	at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100)
> 	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
> 	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> 	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
> 	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
> 	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:10:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-175) jBPM Process Designer
 fails with class cast exception
Message-ID: <7561128.1192183803723.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-175?page=all ]

Koen Aers updated GPD-175:
--------------------------

    Attachment: processimage.jpg

I guess it is not relevant anymore. I have attached the diagram that I get when opening the file (after some node-dragging to make it look better)

> jBPM Process Designer fails with class cast exception
> -----------------------------------------------------
>
>                 Key: GPD-175
>                 URL: http://jira.jboss.com/jira/browse/GPD-175
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Fedora Core 6 with Sun's Java 1.5.0_12
> Lenovo ThinkPad T60
> 2GB RAM
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.0.SP1
>
>         Attachments: processdefinition.xml, processimage.jpg
>
>
> I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open:
> java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput
> 	at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source)
> 	at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
> 	at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
> 	at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> 	at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> 	at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
> 	at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
> 	at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
> 	at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
> 	at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> 	at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822)
> 	at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721)
> 	at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100)
> 	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
> 	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> 	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
> 	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
> 	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:12:12 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:12:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-175) jBPM Process Designer
 fails with class cast exception
Message-ID: <23678244.1192183932844.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-175?page=all ]

Koen Aers closed GPD-175.
-------------------------

    Resolution: Done

I am closing this issue. Micah, if you still experience problems feel free to reopen.

> jBPM Process Designer fails with class cast exception
> -----------------------------------------------------
>
>                 Key: GPD-175
>                 URL: http://jira.jboss.com/jira/browse/GPD-175
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Fedora Core 6 with Sun's Java 1.5.0_12
> Lenovo ThinkPad T60
> 2GB RAM
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.0.SP1
>
>         Attachments: processdefinition.xml, processimage.jpg
>
>
> I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open:
> java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput
> 	at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source)
> 	at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
> 	at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
> 	at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> 	at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> 	at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
> 	at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
> 	at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
> 	at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
> 	at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> 	at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822)
> 	at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721)
> 	at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100)
> 	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
> 	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> 	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
> 	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
> 	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:30:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-176) Add code completion
 inside attributes and values within the xml source
Message-ID: <32030443.1192185004070.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add code completion inside attributes and values within the xml source
----------------------------------------------------------------------

                 Key: GPD-176
                 URL: http://jira.jboss.com/jira/browse/GPD-176
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:32:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-177) Add code completion in
 the text input fields on the properties view
Message-ID: <10554814.1192185123592.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add code completion in the text input fields on the properties view
-------------------------------------------------------------------

                 Key: GPD-177
                 URL: http://jira.jboss.com/jira/browse/GPD-177
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:59:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25969415.1192186743304.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382034 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I installed jbossws-2.0.1.SP2

Yes, QA should integrate our hudson environment, which is part of the jbossws framework codebase.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:08:04 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Fri, 12 Oct 2007 07:08:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4455) LoadBalancePolicy
 that tries to pin all requests associated with a tx to one server
In-Reply-To: <14717863.1180632608477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17049743.1192187284260.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4455?page=comments#action_12382040 ] 
            
Galder Zamarreno commented on JBAS-4455:
----------------------------------------

[private]

Another potential customer interested in this feature:
https://na1.salesforce.com/50030000003i3bC

> LoadBalancePolicy that tries to pin all requests associated with a tx to one server
> -----------------------------------------------------------------------------------
>
>                 Key: JBAS-4455
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4455
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>
> The HA proxies don't allow failover once a tx has reached a server.  This can lead to this kind of situation:
> EJB A deployed on nodes 1 and 2.
> EJB B deployed on nodes 1 and 2.
> 1) Start tx, invoke on A.1.
> 2) Lookup B.
> 3) Invoke on B. LB policy picks B.2
> 4) Node 2 is dead for some reason so call fails.
> 5) Can't fail over because tx context won't allow a failover after a call has reached a server.
> But, B.1 is fine and is running on the only node the tx has invoked on. :(
> Approach to improving this.  This is based on JRMPInovkerProxyHA methods, but the idea is generic:
> In invocationHasReachedAServer, instead of storing null as the value, you store the target (key is the tx).
> In invoke, if there's a tx, you add that target (if there is one) to the invocation as transient metadata 
> The LB policy gets passed the invocation as an arg when it chooses a target (this is already in the API)
> LB policy checks for the metadata. If there, and that target is in its target list, return that target

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:14:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 07:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user only if child folders
 have write or manage permssion for anonymous (read is not enough)
Message-ID: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>

ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
--------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1742
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final
         Environment: JBoss 4.2.1
            Reporter: Mariusz Smykula
         Assigned To: Sohil Shah


I want to execute simple code from my portlet:

 Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
 mainFolder = (Folder) cmsService.execute(listCMD);
 LOG.info(mainFolder .getFolders().size()); 

This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?

This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!

  for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
        {
            Permission specificPermission = (Permission)itr.next();
            
            if( (specificPermission.getService().equals("cms")) && 
                (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
            )
            {
                for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
                {
                    Permission userPermission = (Permission)itr2.next();
                    if( (userPermission.getService().equals("cms")) && 
                        (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
                    )
                    {
                        String pathCriteria = userPermission.findCriteriaValue("path");
                        if(pathCriteria.equals(path))
                        {
                            //this means this user has read access to this path
                            toolAccess = true;
                        }
                    }
                }
            }
        }

This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:20:30 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 07:20:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user
 only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <635736.1192188030146.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=comments#action_12382047 ] 
            
Mariusz Smykula commented on JBPORTAL-1742:
-------------------------------------------

Ok, computeToolAccess have interesting comment, but why this method is included in ACLInterceptor? I want to access CMS resources from my custom portlet and list them.

 * This is used to filter out cms resources in the CMS Admin tool, so that the user
     * can see only the resources that he has write/manage access to

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:41:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 07:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1197) Incorporate
 Spanish XML into Cache docs repo and build
In-Reply-To: <10175107.1192169223335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13491238.1192189263574.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1197?page=comments#action_12382067 ] 
            
Manik Surtani commented on JBCACHE-1197:
----------------------------------------

And where does this belong?  Current English docs reside in subversion alongside the code.  Not sure if we want all translations here as well since translations may be out of sync or a couple of releases behind.  E.g., the code is at version 2.1.0.Beta1, (and so is the English documentation) but given that we cut a public release ever couple of months, there may not be time for translations to catch up.

What would you suggest here?

> Incorporate Spanish XML into Cache docs repo and build
> ------------------------------------------------------
>
>                 Key: JBCACHE-1197
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1197
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Smith
>         Assigned To: Manik Surtani
>
> Need to put the spanish XML file where it belongs

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:13:13 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 08:13:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user
 only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23876766.1192191193680.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=comments#action_12382098 ] 
            
Mariusz Smykula commented on JBPORTAL-1742:
-------------------------------------------

In class ACLInterceptor (line: 270) is this code necessary?

securityContext.removeAttribute("command");

without this line, the ACLEnforcer know than my anonymous user want read subfolders, and then show folders to him.

For full explanation:
* Logged user can see subfolders without write or manage permission (only read is needed). 
* Anonymous user cant see subfolders with read permission - subfolders must be write or manage for Anonymous.

I think this is bad behavior.

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:15:21 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 08:15:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1467) URL's of page's
 whose
 <page-name> attribute has ampersand used as an entity (&amp;) is not
 encoded correctly
In-Reply-To: <18766428.1180623548864.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24166039.1192191321945.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1467?page=all ]

Thomas Heute reassigned JBPORTAL-1467:
--------------------------------------

    Assignee: Thomas Heute  (was: Julien Viet)

> URL's of page's whose <page-name> attribute has ampersand used as an entity (&amp;) is not encoded correctly
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1467
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1467
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.4.1 Final
>         Environment: All
>            Reporter: deepashree krishnamurthy
>         Assigned To: Thomas Heute
>
> URL's of page's whose <page-name> attribute has ampersand used as an entity (&amp;) is not encoded correctly.
> Define a page in *-object.xml eith ampersand in page-name 
> ex: 
> <deployment>
>      <if-exists>overwrite</if-exists>
>      <parent-ref>default</parent-ref>
>      <properties/>
>      <page>
>           <page-name>Auto &amp; Navigator</page-name>
>            :
>     </page>
> :
> </deployment>
> The page is unaccessible on FireFox. Seems that it is not encoded 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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:26:38 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 08:26:38 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-999) Bridge startup
 should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30538482.1192191998374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=all ]

Tim Fox closed JBMESSAGING-999.
-------------------------------

    Resolution: Done

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:37:19 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 12 Oct 2007 08:37:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-18) Work with Marshall on
 defining JBoss AOP IDE requirements
Message-ID: <24473605.1192192639920.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-18?page=all ]

Kabir Khan closed JBAOP-18.
---------------------------

    Resolution: Out of Date

> Work with Marshall on defining JBoss AOP IDE requirements
> ---------------------------------------------------------
>
>                 Key: JBAOP-18
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-18
>             Project: JBoss AOP
>          Issue Type: Feature Request
>    Affects Versions: 2.1.0.GA
>            Reporter: Bill Burke
>         Assigned To: Kabir Khan
>             Fix For: 2.1.0.GA
>
>
> Work with Marshall on what we need to improve JBoss AOP IDE support.  For both performance of the IDE, usability, and features.  Work on the ROADMAP to define when these should go out

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:46:22 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 12 Oct 2007 08:46:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-479) Enable
 org.jboss.test.aop.proxy.ProxyTestCase(jdk14).testAnnotationsExistInProxy
Message-ID: <24646856.1192193182276.JavaMail.jira@cloud.prod.atl2.jboss.com>

Enable org.jboss.test.aop.proxy.ProxyTestCase(jdk14).testAnnotationsExistInProxy
--------------------------------------------------------------------------------

                 Key: JBAOP-479
                 URL: http://jira.jboss.com/jira/browse/JBAOP-479
             Project: JBoss AOP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Kabir Khan
         Assigned To: Kabir Khan
             Fix For: 2.0.0.GA


   public void testAnnotationsExistInProxy() throws Exception
   {
      //THis test fails if we run with jboss retro
      try
      {
         Class.forName("org.jboss.lang.ClassRedirects");
         System.out.println("IGNORING TEST ON JDK 1.4");
         return;
      }
      catch(Exception ignoreWeAreRunningWithJDK5)
      {
      }  

This *might* be deferrable to a later release since it is a JDK 1.4 thing and AOP 2.0 is targeting AS 5 (JDK 5)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:48:19 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 12 Oct 2007 08:48:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1103) Move JBM
	examples
Message-ID: <6865711.1192193299985.JavaMail.jira@cloud.prod.atl2.jboss.com>

Move JBM examples
-----------------

                 Key: JBMESSAGING-1103
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1103
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: AS 5.0 Integration, EAP 4.3 Integration
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:50:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 08:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8808787.1192193403311.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=all ]

Thomas Heute updated JBPORTAL-1742:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:57:26 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 08:57:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1103) Move JBM
	examples
In-Reply-To: <6865711.1192193299985.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13133475.1192193846316.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1103?page=all ]

Tim Fox updated JBMESSAGING-1103:
---------------------------------

        Fix Version/s: AS 5.0 Integration
                       EAP 4.3 Integration
    Affects Version/s:     (was: AS 5.0 Integration)
                           (was: EAP 4.3 Integration)

> Move JBM examples
> -----------------
>
>                 Key: JBMESSAGING-1103
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1103
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:57:26 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 08:57:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2942498.1192193846827.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=all ]

Tim Fox updated JBMESSAGING-1101:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:07:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 12 Oct 2007 09:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1104) Set StrictTCK
 as false by default, and chage TCK to be true
Message-ID: <8986192.1192194423340.JavaMail.jira@cloud.prod.atl2.jboss.com>

Set StrictTCK as false by default, and chage TCK to be true
-----------------------------------------------------------

                 Key: JBMESSAGING-1104
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1104
             Project: JBoss Messaging
          Issue Type: Feature Request
            Reporter: Clebert Suconic
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:16:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 12 Oct 2007 09:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1105) Run
 integration tests against default config as well
Message-ID: <2691823.1192194963472.JavaMail.jira@cloud.prod.atl2.jboss.com>

Run integration tests against default config as well
----------------------------------------------------

                 Key: JBMESSAGING-1105
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1105
             Project: JBoss Messaging
          Issue Type: Feature Request
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For: AS 5.0 Integration




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:25:03 2007
From: jira-events at lists.jboss.org (Delbart Vincent (JIRA))
Date: Fri, 12 Oct 2007 09:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1272) DSL : String
 index out of range: -1
Message-ID: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL : String index out of range: -1
-----------------------------------

                 Key: JBRULES-1272
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Delbart Vincent
         Assigned To: Mark Proctor
            Priority: Critical


Hi,

I have a problem with my DSL and the 4.0.2 version :

this sentence doesn't work in 4.0.2 :

[condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )

log :
!ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
!MESSAGE String index out of range: -1
!STACK 0
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
        at java.lang.String.substring(String.java:1768)
        at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
        at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
        at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
        at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
        at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
        at org.eclipse.jface.window.Window.open(Window.java:796)
        at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:977)
        at org.eclipse.core.launcher.Main.main(Main.java:952)


If I put two blanks between {number} {object}, it's working.
[condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:25:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 09:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1743) Test the bridge
 request dispatching
Message-ID: <20293184.1192195503912.JavaMail.jira@cloud.prod.atl2.jboss.com>

Test the bridge request dispatching
-----------------------------------

                 Key: JBPORTAL-1743
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1743
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 12 Oct 2007 09:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16683674.1192195863836.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis reassigned JBAS-4811:
----------------------------------------

    Assignee: Rajesh Rajasekaran  (was: Dimitris Andreadis)

Assign this to Rajesh, to suggest how we can proceed incorporating the WS suite in the regular QA environment, and make it part of the AS release process.

For the 4.2.2.GA release, I think we don't have to block on this task, as long as Thomas is satisfied with the results of his local hudson runs.



> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:33:04 2007
From: jira-events at lists.jboss.org (Rainer Langbehn (JIRA))
Date: Fri, 12 Oct 2007 09:33:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
Message-ID: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>

Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
----------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1273
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Rainer Langbehn
         Assigned To: Mark Proctor


I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:35:03 2007
From: jira-events at lists.jboss.org (Madhusudhan Konda (JIRA))
Date: Fri, 12 Oct 2007 09:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1106) Deleting A
	Single Message
Message-ID: <10635104.1192196103958.JavaMail.jira@cloud.prod.atl2.jboss.com>

Deleting A Single Message
-------------------------

                 Key: JBMESSAGING-1106
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1106
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
            Reporter: Madhusudhan Konda
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


JBM should have a new feature to remove a single message from the Destination, perhaps based on a message id? Currently, we can only remove *all* messages, but this feature would be helpful so one can pick and delete a message individually. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:57:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 09:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1186)
 ClusteredCacheLoader to wait
 for first positive result rather than all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31834600.1192197423645.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani reopened JBCACHE-1186:
------------------------------------

             

> ClusteredCacheLoader to wait for first positive result rather than all results
> ------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:57:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 09:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1186)
 ClusteredCacheLoader and
 DataGravitationInterceptor to wait for first positive result rather than
 all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23838699.1192197423727.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani updated JBCACHE-1186:
-----------------------------------

          Summary: ClusteredCacheLoader and DataGravitationInterceptor to wait for first positive result rather than all results  (was: ClusteredCacheLoader to wait for first positive result rather than all results)
    Fix Version/s: 2.1.0.CR1
                       (was: 2.1.0.BETA1)

> ClusteredCacheLoader and DataGravitationInterceptor to wait for first positive result rather than all results
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:07:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 12 Oct 2007 10:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7042969.1192198023922.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12382154 ] 
            
Mark Proctor commented on JBRULES-1273:
---------------------------------------

can you attach it to our JIRA for us to look at?

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Mark Proctor
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:13:03 2007
From: jira-events at lists.jboss.org (Joni Niemi (JIRA))
Date: Fri, 12 Oct 2007 10:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4854) Duplicate
 Content-Type charset attribute causes exception
Message-ID: <22500888.1192198383865.JavaMail.jira@cloud.prod.atl2.jboss.com>

Duplicate Content-Type charset attribute causes exception
---------------------------------------------------------

                 Key: JBAS-4854
                 URL: http://jira.jboss.com/jira/browse/JBAS-4854
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.1.GA
         Environment: Windows XP, JBOSS AS 4.2.1.GA
            Reporter: Joni Niemi
         Assigned To: Remy Maucherat


New maemo Mozilla browser has a "feature" which sends duplicate charset parameter in the POST Content-type header. This causes following exception:

java.io.UnsupportedEncodingException: UTF-8;charset=UTF-8
	at java.lang.StringCoding.decode(StringCoding.java:170)
	at java.lang.String.<init>(String.java:444)
	at java.lang.String.<init>(String.java:516)
	at org.apache.catalina.connector.Request.setCharacterEncoding(Request.java:1469)
	at org.apache.catalina.connector.RequestFacade.setCharacterEncoding(RequestFacade.java:307)
	at com.sun.faces.context.ExternalContextImpl.setRequestCharacterEncoding(ExternalContextImpl.java:167)
	at javax.faces.application.ViewHandler.initView(ViewHandler.java:259)
	at org.ajax4jsf.application.ViewHandlerWrapper.initView(ViewHandlerWrapper.java:138)
	at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:208)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at com.jamonapi.http.JAMonTomcatValve.invoke(JAMonTomcatValve.java:72)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
	at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419)
	at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:393)
	at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1513)
	at java.lang.Thread.run(Thread.java:619)

The erraneous* Content-Type header causing this is 
"Content-Type: application/x-www-form-urlencoded; charset=UTF-8;charset=UTF-8" 
("User-agent: Mozilla/5.0 (X11; U; Linux armv6l; en-GB; rv:1.9a6pre) Gecko/20070810
Firefox/3.0a1 Tablet browser 0.1.16 RX-34_2007SE_4.2007.38-2")

Windows version of Mozilla causes no problems:
"Content-Type: application/x-www-form-urlencoded; charset=UTF-8" 
(User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi; rv:1.8.1.7) Gecko/20070914
Firefox/2.0.0"

* I don't think RFC2616 strictly speakings prohibits duplicate attributes.

This seems to be Catalina issue, but I don't know which version JBOSS AS 4.2.1.GA is using, so I'm submitting this here.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:13:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 10:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1106) Deleting A
	Single Message
In-Reply-To: <10635104.1192196103958.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15300623.1192198384446.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1106?page=all ]

Tim Fox updated JBMESSAGING-1106:
---------------------------------

    Fix Version/s: Unscheduled
                       (was: 1.4.0.SP1)
         Priority: Minor  (was: Major)

> Deleting A Single Message
> -------------------------
>
>                 Key: JBMESSAGING-1106
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1106
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Madhusudhan Konda
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> JBM should have a new feature to remove a single message from the Destination, perhaps based on a message id? Currently, we can only remove *all* messages, but this feature would be helpful so one can pick and delete a message individually. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:15:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 10:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user
 only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15857709.1192198503389.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=comments#action_12382157 ] 
            
Mariusz Smykula commented on JBPORTAL-1742:
-------------------------------------------

Removing line 270 is not good idea. 
Solution than work for my is:

change in ACLInterceptor (line 138) from
 hasAccess = this.computeToolAccess(loggedInUser, path);   
to
 hasAccess = this.computeAccess(loggedInUser, path,"read");

computeToolAccess is method dedicated for CMSAdminPortlet:

Comment from code

// * This is used to filter out cms resources in the CMS Admin tool, so that the user
// * can see only the resources that he has write/manage access to

computeAccess(loggedInUser, path,"read") make real checking for READ access to listed resouce.

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:19:05 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 10:19:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1197) Incorporate
 Spanish XML into Cache docs repo and build
In-Reply-To: <10175107.1192169223335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11675575.1192198745219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1197?page=comments#action_12382159 ] 
            
Michael Smith commented on JBCACHE-1197:
----------------------------------------

Hi Manik,

Sorry, there mate, can you assign this task to me? We are in process of recursing all the hibernate content into PO format and have used a new layout that keeps the translation in sync for the 4 AS books. This jira issue is a placeholder for me to ensure it stays in sync with your english. As soon as the tech review is done for AS422 I'll move onto this.

http://jira.jboss.com/jira/browse/JBAS-4696

- Mike



> Incorporate Spanish XML into Cache docs repo and build
> ------------------------------------------------------
>
>                 Key: JBCACHE-1197
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1197
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Smith
>         Assigned To: Manik Surtani
>
> Need to put the spanish XML file where it belongs

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:19:07 2007
From: jira-events at lists.jboss.org (Hontv?ri J?zsef (JIRA))
Date: Fri, 12 Oct 2007 10:19:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (HIBERNATE-50) Embedded
 Objects get set to null if all its members are null
In-Reply-To: <14240556.1164709076284.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6045732.1192198747536.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/HIBERNATE-50?page=comments#action_12382160 ] 
            
Hontv?ri J?zsef commented on HIBERNATE-50:
------------------------------------------

HB-31 is closed and you cannot comment on a closed issue, even though that contains  a better description of the problem

> Embedded Objects get set to null if all its members are null
> ------------------------------------------------------------
>
>                 Key: HIBERNATE-50
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-50
>             Project: Hibernate
>          Issue Type: Bug
>         Environment: WinXP SP2, JBoss 4.0.4 GA as well as JBoss 4.0.5 GA, installation profile ejb3
>            Reporter: milan w?lke
>         Assigned To: Steve Ebersole
>
> When having an embedded object only containing members of non-simple-types (e.g. String) and fetching it with the entity manager the following happens:
> If all columns, the embedded objects values are based on, are null the embedded object itself is set to null even if a non-arg-constructor set it to a non-null value before. A valid workaround is to include a member of a simple-type (e.g. int) in the embedded object. Doing this not all the values can be set to null, which results in not setting the embedded object itself to null, too.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:04 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24268695.1192198864698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Norman Richards updated JBAS-4841:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:04 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31061054.1192198864822.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Norman Richards updated JBAS-4835:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:04 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32235807.1192198864962.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Norman Richards updated JBAS-4839:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:05 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6994262.1192198865093.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Norman Richards updated JBAS-4840:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:25:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 10:25:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1186)
 ClusteredCacheLoader and
 DataGravitationInterceptor to wait for first positive result rather than
 all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2049649.1192199108484.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani resolved JBCACHE-1186.
------------------------------------

    Resolution: Done

> ClusteredCacheLoader and DataGravitationInterceptor to wait for first positive result rather than all results
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:52:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 10:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (SWAP-26) Add RI JSF portlet
	for AS 4.2
In-Reply-To: <24942180.1186503829752.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19132955.1192200723330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SWAP-26?page=all ]

Thomas Heute resolved SWAP-26.
------------------------------

    Resolution: Done
      Assignee: Thomas Heute  (was: Julien Viet)

> Add RI JSF portlet for AS 4.2
> -----------------------------
>
>                 Key: SWAP-26
>                 URL: http://jira.jboss.com/jira/browse/SWAP-26
>             Project: PortletSwap
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portlets
>            Reporter: Chris Laprun
>         Assigned To: Thomas Heute
>
> Add a JSF portlet example showing how to use JSF RI to create a portlet.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 11:16:04 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 12 Oct 2007 11:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <14575825.1192202164110.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil updated JBMESSAGING-381:
------------------------------------

    Attachment: patch-JBMESSAGING-381.txt

2nd version of the patch.

removed a nasty bug in the test which kept old references on ConnectionFactory (after server restart) making all over subsequent local tests fail...

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 11:16:04 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 12 Oct 2007 11:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <19196062.1192202164236.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil updated JBMESSAGING-381:
------------------------------------

    Attachment:     (was: patch-JBMESSAGING-381.txt)

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:35:06 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:35:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19162639.1192206906415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Vlad Skarzhevskyy updated JASSIST-37:
-------------------------------------

    Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga  (was: Java 5, javassist 3.4.ga)
    Description: 
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = field.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .

BUT When javassist  loads again the generated classes field.getConstantValue(); still null!



  was:
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = fields.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .






> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:37:12 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:37:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30935870.1192207032823.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Vlad Skarzhevskyy updated JASSIST-37:
-------------------------------------

    Attachment: AChildClass-generated.class

This is the resulting class with fileds created  by:
klass.addField(field, initializer);

Original class source:
class AChildClass extends AClass {
	public static final boolean booleanField = true;
	
	public static final float floatField = (float)3.14;
	
	public static final double doubleField = 3.1415;
     ...
}

When decompiled using jad constants are visible but javassist don't see them.

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:43:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18345357.1192207383441.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Vlad Skarzhevskyy updated JASSIST-37:
-------------------------------------

    Workaround Description: 
The problem was field.setModifiers() was not called before klass.addField(field, initializer);
So initializer was not suppose to be created. Later filed was modified to static final. But this does not affect initializer
               Description: 
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = field.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .

BUT When javassist  loads again the generated classes field.getConstantValue(); still null!




  was:
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = field.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .

BUT When javassist  loads again the generated classes field.getConstantValue(); still null!




> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:55:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <142262.1192208104015.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JASSIST-37?page=comments#action_12382206 ] 
            
Vlad Skarzhevskyy commented on JASSIST-37:
------------------------------------------

Now the only problem I see that there are no Initializer factory for boolean and float.


> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 13:56:22 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Fri, 12 Oct 2007 13:56:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2508301.1192211782054.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12382223 ] 
            
William DeCoste commented on JBAS-4805:
---------------------------------------

I've got this fixed for Branch_4_2 and Trunk - what other branches should I be merging??

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 15:17:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 12 Oct 2007 15:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1272) DSL : String
 index out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2212092.1192216623922.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Mark Proctor updated JBRULES-1272:
----------------------------------

    Fix Version/s: 4.0.3
                   4.1.0
                   FUTURE

This fix needs to be back ported to be part of 4.0.3

>From kris:
"This does not seem to be related to the editor itself, it is the DSL
compiler which seems to be throwing an exception if you have a DSL
sentence where 2 params are only 1 character apart (doens't matter
whether it is a space or not), like "My DSL sentence with
{key1}_{key2}".  If the distance is at least 2 characters, then there
is no problem.  The problem still exists in trunk as well.

Looking at the svn history, it is probably related to the fix edson
this in DefaultDSLMappingEntry for JBRULES-1164 (commit 15069): Fixing
DSL files with embedded () on key."

> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: FUTURE, 4.0.3, 4.1.0
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 16:15:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Fri, 12 Oct 2007 16:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1107) Less noisy
 client-side failover
Message-ID: <13404207.1192220103325.JavaMail.jira@cloud.prod.atl2.jboss.com>

Less noisy client-side failover
-------------------------------

                 Key: JBMESSAGING-1107
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Ovidiu Feodorov
            Priority: Minor


When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.

If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.

Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. 

The logging information should be naturally still available, but at DEBUG level.





-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 17:24:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 12 Oct 2007 17:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1272) DSL : String
 index out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7327348.1192224243947.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Edson Tirelli reassigned JBRULES-1272:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.0.3, 4.1.0, FUTURE
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 17:51:03 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Fri, 12 Oct 2007 17:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1068) @Interceptors
 defined on
 @Service EJBs do not have @PostConstruct @PreDestroy interceptor methods
 invoked
Message-ID: <18924421.1192225863309.JavaMail.jira@cloud.prod.atl2.jboss.com>

@Interceptors defined on @Service EJBs do not have @PostConstruct @PreDestroy interceptor methods invoked
---------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1068
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1068
             Project: EJB 3.0
          Issue Type: Bug
          Components: EJB3 Extensions
    Affects Versions: AS 4.2.1.GA
            Reporter: Michael McKibben


I've defined an injection-style interceptor class that needs to be called before a @Service EJBs start() method is invoked on service startup. Using @PostConstruct doesn't not work (the container never calls my @PostConstruct annotated method). @AroundInvoke only works for methods defined on the @Local or @Remote business interface, not the @Management interface.

Shouldn't @PostConstruct and @PreDestroy be invoked on @Service EJBs? I need my interceptor to behave like the standard injection interceptors do.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:06:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 12 Oct 2007 18:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1272) DSL : String
 index out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1568216.1192226763328.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Edson Tirelli resolved JBRULES-1272.
------------------------------------

    Fix Version/s: 4.0.2_SOA_4.2
       Resolution: Done

Fixed. Thanks for reporting and providing test case.

> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.0.2_SOA_4.2, 4.0.3, 4.1.0, FUTURE
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:16:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1744) Documentation
	improvements
Message-ID: <14343449.1192227363463.JavaMail.jira@cloud.prod.atl2.jboss.com>

Documentation improvements
--------------------------

                 Key: JBPORTAL-1744
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1744
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Reference Guide
    Affects Versions: 2.6.2 Final, 2.8 Final
            Reporter: Chris Laprun
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:18:13 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:18:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1745) DTD
 documentation is out of date
Message-ID: <29827431.1192227493792.JavaMail.jira@cloud.prod.atl2.jboss.com>

DTD documentation is out of date
--------------------------------

                 Key: JBPORTAL-1745
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1745
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun


This applies to the actual documentation in the DTD but also to the DTD documentation in the reference guide.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:31:15 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:31:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1746) Explain concept
 of context better
Message-ID: <10930468.1192228275087.JavaMail.jira@cloud.prod.atl2.jboss.com>

Explain concept of context better
---------------------------------

                 Key: JBPORTAL-1746
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1746
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:35:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1746) Explain concept
 of context (for portal objects) better
In-Reply-To: <10930468.1192228275087.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26317133.1192228503190.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1746?page=all ]

Chris Laprun updated JBPORTAL-1746:
-----------------------------------

    Summary: Explain concept of context (for portal objects) better  (was: Explain concept of context better)

> Explain concept of context (for portal objects) better
> ------------------------------------------------------
>
>                 Key: JBPORTAL-1746
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1746
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:07:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1747) Merge user guide
 and reference guide
Message-ID: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>

Merge user guide and reference guide
------------------------------------

                 Key: JBPORTAL-1747
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:09:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26055254.1192230543167.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382272 ] 
            
Chris Laprun commented on JBPORTAL-1747:
----------------------------------------

There's not much point keeping them separate and user guide and quick start guide kind of overlap.

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:11:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1748) Remove
 duplicated information by linking to appropriate sections
Message-ID: <25314407.1192230663362.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove duplicated information by linking to appropriate sections
----------------------------------------------------------------

                 Key: JBPORTAL-1748
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1748
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:11:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1748) Remove
 duplicated information by linking to appropriate sections
In-Reply-To: <25314407.1192230663362.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5987920.1192230663444.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1748?page=comments#action_12382273 ] 
            
Chris Laprun commented on JBPORTAL-1748:
----------------------------------------

The same information is repeated at several spots with tiny variations. Just like in OOP, removing the duplicates would help with maintenance and improve the overall quality of the documentation.

> Remove duplicated information by linking to appropriate sections
> ----------------------------------------------------------------
>
>                 Key: JBPORTAL-1748
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1748
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:13:07 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:13:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1749) Consider
	creating an index
Message-ID: <13224455.1192230787616.JavaMail.jira@cloud.prod.atl2.jboss.com>

Consider creating an index
--------------------------

                 Key: JBPORTAL-1749
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1749
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:26:18 2007
From: jira-events at lists.jboss.org (Seth Wilcox (JIRA))
Date: Fri, 12 Oct 2007 19:26:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2681) Add real support for
 password-stacking (useFirstPass) in LDAPExtLoginModule
Message-ID: <5377477.1192231578331.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2681?page=all ]

Seth Wilcox updated JBAS-2681:
------------------------------

    Attachment: LDAPAuth.patch

Fixes unexpected behavior with LdapExtLoginModule when using the password-stacking

> Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-2681
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2681
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.3 SP1
>         Environment: All
>            Reporter: Didier Kreutter
>         Attachments: LDAPAuth.patch
>
>
> It would be nice, we could use the "useFirstPass" option of this login-module, like it can be done with the DatabaseServerLoginModule.
> With the construct of the LDAPExtLoginModule, it is not possible to use the LDAP-Directory to search for Roles without having to validate the Password, if this has been done by an precedent LoginModule (DB or SSO).
> I think the problem is in the fact, that the effective Role-Search is done in the overridden "validatePassword" function... witch will never been called when the "useFirstPass" option is set. Is it Possible to fulfill the roles in the getRoleSets() function?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 20:54:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 20:54:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1192) Cannot
 gravitate data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24889437.1192236854596.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=comments#action_12382278 ] 
            
Manik Surtani commented on JBCACHE-1192:
----------------------------------------

Resolved in trunk/2.1.x.  Now to back port the fix ... 

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction, Replication
>    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6, 2.1.0.GA, 2.1.0.CR1
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 21:21:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 12 Oct 2007 21:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1274) NPE when using
 reserved word "action" as a bound variable
Message-ID: <16945042.1192238463411.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE when using reserved word "action" as a bound variable
---------------------------------------------------------

                 Key: JBRULES-1274
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1274
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Justin Wick
         Assigned To: Mark Proctor


The following code using the reserved word "action" causes an NPE:

rule
	when
		action : Object()
	then
		System.out.println("A RHS");
end

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 21:24:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 12 Oct 2007 21:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1274) NPE when using
 reserved word "action" as a bound variable, or omitting rule title
In-Reply-To: <16945042.1192238463411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31939049.1192238643270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1274?page=all ]

Justin Wick updated JBRULES-1274:
---------------------------------

        Summary: NPE when using reserved word "action" as a bound variable, or omitting rule title  (was: NPE when using reserved word "action" as a bound variable)
    Description: 
The following code using the reserved word "action" causes an NPE:

rule "Test"
	when
		action : Object()
	then
		System.out.println("A RHS");
end

or this code (omitting title):


rule 
	when
		Object()
	then
		System.out.println("A RHS");
end

  was:
The following code using the reserved word "action" causes an NPE:

rule
	when
		action : Object()
	then
		System.out.println("A RHS");
end


> NPE when using reserved word "action" as a bound variable, or omitting rule title
> ---------------------------------------------------------------------------------
>
>                 Key: JBRULES-1274
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1274
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>
> The following code using the reserved word "action" causes an NPE:
> rule "Test"
> 	when
> 		action : Object()
> 	then
> 		System.out.println("A RHS");
> end
> or this code (omitting title):
> rule 
> 	when
> 		Object()
> 	then
> 		System.out.println("A RHS");
> end

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 21:31:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 21:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1750) Explain effect
 of different values for error handling properties
Message-ID: <25923070.1192239063167.JavaMail.jira@cloud.prod.atl2.jboss.com>

Explain effect of different values for error handling properties
----------------------------------------------------------------

                 Key: JBPORTAL-1750
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1750
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 22:50:06 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Fri, 12 Oct 2007 22:50:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (BPEL-272) allow xpath
 expression/query to create more than one occurrence of an element
In-Reply-To: <21460509.1185436907082.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22765873.1192243806337.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-272?page=all ]

Alejandro Guizar resolved BPEL-272.
-----------------------------------

    Resolution: Partially Completed

The "last plus one" predicate proposal is already implemented and works for the time being. I will mark this issue as partially completed and revisit the extension assign operation proposal in a future release.

> allow xpath expression/query to create more than one occurrence of an element
> -----------------------------------------------------------------------------
>
>                 Key: BPEL-272
>                 URL: http://jira.jboss.com/jira/browse/BPEL-272
>             Project: JBoss jBPM BPEL
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>            Priority: Critical
>             Fix For: jBPM BPEL 1.1 GA
>
>
> PROBLEM The current XPath sublanguage implementation automatically creates nodes missing from location paths during assignment. This facility has a number of conceptual limitations. One of them is the inability to append a child element to an existing element if the latter already has a child element with the same name. There is no XPath syntax to express that a new element is required!
> It is tempting to think of a numeric XPath predicate as an array index, leading to the next snippet:
> <copy>
>  <from><literal>haha</literal></from>
>  <to variable='laughter' xmlns:ex='http://jbpm.org/bpel/examples'>
>   <query>ex:laugh[last() + 1]</query>
>  </to>
> </copy>
> However, such an interpretation of a predicate is wrong. Consider the following extract from XPath 1.0 specification on predicates:
> "A PredicateExpr is evaluated by evaluating the Expr and converting the result to a boolean. If the result is a number, the result will be converted to true if the number is equal to the context position and will be converted to false otherwise."
> The description of the last() function reads:
> "The last function returns a number equal to the context size from the expression evaluation context."
> Noticed the problem? The context position is never greater than the context size. Therefore the predicate [last() + 1] does not represent the position "one past the context size" but the boolean value false. Unfortunately, no other predicate seems appropriate. 
> PROPOSAL Introduce a minor deviation from the XPath 1.0 specification. Interpret the result of a numeric predicate that equals the context size plus one as a  request to create a new occurrence of the node.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 22:55:18 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Fri, 12 Oct 2007 22:55:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (BPEL-218) introduce a central
 service catalog
In-Reply-To: <17113795.1166408025580.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16395028.1192244118659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-218?page=all ]

Alejandro Guizar resolved BPEL-218.
-----------------------------------

    Resolution: Done

Completed the central service catalog, along with a registration servlet for programmatic registration and a console page that allows manual registration.

> introduce a central service catalog
> -----------------------------------
>
>                 Key: BPEL-218
>                 URL: http://jira.jboss.com/jira/browse/BPEL-218
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> In scenarios where full deployment information is missing (e.g. deployment from the eclipse designer) there is no source of partner service descriptions. An earlier proposal mentioned the imported WSDL documents. However, it is not a good solution as most BPEL processes are defined "in the abstract", i.e. without port-specific information.
> A better alternative is to maintain a central service catalog available to all processes. Registration in the central catalog can be either programmatic (ant task) or manual (web console). There are two registration modes: containment and reference. In the first mode, the WSDL document is stored in the jBPM database. In the second, only the document URL is remembered; the actual content is retrieved on demand.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 23:22:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 23:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5156981.1192245723305.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JASSIST-37?page=comments#action_12382286 ] 
            
Vlad Skarzhevskyy commented on JASSIST-37:
------------------------------------------

Also there are no Initializer for byte 

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 08:24:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 13 Oct 2007 08:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1700028.1192278243790.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=all ]

Tim Fox updated JBMESSAGING-1101:
---------------------------------

          Component/s:     (was: Messaging Core)
    Affects Version/s:     (was: 1.4.0.GA)

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 08:26:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 13 Oct 2007 08:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14042151.1192278363345.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=comments#action_12382294 ] 
            
Tim Fox commented on JBMESSAGING-1101:
--------------------------------------

This is replicated in QueueTest::testBytesMessagePersistence

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 08:56:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sat, 13 Oct 2007 08:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1275) Multiple moves
 win a step (moves without direct tabu property relations)
Message-ID: <33061919.1192280163254.JavaMail.jira@cloud.prod.atl2.jboss.com>

Multiple moves win a step (moves without direct tabu property relations)
------------------------------------------------------------------------

                 Key: JBRULES-1275
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1275
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Solver
            Reporter: Geoffrey De Smet
         Assigned To: Geoffrey De Smet
            Priority: Optional


Currently only one move can win a step.
If moves are evaluated not on their score, but on "the difference in score", it probably won't be a bad idea to take a low number of improving moves that have not tabu property's in common and do a step of all of them instead of just one, especially in the beginning.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 16:21:20 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 16:21:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1108) Shutting down
 simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
Message-ID: <7844397.1192306880579.JavaMail.jira@cloud.prod.atl2.jboss.com>

Shutting down simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
----------------------------------------------------------------------------------

                 Key: JBMESSAGING-1108
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1108
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Ovidiu Feodorov
            Priority: Minor


This is just an initial finding. I don't have more details at this point. I will investigate if necessary.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 17:02:13 2007
From: jira-events at lists.jboss.org (Cypher Punk (JIRA))
Date: Sat, 13 Oct 2007 17:02:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-29) Unable to read
 in jarfile if
 application installed to location with spaces in directory name
In-Reply-To: <3806585.1184593564214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19621656.1192309333612.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-29?page=comments#action_12382309 ] 
            
Cypher Punk commented on JBCOMMON-29:
-------------------------------------

Dimitris,

It seems that your code change (JBCOMMON-19, Deal with spaces in local file URIs) introduced this error. See the test below.



import junit.framework.TestCase;

import java.io.File;

import java.net.URL;


public class UrlTest extends TestCase {
    public void test1() throws Exception {
        URL url = new URL("file", "", "/C:/Documents%20and%20Settings/Administrator");

        File file = new File(url.toURI());
        assertTrue(file.exists());
    }

    public void test2() throws Exception {
        URL url = new URL("file", "", "/C:/Documents%20and%20Settings/Administrator");

        File file = new File(url.getPath());
        assertTrue(file.exists());
    }
}


Please add tests!

> Unable to read in jarfile if application installed to location with spaces in directory name
> --------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-29
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-29
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core
>    Affects Versions: 2.0.4.GA
>         Environment: windows XP sun-jre, happens also in core-2.2.0.GA
>            Reporter: klaasjan elzinga
>         Assigned To: Dimitris Andreadis
>
> I get an exception if the application is installed to a directory containing a space. I I rename the directory to a name without a space, the application runs perfectly.
> Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [loadtool/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/TIS%20FIIBLoadTool-3.0.2.SN
> APSHOT/TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar
> Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/TIS%20FIIBLoadTool-3.0.2.SNAPSHOT/TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar
>         at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:635)
>         at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350)
>         at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126)
>         at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:218)
>         at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:251)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425)
>         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
>         at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
>         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
> ...
>         at loadtool.Main.main(Main.java:40)
> Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: C:\TIS%20FIIBLoadTool-3.0.2.SNAPSHOT\TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar (The system cannot find th
> e path specified)
>         at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:74)
>         at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48)
>         at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:57)
>         at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:626)
>         ... 29 more
> Caused by: java.io.FileNotFoundException: C:\TIS%20FIIBLoadTool-3.0.2.SNAPSHOT\TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar (The system cannot find the path specified)
>         at java.util.zip.ZipFile.open(Native Method)
>         at java.util.zip.ZipFile.<init>(ZipFile.java:114)
>         at java.util.jar.JarFile.<init>(JarFile.java:133)
>         at java.util.jar.JarFile.<init>(JarFile.java:97)
>         at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:69)
>         ... 32 more

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 19:37:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 19:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1109) Client-side
 race condition while closing connection
Message-ID: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>

Client-side race condition while closing connection
---------------------------------------------------

                 Key: JBMESSAGING-1109
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Minor


I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())

@Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
org.jboss.jms.exception.MessagingJMSException: Failed to invoke
        at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
        at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
        at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
        at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
        at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
        at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
        at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
        at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
        at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
        at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.remoting.Client.invoke(Client.java:536)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
        ... 17 more


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 19:37:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 19:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3910103.1192318623503.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1109:
-----------------------------------------

    Summary: Client-side race condition while receiving concurrently  (was: Client-side race condition while closing connection)

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 19:47:08 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Sat, 13 Oct 2007 19:47:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (BPEL-280) redeploy web modules
 upon server restart
Message-ID: <6144861.1192319228417.JavaMail.jira@cloud.prod.atl2.jboss.com>

redeploy web modules upon server restart
----------------------------------------

                 Key: BPEL-280
                 URL: http://jira.jboss.com/jira/browse/BPEL-280
             Project: JBoss jBPM BPEL
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Engine
            Reporter: Alejandro Guizar
         Assigned To: Alejandro Guizar
             Fix For: jBPM BPEL 1.1 GA


PROBLEM With the automated deployment procedure in place, new processes and the associated web services can be deployed on the fly. There is an issue, however. Upon server restart, web modules deployed through the JBoss AS main deployer dissapear. Three approaches come quickly to mind to address this situation:

PROPOSAL 1. Place the modules directly in the deployment directory of the application server

* Pros. The engine needs not perform any task at startup. The server is responsible for reading and deploying the modules.

* Cons. Loss of portability. Servers other than JBoss AS use different deployment directories. Some may not even support the concept of a deployment directory.
Furthermore, what if the modules are deleted? Because the responsibility is trasferred to the server, there can be a disconnection between the process definitions in the jBPM database and the deployed web services.

PROPOSAL 2. Save the prefabricated deployment artifacts in the process definition. Rebuild the module at startup.

* Pros. No external location is required to place the modules. All information required to rebuild them is saved along the process definition. The disconnection between the process definitions and the deployed web services dissapear.
* Cons. The engine has to process each process definition at startup to rebuild the modules. This could result in a significant startup time.
Plus, database space consumption might become excessive.

PROPOSAL 3. Save the prefabricated module in a content repository. Leverage the repository facilities provided by jBPM.

* Pros. Same as 2. Plus, no large database storage requirements.
* Cons. The engine still has to process each process definition at startup. Plus, an external content repository introduces new dependencies and installation complexities to the product.

Among these proposals, #1 looks good because it neither imposes large database storage requirements nor a significant startup processing time. It is also the easiest to implement, at the expense of brittleness due to the reliance on the app server.

Any comments or new proposals welcome.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 21:22:08 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 21:22:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
Message-ID: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>

Client incorrectly initiates client-side fail over on high concurrency
----------------------------------------------------------------------

                 Key: JBMESSAGING-1110
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Facade
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox


Dump of a faulty test run:

ofeodorov at yamato$ mess -sessions 50 receive all
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
Consumer21 starting to consume ...
Consumer43 starting to consume ...
Consumer23 starting to consume ...
Consumer44 starting to consume ...
Consumer11 starting to consume ...
Consumer29 starting to consume ...
Consumer26 starting to consume ...
Consumer39 starting to consume ...
Consumer40 starting to consume ...
Consumer01 starting to consume ...
Consumer17 starting to consume ...
Consumer14 starting to consume ...
Consumer04 starting to consume ...
Consumer16 starting to consume ...
Consumer49 starting to consume ...
Consumer42 starting to consume ...
Consumer41 starting to consume ...
Consumer34 starting to consume ...
Consumer18 starting to consume ...
Consumer46 starting to consume ...
Consumer20 starting to consume ...
Consumer02 starting to consume ...
Consumer06 starting to consume ...
Consumer32 starting to consume ...
Consumer07 starting to consume ...
Consumer19 starting to consume ...
Consumer35 starting to consume ...
Consumer48 starting to consume ...
Consumer24 starting to consume ...
Consumer30 starting to consume ...
Consumer08 starting to consume ...
Consumer12 starting to consume ...
Consumer36 starting to consume ...
Consumer09 starting to consume ...
Consumer47 starting to consume ...
Consumer00 starting to consume ...
Consumer13 starting to consume ...
Consumer31 starting to consume ...
Consumer27 starting to consume ...
Consumer33 starting to consume ...
Consumer10 starting to consume ...
Consumer05 starting to consume ...
Consumer45 starting to consume ...
Consumer15 starting to consume ...
Consumer03 starting to consume ...
Consumer37 starting to consume ...
Consumer28 starting to consume ...
Consumer38 starting to consume ...
Consumer22 starting to consume ...
Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
@Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network



closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...




@Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection



-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 21:22:08 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 21:22:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14503602.1192324928699.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382312 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1110:
----------------------------------------------

Server-side logs:

2007-10-13 18:20:01,630 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[465863, bisocket://10.152.1.38:1428632584] control socket replaced by: Socket[addr=/10.152.1.38,port=37373,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[6793a317, bisocket://10.152.1.85:310396915] replacing control socket: Socket[addr=/10.152.1.85,port=50855,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[6793a317, bisocket://10.152.1.85:310396915] control socket replaced by: Socket[addr=/10.152.1.85,port=50859,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[465863, bisocket://10.152.1.38:1428632584] replacing control socket: Socket[addr=/10.152.1.38,port=37373,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[465863, bisocket://10.152.1.38:1428632584] control socket replaced by: Socket[addr=/10.152.1.38,port=37376,localport=3309]


> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 22:12:03 2007
From: jira-events at lists.jboss.org (David Navara (JIRA))
Date: Sat, 13 Oct 2007 22:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4361)
 java.util.logging.FileHandler.formatter cannot be changed to
 java.util.logging.SimpleFormatter
In-Reply-To: <24133361.1177358310492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28870258.1192327923582.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4361?page=comments#action_12382313 ] 
            
David Navara commented on JBAS-4361:
------------------------------------

I had a similar problem and to my suprise I realized there is a space char ' ' after the class name java.util.logging.SimpleFormatter which causes the problem. Try to remove the whitespace at the end of the line.

> java.util.logging.FileHandler.formatter cannot be changed to java.util.logging.SimpleFormatter
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4361
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4361
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.0.CR2
>         Environment: JDK is 1.5.0_11-b03
>            Reporter: Wolfgang Knauf
>         Assigned To: Scott M Stark
>            Priority: Minor
>
> I tried to create a plain text log output with this logging.properties file:
> handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler
> .level= INFO
> java.util.logging.FileHandler.pattern = c:/temp/logfile.log 
> java.util.logging.FileHandler.level = INFO
> java.util.logging.FileHandler.limit = 50000
> java.util.logging.FileHandler.count = 1
> java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter 
> java.util.logging.ConsoleHandler.level = INFO
> java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
> I startup the server with this commandline:
> run.bat -c default -Djava.util.logging.config.file=c:/temp/logging.properties
> The log file is placed in c:\temp\logfile.log and contains my output, but it is in XML, not in Simple format. Console output is in SimpleFormat as expected.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 22:18:03 2007
From: jira-events at lists.jboss.org (Len DiMaggio (JIRA))
Date: Sat, 13 Oct 2007 22:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1111) JBM 1.4.0 in
 ESB from svn
 revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore]
 *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE
 INSTALLATION DEFAULT
Message-ID: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1111
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Security
    Affects Versions: 1.4.0.GA
         Environment: RHEL5
Java 1.5

JBESB - At revision 15800

JBM 1.4.0.GA
            Reporter: Len DiMaggio
         Assigned To: Tim Fox
            Priority: Minor


This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java

14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **

I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172



-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 22:56:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 22:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29498715.1192330563492.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382315 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1110:
----------------------------------------------

Also, messages seem to be vanished from the database. 

I started with 50,000 10K persistent text messages stored in the queue "ovidiu" on the node with the ID 39 (looked up a clustered but not load-balanced connection factory from that node and got confirmation by calling getServerID()). The queue was deployed as "clustered"

State of the database after killing the client (which became unresponsive):

mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             49288 | 
+-------------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 35528; (this is MIN(MESSAGE_ID))
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      35528 |           NULL | C     | 39070061203453943 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 84912; (this is MAX(MESSAGE_ID))
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      84912 |           NULL | C     | 39070075545073791 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_POSTOFFICE; (irrelevant destination names edited for privacy reasons)
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | *** | queue.***              | NULL     |         27 | Y         | N         | 
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         29 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         30 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         31 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         32 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         36 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         34 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         35 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         33 | Y         | N         | 
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         23 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         25 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         26 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         24 | Y         | N         | 
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |         12 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |         15 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |         13 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |          3 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |          5 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |          4 | Y         | N         | 
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
26 rows in set (0.00 sec)

Please note that the channel corresponding to the "ovidiu" queue on node 39 vanished, and it seems there's no "ovidiu" queue on 39.

The JMX console on node 39 became unresponsive as well (couldn't check whether the queue is visible via the JMX interface)
Any attempt to connect to node 39 (even just to create a Connection and then close it) was unsuccessful .

This is the client-side log on a connection attempt:

ofeodorov at yamato$ mess ping
@Timer-1 19:45:51,445 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51137],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:46:31,458 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51142],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:46:56,467 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51143],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:47:31,479 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51146],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:48:21,497 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51147],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:48:46,506 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51148],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:49:26,521 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51150],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:50:36,548 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51154],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:51:31,567 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51159],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:52:21,586 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51160],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:53:06,603 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51162],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:53:46,619 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51164],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:54:26,633 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51177],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection






> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:11:12 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:11:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1112) Highly
 concurrent clients
 lock a JBM server node and apparently cause persistent messages to
 "dissapear"
Message-ID: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>

Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
--------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1112
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Critical


The log of the experiment. 

* Empty database

mysql> CONNECT ovidiu
Connection id:    5288
Current database: ovidiu

mysql> SHOW TABLES;
Empty set (0.00 sec)

mysql> 

* Both cluster nodes down.

* Start node 39 

2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms

mysql> SELECT * FROM JBM_MSG_REF;
Empty set (0.00 sec)

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
...
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
17 rows in set (0.00 sec)


* Start node 38

2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms

mysql> SELECT * FROM JBM_MSG_REF;
Empty set (0.00 sec)

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
...
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
34 rows in set (0.00 sec)

* Make sure I look up a clustered but non load-balanced connection factory from node 39

ofeodorov at yamato$ mess ping
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
node 39 alive
closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...


* Sending 50,000 10K persistent text messages to "ovidiu" on node 39.

ofeodorov at yamato$ mess -stat send -size 10240 50000
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
.....
sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far

50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec

closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...


* Database content after send:

mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             50000 | 
+-------------------+

mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MIN(MESSAGE_ID) |
+-----------------+
|               0 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MAX(MESSAGE_ID) |
+-----------------+
|           54192 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
...
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
...
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
...
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
...
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
34 rows in set (0.00 sec)

* Receiving on 50 concurrent threads, from node 39

ofeodorov at yamato$ mess -stat -sessions 50 receive all
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
Consumer43 starting to consume, 1 active consumers ...
Consumer06 starting to consume, 2 active consumers ...
Consumer38 starting to consume, 3 active consumers ...
Consumer13 starting to consume, 4 active consumers ...
Consumer37 starting to consume, 5 active consumers ...
Consumer10 starting to consume, 6 active consumers ...
Consumer11 starting to consume, 7 active consumers ...
Consumer25 starting to consume, 8 active consumers ...
Consumer12 starting to consume, 9 active consumers ...
Consumer04 starting to consume, 10 active consumers ...
Consumer48 starting to consume, 11 active consumers ...
Consumer32 starting to consume, 12 active consumers ...
Consumer40 starting to consume, 13 active consumers ...
Consumer39 starting to consume, 14 active consumers ...
Consumer05 starting to consume, 15 active consumers ...
Consumer09 starting to consume, 16 active consumers ...
Consumer03 starting to consume, 17 active consumers ...
Consumer41 starting to consume, 18 active consumers ...
Consumer19 starting to consume, 19 active consumers ...
Consumer07 starting to consume, 20 active consumers ...
Consumer22 starting to consume, 21 active consumers ...
Consumer36 starting to consume, 22 active consumers ...
Consumer01 starting to consume, 23 active consumers ...
Consumer46 starting to consume, 24 active consumers ...
Consumer16 starting to consume, 25 active consumers ...
Consumer18 starting to consume, 26 active consumers ...
Consumer23 starting to consume, 28 active consumers ...
Consumer33 starting to consume, 27 active consumers ...
Consumer02 starting to consume, 29 active consumers ...
Consumer00 starting to consume, 30 active consumers ...
Consumer17 starting to consume, 31 active consumers ...
Consumer15 starting to consume, 32 active consumers ...
Consumer47 starting to consume, 33 active consumers ...
Consumer31 starting to consume, 34 active consumers ...
Consumer27 starting to consume, 35 active consumers ...
Consumer49 starting to consume, 36 active consumers ...
Consumer44 starting to consume, 37 active consumers ...
Consumer26 starting to consume, 38 active consumers ...
Consumer24 starting to consume, 39 active consumers ...
Consumer42 starting to consume, 40 active consumers ...
Consumer28 starting to consume, 41 active consumers ...
Consumer20 starting to consume, 42 active consumers ...
Consumer29 starting to consume, 43 active consumers ...
Consumer35 starting to consume, 44 active consumers ...
Consumer45 starting to consume, 45 active consumers ...
Consumer30 starting to consume, 47 active consumers ...
Consumer08 starting to consume, 46 active consumers ...
received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far

Could not just close() connection, I had to kill the java process

SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             34091 | 
+-------------------+

50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)

* Tried to create a new connection to the server, the JNDI invocation hung.

* Killed both servers, restarted.

Database situation:

mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             34091 | 
+-------------------+

mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MIN(MESSAGE_ID) |
+-----------------+
|            8957 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MAX(MESSAGE_ID) |
+-----------------+
|           54192 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
...
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
...
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
...
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
...
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
34 rows in set (0.00 sec)


* Pinged 39

ofeodorov at yamato$ mess ping
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
node 39 alive
closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

* Browsed the queue (I don't expect any, since channel 0 does not exist anymore)

ofeodorov at yamato$ mess browse
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]

NO messages in queue

closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:13:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29224280.1192335183381.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1110:
-----------------------------------------

    Priority: Critical  (was: Major)

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:41:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31557765.1192336863436.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382318 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries generated during the above experiment:

2007-10-13 21:38:41,806 WARN  [org.jboss.messaging.core.impl.JDBCSupport] SQLException caught, SQLState 40001 code:1213- assuming deadlock detected, try:1
com.mysql.jdbc.exceptions.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:941)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2934)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1616)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1708)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:3255)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1293)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1566)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1480)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1465)
        at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251)
        at org.jboss.messaging.core.impl.JDBCPersistenceManager$1RemoveReferenceRunner.doTransaction(JDBCPersistenceManager.java:1279)
        at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner.execute(JDBCSupport.java:385)
        at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner.executeWithRetry(JDBCSupport.java:407)
        at org.jboss.messaging.core.impl.JDBCPersistenceManager.removeReference(JDBCPersistenceManager.java:1310)
        at org.jboss.messaging.core.impl.ChannelSupport.acknowledgeInternal(ChannelSupport.java:694)
        at org.jboss.messaging.core.impl.ChannelSupport.acknowledge(ChannelSupport.java:153)
        at org.jboss.messaging.core.impl.SimpleDelivery.acknowledge(SimpleDelivery.java:99)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeDeliveryInternal(ServerSessionEndpoint.java:1767)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeDelivery(ServerSessionEndpoint.java:355)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$acknowledgeDelivery$aop(SessionAdvised.java:113)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised$acknowledgeDelivery_N8255607227065177522.invokeNext(SessionAdvised$acknowledgeDelivery_N8255607227065177522.java)
        at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised$acknowledgeDelivery_N8255607227065177522.invokeNext(SessionAdvised$acknowledgeDelivery_N8255607227065177522.java)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised.acknowledgeDelivery(SessionAdvised.java)
        at org.jboss.jms.wireformat.SessionAcknowledgeDeliveryRequest.serverInvoke(SessionAcknowledgeDeliveryRequest.java:78)
        at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
        at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
2007-10-13 21:38:41,811 WARN  [org.jboss.messaging.core.impl.JDBCSupport] Trying again after a pause
2007-10-13 21:38:42,831 WARN  [org.jboss.messaging.core.impl.JDBCSupport] Update worked after retry
2007-10-13 21:38:52,316 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:52,474 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:52,660 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:53,171 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:53,325 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:53,488 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:39:05,279 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive



> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:47:15 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:47:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9252225.1192337235815.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382319 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries generated during the above experiment: 

2007-10-13 21:43:38,274 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session d3-4ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,274 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session j3-cezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,275 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session g3-8ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,367 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session c3-2ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,442 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session r3-lezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,443 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session u3-pezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,443 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session b3-wdzf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,443 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session d3-4ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,444 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session j3-cezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,444 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session g3-8ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,444 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session c3-2ezf2r7f-1-w4qq1r7f-yi60n8-31184a


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:51:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22231649.1192337463751.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382320 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries seen during the above experiment:

2007-10-13 21:44:39,657 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session r3-lezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:44:39,889 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session u3-pezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:44:54,192 WARN  [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 460ad983: detected failure on control connection 
Thread[control: Socket[addr=/10.152.1.38,port=3028,localport=58599],5,jboss] (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j: requesting new control connection
2007-10-13 21:44:54,194 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] getting secondary locator2007-10-13 21:44:54,196 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] secondary locator: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:44:54,196 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] creating control connection: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:44:54,197 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] created control connection (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j): Socket[addr=/10.152.1.38,port=30
28,localport=58663]
2007-10-13 21:44:54,215 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51615,localport=3995]
2007-10-13 21:44:54,215 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51663,localport=3995]
2007-10-13 21:44:54,232 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38149,localport=3995]
2007-10-13 21:44:54,233 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38190,localport=3995]
2007-10-13 21:45:03,889 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session b3-wdzf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:45:03,910 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session d3-4ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:45:03,916 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session j3-cezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:45:03,922 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session g3-8ezf2r7f-1-w4qq1r7f-yi60n8-31184a


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:55:06 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32536852.1192337706109.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382321 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries seen during the above experiment:

2007-10-13 21:47:43,373 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
2007-10-13 21:48:06,642 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] replacing control socket: Socket[addr=/10.152.1.85,port=51617,localport=3995]
2007-10-13 21:48:06,642 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] control socket replaced by: Socket[addr=/10.152.1.85,port=51668,localport=3995]
2007-10-13 21:48:06,643 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38190,localport=3995]
2007-10-13 21:48:06,643 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38197,localport=3995]
2007-10-13 21:48:06,644 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51663,localport=3995]
2007-10-13 21:48:06,644 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51669,localport=3995]2007-10-13 21:48:37,005 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38197,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38198,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51669,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51670,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] replacing control socket: Socket[addr=/10.152.1.85,port=51668,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] control socket replaced by: Socket[addr=/10.152.1.85,port=51671,localport=3995]
2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

       



From jira-events at lists.jboss.org  Sun Oct 14 00:55:06 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24723417.1192337706577.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382322 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

...............

2007-10-13 21:53:57,616 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:612)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
2007-10-13 21:53:57,614 WARN  [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 460ad983: detected failure on control connection Thread[control: Socket[addr=/10.152.1.38,port=3028,localport=58680],5,jboss] (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j: requesting new control connection
2007-10-13 21:53:57,617 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] getting secondary locator
2007-10-13 21:53:57,628 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] secondary locator: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:53:57,628 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] creating control connection: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:54:12,195 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38211,localport=3995]
2007-10-13 21:54:12,195 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38213,localport=3995]
2007-10-13 21:54:12,195 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] created control connection (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j): Socket[addr=/10.152.1.38,port=3028,localport=58687]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] replacing control socket: Socket[addr=/10.152.1.85,port=51685,localport=3995]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] control socket replaced by: Socket[addr=/10.152.1.85,port=51699,localport=3995]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51687,localport=3995]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51700,localport=3995]


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 04:11:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Sun, 14 Oct 2007 04:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1751)
 portlet-instances.xml
 security-constraints are not verified using request.isUserInRole()
Message-ID: <28407251.1192349463289.JavaMail.jira@cloud.prod.atl2.jboss.com>

portlet-instances.xml security-constraints are not verified using request.isUserInRole()
----------------------------------------------------------------------------------------

                 Key: JBPORTAL-1751
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Security
    Affects Versions: 2.6.2 Final, 2.6.1 Final
         Environment: Java JDK 1.4.2
            Reporter: Johannes Fiala
         Assigned To: Julien Viet


The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole().

Fact 1:
If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule))
<portlet>
...
<security-role-ref>
			<role-name>PortletUser</role-name>
			<role-link>User</role-link>
		</security-role-ref>
</portlet>

and then use it in the portlet-instances.xml:
<instance>
...
<security-constraint>
				<policy-permission>
					<role-name>PortletUser</role-name>
					<action-name>view</action-name>
				</policy-permission>
			</security-constraint>
</instance>
</deployment>

the portlet instance will not show up.
If you use the User-role instead, it works correctly.

However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected.

Fact 2:
Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal.
I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule.
If I check it using request.isUserInRole("User"), it shows up 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

        


From jira-events at lists.jboss.org  Sun Oct 14 04:37:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Sun, 14 Oct 2007 04:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1751)
 portlet-instances.xml
 security-constraints are not verified using request.isUserInRole()
In-Reply-To: <28407251.1192349463289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30786854.1192351023548.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1751?page=all ]

Johannes Fiala updated JBPORTAL-1751:
-------------------------------------

    Attachment: fwd-jbportal-securitycheck-1.0.0.0.war


Installation:
Deploy this WAR-file to the JBOSS_HOME/server/default/deploy directory.
(tested with JBP 2.6.1 and 2.6.2)

Two pages should be showing up:
- SimplePortletPage
- SecurePortletPage

How to verify the issue:
1. Login using the user "user".
The SimplePortletPage shows that the role "PortletUser" is present.
However, the user is not allowed to access SecurePortletPage, although the security-constraints there allow the role "PortletUser" to view it (NOT working as expected / specified in the Java Portlet Specification, page 76).

2. Login using the user "admin"
The admin-user is allowed to see the SecurePortletPage because he has the role "Admin" assigned (this is working as expected).

> portlet-instances.xml security-constraints are not verified using request.isUserInRole()
> ----------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1751
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final, 2.6.2 Final
>         Environment: Java JDK 1.4.2
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>         Attachments: fwd-jbportal-securitycheck-1.0.0.0.war
>
>
> The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole().
> Fact 1:
> If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule))
> <portlet>
> ...
> <security-role-ref>
> 			<role-name>PortletUser</role-name>
> 			<role-link>User</role-link>
> 		</security-role-ref>
> </portlet>
> and then use it in the portlet-instances.xml:
> <instance>
> ...
> <security-constraint>
> 				<policy-permission>
> 					<role-name>PortletUser</role-name>
> 					<action-name>view</action-name>
> 				</policy-permission>
> 			</security-constraint>
> </instance>
> </deployment>
> the portlet instance will not show up.
> If you use the User-role instead, it works correctly.
> However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected.
> Fact 2:
> Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal.
> I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule.
> If I check it using request.isUserInRole("User"), it shows up 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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:49:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1111) JBM 1.4.0
 in ESB from svn revision 15800 writes WARNING to server log: WARN
 [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE
 CHANGED FROM THE INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27182619.1192358943362.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=comments#action_12382327 ] 
            
Tim Fox commented on JBMESSAGING-1111:
--------------------------------------

Why is this a bug?

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1716268.1192359363753.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=comments#action_12382328 ] 
            
Tim Fox commented on JBMESSAGING-1109:
--------------------------------------

Can you post a test program that replicates the issue?

I think you must be doing something else other than just receiving (closing?)

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1111) JBM 1.4.0 in
 ESB from svn
 revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore]
 *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE
 INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1980580.1192359364598.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=all ]

Tim Fox updated JBMESSAGING-1111:
---------------------------------

    Fix Version/s: Unscheduled

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2534892.1192359364856.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Tim Fox updated JBMESSAGING-1109:
---------------------------------

    Fix Version/s: Unscheduled

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Highly
 concurrent clients
 lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4899216.1192359365270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox updated JBMESSAGING-1112:
---------------------------------

    Fix Version/s: Unscheduled

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10653588.1192359365680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Tim Fox updated JBMESSAGING-1110:
---------------------------------

    Fix Version/s: Unscheduled

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1107) Less noisy
 client-side failover
In-Reply-To: <13404207.1192220103325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10481183.1192359365804.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1107?page=all ]

Tim Fox updated JBMESSAGING-1107:
---------------------------------

    Fix Version/s: Unscheduled

> Less noisy client-side failover
> -------------------------------
>
>                 Key: JBMESSAGING-1107
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.
> If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.
> Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. 
> The logging information should be naturally still available, but at DEBUG level.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1108) Shutting down
 simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
In-Reply-To: <7844397.1192306880579.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20558314.1192359365962.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1108?page=all ]

Tim Fox updated JBMESSAGING-1108:
---------------------------------

    Fix Version/s: Unscheduled

> Shutting down simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1108
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1108
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is just an initial finding. I don't have more details at this point. I will investigate if necessary.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:58:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:58:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21835040.1192359494119.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382329 ] 
            
Tim Fox commented on JBMESSAGING-1110:
--------------------------------------

Please post a test program that replicates the issue.

BTW 50 consumers on a single queue doesn't seem a very likely use case - why would you want to do that? Probably not going to get very good throughput with that many.

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 07:05:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 07:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5769091.1192359903527.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382330 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

Would need to see your source code, to understand why you think messages are "disappearing"?

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:19:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1274) NPE when using
 reserved word "action" as a bound variable, or omitting rule title
In-Reply-To: <16945042.1192238463411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2512181.1192364343543.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1274?page=all ]

Edson Tirelli reassigned JBRULES-1274:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> NPE when using reserved word "action" as a bound variable, or omitting rule title
> ---------------------------------------------------------------------------------
>
>                 Key: JBRULES-1274
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1274
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Justin Wick
>         Assigned To: Edson Tirelli
>
> The following code using the reserved word "action" causes an NPE:
> rule "Test"
> 	when
> 		action : Object()
> 	then
> 		System.out.println("A RHS");
> end
> or this code (omitting title):
> rule 
> 	when
> 		Object()
> 	then
> 		System.out.println("A RHS");
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:21:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1262) DSL Parser "eval"
In-Reply-To: <29036708.1191916263283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20657665.1192364463478.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1262?page=all ]

Edson Tirelli reassigned JBRULES-1262:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> DSL Parser "eval"
> -----------------
>
>                 Key: JBRULES-1262
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1262
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: M H
>         Assigned To: Edson Tirelli
>
> [when]of type Item=Item()
> [when]- Title equals "{value}"=eval(title.isEqual("{value}")
> [when]- Event equals "{value}"=eval(id.isEqual("{value}")
> [then]Log : "{message}"=System.out.println("{message}");
> the dslr File:
> expander Test.dsl
> rule "Your First Rule"
>      when
>             $p : of type Item
>                - Title equals "test"
>                - Event equals "test"
>      then
>            #actions
> end
> resolves to (could be seen in the drl viewer)
> rule "Your First Rule"
>        when
>                $p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) )
>        then
>                #actions
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:23:05 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:23:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27424885.1192364585693.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=comments#action_12382335 ] 
            
Edson Tirelli commented on JBRULES-1247:
----------------------------------------

We need more info. Can you please provide a rule that causes this error for you?

Thanks,
Edson

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:23:06 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:23:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1243) Pattern matching
 does not allow spaces
In-Reply-To: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7322218.1192364586021.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1243?page=all ]

Edson Tirelli reassigned JBRULES-1243:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> Pattern matching does not allow spaces
> --------------------------------------
>
>                 Key: JBRULES-1243
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Edson Tirelli
>
> When I have a rule condition like this:
>   Something( test matches "abc def")
> I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
> When I remove the space and replace it with \s it does compile well.
> Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:23:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 08:23:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18366406.1192364586368.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382336 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

BTW if you're using an ack mode of auto_ack  then this would be expected behaviour, since messages are acked before the call to receive() has returned.

auto_ack = "at most once" delivery when used with synchronous receive()

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 14 Oct 2007 08:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11879.1192365303409.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Fix Version/s: 4.0.2_SOA_4.2
                   4.0.3
                   4.1.0

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2
>
>         Attachments: JBRULES-1264.patch
>
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 14 Oct 2007 08:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15081008.1192365303652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor closed JBRULES-1264.
---------------------------------

    Resolution: Done

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2_SOA_4.2, 4.0.3, 4.1.0
>
>         Attachments: JBRULES-1264.patch
>
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:41:03 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Sun, 14 Oct 2007 08:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5331774.1192365663357.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Markus Wolf updated JBRULES-1247:
---------------------------------

     Original Estimate: 0 minutes
    Remaining Estimate: 0 minutes

The '=' in the agenda-group option does caused this error. I know it is an invalid char at that position, but the error message is confusing and should state a syntax error.

rule "SomeName"
  agenda-group = "action"
  when
    SomeThing()
  then
    System.out.println("Test");
end

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 09:09:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Sun, 14 Oct 2007 09:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1038) Allow export of
 database to xml
In-Reply-To: <24585280.1158190113259.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1216887.1192367343282.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1038?page=all ]

Chris Laprun resolved JBPORTAL-1038.
------------------------------------

    Resolution: Duplicate Issue

> Allow export of database to xml
> -------------------------------
>
>                 Key: JBPORTAL-1038
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1038
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4 Final
>            Reporter: William DeCoste
>            Priority: Minor
>
> This feature was requested by Intuit.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 09:26:17 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Sun, 14 Oct 2007 09:26:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1752) Update SSO
 documentation to use AS 4.2 instead of 4.0.x
Message-ID: <25761598.1192368377472.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update SSO documentation to use AS 4.2 instead of 4.0.x
-------------------------------------------------------

                 Key: JBPORTAL-1752
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1752
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 13:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1079) JBM should
 call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7518044.1192381504205.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox reopened JBMESSAGING-1079:
----------------------------------

             

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 13:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1079) JBM should
 call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5108115.1192381504871.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox reassigned JBMESSAGING-1079:
------------------------------------

    Assignee: Tim Fox  (was: Clebert Suconic)

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:05:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 13:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1079) JBM should
 call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25156747.1192381505518.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox updated JBMESSAGING-1079:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: 1.4.0.GA)

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:26:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 13:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19945973.1192382763445.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382347 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

You don't need to see any source code, you only need to read what I dumped above. Here, to make it easier:

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
+------------+------------+
| CHANNEL_ID | MESSAGE_ID | ..........
+------------+------------+
|            0    | 8957       | ..........
+------------+------------+

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME | COND | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office | 38 | ovidiu | queue.ovidiu | NULL | 20 | Y | N |
| JMS post office | 39 | ovidiu | queue.ovidiu | NULL | 40 | Y | N |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+ 


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:51:26 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Sun, 14 Oct 2007 13:51:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4809) JCA deployer and
 metadata
 incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
In-Reply-To: <29252975.1192034414855.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4964342.1192384286301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4809?page=all ]

Weston Price resolved JBAS-4809.
--------------------------------

    Resolution: Done

Modified metadata to correctly identify local transaction on both non datasource and datasource deployments in the metadata subtypes versus the parent.

> JCA deployer and metadata incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4809
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4809
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>            Reporter: Weston Price
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The ManagedConnectionEmptyContentAdapter did not correctly unmarshall XA based deployments. As a result, non datasource XA deployments (most notably JmsXA) are being incorrectly identified with local tx support and causing failures.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 17:48:03 2007
From: jira-events at lists.jboss.org (Willian Mitsuda (JIRA))
Date: Sun, 14 Oct 2007 17:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1276) Drools toolbar
 should not
 appear in all perspectives and should reuse the standard "new" dropdown
Message-ID: <18713344.1192398483316.JavaMail.jira@cloud.prod.atl2.jboss.com>

Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown
-------------------------------------------------------------------------------------------------

                 Key: JBRULES-1276
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1276
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
    Affects Versions: 4.0.2
            Reporter: Willian Mitsuda
         Assigned To: Mark Proctor


I just installed the drools plugin and noted that it automatically enables a drools toolbar in every perspective.

This is not a good UI policy because it looks like the plugin is trying to appear more important than the others. I have other plugins installed, and I don't like the drools button appearing by default in the C++ or the Profilling perspective, for example. It could be enabled by default just in the Drools perspective, since it exists, and the user could enable it on the others, if he desires.

Also, since your actions are all about resource creation, you could hook them into the standard "new" dropdown, instead of creating your own actionset. This should make your plugin to appear more integrated to Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 01:24:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 01:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23900507.1192425843587.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Rubinger resolved EJBTHREE-1062.
---------------------------------------

    Resolution: Done

JNDI Naming fixes in unrelated unit tests reverted; issue corrected to cover previously-failing cases in which @Remote is specified using XML metadata.

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 02:49:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 15 Oct 2007 02:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1277) BRDRLPersitence
 is not rendering OR's correctly
Message-ID: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRDRLPersitence is not rendering OR's correctly
-----------------------------------------------

                 Key: JBRULES-1277
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Edson Tirelli
             Fix For: 4.0.2_SOA_4.2


Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 02:51:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 15 Oct 2007 02:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1277) BRDRLPersitence
 is not rendering OR's correctly
In-Reply-To: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23150533.1192431063350.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1277?page=all ]

Michael Neale updated JBRULES-1277:
-----------------------------------

    Attachment: BRDRLPersistence.java

This is the corrected one.

> BRDRLPersitence is not rendering OR's correctly
> -----------------------------------------------
>
>                 Key: JBRULES-1277
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2
>
>         Attachments: BRDRLPersistence.java, BRDRLPersistence.old
>
>
> Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 02:51:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 15 Oct 2007 02:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1277) BRDRLPersitence
 is not rendering OR's correctly
In-Reply-To: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24442419.1192431063500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1277?page=all ]

Michael Neale updated JBRULES-1277:
-----------------------------------

    Attachment: BRDRLPersistence.old

And pre patch

> BRDRLPersitence is not rendering OR's correctly
> -----------------------------------------------
>
>                 Key: JBRULES-1277
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2
>
>         Attachments: BRDRLPersistence.java, BRDRLPersistence.old
>
>
> Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:00:05 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Mon, 15 Oct 2007 03:00:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (BPEL-280) redeploy web modules
 upon server restart
In-Reply-To: <6144861.1192319228417.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32639890.1192431605538.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-280?page=all ]

Alejandro Guizar resolved BPEL-280.
-----------------------------------

    Resolution: Done

SOLUTION Adopting proposal 1. The other proposals might be revisited in a future release.

> redeploy web modules upon server restart
> ----------------------------------------
>
>                 Key: BPEL-280
>                 URL: http://jira.jboss.com/jira/browse/BPEL-280
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> PROBLEM With the automated deployment procedure in place, new processes and the associated web services can be deployed on the fly. There is an issue, however. Upon server restart, web modules deployed through the JBoss AS main deployer dissapear. Three approaches come quickly to mind to address this situation:
> PROPOSAL 1. Place the modules directly in the deployment directory of the application server
> * Pros. The engine needs not perform any task at startup. The server is responsible for reading and deploying the modules.
> * Cons. Loss of portability. Servers other than JBoss AS use different deployment directories. Some may not even support the concept of a deployment directory.
> Furthermore, what if the modules are deleted? Because the responsibility is trasferred to the server, there can be a disconnection between the process definitions in the jBPM database and the deployed web services.
> PROPOSAL 2. Save the prefabricated deployment artifacts in the process definition. Rebuild the module at startup.
> * Pros. No external location is required to place the modules. All information required to rebuild them is saved along the process definition. The disconnection between the process definitions and the deployed web services dissapear.
> * Cons. The engine has to process each process definition at startup to rebuild the modules. This could result in a significant startup time.
> Plus, database space consumption might become excessive.
> PROPOSAL 3. Save the prefabricated module in a content repository. Leverage the repository facilities provided by jBPM.
> * Pros. Same as 2. Plus, no large database storage requirements.
> * Cons. The engine still has to process each process definition at startup. Plus, an external content repository introduces new dependencies and installation complexities to the product.
> Among these proposals, #1 looks good because it neither imposes large database storage requirements nor a significant startup processing time. It is also the easiest to implement, at the expense of brittleness due to the reliance on the app server.
> Any comments or new proposals welcome.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:29:03 2007
From: jira-events at lists.jboss.org (M H (JIRA))
Date: Mon, 15 Oct 2007 03:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1278) DSL Parser "eval"
Message-ID: <17218346.1192433343339.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL Parser "eval"
-----------------

                 Key: JBRULES-1278
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1278
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: M H
         Assigned To: Mark Proctor
            Priority: Blocker


rule "PatternTest"
       when
               $pli:Item( title matches "^Test\s*")
       then
                       #
end

this one compiles but on Runtime it ends in an Exception when title looks for example like this "BlaBla (Test)".

as workaround i thought about using the next part, but

rule "PatternTest"
       when
               $pli:Item( eval(title.matches("^Test\s*")) )
       then
                       #
end

it resolves into, also it shouldn't (because title.matches() is Java Code a shouldn't be parsed by the DSL Parser itself):

SyntaxfehlerRule Compilation error : [Rule name=OnlineStreaming Start,
agendaGroup=MAIN, salience=100, no-loop=true]
com/p7s1/swi/phoenix/n24/Rule_OnlineStreaming_Start_0.java (19:923) :
Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ )

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:46:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1751)
 portlet-instances.xml
 security-constraints are not verified using request.isUserInRole()
In-Reply-To: <28407251.1192349463289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28601821.1192434363520.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1751?page=all ]

Thomas Heute updated JBPORTAL-1751:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> portlet-instances.xml security-constraints are not verified using request.isUserInRole()
> ----------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1751
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final, 2.6.2 Final
>         Environment: Java JDK 1.4.2
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: fwd-jbportal-securitycheck-1.0.0.0.war
>
>
> The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole().
> Fact 1:
> If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule))
> <portlet>
> ...
> <security-role-ref>
> 			<role-name>PortletUser</role-name>
> 			<role-link>User</role-link>
> 		</security-role-ref>
> </portlet>
> and then use it in the portlet-instances.xml:
> <instance>
> ...
> <security-constraint>
> 				<policy-permission>
> 					<role-name>PortletUser</role-name>
> 					<action-name>view</action-name>
> 				</policy-permission>
> 			</security-constraint>
> </instance>
> </deployment>
> the portlet instance will not show up.
> If you use the User-role instead, it works correctly.
> However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected.
> Fact 2:
> Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal.
> I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule.
> If I check it using request.isUserInRole("User"), it shows up 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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:46:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:46:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-531) Import/Export of
 Portal Page and Portlet Database Settings
Message-ID: <5714337.1192434364250.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=all ]

Thomas Heute updated JBPORTAL-531:
----------------------------------

    Affects Version/s: 2.6.2 Final

> Import/Export of Portal Page and Portlet Database Settings
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-531
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-531
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.2 Final, 2.6.2 Final
>            Reporter: James Williams
>
> There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance.
> For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:50:03 2007
From: jira-events at lists.jboss.org (Magnus Sandberg (JIRA))
Date: Mon, 15 Oct 2007 03:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1069) persistance.xml
 with <jar-file> looks for jar file in the wrong place
Message-ID: <20172525.1192434603555.JavaMail.jira@cloud.prod.atl2.jboss.com>

persistance.xml with <jar-file> looks for jar file in the wrong place
---------------------------------------------------------------------

                 Key: EJBTHREE-1069
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1069
             Project: EJB 3.0
          Issue Type: Bug
         Environment: JBoss AS 4.2.0.GA (Hibernate 3.3.1.GA)
            Reporter: Magnus Sandberg
             Fix For: AS 4.2.0 GA


When using <jar-file> references in persistance.xml the Ejb3Configuration does not look for the jar relative to the jar with the persistance.xml but relative to from where jboss is started.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:52:07 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:52:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-531) Import/Export
 of Portal Page and Portlet Database Settings
Message-ID: <32166593.1192434727717.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=comments#action_12382373 ] 
            
Thomas Heute commented on JBPORTAL-531:
---------------------------------------

THis is not something we can do with the current isntances deployment.

Each portlet-instances.xml must live within their war file (so that the class is loaded before the instance is created), this is not something that can be centralized in 2.6 branch,

> Import/Export of Portal Page and Portlet Database Settings
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-531
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-531
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.2 Final, 2.6.2 Final
>            Reporter: James Williams
>
> There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance.
> For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:54:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-531) Import/Export of
 Portal Page and Portlet Database Settings
Message-ID: <1194964.1192434843215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=all ]

Thomas Heute updated JBPORTAL-531:
----------------------------------

    Fix Version/s: 2.8 Final

> Import/Export of Portal Page and Portlet Database Settings
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-531
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-531
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.2 Final, 2.6.2 Final
>            Reporter: James Williams
>             Fix For: 2.8 Final
>
>
> There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance.
> For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:56:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15747969.1192434963339.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382374 ] 
            
Thomas Heute commented on JBPORTAL-1747:
----------------------------------------

While i'm concern about the extra work needed in the user guide which doesn't bring much value i think, the 2 guides have different scopes:

User guide: "where to click" guide, basically it should mention all the existing features of the embedded portlets and how to access them. 

QuickStartGuide: Drives the user through common configuration ex:
lead the user from the jboss-portal zip file to a fully customized portal.

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 04:24:03 2007
From: jira-events at lists.jboss.org (Ingo Bruell (JIRA))
Date: Mon, 15 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25091765.1192436643598.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12382375 ] 
            
Ingo Bruell commented on JBAS-4704:
-----------------------------------

How could i get JBoss Remoting 2.2.2 SP2 ?

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 04:49:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 04:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1111) JBM 1.4.0
 in ESB from svn revision 15800 writes WARNING to server log: WARN
 [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE
 CHANGED FROM THE INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4152510.1192438143312.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=comments#action_12382376 ] 
            
Tim Fox commented on JBMESSAGING-1111:
--------------------------------------

Nothings stops the server running, they just get the warning since there's a potential security risk until they specify a password.

It's a bit like installing Oracle and not changing the default password (if there is one - I can't remember?) - you get the idea.

We could take a "head in the sand" approach and not log a warning but I don't think this is a good idea - is this what you are suggesting?

BTW the text was changed some days ago.

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 04:49:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 04:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1111) JBM 1.4.0 in
 ESB from svn
 revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore]
 *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE
 INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14987178.1192438143493.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=all ]

Tim Fox closed JBMESSAGING-1111.
--------------------------------

    Resolution: Rejected

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:19:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 05:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1532568.1192439943549.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12382381 ] 
            
Dimitris Andreadis commented on JBAS-4704:
------------------------------------------

http://repository.jboss.com/jboss/remoting/2.2.2.SP2/lib/

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:24:07 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 15 Oct 2007 05:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3413050.1192440247912.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12382383 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

Potentially the 4.2 CP branch, but depends on Patch Triage Team
approving it. See JBPAPP-356.

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:48:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:48:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-155) secure the gpd
	deployment servlet
In-Reply-To: <684538.1181894171603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9491212.1192441685338.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-155?page=all ]

Koen Aers updated GPD-155:
--------------------------

    Component/s: jpdl

A number of tasks have to be done:
- upload of the archive should be done using username/password combo
- servlet in engine should be secured 

> secure the gpd deployment servlet
> ---------------------------------
>
>                 Key: GPD-155
>                 URL: http://jira.jboss.com/jira/browse/GPD-155
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>
> the gpd deployment servlet should be secured.  the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that.  then the users will be able to control the authorization through the web interface itself.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:50:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-155) secure the gpd
	deployment servlet
In-Reply-To: <684538.1181894171603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24968503.1192441803727.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-155?page=all ]

Koen Aers updated GPD-155:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> secure the gpd deployment servlet
> ---------------------------------
>
>                 Key: GPD-155
>                 URL: http://jira.jboss.com/jira/browse/GPD-155
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> the gpd deployment servlet should be secured.  the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that.  then the users will be able to control the authorization through the web interface itself.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:50:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-171) Split the jPDL plugin
 in a Common/jPDL/BPEL plugin triad
In-Reply-To: <25610757.1192180563603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6009047.1192441803816.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-171?page=all ]

Koen Aers updated GPD-171:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1

> Split the jPDL plugin in a Common/jPDL/BPEL plugin triad
> --------------------------------------------------------
>
>                 Key: GPD-171
>                 URL: http://jira.jboss.com/jira/browse/GPD-171
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>
> the common classes and extension points have to be included in the common plugin

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:52:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-172) Develop an extension
 example for a simple DSL in its own plugin
In-Reply-To: <16781370.1192180683620.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <36794.1192441923539.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-172?page=all ]

Koen Aers updated GPD-172:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha2

> Develop an extension example for a simple DSL in its own plugin
> ---------------------------------------------------------------
>
>                 Key: GPD-172
>                 URL: http://jira.jboss.com/jira/browse/GPD-172
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:56:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-172) Develop an extension
 example for a simple DSL in its own plugin
In-Reply-To: <16781370.1192180683620.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30413350.1192442163383.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-172?page=all ]

Koen Aers updated GPD-172:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1
                       (was: jBPM jPDL Designer 3.2.0.alpha2)

> Develop an extension example for a simple DSL in its own plugin
> ---------------------------------------------------------------
>
>                 Key: GPD-172
>                 URL: http://jira.jboss.com/jira/browse/GPD-172
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:56:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 15 Oct 2007 05:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5517686.1192442163567.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382390 ] 
            
Alexey Loubyansky commented on JBAS-4853:
-----------------------------------------

Due to 1.0.0.GA not being released in JIra, CR11 was released after the 1.0.0.GA.

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:56:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-173) Develop a complete
 jPDL extension example
In-Reply-To: <19634315.1192180685849.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12875029.1192442163651.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-173?page=all ]

Koen Aers updated GPD-173:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha2

> Develop a complete jPDL extension example
> -----------------------------------------
>
>                 Key: GPD-173
>                 URL: http://jira.jboss.com/jira/browse/GPD-173
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:01:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-174) Develop a jPDL
	cheatsheet
In-Reply-To: <1560923.1192180803591.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14644850.1192442463468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-174?page=all ]

Koen Aers updated GPD-174:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.1.2

> Develop a jPDL cheatsheet
> -------------------------
>
>                 Key: GPD-174
>                 URL: http://jira.jboss.com/jira/browse/GPD-174
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-176) Add code completion
 inside attributes and values within the xml source
In-Reply-To: <32030443.1192185004070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13301781.1192442464772.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-176?page=all ]

Koen Aers updated GPD-176:
--------------------------

    Component/s: jpdl

> Add code completion inside attributes and values within the xml source
> ----------------------------------------------------------------------
>
>                 Key: GPD-176
>                 URL: http://jira.jboss.com/jira/browse/GPD-176
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-177) Add code completion in
 the text input fields on the properties view
In-Reply-To: <10554814.1192185123592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17672036.1192442464914.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-177?page=all ]

Koen Aers updated GPD-177:
--------------------------

    Component/s: jpdl

> Add code completion in the text input fields on the properties view
> -------------------------------------------------------------------
>
>                 Key: GPD-177
>                 URL: http://jira.jboss.com/jira/browse/GPD-177
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:03:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 15 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-112) Failed to create a
	new SAX parser
Message-ID: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failed to create a new SAX parser
---------------------------------

                 Key: JBXB-112
                 URL: http://jira.jboss.com/jira/browse/JBXB-112
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Bug
    Affects Versions: JBossXB-2.0.0.CR4
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-2.0.0.CR5


package org.jboss.xb.binding.parser.sax;
public class SaxJBossXBParser

   public SaxJBossXBParser()
      throws JBossXBException
   {
...
 parser = saxFactory.newSAXParser();
         log.debug("Created parser: "+parser
               + ", isNamespaceAware: "+parser.isNamespaceAware()
               + ", isValidating: "+parser.isValidating()
               + ", isXIncludeAware: "+parser.isXIncludeAware()
               );

This is the javadoc for isXIncludeAware:

boolean javax.xml.parsers.SAXParser.isXIncludeAware()

Get the XInclude processing mode for this parser.

See Also:
SAXParserFactory.setXIncludeAware(boolean)
Returns:
the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
Throws:
UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
Since:
1.5

Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:07:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-15) add a readme in the
 create-project wizard
In-Reply-To: <29451119.1168949572678.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15168091.1192442823404.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-15?page=all ]

Koen Aers updated GPD-15:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.2

> add a readme in the create-project wizard
> -----------------------------------------
>
>                 Key: GPD-15
>                 URL: http://jira.jboss.com/jira/browse/GPD-15
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.2
>
>
> all features that help beginner get started are vital imho. therefor, i think the forum user points out a good opportunity for us: we could create a readme.txt in the root of the generated project. that readme is opened when the wizard creates the project and it explains the contents of the project and what do to next.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-25) Saving
 processdefinition should add
 problem markers and entries in problem view if any problems occur
In-Reply-To: <32549222.1168955452884.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23768689.1192443063533.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-25?page=all ]

Koen Aers updated GPD-25:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Saving processdefinition should add problem markers and entries in problem view if any problems occur
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GPD-25
>                 URL: http://jira.jboss.com/jira/browse/GPD-25
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-19) Endpoint Editing
In-Reply-To: <23652487.1168954132731.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2114039.1192443063615.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-19?page=all ]

Koen Aers updated GPD-19:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Endpoint Editing
> ----------------
>
>                 Key: GPD-19
>                 URL: http://jira.jboss.com/jira/browse/GPD-19
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Move endpoints of connections to wherever location on the edge of a node. Involves implementing a particular form of anchor point.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:11:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 15 Oct 2007 06:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4421433.1192443063739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

The isXIncludeAware() call is now in the try-catch block.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-18) Reordering graph
 elements in outline view
In-Reply-To: <4677367.1168954014581.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23984546.1192443183298.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-18?page=all ]

Koen Aers updated GPD-18:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Reordering graph elements in outline view
> -----------------------------------------
>
>                 Key: GPD-18
>                 URL: http://jira.jboss.com/jira/browse/GPD-18
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Reordering elements is possible by directly editing the xml. It should be possible to obtain the same effect by dragging and dropping elements in the outline view.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-17) jpdl designer user
 guide and documentation
In-Reply-To: <8987007.1168951973156.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15004350.1192443183443.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-17?page=all ]

Koen Aers updated GPD-17:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.2
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> jpdl designer user guide and documentation
> ------------------------------------------
>
>                 Key: GPD-17
>                 URL: http://jira.jboss.com/jira/browse/GPD-17
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.2
>
>
> A new user guide using screenshots of the new product should be written.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:17:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-36) Choose to have
 classpath container or expanded libraries
In-Reply-To: <16017528.1168963695187.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4802901.1192443423381.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-36?page=all ]

Koen Aers updated GPD-36:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Choose to have classpath container or expanded libraries
> --------------------------------------------------------
>
>                 Key: GPD-36
>                 URL: http://jira.jboss.com/jira/browse/GPD-36
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> It would be good to be able to choose between expanded libraries or a classpath container when creating a process project with the new... wizard. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:21:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-37) include snap to grid
In-Reply-To: <30030403.1168963978540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30727317.1192443663366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-37?page=all ]

Koen Aers updated GPD-37:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> include snap to grid
> --------------------
>
>                 Key: GPD-37
>                 URL: http://jira.jboss.com/jira/browse/GPD-37
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> While designing processes, it would be a lot easier if there is some kind of 'snap to grid'. You can then have easier manual allignment etc. Besides that, the images look better
> - transitions should snap to the grid to
> - transitions should be perpendicular at least if there are more than three points in the line 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:21:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-40) A slash character in
 Task Node name
 causes crash. Graphical Process Designer allows the slash to be entered
 anyway.
In-Reply-To: <30389570.1168965113514.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7733519.1192443663504.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-40?page=all ]

Koen Aers updated GPD-40:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> A slash character in Task Node name causes crash. Graphical Process Designer allows the slash to be entered anyway.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: GPD-40
>                 URL: http://jira.jboss.com/jira/browse/GPD-40
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> The Graphical Process Designer allows the user to enter a Task Node name that includes a slash, such as "Accounting/Finance". The slash causes a crash later on when the process is run, and it isn't obvious what the source of the problem is. Suggestion: somehow prevent the user from entering a name that includes a slash. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:21:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-34) Review the extension
 points and mechanism.
In-Reply-To: <4787168.1168962293366.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16583713.1192443663594.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-34?page=all ]

Koen Aers updated GPD-34:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1

> Review the extension points and mechanism.
> ------------------------------------------
>
>                 Key: GPD-34
>                 URL: http://jira.jboss.com/jira/browse/GPD-34
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:23:14 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:23:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-50) review the packaging
	mechanism
In-Reply-To: <12577296.1169589052820.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5901285.1192443794238.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-50?page=all ]

Koen Aers updated GPD-50:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> review the packaging mechanism
> ------------------------------
>
>                 Key: GPD-50
>                 URL: http://jira.jboss.com/jira/browse/GPD-50
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Leverage the eclipse packager mechanism to include the necessary features in the distributable and make the site installation mechanism work again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:25:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-33) remember the previous
 form generation data fields
In-Reply-To: <11469034.1168960792592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15663339.1192443903273.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-33?page=all ]

Koen Aers updated GPD-33:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> remember the previous form generation data fields
> -------------------------------------------------
>
>                 Key: GPD-33
>                 URL: http://jira.jboss.com/jira/browse/GPD-33
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> In the form generation, we currently start from the data entered in the task controller (if any)
> Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again.
> The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields).
> I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:28:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 06:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22340509.1192444083484.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382394 ] 
            
Dimitris Andreadis commented on JBAS-4853:
------------------------------------------

Alexey, can you prepare quickly a 1.0.0.SP1 ?

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:33:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-51) Integration of web
	console in GPD
In-Reply-To: <363597.1169633217418.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20640854.1192444383513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-51?page=all ]

Koen Aers updated GPD-51:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.4

> Integration of web console in GPD
> ---------------------------------
>
>                 Key: GPD-51
>                 URL: http://jira.jboss.com/jira/browse/GPD-51
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>
> Provide a number of links (throug hyperlinks or menu buttons) that open a browser on the configured url pointing at a jBPM server installation. These options should be disabled if no server installation is configured.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:35:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-74) Add a server adaptor to
 enable starting and stopping the 'jbpm server'.
In-Reply-To: <15710853.1178575432195.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4223589.1192444503411.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-74?page=all ]

Koen Aers updated GPD-74:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.4

> Add a server adaptor to enable starting and stopping the 'jbpm server'.
> -----------------------------------------------------------------------
>
>                 Key: GPD-74
>                 URL: http://jira.jboss.com/jira/browse/GPD-74
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:35:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-3) implement a generation
 mechanism for the new task forms
Message-ID: <30599002.1192444504979.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-3?page=all ]

Koen Aers updated GPD-3:
------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> implement a generation mechanism for the new task forms
> -------------------------------------------------------
>
>                 Key: GPD-3
>                 URL: http://jira.jboss.com/jira/browse/GPD-3
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:35:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:35:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-73) Review deployment
In-Reply-To: <19314408.1178573812166.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <326529.1192444505137.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-73?page=all ]

Koen Aers updated GPD-73:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> Review deployment
> -----------------
>
>                 Key: GPD-73
>                 URL: http://jira.jboss.com/jira/browse/GPD-73
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> - better status messages
> - saving the settings

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:37:10 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:37:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-9) save deployment options
In-Reply-To: <27696282.1163433282004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24059310.1192444630457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-9?page=all ]

Koen Aers updated GPD-9:
------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> save deployment options
> -----------------------
>
>                 Key: GPD-9
>                 URL: http://jira.jboss.com/jira/browse/GPD-9
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.0.11
>            Reporter: Brice Ruth
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> The current jBPM Process Designer plugin for Eclipse does not save deployment settings for a process definition. It would be useful to set remote deploy settings as a workspace preference (host/port/path). Then, what files are to be deployed (gpd.xml, processdefinition.xml, processimage.xml, src files, etc.) should be saved per process, and stored as part of the project/process files (whichever, just not in .metadata, so it can be committed to CVS and shared by a team).
> JBoss Support Case: 00012512

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:37:15 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:37:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-29) referencing an unknown
 class gives exception at deployment
In-Reply-To: <9620863.1168957132750.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32690023.1192444635574.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-29?page=all ]

Koen Aers updated GPD-29:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.1
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> referencing an unknown class gives exception at deployment
> ----------------------------------------------------------
>
>                 Key: GPD-29
>                 URL: http://jira.jboss.com/jira/browse/GPD-29
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> preferrably, this should be a warning in the problems view. in case the class is not found to be included in the .par, it just shouldn't be included. maybe a warning would be good;

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:37:15 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:37:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-10) can't find resource
In-Reply-To: <27226412.1163761961694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32811145.1192444635745.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-10?page=all ]

Koen Aers updated GPD-10:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> can't find resource
> -------------------
>
>                 Key: GPD-10
>                 URL: http://jira.jboss.com/jira/browse/GPD-10
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> i don't know why, but when trying to deploy the example process websale after modifying the form.create.xhtml, i got this exception that disabled depoyment of the process.
> java.lang.NullPointerException
> at org.jbpm.ui.util.ProcessDeployer.addClassOrResource(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.addClassesAndResources(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.createParBytes(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.access$1(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer$1.run(Unknown Source)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479)
> at org.jbpm.ui.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.deploy(Unknown Source)
> at org.jbpm.ui.editor.form.deployment.DeploymentForm$1.widgetSelected(Unknown Source)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:39:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-63) Inner classes are not
	deployed.
In-Reply-To: <21438537.1171956228437.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27014094.1192444743726.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-63?page=all ]

Koen Aers updated GPD-63:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.1
    Affects Version/s:     (was: jBPM JPDL Designer 3.0.13)

> Inner classes are not deployed.
> -------------------------------
>
>                 Key: GPD-63
>                 URL: http://jira.jboss.com/jira/browse/GPD-63
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Matej Knopp
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: patch.txt
>
>
> When process is being deployed, the inner classes are ignored. So when I have class Foo with inner class Bar, the Foo.class file gets deployed, but the Foo$Bar.class is not. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:41:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-23) deployment with
 problems still gives "process was deployed successfull"
In-Reply-To: <632757.1168954978751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20917529.1192444863356.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-23?page=all ]

Koen Aers updated GPD-23:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.4
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> deployment with problems still gives "process was deployed successfull"
> -----------------------------------------------------------------------
>
>                 Key: GPD-23
>                 URL: http://jira.jboss.com/jira/browse/GPD-23
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>
> Add more meaningful result notifications upon deploying process archives.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:41:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-32) Class chooser limited
 to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)
In-Reply-To: <25271593.1168960312566.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25603748.1192444863614.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-32?page=all ]

Koen Aers updated GPD-32:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.1
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)
> -------------------------------------------------------------------------------
>
>                 Key: GPD-32
>                 URL: http://jira.jboss.com/jira/browse/GPD-32
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> When trying to lookup the class implementing an action handler, the class chooser dialog fails to see classes other than those in jBPM-3.1.1.
> This applies to task assignments as well.
> To re-create, create an action handler in a different eclipse project, place that project on the classpath of the process project, and invoke the class chooser for an action in a process definition. Typing the short name of the class does not cause the list of candidates to appear. Nor does typing the fully qualified name. Typing in "ActionHandler" causes candidates from the jBPM-3.1.1 jar file to appear.
> Classpath is proven to be complete, because pasting the fully qualified class name into the handler class field causes the designer to display the configuration fields that are available. This is also the workaround.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:43:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-112) Super state node name
 is not displayed
In-Reply-To: <8165273.1184094980612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27378920.1192444983565.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-112?page=all ]

Koen Aers updated GPD-112:
--------------------------

        Fix Version/s: jBPM jPDL Designer 3.2.0.GA
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0.alpha2)
                           (was: jBPM JPDL Designer 3.1.0.alpha3)
                           (was: jBPM JPDL Designer 3.1.0.beta1)
                           (was: jBPM JPDL Designer 3.1.0.alpha4)

> Super state node name is not displayed
> --------------------------------------
>
>                 Key: GPD-112
>                 URL: http://jira.jboss.com/jira/browse/GPD-112
>             Project: JBoss jBPM GPD
>          Issue Type: Sub-task
>          Components: jpdl
>         Environment: all
>            Reporter: vladimir mezhibovsky
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Having a name of the super state shown on the process diagram would really help. Currently it is only visible in the outline window which make it hard to understand the process by just looking on the diagram. You have to click on the rectangle that represent super state to see the name.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:45:32 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 06:45:32 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
Message-ID: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>

jboss-web with 4.0 dtd does not deploy
--------------------------------------

                 Key: JBAS-4855
                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky
             Fix For:  JBossAS-5.0.0.Beta3


[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
        at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
        at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
        ... 66 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:45:32 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 06:45:32 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25496281.1192445132626.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4855?page=comments#action_12382399 ] 
            
Thomas Diesler commented on JBAS-4855:
--------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <security-domain>java:/jaas/JBossWS</security-domain>
</jboss-web>

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:49:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24682854.1192445343614.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4853?page=all ]

Dimitris Andreadis reassigned JBAS-4853:
----------------------------------------

    Assignee: Alexey Loubyansky

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:49:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-26) Offer the GPD as a
 standalone package
In-Reply-To: <6979309.1168955692736.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9084296.1192445343690.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-26?page=all ]

Koen Aers updated GPD-26:
-------------------------

    Fix Version/s: jBPM jPDL Designer 4.0.x

> Offer the GPD as a standalone package
> -------------------------------------
>
>                 Key: GPD-26
>                 URL: http://jira.jboss.com/jira/browse/GPD-26
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 4.0.x
>
>
> This can be done in a number of ways:
> - Most easy way is to use the perspective mechanism to distinguish between a 'developer' and a 'analist' perspective
> - Another way is to deliver the designer as an Eclipse RCP application

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:51:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-75) Add undo/redo ability
 for every possible action
In-Reply-To: <7347368.1178575552167.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4139600.1192445463416.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-75?page=all ]

Koen Aers updated GPD-75:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Add undo/redo ability for every possible action
> -----------------------------------------------
>
>                 Key: GPD-75
>                 URL: http://jira.jboss.com/jira/browse/GPD-75
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:51:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-38) Comment in graphical
 editor (UML annotations)
In-Reply-To: <20069791.1168964512751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1319738.1192445463489.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-38?page=all ]

Koen Aers updated GPD-38:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Comment in graphical editor (UML annotations)
> ---------------------------------------------
>
>                 Key: GPD-38
>                 URL: http://jira.jboss.com/jira/browse/GPD-38
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> It should be possible to annotate the graphical elements in the graphical editor with comments.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:53:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-39) Adapt property sheet
 according to context in xml tab
In-Reply-To: <31483791.1168964513032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20362965.1192445583393.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-39?page=all ]

Koen Aers updated GPD-39:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Adapt property sheet according to context in xml tab
> ----------------------------------------------------
>
>                 Key: GPD-39
>                 URL: http://jira.jboss.com/jira/browse/GPD-39
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Currently the property sheet does not reflect the context when editing the process definition in the xml source tab.
> Solution : define a selection listener that activates the model object corresponding to the cursor location in the xml source tab.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:53:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:53:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-54) Label and name support
 for graph elements
In-Reply-To: <17703731.1170780140362.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17515961.1192445584125.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-54?page=all ]

Koen Aers updated GPD-54:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.2.0.GA
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0.alpha2)

> Label and name support for graph elements
> -----------------------------------------
>
>                 Key: GPD-54
>                 URL: http://jira.jboss.com/jira/browse/GPD-54
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:57:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-31) Make sure all tasks in
 a process definition have a unique name
In-Reply-To: <27583187.1168958633498.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6725644.1192445823399.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-31?page=all ]

Koen Aers updated GPD-31:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> Make sure all tasks in a process definition have a unique name
> --------------------------------------------------------------
>
>                 Key: GPD-31
>                 URL: http://jira.jboss.com/jira/browse/GPD-31
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> When retrieving all tasks from a process definition like so:
>         processDefinition.getTaskMgmtDefinition().getTasks() 
> it returns a MAP of tasks, keyed by task name. This is a problem if two tasks anywhere in the same process definition have the same name.
> By default, the GPD creates all tasks as "task1" when it is the first task on a task node. If none of these were renamed, you would only get a single task when trying to get all of them for the process definition.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:57:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-20) refactor naming strategy
In-Reply-To: <32621900.1168954252939.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5171569.1192445823644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-20?page=all ]

Koen Aers updated GPD-20:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.2

> refactor naming strategy
> ------------------------
>
>                 Key: GPD-20
>                 URL: http://jira.jboss.com/jira/browse/GPD-20
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.2
>
>
> 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type.
> 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though.
> 3) use the following naming strategy for end states: {end, end2, end3, end4, ...}
> 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name.
> 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:57:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-75) Add undo/redo ability
 for every possible action
In-Reply-To: <7347368.1178575552167.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28163367.1192445823917.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-75?page=all ]

Koen Aers updated GPD-75:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.2
                       (was: jBPM jPDL Designer 3.2.0.GA)

> Add undo/redo ability for every possible action
> -----------------------------------------------
>
>                 Key: GPD-75
>                 URL: http://jira.jboss.com/jira/browse/GPD-75
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:11 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:59:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-136) Widget is disposed in
 Task Controller Variables Table
In-Reply-To: <24052817.1186484989796.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14139989.1192445951706.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-136?page=all ]

Koen Aers updated GPD-136:
--------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0.beta2)

> Widget is disposed in Task Controller Variables Table
> -----------------------------------------------------
>
>                 Key: GPD-136
>                 URL: http://jira.jboss.com/jira/browse/GPD-136
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Eclipse 3.2.2 on Windows 2000
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> Select a Task Node. Go to Properties View.
> Select Tasks:<task>:Controller (default).
> Add two variables, remove the second.
> Error Log view contains the following SWT Exception:
> org.eclipse.swt.SWTException: Widget is disposed
> 	at org.eclipse.swt.SWT.error(SWT.java:3374)
> 	at org.eclipse.swt.SWT.error(SWT.java:3297)
> 	at org.eclipse.swt.SWT.error(SWT.java:3268)
> 	at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
> 	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330)
> 	at org.eclipse.swt.widgets.Control.setVisible(Control.java:2642)
> 	at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.applyName(VariableTableItemWrapper.java:164)
> 	at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.cancelEditing(VariableTableItemWrapper.java:150)
> 	at org.jbpm.gd.jpdl.util.VariableTableCellClickedResolver.mouseDown(VariableTableCellClickedResolver.java:25)
> 	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)
> After that, table input is not working anymore ("Mapped Name" column not editable anymore, for example).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17152056.1192445952519.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox reopened JBMESSAGING-1047:
----------------------------------

             

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:13 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-100) review the delegation
 configuration form
In-Reply-To: <9679061.1182417596922.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <871568.1192445953489.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-100?page=all ]

Koen Aers updated GPD-100:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> review the delegation configuration form
> ----------------------------------------
>
>                 Key: GPD-100
>                 URL: http://jira.jboss.com/jira/browse/GPD-100
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> - have a look at the visibility of the text and table in the configuration form
> - try to fix the resize problem

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20659946.1192445953655.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox updated JBMESSAGING-1047:
---------------------------------

    Priority: Minor  (was: Major)

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28464493.1192445953983.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox closed JBMESSAGING-1047.
--------------------------------

    Resolution: Done

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:14 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-109) review task form
	generation dialog
In-Reply-To: <22119502.1182883917540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <985571.1192445954424.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-109?page=all ]

Koen Aers updated GPD-109:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> review task form generation dialog
> ----------------------------------
>
>                 Key: GPD-109
>                 URL: http://jira.jboss.com/jira/browse/GPD-109
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> implement focuslost behaviour

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2987761.1192445954564.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Tim Fox reopened JBMESSAGING-1095:
----------------------------------

             

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16288547.1192446063912.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Tim Fox updated JBMESSAGING-1095:
---------------------------------

    Priority: Minor  (was: Major)

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20773895.1192446064067.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Tim Fox closed JBMESSAGING-1095.
--------------------------------

    Resolution: Done

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-133) with two transitions
 from a node, both need to be labelled, or jbpm-console exceptions
In-Reply-To: <11120214.1186477706404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12237209.1192446064397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-133?page=all ]

Koen Aers updated GPD-133:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> with two transitions from a node, both need to be labelled, or jbpm-console exceptions
> --------------------------------------------------------------------------------------
>
>                 Key: GPD-133
>                 URL: http://jira.jboss.com/jira/browse/GPD-133
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: osx, macbook pro, eclipse 3.3.0, tomcat 5.0.28
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: broken_process.xml, broken_process_exception.txt, fixed_process.xml
>
>
> when there are two transitions from a node, both need to be labelled (given a name), I am not sure if there is a validate xml option within the plugin, it would help if there was, if both are not given a name, the jbpm-console exceptions across multiple 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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1091) Selector
 parser should
 use string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17234713.1192446064562.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox reopened JBMESSAGING-1091:
----------------------------------

             

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-141)
 IType.getCompilationUnit() can be
 null if handler class is in jar, leads to event loop exception
In-Reply-To: <31471639.1186745521420.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7841179.1192446064695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-141?page=all ]

Koen Aers updated GPD-141:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception
> ------------------------------------------------------------------------------------------------
>
>                 Key: GPD-141
>                 URL: http://jira.jboss.com/jira/browse/GPD-141
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: Eclipse 3.2 on Windows 2000
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> Following part of my processdefinition.xml:
> 		<event type="node-leave">
> 			<action class="x.y.z.MyClass" name="An Action">
> 				<arg>
> 					anArg
> 				</arg>
> 			</action>
> 		</event>
> MyClass is in a jar which is added to the classpath of the Process Project. Saving throws an event loop exception in Error Log View with the following stack.
> Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null argument;
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:150)
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:126)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:577)
> at org.eclipse.jface.viewers.CheckboxTreeViewer.setCheckedElements(CheckboxTreeViewer.java:431)
> at org.jbpm.gd.jpdl.deployment.IncludeInDeploymentTreeViewer.setCheckedElements(IncludeInDeploymentTreeViewer.java:61)
> at org.jbpm.gd.jpdl.deployment.DeploymentForm$17.run(DeploymentForm.java:635)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> The problem is, that DeploymentForm.getElementsToCheckFor() does not respect that MyClass returns null for getCompilationUnit(). As a consequence, setCheckedElements is called with null in the Object[].

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26118761.1192446065958.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox closed JBMESSAGING-1091.
--------------------------------

    Resolution: Done

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31339101.1192446065798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox updated JBMESSAGING-1091:
---------------------------------

    Priority: Minor  (was: Major)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:06 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-143) Load the icon of a
 paletteContribution entry from the plugin directory where it is defined
In-Reply-To: <28132773.1186761253835.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29101365.1192446066085.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-143?page=all ]

Koen Aers updated GPD-143:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1

> Load the icon of a paletteContribution entry from the plugin directory where it is defined
> ------------------------------------------------------------------------------------------
>
>                 Key: GPD-143
>                 URL: http://jira.jboss.com/jira/browse/GPD-143
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>
> In PaletteRoot class, the icon of a palette entry is always loaded from org.jbpm.gd.jpdl plugin, even if the paletteContribution entry is defined in a dependent plugin.
> The information, where the palette entry element (entryElement in PaletteRoot.addControls) is defined, can be found in entryElement.getContributor().getName().
> So also the corresponding image can be loaded from the correct bundle.
> [ Sorry to only give a verbal description of the implementation. I would sign a corporate contributor's agreement, but I have problems with the procedure, e.g.
> - do we need a corporate jboss account for my boss to sign
> - if we sign with the "corporate" account, with which account I need to contribute then
> etc.
> So I would need some assistance here. Then you would get a real diff also.
> ]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1102) JBM should
 use
 TransactionManagerLocator instead of the MBean API as that is being removed
 from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26225400.1192446066216.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Tim Fox reopened JBMESSAGING-1102:
----------------------------------

             

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:06 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-35) enhancement drawing
	transitions
In-Reply-To: <9729958.1168962532978.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24562680.1192446066373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-35?page=all ]

Koen Aers updated GPD-35:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> enhancement drawing transitions
> -------------------------------
>
>                 Key: GPD-35
>                 URL: http://jira.jboss.com/jira/browse/GPD-35
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> When the mousepointer is in the outer area of a node/state/task/.... but within it's boundaries, it should be possible to draw a transition. This is makes using the gpd a lot faster (not switching in the toolbar)
> Maybe it should only be in the 'middle areas' of top, bottom, left and right and not the corners

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:03:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-149) Creating tasks by
 editing XML source will prevent the XML file from being re-opened
In-Reply-To: <5015540.1187215741100.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26636521.1192446183414.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-149?page=all ]

Koen Aers updated GPD-149:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Creating tasks by editing XML source will prevent the XML file from being re-opened
> -----------------------------------------------------------------------------------
>
>                 Key: GPD-149
>                 URL: http://jira.jboss.com/jira/browse/GPD-149
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: Eclipse 3.3, Designer 3.1.0 CR
>            Reporter: Jeff Wang
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> When you create new tasks by editing the source, it will break the process definition and not allow you to re-open it in Eclipse.
> Steps to recreate:
> 1) Create a new process definition
> 2) Create a task node using the GUI
> 3) Switch to the source tab
> 4) Copy the task xml tag
> 5) Rename the task name to something unique
> 6) Close the file
> 7) Re-open using the JBPM editor

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:03:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-156)
 GenericElementXmlAdapter doesnt add child nodes
In-Reply-To: <9558754.1188946691290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2161733.1192446183635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-156?page=all ]

Koen Aers updated GPD-156:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> GenericElementXmlAdapter doesnt add child nodes
> -----------------------------------------------
>
>                 Key: GPD-156
>                 URL: http://jira.jboss.com/jira/browse/GPD-156
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Imran Naqvi
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> If you have a template such as:
> <?xml version="1.0"?> 
> <process-definition name="Movie" version="11"> 
> <start-state name="Start"> 
> <transition to="Get MPEG Properties" /> 
> </start-state> 
> <node name="Get MPEG Properties"> 
> <action class="SomeActionHandler"><send>010901</send> 
> <keys> 
> <entry> 
>                                             <key>VarName</key> 
>                                             <value>1122</value> 
>                                 </entry> 
> </keys> 
> <receive> 
> <element>030101</element> 
> <element>030102</element> 
> </receive> 
> </action> 
> <transition to="End"/> </node> 
> <end-state name="End" /> 
> The nested Generic Elements arent added by the adapter. The reason for this is that the GenericElementXmlAdapter.doModelAdd() doesnt do anything. We need to add the following code to this method:
>                                            String type = child.getElementType();
> 		SemanticElement jpdlElement;
> 		jpdlElement = getSemanticElementFactory().createById("org.jbpm.gd.jpdl.genericElement");
> 		child.initialize(jpdlElement);
> 		GenericElement genericElement= (GenericElement )getSemanticElement();
> 		genericElement.addGenericElement((GenericElement)jpdlElement);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:03:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-98) GPD creates invalid
 gpd.xml when nodes contain special characters on Windows
In-Reply-To: <10767958.1182332992363.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32336959.1192446184341.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-98?page=all ]

Koen Aers updated GPD-98:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> GPD creates invalid gpd.xml when nodes contain special characters on Windows 
> -----------------------------------------------------------------------------
>
>                 Key: GPD-98
>                 URL: http://jira.jboss.com/jira/browse/GPD-98
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.0.13, jBPM JPDL Designer 3.1.0.alpha4
>         Environment: Windows XP, Eclipse 3.2.1
>            Reporter: Martin Putz
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: processdefintion.xml
>
>
> A process with a node containing a special character, such as <start-state name="D?but">, leads to an invalid gpd.xml. This is reproducible with the attached sample processdefinition.xml on a Windows machine.

-- 
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

       



From jira-events at lists.jboss.org  Mon Oct 15 07:03:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-162) Deploying a process
 does not pull in necessary Java classes
In-Reply-To: <31205902.1189443251838.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33118550.1192446184462.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-162?page=all ]

Koen Aers updated GPD-162:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Deploying a process does not pull in necessary Java classes
> -----------------------------------------------------------
>
>                 Key: GPD-162
>                 URL: http://jira.jboss.com/jira/browse/GPD-162
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> GPD 3.1.0.CR1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: websale.par
>
>
> When I try to deploy a process from the GPD, the class files referenced in the definition do not come across properly.
> 1) Modified an existing process (as per GPD 161).
> 2) Save the process. (.par will be attached)
> 3) Use the Deployment tab to deploy the updated process.
> 4) Execute the process and you get the following error:
> In the web page:
> Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown.
> On the console:
> 12:48:35,403 ERROR [Delegation] couldn't instantiate delegation class 'org.jbpm.websale.DeciderHandler'
> java.lang.NullPointerException
>         at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105)
>         at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:48)
>         at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:163)
>         at org.jbpm.instantiation.Delegation$$FastClassByCGLIB$$6bae1598.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.instantiation.Delegation$$EnhancerByCGLIB$$a8c02805.instantiate(<generated>)
>         at org.jbpm.graph.node.Decision.execute(Decision.java:87)
>         at org.jbpm.graph.def.Node.enter(Node.java:318)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.enter(<generated>)
>         at org.jbpm.graph.def.Transition.take(Transition.java:151)
>         at org.jbpm.graph.def.Node.leave(Node.java:393)
>         at org.jbpm.graph.node.StartState.leave(StartState.java:70)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.leave(<generated>)
>         at org.jbpm.graph.exe.Token.signal(Token.java:194)
>         at org.jbpm.graph.exe.Token.signal(Token.java:139)
>         at org.jbpm.graph.exe.Token$$FastClassByCGLIB$$74df1c6e.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5a16e027.signal(<generated>)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:476)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:390)
>         at org.jbpm.jsf.core.action.CompleteTaskActionListener.handleAction(CompleteTaskActionListener.java:47)
>         at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82)
>         at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
>         at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758)
>         at javax.faces.component.UICommand.broadcast(UICommand.java:368)
>         at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.broadcast(UITaskFormButtonBase.java:56)
>         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
>         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
>         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
>         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
>         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
>         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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-170) misspelling: Assignmnet
In-Reply-To: <814774.1190993382986.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20559218.1192446303471.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-170?page=all ]

Koen Aers updated GPD-170:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> misspelling: Assignmnet
> -----------------------
>
>                 Key: GPD-170
>                 URL: http://jira.jboss.com/jira/browse/GPD-170
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Chris Whalen
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> "Assignment" misspelled on task and swimlane configuration tabs.
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/TaskConfigurationComposite.java   and
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/SwimlaneConfigurationComposite.java

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28954024.1192446304291.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

Koen Aers updated GPD-169:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-168) feature not recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1388539.1192446304460.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-168?page=all ]

Koen Aers updated GPD-168:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-161) Overwriting a node in
 the source yields an out-of-sync diagram
In-Reply-To: <28293293.1189441931051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33037812.1192446305079.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-161?page=all ]

Koen Aers updated GPD-161:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Overwriting a node in the source yields an out-of-sync diagram
> --------------------------------------------------------------
>
>                 Key: GPD-161
>                 URL: http://jira.jboss.com/jira/browse/GPD-161
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> 3.1.0cr1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: cheat.txt, processdefinition.xml, websale.par
>
>
> I edited the source xml by pasting in the Decision Node from the cheat.txt (attached) over the "Evaluate web order" found in the example websale process.  When I switched back to visual mode, I found an unattached Decision Node with no name and the "Evaluate web order" remained as before.
> I'll attach the before and after JPDL as well as the substitution text after I open this bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:07:21 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:07:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-65) Would it possible to
 take parameters
 from an abstract super class of the Delegation class in the GPD?
In-Reply-To: <9401534.1174487808759.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18214342.1192446441714.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-65?page=all ]

Koen Aers updated GPD-65:
-------------------------

    Fix Version/s: jBPM jPDL Designer 4.0.x

> Would it possible to take parameters from an abstract super class of the Delegation class in the GPD?
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GPD-65
>                 URL: http://jira.jboss.com/jira/browse/GPD-65
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>         Environment: Eclipse (Windows XP)
>            Reporter: Nicolas Arnaud
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 4.0.x
>
>
> I have a problem with my AssignHandler class 
> I want to have a generic abstract class wich implements AssignHandler Other class extend this class 
> I put the parameters in my abstract class, but with the GPD, when I use Delegation to associate the sub-class to a Task, I can't get the parameters. 
> Would it possible to take parameters from the abstract super class of the Delegation class?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:07:21 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:07:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
In-Reply-To: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27963615.1192446441838.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1089?page=all ]

Tim Fox updated JBMESSAGING-1089:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                       (was: 1.4.0.SP1)

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1089
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> Update to JGroups 2.5 to take advantage of better throughput.
> We need to ensure the post office code is sufficiently thread safe.
> We may need to do another release for 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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16745314.1192446543650.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=all ]

Tim Fox updated JBMESSAGING-1084:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                       (was: 1.4.0.SP1)

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as that is being removed
 from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26483543.1192446543872.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Tim Fox updated JBMESSAGING-1102:
---------------------------------

    Fix Version/s:     (was: 1.4.0.SP1)

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-176) Add code completion
 inside attributes and values within the xml source
In-Reply-To: <32030443.1192185004070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13990763.1192446663279.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-176?page=all ]

Koen Aers updated GPD-176:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Add code completion inside attributes and values within the xml source
> ----------------------------------------------------------------------
>
>                 Key: GPD-176
>                 URL: http://jira.jboss.com/jira/browse/GPD-176
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-177) Add code completion in
 the text input fields on the properties view
In-Reply-To: <10554814.1192185123592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20721062.1192446663380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-177?page=all ]

Koen Aers updated GPD-177:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Add code completion in the text input fields on the properties view
> -------------------------------------------------------------------
>
>                 Key: GPD-177
>                 URL: http://jira.jboss.com/jira/browse/GPD-177
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-16) moving nodes around
	corrupts process
In-Reply-To: <24369874.1168951377529.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30450926.1192446663468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-16?page=all ]

Koen Aers updated GPD-16:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> moving nodes around corrupts process
> ------------------------------------
>
>                 Key: GPD-16
>                 URL: http://jira.jboss.com/jira/browse/GPD-16
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> in the XML i moves some nodes around. that lead to a corrupted graphical view. i tried to delete the whole gpd.xml content (and then the whole) file in the hope that the graphical content would be restored, but instead i lost the content of the processdefinition.xml and had to start all over again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-27) Make transitions
 identifiable by position
In-Reply-To: <26589236.1168956532704.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29815328.1192446663541.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-27?page=all ]

Koen Aers updated GPD-27:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Make transitions identifiable by position
> -----------------------------------------
>
>                 Key: GPD-27
>                 URL: http://jira.jboss.com/jira/browse/GPD-27
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Try and implement a strategy where transitions are identified by their position in the list of transitions rather than by a name. This should be done to eliminate the need for a transition name. When this is done the bendpoints in the gpd.xml file can be associated with their transition based on the position.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-67) GPD support for editing
 non-files (any IEditorInput, not just FileEditorInput)
In-Reply-To: <17125585.1175836378572.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24664447.1192446783593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-67?page=all ]

Koen Aers updated GPD-67:
-------------------------

    Fix Version/s: jBPM jPDL Designer 4.0.x

> GPD support for editing non-files (any IEditorInput, not just FileEditorInput)
> ------------------------------------------------------------------------------
>
>                 Key: GPD-67
>                 URL: http://jira.jboss.com/jira/browse/GPD-67
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: John Ruud
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 4.0.x
>
>
> We need to edit process defs that are stored in a DB, as opposed to the processdefinition.xml, gpd.xml files stored in the workspace. There are currently many dependencies to FileEditorInput/File throughout GPD (as is the case for a lot of other Eclipse editors BTW).
> It would be very helpful if it would be feasible to separate out the code that deals with a particular type of IEditorInput from the rest of the editor, possibly into a separete delegate class. For FileEditorInput the delegate would deal with reading, writing, and syncronizing the view (resource listeners), plus whatever else I may have forgotten. We could then replace the default "file" delegate with our own that knows how to deal our DB (by subclassing of the editor would be fine). 
> Probably not the #1 GPD issue for many other users, but hopefully something you would keep in mind...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-123) Ability to zoom
In-Reply-To: <18835035.1185455627463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2891026.1192446783734.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-123?page=all ]

Koen Aers updated GPD-123:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Ability to zoom
> ---------------
>
>                 Key: GPD-123
>                 URL: http://jira.jboss.com/jira/browse/GPD-123
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta1
>            Reporter: Matthew Sandoz
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> It would be nice especially for large flows to be able to zoom in and out of the process designer view.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-134) form file names
 generated from the task dialogue are unstable
In-Reply-To: <9189503.1186477849412.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12997119.1192446784375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-134?page=all ]

Koen Aers updated GPD-134:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> form file names generated from the task dialogue are unstable
> -------------------------------------------------------------
>
>                 Key: GPD-134
>                 URL: http://jira.jboss.com/jira/browse/GPD-134
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta1
>         Environment: osx macbook pro, eclipse 3.3.0
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> the form names generated from the task dialogue are sensitive to content...
> 'fbm-rejects.xhtml' is ok, and is stored in the DB fine when deployed,
> 'fbm-rejects-psr.xhtml' is not stored in the DB when deployed and therefore the form does not display within the jbpm-console
> the DB schema says the name field is varchar(255), which suggests that perhaps the second hyphen in the name is causing a problem somewhere

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-146) improve feedback when
 creating self referencing transitions
In-Reply-To: <14993915.1187097560953.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20590013.1192446784592.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-146?page=all ]

Koen Aers updated GPD-146:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> improve feedback when creating self referencing transitions
> -----------------------------------------------------------
>
>                 Key: GPD-146
>                 URL: http://jira.jboss.com/jira/browse/GPD-146
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> At the moment creating self referencing transitions is done by clicking twice on the source/target node. In the future some feedback (a dummy transition) should make this proces more obvious

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-138) error dialogue appears
 on task panel of properties for task node
In-Reply-To: <21642934.1186578244471.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32881218.1192446903556.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-138?page=all ]

Koen Aers updated GPD-138:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> error dialogue appears on task panel of properties for task node
> ----------------------------------------------------------------
>
>                 Key: GPD-138
>                 URL: http://jira.jboss.com/jira/browse/GPD-138
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta1
>         Environment: os x macbok pro, eclipse 3.3.0
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: stacktrace.txt
>
>
> Hi,
> when working with the designer in eclipse, if I put a new task node on the screen, immediately enter a value against the name on the 'general' panel under properties, then click on the tasks panel under properties, I get an error dialogue with the following details :
> Reason:
> 0
> 'An error has occurred. See error log for more details.
> 0
> On the other hand, if after entering a name, I click on the description input field, but do not enter anything, then click on the task panel under properties, there is no error.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-150) In-place label edit
 box offset in scrolled editor
In-Reply-To: <33534539.1187343121259.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14208971.1192446904561.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-150?page=all ]

Koen Aers updated GPD-150:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> In-place label edit box offset in scrolled editor
> -------------------------------------------------
>
>                 Key: GPD-150
>                 URL: http://jira.jboss.com/jira/browse/GPD-150
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: Eclipse 3.3, Windows XP SP2, JDK 6
>            Reporter: David Good
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: screenshot-1.jpg
>
>
> When editing a diagram larger than the editor window, clicking on a node label causes the edit box to appear in an offset position if the scroll bars are not in the origin. (see attachment)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-151) entries in mail node
 subject and
 body elements disappear depending on click order before save
In-Reply-To: <17748603.1187967378477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3730940.1192446904695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-151?page=all ]

Koen Aers updated GPD-151:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> entries in mail node subject and body elements disappear depending on click order before save
> ---------------------------------------------------------------------------------------------
>
>                 Key: GPD-151
>                 URL: http://jira.jboss.com/jira/browse/GPD-151
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: os x, eclipse 3.3.0, 
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> when I enter text in a mail node 'subject' input box, if I just click straight on the save button in eclipse, I lose the text entered...
> the same is true of the 'body' input box on the mail node
> to get this process to work I need to enter my text in the 'subject' input box, then click on the body input box, then click on the save button on the toolbar, this ensures my entry is in fact saved

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-158) Have the
 formsgenerator put a required attribute on jsf components
In-Reply-To: <14285454.1188998591044.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9699851.1192446904828.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-158?page=all ]

Koen Aers updated GPD-158:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> Have the formsgenerator put a required attribute on jsf components
> ------------------------------------------------------------------
>
>                 Key: GPD-158
>                 URL: http://jira.jboss.com/jira/browse/GPD-158
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: James Baxter
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> Tasks can have variables specified as 'required'. This is not built into the taskform, the forms are missing the following attribute from the h:input tag:
> [code]
> required="true"
> [/code]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-167) Diagram should not
 scroll after adding nodes from palette
In-Reply-To: <26566612.1189755791340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16757867.1192446904967.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-167?page=all ]

Koen Aers updated GPD-167:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Diagram should not scroll after adding nodes from palette
> ---------------------------------------------------------
>
>                 Key: GPD-167
>                 URL: http://jira.jboss.com/jira/browse/GPD-167
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>            Reporter: John Ruud
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> After adding nodes from the palette to diagrams where the scroll-bars are not in the top left corner position, the diagram will automatically scroll (to the top-left position). This is not desirable IMO, as it makes it easy to loose track of just-added nodes for large diagrams.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-154) process image rendered
 incorrectly for large process definition
In-Reply-To: <2916967.1186754521287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4668547.1192446905267.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-154?page=all ]

Koen Aers updated GPD-154:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> process image rendered incorrectly for large process definition
> ---------------------------------------------------------------
>
>                 Key: GPD-154
>                 URL: http://jira.jboss.com/jira/browse/GPD-154
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: mac osx,  tomcat 5.0.28
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> Hi,
> then I create a large process, and extend to the left beyond the original boundary, by placing and element in the designer and dragging, so scrollbars appear, the image when rendered in the console is offset incorrectly while on any given node,
> cheers
> Ross

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:17:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-14) Lay out Algorithm
In-Reply-To: <763449.1168949213846.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18908090.1192447023638.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-14?page=all ]

Koen Aers updated GPD-14:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Lay out Algorithm
> -----------------
>
>                 Key: GPD-14
>                 URL: http://jira.jboss.com/jira/browse/GPD-14
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Integrate a layout algorithm that is used when users add nodes to the xml directly to lay out the newly created components in an orderly fashion on the graphical canvas.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:17:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-140) when working with
 large process
 definitions, screen jumps to top whenever new nodes added in designer
In-Reply-To: <12103377.1186742271676.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9821009.1192447023785.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-140?page=all ]

Koen Aers updated GPD-140:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> when working with large process definitions, screen jumps to top whenever new nodes added in designer
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GPD-140
>                 URL: http://jira.jboss.com/jira/browse/GPD-140
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta2
>         Environment: osx macbook pro, eclipse 3.3.0, designer plugin 3.1.0 beta 1, beta 2, CR1
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Trivial
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> Hi,
> when working with large process diagrams, if I am scrolled down to the bottom of the view, and add a new node, when the screen is updated it jumps back up to the top, so I need to scroll down again.
> Obviously when adding many nodes, this costs time, its just a trivial thing.
> Cheers
> Ross

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:38:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 15 Oct 2007 07:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBSER-97)
 RegularObjectPersister.readSlotWithFields to log number of fields being
 read
Message-ID: <32246194.1192448283370.JavaMail.jira@cloud.prod.atl2.jboss.com>

RegularObjectPersister.readSlotWithFields to log number of fields being read
----------------------------------------------------------------------------

                 Key: JBSER-97
                 URL: http://jira.jboss.com/jira/browse/JBSER-97
             Project: JBoss Serialization
          Issue Type: Task
    Affects Versions: 1.0.3 GA
            Reporter: Galder Zamarreno
         Assigned To: Clebert Suconic
            Priority: Minor


writeSlotWithFields logs the slot name and number of fields to be written.

for debugging pupouses, readSlotWithFields could do with logging the number of fields written too, i.e.

RegularObjectPersister.readSlotWithFields() to start like this:

     short numberOfFields = (short)fieldsKey.length;

      if (isDebug)
      {
         log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName() + " and " + numberOfFields + " fields");
      }

instead of:

       if (isDebug)
       {
          log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName());
       }

       //final int numberOfFields = input.readShort();
      short numberOfFields = (short)fieldsKey.length;

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:40:30 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 15 Oct 2007 07:40:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11366225.1192448430259.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382414 ] 
            
Chris Laprun commented on JBPORTAL-1747:
----------------------------------------

I think that there should only be one guide that shows the GUI way and the XML way (which is actually expected to progressively disappear) in the same place. It doesn't make much sense to separate that information: why should an admin look at 2 different places to learn everything there is to know about Portal? Chapters could be structured with an overview, then how to proceed in the GUI then a more detailed look (if required). This is kind of the approach I took with the WSRP chapter and I think it works quite well. Moreover, looking at the reference guide, there are already some coverage of the GUI so it's kind of confusing that not everything is in there.

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:49:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 07:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24515743.1192448943498.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382416 ] 
            
Thomas Heute commented on JBPORTAL-1747:
----------------------------------------

Ok, i misread...

I though you were talking about userGuide and Quickstartguide merging :(

Yes i agree we could merge those 2

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4856) Fix web service
 issues related to the new metadata model
Message-ID: <28485098.1192452063304.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix web service issues related to the new metadata model
--------------------------------------------------------

                 Key: JBAS-4856
                 URL: http://jira.jboss.com/jira/browse/JBAS-4856
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:49:16 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:49:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4857) NPE in
 ContainerConfigurationMetaDataWrapper
Message-ID: <29114130.1192452556750.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in ContainerConfigurationMetaDataWrapper
--------------------------------------------

                 Key: JBAS-4857
                 URL: http://jira.jboss.com/jira/browse/JBAS-4857
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark


[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test

getContainerConfigurations returns null

      configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
            defaults.getContainerConfigurations());


Caused by: java.lang.NullPointerException
        at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:57:15 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:57:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5486656.1192453035963.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4855?page=comments#action_12382447 ] 
            
Thomas Diesler commented on JBAS-4855:
--------------------------------------

You should be able to see this when you change the jboss-web.xml for the jmx-console


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:59:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6610902.1192453143284.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4855?page=comments#action_12382449 ] 
            
Thomas Diesler commented on JBAS-4855:
--------------------------------------

14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:01:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 15 Oct 2007 09:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-472) Wrappers lack the
 generic type information
In-Reply-To: <5055386.1191269501072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1261007.1192453263831.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-472?page=all ]

Flavia Rainone closed JBAOP-472.
--------------------------------

    Resolution: Done

Notice that this affects only @Arg and @Return-annotated parameters.

The wrappers are not of too much use when it comes to @Target types, and to @Caller types.

Regarding @Thrown, we can test it know due to the fact that currently the type of a @Thrown-annotated advice parameter is forced to be Throwable, which is not a parameterized type.

> Wrappers lack the generic type information
> ------------------------------------------
>
>                 Key: JBAOP-472
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-472
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> This issue has already been fixed by Kabir with method wrappers.
> This task consists of fixing the issue for all other joinpoint types.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 09:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1079) JBM should call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14182746.1192453504583.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox closed JBMESSAGING-1079.
--------------------------------

    Resolution: Done

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 09:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21051765.1192453504876.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=all ]

Tim Fox closed JBMESSAGING-1101.
--------------------------------

    Resolution: Done

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:07:04 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 15 Oct 2007 09:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-415) Advice Matching
 algorithm is ignoring generics
In-Reply-To: <25286165.1181706071627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27068144.1192453624742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-415?page=all ]

Flavia Rainone closed JBAOP-415.
--------------------------------

    Resolution: Done

Generics information cannot currently be retrieved for @Target and @Caller.

To understand why, consider the following class:

public class MyClass<A>
{
    public void method()
    {}
}

When we intercept an execution of method, we have access to a target of type MyClass. To know the generics type of the target, we would need some method like Object.getType(), which we do not have.

The same explanation goes to @Caller on call pointcuts.

And for @Target on call joinpoints, we would also need some way to know the type of the object being called. Despite the difference that now we are in the context of the call, and not inside the method being executed, we cannot access the generics target type information for the same reasons as we cant in a method execution joinpoint.

> Advice Matching algorithm is ignoring generics
> ----------------------------------------------
>
>                 Key: JBAOP-415
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-415
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Advice Matching does not takes into account generic types; it is working with the old reflection API instead (Class instead of Type).
> To modifiy this, we need to update code in classes:
> - org.jboss.aop.advice.annotation.AdviceInfo
> - org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo
> - org.jboss.aop.advice.AdviceMethodProperties
> - joinpoint generators that pass the return, arguments and exception types to AdviceMethodProperties instances.
> This includes updating the assignability degree algorithm of org.jboss.aop.advice.annotation package.
> The methods for this task are partly written in org.jboss.test.aop.beforeafterArgs.ArgAspectGenerics.
> Tests for generic return types are also necessary, and need to be written.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:33:21 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 09:33:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-155) secure the gpd
	deployment servlet
In-Reply-To: <684538.1181894171603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20892072.1192455201333.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-155?page=all ]

Koen Aers updated GPD-155:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.4
                       (was: jBPM jPDL Designer 3.1.1)

> secure the gpd deployment servlet
> ---------------------------------
>
>                 Key: GPD-155
>                 URL: http://jira.jboss.com/jira/browse/GPD-155
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>
> the gpd deployment servlet should be secured.  the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that.  then the users will be able to control the authorization through the web interface itself.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 15 Oct 2007 09:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24085504.1192456743389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=all ]

Manik Surtani resolved JBCACHE-1192.
------------------------------------

    Resolution: Done

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication, Eviction
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6, 2.1.0.CR1, 2.1.0.GA
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 10:07:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 10:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1753) Align WSRP with
	WS 2.0
Message-ID: <3188765.1192457223550.JavaMail.jira@cloud.prod.atl2.jboss.com>

Align WSRP with WS 2.0
----------------------

                 Key: JBPORTAL-1753
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1753
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal WSRP
    Affects Versions: 2.6.2 Final
            Reporter: Thomas Heute
         Assigned To: Chris Laprun
             Fix For: 2.6.3 Final


At least portal-wsrp.jse must be renamed portal-wsrp.war.

There are also some WARN when you start WSRP on JBoss AS 4.2.2.GA

15:49:57,971 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_ServiceDescription_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null
15:49:58,920 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Markup_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null
15:49:59,827 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_PortletManagement_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null
15:50:01,753 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Registration_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 10:28:15 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 10:28:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-156)
 GenericElementXmlAdapter doesnt add child nodes
In-Reply-To: <9558754.1188946691290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25320190.1192458495935.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-156?page=all ]

Koen Aers closed GPD-156.
-------------------------

    Resolution: Done

The fix was applied to HEAD. Thanks for the contribution and sorry for the delay. Feel free to reopen if there are still problems.

> GenericElementXmlAdapter doesnt add child nodes
> -----------------------------------------------
>
>                 Key: GPD-156
>                 URL: http://jira.jboss.com/jira/browse/GPD-156
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Imran Naqvi
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> If you have a template such as:
> <?xml version="1.0"?> 
> <process-definition name="Movie" version="11"> 
> <start-state name="Start"> 
> <transition to="Get MPEG Properties" /> 
> </start-state> 
> <node name="Get MPEG Properties"> 
> <action class="SomeActionHandler"><send>010901</send> 
> <keys> 
> <entry> 
>                                             <key>VarName</key> 
>                                             <value>1122</value> 
>                                 </entry> 
> </keys> 
> <receive> 
> <element>030101</element> 
> <element>030102</element> 
> </receive> 
> </action> 
> <transition to="End"/> </node> 
> <end-state name="End" /> 
> The nested Generic Elements arent added by the adapter. The reason for this is that the GenericElementXmlAdapter.doModelAdd() doesnt do anything. We need to add the following code to this method:
>                                            String type = child.getElementType();
> 		SemanticElement jpdlElement;
> 		jpdlElement = getSemanticElementFactory().createById("org.jbpm.gd.jpdl.genericElement");
> 		child.initialize(jpdlElement);
> 		GenericElement genericElement= (GenericElement )getSemanticElement();
> 		genericElement.addGenericElement((GenericElement)jpdlElement);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:05:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 15 Oct 2007 11:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25920044.1192460703605.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382498 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Summary of the case:
1. 50  (and then 20) concurrent consumers overload the node they're connected to, rendering it useless (including making the JMX console inaccessible)
2. Killing and then restarting the server makes messages disappear

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:05:04 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 15 Oct 2007 11:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20416391.1192460704116.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382500 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

Since this is a release task, and as i am testing the version of jbossws already installed in AS (in this case, 2.0.1.SP2), i think i can ignore the undeploy and deploy tasks before running the test suite?
As far as the testsuite src is concerned should i be using jbossws/native/trunk or jbossws/tags/jbossws-native-2.0.1.SP2 ?



> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:05:04 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Mon, 15 Oct 2007 11:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <11549323.1192460704766.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]

Jeff Mesnil updated JBMESSAGING-375:
------------------------------------

    Attachment: patch-JBMESSAGING-375.txt

updated Stian's patch for JBoss Messaging 1.4.0 (based on r3190):
- base class is RoundRobinDistributor
- "grouping" round robin algorithm is done in GroupingRoundRobinDistributor
- associated tests are in GroupingRoundRobinDistributorTest
- put test code common to RRDTest and GroupingRRDTest into
  SimpleReferenceableReceiver class
- added support to reset bound receiver by setting JMSXGroupSeq to 0

some caveats:
- GroupingRRD's algorithm is brittle and depends on a lot of internals from
RRD which should not be exposed
  -> maybe grouping should be handled directly by RRD?
- GroupingRRD is not used by MessagingQueue (still using RRD)

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:13:04 2007
From: jira-events at lists.jboss.org (Paul Jackson (JIRA))
Date: Mon, 15 Oct 2007 11:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1279) Memory leak in
	release 4.0.2
Message-ID: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory leak in release 4.0.2
----------------------------

                 Key: JBRULES-1279
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
         Environment: tested with windows jdk5 and jdk6
            Reporter: Paul Jackson
         Assigned To: Mark Proctor


I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:

DroolsTest.java

import java.io.InputStreamReader;
import java.io.Reader;

import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.StatefulSession;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;

public class DroolsTest {

	public void run() throws Exception {
		
		RuleBase ruleBase = createRuleBase();

		long counter = 0;
		while(true) {
			StatefulSession session = ruleBase.newStatefulSession(false);
			if(++counter % 100 == 0) {
				System.out.println(counter);
			}
			session.dispose();
		}
	}
	
	private RuleBase createRuleBase() throws Exception {
		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );

		PackageBuilder builder = new PackageBuilder();
		builder.addPackageFromDrl( source );
		if ( builder.hasErrors() ) {
		    System.out.println( builder.getErrors().toString() );
		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
		}
		Package pkg = builder.getPackage();
		
		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
		ruleBase.addPackage( pkg );

		return ruleBase;
	}
	
	public static void main(String[] args) throws Exception {
		new DroolsTest().run();
	}
}

HelloWorld.drl

#list any import classes here.



#declare any global variables here




rule "Your First Rule"
	
	when
		#conditions
	then 
		#actions
		
end

rule "Your Second Rule"
	#include attributes such as "salience" here...
	when
		#conditions
	then 
		#actions
		
end

When I run this with release 4.0.1 I have to manually break the program to get it to stop.

When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:25:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 11:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26077558.1192461903429.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382509 ] 
            
Dimitris Andreadis commented on JBAS-4853:
------------------------------------------

I upgraded Branch_4_2 to jbossxb 1.0.0.SP1. 

Hopefully that will solve the regression seen by Thomas.

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:25:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 11:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33009617.1192461903654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4853?page=all ]

Dimitris Andreadis closed JBAS-4853.
------------------------------------

    Resolution: Done

Thomas, please re-open if the problem persists.

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:49:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 15 Oct 2007 11:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21755702.1192463343391.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120411  (was: http://www.jboss.com/index.html?module=bb&op=viewforum&f=153)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:07:47 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 15 Oct 2007 12:07:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20234407.1192464467533.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4766?page=comments#action_12382530 ] 
            
Dominik Pospisil commented on JBAS-4766:
----------------------------------------

Confirming that this is fixed in JBossCache trunk.

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: buddy-sync-20s.tgz, driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:18:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 15 Oct 2007 12:18:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4858) SecurityDeployer
 changes with metadata
Message-ID: <15605108.1192465087771.JavaMail.jira@cloud.prod.atl2.jboss.com>

SecurityDeployer changes with metadata
--------------------------------------

                 Key: JBAS-4858
                 URL: http://jira.jboss.com/jira/browse/JBAS-4858
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Security
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For:  JBossAS-5.0.0.Beta3


The Security Deployer needs to be changed as per the following rant from Adrian


=============================
To me this is the wrong approach anyway.

There shouldn't be any code that does

if (ejbdeployment)
  doThis();
else if (webdeployment)
  doThat();
else if (unknowntype) // OOPS (pun intended  ;-) 
  cantDoIt();

The webservice deployers should be working off some generic metadata that triggers them to operate.

Then each type of deployment can populate that metadata to say "I want a webservice endpoint for this".

This is a seperate deployer for each type we know how to map to a webservice it takes the ejb/web/other metadata and maps or bridges it to the webservice metadata.

It shouldn't just be restricted to ejbs and wars.

e.g. An MBean should be capable of being an endpoint if there is a deployer that creates the relevant metadata attachment from say a META-INF/jboss-webservice.xml in the sar.

The security deployers take the same brain dead (non object orientated) approach.
============================================================

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 15 Oct 2007 12:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8905339.1192465203491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=comments#action_12382537 ] 
            
Manik Surtani commented on JBCACHE-1009:
----------------------------------------

A bit tricky at the moment since regions aren't a top level construct.  Caches are preloaded at startup, and these preload Fqns are loaded regardless of whether it is in an active region or not.  Then, *after* the cache starts, regions are defined as active or inactive.

I guess this approach does make some sense when defaultInactive is true, and cache loader preloads *only* happens when regions are activated.

Still though, moving to 3.0.0 once we have regions as a top level construct since the shape of all this may yet change.

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 15 Oct 2007 12:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27729935.1192465203615.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=all ]

Manik Surtani updated JBCACHE-1009:
-----------------------------------

    Fix Version/s: 3.0.0
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:52:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 15 Oct 2007 12:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7121210.1192467123354.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4766?page=comments#action_12382552 ] 
            
Brian Stansberry commented on JBAS-4766:
----------------------------------------

Actually that's fixed in current head of JBoss Cache branch 1.4.X; JBC trunk produces the 2.x releases and isn't being tested in these tests.

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: buddy-sync-20s.tgz, driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:54:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 15 Oct 2007 12:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-295) Add unit tests for
 ReplicationQueue
Message-ID: <19003617.1192467243481.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-295?page=all ]

Brian Stansberry updated JBCACHE-295:
-------------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)

> Add unit tests for ReplicationQueue
> -----------------------------------
>
>                 Key: JBCACHE-295
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-295
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:54:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 12:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16450045.1192467243768.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=all ]

Andrew Rubinger updated EJBTHREE-1066:
--------------------------------------

    Workaround Description: 
Instead of using 2 <business-remote> nodes, use one with comma-delimited values ie:

<business-remote>org.jboss.ejb3.test.ejbthree1066.Adder,org.jboss.ejb3.test.ejbthree1066.Subtractor</business-remote>
                Workaround: [Workaround Exists]

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:59:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 15 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29144613.1192467543395.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=comments#action_12382556 ] 
            
Brian Stansberry commented on JBCACHE-1009:
-------------------------------------------

Yeah, should have made that clearer; assumption is defaultInactive = true. TBH, having region-based marshalling enabled and inactiveOnStartup=false doesn't really make sense; only useful for a corner case where someone would instantiate a cache, register some classloaders, and *then* start the cache (and even that might not work properly).  For 3.0 we might be better off getting rid of inactiveOnStartup as a config option.

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 13:07:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Mon, 15 Oct 2007 13:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-469) Make sure @Aspect
 works in older versions of AS
In-Reply-To: <21626519.1190893361105.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25000476.1192468023577.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-469?page=all ]

Kabir Khan reassigned JBAOP-469:
--------------------------------

    Assignee: Kabir Khan  (was: Stale Pedersen)

> Make sure @Aspect works in older versions of AS
> -----------------------------------------------
>
>                 Key: JBAOP-469
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-469
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.beta2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repackaging of the annotations stuff http://jira.jboss.com/jira/browse/JBAOP-428 has caused some problems. Create a simple test in the testsuite for https://svn.jboss.org/repos/jbossas/branches/Branch_4_2/ using @Aspect + @Bind, instead of a jboss-aop.xml file.
> If any classes are missing, add jars taken from jboss-container.jar to the AS 4.x deployers for both jdk 1.4 and jdk 5. There are some examples for this already in https://svn.jboss.org/repos/jbossas/projects/aop/trunk/build/build-release.xml
> JBoss 5 uses the correct version of MC, so all the classes will be available there.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 13:09:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Mon, 15 Oct 2007 13:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-469) Make sure @Aspect
 works in older versions of AS
In-Reply-To: <21626519.1190893361105.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14916855.1192468143266.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-469?page=all ]

Kabir Khan closed JBAOP-469.
----------------------------

    Resolution: Done

This should be fine, we already are creating a jboss-container-annotation.jar, and the ScopedUnitTestCase uses annotations already

> Make sure @Aspect works in older versions of AS
> -----------------------------------------------
>
>                 Key: JBAOP-469
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-469
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.beta2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repackaging of the annotations stuff http://jira.jboss.com/jira/browse/JBAOP-428 has caused some problems. Create a simple test in the testsuite for https://svn.jboss.org/repos/jbossas/branches/Branch_4_2/ using @Aspect + @Bind, instead of a jboss-aop.xml file.
> If any classes are missing, add jars taken from jboss-container.jar to the AS 4.x deployers for both jdk 1.4 and jdk 5. There are some examples for this already in https://svn.jboss.org/repos/jbossas/projects/aop/trunk/build/build-release.xml
> JBoss 5 uses the correct version of MC, so all the classes will be available there.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 14:05:03 2007
From: jira-events at lists.jboss.org (Chris Lee (JIRA))
Date: Mon, 15 Oct 2007 14:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4859) No facility to
 change location of Tomcat 'work' directory (catalina home)
Message-ID: <638196.1192471503492.JavaMail.jira@cloud.prod.atl2.jboss.com>

No facility to change location of Tomcat 'work' directory (catalina home)
-------------------------------------------------------------------------

                 Key: JBAS-4859
                 URL: http://jira.jboss.com/jira/browse/JBAS-4859
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.1.GA
         Environment: n/a
            Reporter: Chris Lee
         Assigned To: Remy Maucherat


Presently the location for Tomcat's 'work' directory is hard-coded to jboss.server.home.dir; it would be nice to override this (as is done with jboss.server.data.dir, jboss.server.log.dir, and jboss.server.temp.dir) to move 'data' directories outside the server home.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:11:04 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 15 Oct 2007 15:11:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1754) RoleModule
 documentation has duplicate code in identity chapter
Message-ID: <8051413.1192475464311.JavaMail.jira@cloud.prod.atl2.jboss.com>

RoleModule documentation has duplicate code in identity chapter
---------------------------------------------------------------

                 Key: JBPORTAL-1754
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1754
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun
         Assigned To: Boleslaw Dawidowicz




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:17:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 15:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26250721.1192475823517.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382587 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

Large number of consumers appear fine *as long* supportsFailover on the connection factory is false.

When it is set to true, throughput dramtically drops. This implies a problem with session replication between nodes. Will investigate further.

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:20:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 15:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1113) Post office
 and message updates at failover need to be transactional
Message-ID: <32831290.1192476003623.JavaMail.jira@cloud.prod.atl2.jboss.com>

Post office and message updates at failover need to be transactional
--------------------------------------------------------------------

                 Key: JBMESSAGING-1113
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Ovidiu Feodorov


At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.

If the failing over server is itself killed during this process, then the system can enter an inconsistent state.

Need to make sure all database updates are performed in a single transaction.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:26:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 15:26:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9316960.1192476364546.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=comments#action_12382590 ] 
            
Andrew Rubinger commented on EJBTHREE-1066:
-------------------------------------------

EnterpriseBean.remote and EnterpriseBean.local are overwritten in org.jboss.ejb3.metamodel.EjbJarDDObjectFactory.isEjbParentName() when more than one invocation is made (multiple "business-remote" or "business-local" nodes).

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:40:03 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Mon, 15 Oct 2007 15:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24440057.1192477203620.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Damien Delautre reopened JBRULES-1252:
--------------------------------------

             
When I have two function imports, only the last one is dumped.

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:42:03 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Mon, 15 Oct 2007 15:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <538412.1192477323895.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Damien Delautre updated JBRULES-1252:
-------------------------------------

    Attachment: DrlDumper.patch

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch, DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:42:07 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 15 Oct 2007 15:42:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1755) Identity chapter
 has lots of typos
Message-ID: <8667873.1192477327630.JavaMail.jira@cloud.prod.atl2.jboss.com>

Identity chapter has lots of typos
----------------------------------

                 Key: JBPORTAL-1755
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1755
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 16:05:03 2007
From: jira-events at lists.jboss.org (Frank Langelage (JIRA))
Date: Mon, 15 Oct 2007 16:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4860) List of Timers
 contains all SLSB and MDB, not only those implementing TimedObject
Message-ID: <1925938.1192478703269.JavaMail.jira@cloud.prod.atl2.jboss.com>

List of Timers contains all SLSB and MDB, not only those implementing TimedObject
---------------------------------------------------------------------------------

                 Key: JBAS-4860
                 URL: http://jira.jboss.com/jira/browse/JBAS-4860
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
         Environment: JBoss-4.2.2.GA, built from the current sources.
Sun JDK 1.5.0_13 on Sun Solaris 10 SPARC.
            Reporter: Frank Langelage
            Priority: Minor


If I call the listTimers operation using the jmx-console I see all Stateless session Beans and all Message Driven Beans now, but only 5 of this 64 are really TimeObjects:
Output is for example:
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MbiWaehrFacade]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-planning.jar,name=MbiProbfSelect]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-costing.jar,name=PreliminaryCosting]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-common.jar,name=Version]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=Calendar]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-inventory.jar,name=StockManagement]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-sales.jar,name=SalesOrder]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-sales.jar,name=SalesItem]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService]
handle: [id=1190398872277,target=[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService],first=21-Sep-2007 20:23:00.000,periode=60000]
[id=1190398872277,target=[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService],remaining=47564,periode=60000,in_timeout]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MbiFistaFacade]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MessageRetrieval]

MailService implements TimeObject, but all others do not.
My Stateful Session Beans don't appear in the list, but all Stateless and MDBs do.


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 16:39:03 2007
From: jira-events at lists.jboss.org (Danilo Guerra (JIRA))
Date: Mon, 15 Oct 2007 16:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1070) dlqhandler fails
 on
 redelivery for messages missing  the JMS property "JMSXDeliveryCount"
Message-ID: <24854922.1192480743296.JavaMail.jira@cloud.prod.atl2.jboss.com>

dlqhandler fails on redelivery for messages missing  the JMS property "JMSXDeliveryCount"
-----------------------------------------------------------------------------------------

                 Key: EJBTHREE-1070
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1070
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.1.GA
            Reporter: Danilo Guerra


GenericDLQHandler fails when handling redelivery of messages missing the property "JMSXDeliveryCount" when using non JbossMQ providers.

excerpt from the class: org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler

   protected boolean handleDelivery(Message msg)
   {
   .....
         try
         {
            if (msg.propertyExists(PROPERTY_DELIVERY_COUNT))
               count = msg.getIntProperty(PROPERTY_DELIVERY_COUNT) - 1;
         }
         catch (JMSException ignored)
         {
            count = incrementResentCounter(id);
         }
...
}

This code fails because the property PROPERTY_DELIVERY_COUNT is checked and the exception is never thrown. As a result the resent counter is not incremented and the message will not be sent to the DLQ.


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 15 Oct 2007 17:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25263483.1192483983474.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 1.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 15 Oct 2007 17:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26579506.1192483983688.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 2.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 15 Oct 2007 17:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25219704.1192483983926.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 3.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:37:41 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 17:37:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1060)
 getInvokedBusinessInterface doesn't return correct interface
In-Reply-To: <22610729.1191919853782.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22996228.1192484261848.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1060?page=comments#action_12382619 ] 
            
Andrew Rubinger commented on EJBTHREE-1060:
-------------------------------------------

Root of problem is org.jboss.ejb3.session.SessionContainer.getInvokedBusinessInterface() matching Remote invocations by method signature to implemented interfaces, incorrectly assuming that if a business interface contains the method invoked, than this interface was in turn invoked.  This is not the case with inheritance or if many interfaces dictate the same method signature.

> getInvokedBusinessInterface doesn't return correct interface
> ------------------------------------------------------------
>
>                 Key: EJBTHREE-1060
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>
> When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface.
> @Stateless
> @Remote({Remote1.class, Remote2.class})
> interface Remote1 extends CommonRemote
> interface Remote2 extends CommonRemote

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:41:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 15 Oct 2007 18:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-819) Consider removing
 dependency on jboss-commons
Message-ID: <26278208.1192488064482.JavaMail.jira@cloud.prod.atl2.jboss.com>

Consider removing dependency on jboss-commons
---------------------------------------------

                 Key: JBREM-819
                 URL: http://jira.jboss.com/jira/browse/JBREM-819
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA
            Reporter: Ron Sigal
         Assigned To: Trustin Lee
             Fix For: 3.0.0.Alpha1 (Otter)


>From Greg Hinkle of the JBoss Operations Network group:  

"... not only are the including tons of crap in the garbage pale called commons, but they dictate tons of library dependencies and serialization versions. For a group like ours that has to be able to simultaneously connect to every version of jboss released in the last 3 years it is not a good situation. We end up having to create a separate class loader per connection.

"Now with remoting, we're actually using it as a core infrastructure piece. That means its in parent classloaders to these connection classloaders. As long as commons is in that required list we can't use remoting this way. We're going to have to do some serious classloader restructuring to be able to support our needs."


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:50:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 18:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-751) @Local and
 @Remote on one interface must not be allowed
In-Reply-To: <25136912.1161262361433.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13850398.1192488603396.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-751?page=all ]

Andrew Rubinger updated EJBTHREE-751:
-------------------------------------

    Description: 
EJB3 4.6.6 bullet 5.4
'The same business interface cannot be both a local and a remote business interface of the bean.'

Deployment must fail with a nice friendly message.

  was:
EJB3 4.6.7 bullet 5.4
'The same business interface cannot be both a local and a remote business interface of the bean.'

Deployment must fail with a nice friendly message.


Corrected EJB3 Specification reference in description

> @Local and @Remote on one interface must not be allowed
> -------------------------------------------------------
>
>                 Key: EJBTHREE-751
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-751
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.0 GA
>
>
> EJB3 4.6.6 bullet 5.4
> 'The same business interface cannot be both a local and a remote business interface of the bean.'
> Deployment must fail with a nice friendly message.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:52:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 18:52:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19448736.1192488724368.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=comments#action_12382631 ] 
            
Andrew Rubinger commented on EJBTHREE-1063:
-------------------------------------------

Test Cases now deploy, 17 total, 3 errors, 0 failures.

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:52:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 18:52:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24322401.1192488724642.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=all ]

Andrew Rubinger updated EJBTHREE-1063:
--------------------------------------

    Description: Requested by Anil  (was: Requested by Anil; possibly related to EJB3Registry)

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 19:03:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 19:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19172621.1192489383382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=all ]

Andrew Rubinger updated EJBTHREE-1063:
--------------------------------------

    Assignee: Anil Saldhana  (was: Andrew Rubinger)

Sending back to Anil; deployment successful.

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Anil Saldhana
>             Fix For: HEAD
>
>
> Requested by Anil

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 19:13:03 2007
From: jira-events at lists.jboss.org (Burr Sutter (JIRA))
Date: Mon, 15 Oct 2007 19:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-987) display non GMT+0
	time zones
In-Reply-To: <14779733.1181746286332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28705834.1192489983868.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-987?page=comments#action_12382634 ] 
            
Burr Sutter commented on JBPM-987:
----------------------------------

why is the GUI playing with timezone?  It should just display what ever is in the database for that process instance.  



> display non GMT+0 time zones
> ----------------------------
>
>                 Key: JBPM-987
>                 URL: http://jira.jboss.com/jira/browse/JBPM-987
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: Jean-Louis Rastapoc
>         Assigned To: David Lloyd
>
> The web-console currently uses the default JSF timezone conversion and displays GMT+0.
> Other time zones should be read from the client or be configurable.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 20:18:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 20:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
In-Reply-To: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31445879.1192493884429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1058?page=all ]

Andrew Rubinger resolved EJBTHREE-1058.
---------------------------------------

    Resolution: Rejected

This construct is a violation of EJB3 Spec 4.6.6 Bullet 1:

"The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface."


> Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
> -------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1058
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Assuming:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean
> ..when invoking:
> Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
> EJBObject ejbObject = (EJBObject) obj;
> ejbObject.remove();
> ...the following exception is encountered:
> Could not resolve beanClass method from proxy call
> java.lang.RuntimeException: Could not resolve beanClass method from proxy call
> 	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1634)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
> 	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 20:22:09 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 20:22:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1071) Business
 Interface must not extend EJBObject or EJBLocalObject
Message-ID: <18467162.1192494129846.JavaMail.jira@cloud.prod.atl2.jboss.com>

Business Interface must not extend EJBObject or EJBLocalObject
--------------------------------------------------------------

                 Key: EJBTHREE-1071
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1071
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


EJB3 Spec 4.6.6 Bullet 1:

"The following are the requirements for the session bean's business interface:
     * The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface."

...thus the following construct:

public interface StatefulRemote extends EJBObject{...}

...and:

@Stateful
@Remote(StatefulRemote.class)
@RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
public class StatefulRemoteBean 

...should fail with a deployment exception referencing the specification.


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 21:43:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Mon, 15 Oct 2007 21:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-480) NPE in concurrent
 join point generation
Message-ID: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in concurrent join point generation
---------------------------------------

                 Key: JBAOP-480
                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
            Reporter: Jason T. Greene
             Fix For: 2.0.0.beta2


Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 

Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
	... 14 more
Caused by: java.lang.NullPointerException
	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
	... 33 more


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:13:03 2007
From: jira-events at lists.jboss.org (lepe (JIRA))
Date: Tue, 16 Oct 2007 03:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4861) CLONE -bin/run.sh
 should force IPv4 on Darwin systems
Message-ID: <7505315.1192518783592.JavaMail.jira@cloud.prod.atl2.jboss.com>

CLONE -bin/run.sh should force IPv4 on Darwin systems
-----------------------------------------------------

                 Key: JBAS-4861
                 URL: http://jira.jboss.com/jira/browse/JBAS-4861
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: System service
            Reporter: lepe
         Assigned To: Dimitris Andreadis
             Fix For: JBossAS-4.2.0.CR2,  JBossAS-5.0.0.Beta3


There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. 

Something like:

   if [ "`uname`" = "Linux" ]; then 
       JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" 
   fi 
fi 

So that Linux systems use ipv4 


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:13:03 2007
From: jira-events at lists.jboss.org (lepe (JIRA))
Date: Tue, 16 Oct 2007 03:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4862) Verify whether
 -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
Message-ID: <13570609.1192518783751.JavaMail.jira@cloud.prod.atl2.jboss.com>

Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
--------------------------------------------------------------------------------

                 Key: JBAS-4862
                 URL: http://jira.jboss.com/jira/browse/JBAS-4862
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: System service
            Reporter: lepe
         Assigned To: Dimitris Andreadis
             Fix For: JBossAS-5.0.1.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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:17:03 2007
From: jira-events at lists.jboss.org (lepe (JIRA))
Date: Tue, 16 Oct 2007 03:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4861) CLONE -bin/run.sh
 should force IPv4 on Darwin systems
In-Reply-To: <7505315.1192518783592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1217785.1192519023424.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4861?page=comments#action_12382654 ] 
            
lepe commented on JBAS-4861:
----------------------------

Sorry, bad idea of cloning the issue, thought I would have a chance an modify the description etc... :)

What I would like is to have the same stuff added for Darwin, that is to preferIPv4Stack.

regards,

/L

Redpill AB

> CLONE -bin/run.sh should force IPv4 on Darwin systems
> -----------------------------------------------------
>
>                 Key: JBAS-4861
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4861
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: System service
>            Reporter: lepe
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.0.CR2,  JBossAS-5.0.0.Beta3
>
>
> There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. 
> Something like:
>    if [ "`uname`" = "Linux" ]; then 
>        JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" 
>    fi 
> fi 
> So that Linux systems use ipv4 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:30:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 03:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13960270.1192519803453.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382656 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

Yes, do not call the deploy target.

Run 

ant tests

from  https://svn.jboss.org/repos/jbossws/stack/native/tags/jbossws-native-2.0.1.SP2


> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 03:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4861) CLONE -bin/run.sh
 should force IPv4 on Darwin systems
In-Reply-To: <7505315.1192518783592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29014143.1192520223412.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4861?page=all ]

Dimitris Andreadis updated JBAS-4861:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.2.0.CR2)
                       (was:  JBossAS-5.0.0.Beta3)

Please don't set the fix version.

> CLONE -bin/run.sh should force IPv4 on Darwin systems
> -----------------------------------------------------
>
>                 Key: JBAS-4861
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4861
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: System service
>            Reporter: lepe
>         Assigned To: Dimitris Andreadis
>
> There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. 
> Something like:
>    if [ "`uname`" = "Linux" ]; then 
>        JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" 
>    fi 
> fi 
> So that Linux systems use ipv4 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 03:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4862) Verify whether
 -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
In-Reply-To: <13570609.1192518783751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25303140.1192520223698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4862?page=all ]

Dimitris Andreadis updated JBAS-4862:
-------------------------------------

    Fix Version/s:     (was: JBossAS-5.0.1.CR1)

> Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4862
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4862
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: System service
>            Reporter: lepe
>         Assigned To: Dimitris Andreadis
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:20:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 04:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2196067.1192522803325.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382668 ] 
            
Dimitris Andreadis commented on JBAS-4853:
------------------------------------------

The following are the issues that were included into the CR11/SP1

JBXB-97 org.w3c.dom.Element is being mapped incorrectly
JBXB-105 switch from oswego to java.util concurrent
JBXB-103 JBossXB ignores non-ignorable white space
JBXB-96 JAXB error when using different derived types in the same container/array type

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:24:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6425861.1192523043711.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12382669 ] 
            
Dimitris Andreadis commented on JBAS-4754:
------------------------------------------

The TCK should be fully passing now. We did a jbossxb upgrade in JBAS-4853, so maybe we should retest? :-/



> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:24:04 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Tue, 16 Oct 2007 04:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1070) The jBPM test
 configuration has problem with database setup
Message-ID: <18592858.1192523044126.JavaMail.jira@cloud.prod.atl2.jboss.com>

The jBPM test configuration has problem with database setup
-----------------------------------------------------------

                 Key: JBPM-1070
                 URL: http://jira.jboss.com/jira/browse/JBPM-1070
             Project: JBoss jBPM
          Issue Type: Bug
    Affects Versions: jBPM jPDL 3.2.2
            Reporter: Jiri Pechanec
         Assigned To: Tom Baeyens


The jBPM test process expects hiberante.properties file to be placed in defined configuration directory. jBPM config file JBPM.3/jpdl/jar/src/test/config/jbpm.cfg.xml orders to use hibernate.properties file (<string name="resource.hibernate.properties" value="hibernate.properties" />).
But the JBPM.3/jpdl/jar/src/test/java/org/jbpm/db/AbstractDbTestCase.java uses config file less JBPM.3/jpdl/jar/src/test/java/org/jbpm/jbpm.test.cfg.xml and the line mentioned above is missing. Thus the configuration is read from standard hibernate.cfg.xml.

Solution
Either add the missing line to jbpm.test.cfg.xml or change AbstractDbTestCase.java to use central config file in config directory. The second one is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:37:08 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:37:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4863) NPE in
 ContainerConfigurationMetaDataWrapper
Message-ID: <22857669.1192523828772.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in ContainerConfigurationMetaDataWrapper
--------------------------------------------

                 Key: JBAS-4863
                 URL: http://jira.jboss.com/jira/browse/JBAS-4863
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark
             Fix For:  JBossAS-5.0.0.Beta3


[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test

getContainerConfigurations returns null

      configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
            defaults.getContainerConfigurations());


Caused by: java.lang.NullPointerException
        at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:37:08 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:37:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4857) NPE in
 ContainerConfigurationMetaDataWrapper
Message-ID: <17176280.1192523828962.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4857?page=all ]

Thomas Diesler deleted JBAS-4857:
---------------------------------


> NPE in ContainerConfigurationMetaDataWrapper
> --------------------------------------------
>
>                 Key: JBAS-4857
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4857
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> getContainerConfigurations returns null
>       configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
>             defaults.getContainerConfigurations());
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
>         at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
Message-ID: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>

jboss-web with 4.0 dtd does not deploy
--------------------------------------

                 Key: JBAS-4864
                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30735970.1192524063851.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382670 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
        at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
        at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
        ... 66 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30521598.1192524064063.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382671 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

 <?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <security-domain>java:/jaas/JBossWS</security-domain>
</jboss-web>

You should be able to see this when you change the jboss-web.xml for the jmx-console

14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26164928.1192524064335.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4864?page=all ]

Thomas Diesler updated JBAS-4864:
---------------------------------

    Comment: was deleted

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33129325.1192524064519.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382672 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <security-domain>java:/jaas/JBossWS</security-domain>
</jboss-web>

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24919213.1192524183445.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382673 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/

You should be able to see this when you change the jboss-web.xml for the jmx-console 

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
[ Show ? ]
Thomas Diesler [15/Oct/07 08:58 AM] 14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

       



From jira-events at lists.jboss.org  Tue Oct 16 04:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12380199.1192524183786.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4864?page=all ]

Thomas Diesler updated JBAS-4864:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
Message-ID: <8727861.1192524183617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4855?page=all ]

Thomas Diesler deleted JBAS-4855:
---------------------------------


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 05:50:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Tue, 16 Oct 2007 05:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27404211.1192528203607.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382679 ] 
            
Alexey Loubyansky commented on JBAS-4864:
-----------------------------------------

Strange, if I do that for jmx-console.war, it starts w/o an error. With or w/o Internet connection.

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:19:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 06:19:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10958405.1192529955085.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=comments#action_12382683 ] 
            
Manik Surtani commented on JBCACHE-1009:
----------------------------------------

Yes, well we really need to get into the detailed design of JBCACHE-64, including whether each region has it's own lifecycle, which in effect is your region activation.

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:21:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
In-Reply-To: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11944812.1192530063377.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1195?page=all ]

Manik Surtani reassigned JBCACHE-1195:
--------------------------------------

    Assignee: Mircea Markus  (was: Manik Surtani)

> Fix tutorial for 2.1.0 series
> -----------------------------
>
>                 Key: JBCACHE-1195
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.
> Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:21:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-486) Optimize
	activations
Message-ID: <30176370.1192530063651.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-486?page=all ]

Manik Surtani updated JBCACHE-486:
----------------------------------

    Fix Version/s: 2.1.0.CR1

> Optimize activations
> --------------------
>
>                 Key: JBCACHE-486
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-486
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.3.0.GA
>            Reporter: Jerry Gauthier
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> JBCACHE-420 notes that activation processing is performed excessively.  The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue.
> The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor.  Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated.  This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination.  This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader).
> It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance.  One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__
> to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when
> activated.  

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:27:13 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 16 Oct 2007 06:27:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBSER-98) Write slot with
 fields only if both readObject and writeObject are missing
Message-ID: <1789794.1192530433263.JavaMail.jira@cloud.prod.atl2.jboss.com>

Write slot with fields only if both readObject and writeObject are missing
--------------------------------------------------------------------------

                 Key: JBSER-98
                 URL: http://jira.jboss.com/jira/browse/JBSER-98
             Project: JBoss Serialization
          Issue Type: Feature Request
    Affects Versions: 1.0.3 GA
            Reporter: Galder Zamarreno
         Assigned To: Clebert Suconic


Over the last few weeks, I've been dealing with a funky support case which showed the following 
stacktrace:

...
Caused by: org.jboss.serial.exception.SerializationException: Excepted to be String
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1120)
at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:71)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
at org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
at org.jboss.serial.io.MarshalledObjectForLocalCalls.get(MarshalledObjectForLocalCalls.java:60)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
... 28 more
Caused by: java.lang.ClassCastException: org.jboss.serial.finalcontainers.IntegerContainer
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1116)
... 42 more 

The cause of the issue was that the customer had a class where it had re-implemented 
readObject(java.io.ObjectInputStream stream) but had not re-implemented 
writeObject(java.io.ObjectOutputStream stream). This is obviously a programming error on their side,
but it took a while to detect such stupid mistake.

The problem within JBoss Serialization was that because this class didn't have a writeObject() 
reimplementation, it was a writing the class as a slot with fields, but when it came to reading it, it 
was reading the class as a slot with method because readObject had been reimplemented. The 
next time a slot with fields was read, the fields were mixed up.

To avoid these type of situations, I'd suggest that:
- JBS only writes as fields if *both* writeObject and readObject are missing. Right now, can't see a 
situation where you'd implement one and not the other, thoughts?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 07:59:03 2007
From: jira-events at lists.jboss.org (Olaf Fricke (JIRA))
Date: Tue, 16 Oct 2007 07:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1072) Ejb3TxPolicy
 does not rollback the transaction in case of an error
Message-ID: <20940487.1192535943615.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ejb3TxPolicy does not rollback the transaction in case of an error
------------------------------------------------------------------

                 Key: EJBTHREE-1072
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1072
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: HEAD
            Reporter: Olaf Fricke
            Priority: Blocker


The class Ejb3TxPolicy is used to rollback the transaction in the case of exceptions. According to the ejb 3.0 spec, the transaction is rolled back in case of ApplicationException with rollback() evaluating to true, in case of RuntimeExceptions or in case of EjbException. 

All other exception will not lead to a rollback on the current transaction.

Unfortunately, the same is true in case of errors. If, for example, an AssertionError (or a ClassDefNotFoundError etc.) occurs, the current transaction will be committed and not rolled back. This behaviour is wrong with respect to the ejb 3.0 spec (see for example table 14 on page 360 of ejbcore.pdf)

A possible solution would be to wrap the error into a new RuntimeException after handling ApplicationException (in both methods handleExceptionInOurTx and handleInCallerTx):

<code>
if (t instanceof Error)
      {
         t = new RuntimeException(t);
      }
if (!(t instanceof RuntimeException || t instanceof RemoteException))
      {
         throw t;
      }
</code>

The wrapping is necessary, because both the EJBException and the EJBTransactionRolledbackException can only handle exceptions, but not errors.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 08:32:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 08:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <27580949.1192537923568.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12382707 ] 
            
Tim Fox commented on JBMESSAGING-375:
-------------------------------------

Jeff-

Feel free to implement another way if you wish.

You don't have to use the patch.

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 08:52:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 08:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1154) Introduce ability
 to mark nodes
 as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <594535.1192539123417.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Mircea Markus closed JBCACHE-1154.
----------------------------------

    Resolution: Done

documentation also updated

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:19:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Tue, 16 Oct 2007 09:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28166456.1192540743305.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382720 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

The hudson job is configured here.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBossWS-2.0.1.SP2-testsuite-AS4.2.x/

There are 3 test failures due to java.lang.ClassNotFoundException: org.apache.ws.scout.registry.ConnectionFactoryImpl
Where is this class located?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:28:03 2007
From: jira-events at lists.jboss.org (Davide Baroncelli (JIRA))
Date: Tue, 16 Oct 2007 09:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-38) Use URI instead of
 URL in FileProtocolArchiveBrowserFactory
Message-ID: <12430491.1192541283774.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use URI instead of URL in FileProtocolArchiveBrowserFactory
-----------------------------------------------------------

                 Key: JBCOMMON-38
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-38
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Davide Baroncelli
         Assigned To: Dimitris Andreadis
            Priority: Critical
             Fix For: 2.2.2.GA


Current code in FileProtocolArchiveBrowserFactory has problems when the URL coming from above contains escaped characters. E.g.: In an app. I'm writing, the class receives an URL coming from a ClassLoader.getResources method: resources in directories containing square brackets arrive to the class in escaped URLs such as the following:

file:/C:/Stratosfera/pos_back/%5BCARCON%5Dstratosfera-verifica-cartoline-concorso/war/WEB-INF/classes/

this form fails in the current implementation because of line 40:

File f = new File(url.getPath());

this results in a non existing file. Replacing the line with the following solves the problem:

       File f;
       try {
           f = new File(url.toURI());
       }
       catch ( URISyntaxException e ) {
           throw new RuntimeException( e );
       }

this problems creates various compatibility problems in depending libraries (hibernate entitymanager for one).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:36:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 16 Oct 2007 09:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-856) Use Buddy
 Replication for clustered SFSBs
In-Reply-To: <24225310.1170195680226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13739062.1192541763623.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-856?page=comments#action_12382724 ] 
            
Brian Stansberry commented on EJBTHREE-856:
-------------------------------------------

This remains open for AS 4.2.2 due to JBCACHE-1194; will need JBC 1.4.1.SP6 to resolve.

> Use Buddy Replication for clustered SFSBs
> -----------------------------------------
>
>                 Key: EJBTHREE-856
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-856
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Optimize the replicated SFSB cache for use with Buddy Replication.  Basically means checking cache calls to ensure unwanted data gravitations do not occur. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:42:04 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 16 Oct 2007 09:42:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-987) display non GMT+0
	time zones
In-Reply-To: <14779733.1181746286332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5659386.1192542124516.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-987?page=comments#action_12382726 ] 
            
Ronald van Kuijk commented on JBPM-987:
---------------------------------------

The 'gui' is not, well not the jbpm developers at least... JSF is.... That is the reason the seam convertDateTime does this for you. It converts the date/time to the seam timezone, which is the current users' local timezone. Normally JSF displays date/time always according to Zulu time. 

> display non GMT+0 time zones
> ----------------------------
>
>                 Key: JBPM-987
>                 URL: http://jira.jboss.com/jira/browse/JBPM-987
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: Jean-Louis Rastapoc
>         Assigned To: David Lloyd
>
> The web-console currently uses the default JSF timezone conversion and displays GMT+0.
> Other time zones should be read from the client or be configurable.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:16:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 10:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-38) Use URI instead of
 URL in FileProtocolArchiveBrowserFactory
In-Reply-To: <12430491.1192541283774.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15346559.1192544163903.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-38?page=all ]

Dimitris Andreadis updated JBCOMMON-38:
---------------------------------------

    Fix Version/s:     (was: 2.2.2.GA)
         Priority: Major  (was: Critical)

Please, don't set the fix version and the criticality.

> Use URI instead of URL in FileProtocolArchiveBrowserFactory
> -----------------------------------------------------------
>
>                 Key: JBCOMMON-38
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-38
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Davide Baroncelli
>         Assigned To: Dimitris Andreadis
>
> Current code in FileProtocolArchiveBrowserFactory has problems when the URL coming from above contains escaped characters. E.g.: In an app. I'm writing, the class receives an URL coming from a ClassLoader.getResources method: resources in directories containing square brackets arrive to the class in escaped URLs such as the following:
> file:/C:/Stratosfera/pos_back/%5BCARCON%5Dstratosfera-verifica-cartoline-concorso/war/WEB-INF/classes/
> this form fails in the current implementation because of line 40:
> File f = new File(url.getPath());
> this results in a non existing file. Replacing the line with the following solves the problem:
>        File f;
>        try {
>            f = new File(url.toURI());
>        }
>        catch ( URISyntaxException e ) {
>            throw new RuntimeException( e );
>        }
> this problems creates various compatibility problems in depending libraries (hibernate entitymanager for one).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 10:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20369705.1192544283706.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Fix Version/s: 2.2.3.GA
                       (was: 2.2.2.GA)

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.0.6.GA, 2.2.3.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 10:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15290293.1192544283894.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=all ]

Dimitris Andreadis updated JBCOMMON-35:
---------------------------------------

    Fix Version/s: 2.2.3.GA
                       (was: 2.2.2.GA)

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.0.6.GA, 2.2.3.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCACHE-1128) Add a full
 component-info.xml to source tree
In-Reply-To: <5459575.1184107351575.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12501393.1192544284036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1128?page=all ]

Manik Surtani reassigned JBCACHE-1128:
--------------------------------------

    Assignee: Manik Surtani  (was: Brian Stansberry)

> Add a full component-info.xml to source tree
> --------------------------------------------
>
>                 Key: JBCACHE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1128) Add a full
 component-info.xml to source tree
In-Reply-To: <5459575.1184107351575.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29736576.1192544284219.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1128?page=all ]

Manik Surtani updated JBCACHE-1128:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Add a full component-info.xml to source tree
> --------------------------------------------
>
>                 Key: JBCACHE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCACHE-1129) Specify version
 dependencies in component-info.xml
In-Reply-To: <1176722.1184107471596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18545100.1192544284410.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1129?page=all ]

Manik Surtani reassigned JBCACHE-1129:
--------------------------------------

    Assignee: Manik Surtani  (was: Brian Stansberry)

> Specify version dependencies in component-info.xml
> --------------------------------------------------
>
>                 Key: JBCACHE-1129
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Seems they are listed in pom.xml; need equivalent entries in component-info.xml.
> This adds fun, since we need to ensure consistency with the AS versions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1129) Specify version
 dependencies in component-info.xml
In-Reply-To: <1176722.1184107471596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6423955.1192544284586.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1129?page=all ]

Manik Surtani updated JBCACHE-1129:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Specify version dependencies in component-info.xml
> --------------------------------------------------
>
>                 Key: JBCACHE-1129
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Seems they are listed in pom.xml; need equivalent entries in component-info.xml.
> This adds fun, since we need to ensure consistency with the AS versions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1170) Partial state
 transfer fails when multiple regions present
In-Reply-To: <5358429.1187970318264.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20614273.1192544403310.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1170?page=all ]

Manik Surtani resolved JBCACHE-1170.
------------------------------------

    Resolution: Done

> Partial state transfer fails when multiple regions present
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1170
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.  
> Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase.  Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call.  Using region /JSESSION/localhost/http-field
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
> The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped", or perhaps nothing at all.
> Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal.  Two problems:
> 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
> 2) Need to ensure that the right Fqn gets written.  In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything.  If not, just cleaning up the ThreadLocal should work.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1170) Leakage of
 marshalling region
 stored in ThreadLocal causes partial state transfer to fail when multiple
 regions present
In-Reply-To: <5358429.1187970318264.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19187545.1192544403488.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1170?page=all ]

Manik Surtani updated JBCACHE-1170:
-----------------------------------

       Summary: Leakage of marshalling region stored in ThreadLocal causes partial state transfer to fail when multiple regions present  (was: Partial state transfer fails when multiple regions present)
    Complexity: Medium

> Leakage of marshalling region stored in ThreadLocal causes partial state transfer to fail when multiple regions present
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1170
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.  
> Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase.  Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call.  Using region /JSESSION/localhost/http-field
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
> The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped", or perhaps nothing at all.
> Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal.  Two problems:
> 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
> 2) Need to ensure that the right Fqn gets written.  In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything.  If not, just cleaning up the ThreadLocal should work.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:22:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 10:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1176) Bad performance
 when deleting a large tree from JDBCCacheLoader
In-Reply-To: <22599873.1188997871354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15734615.1192544523639.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1176?page=all ]

Mircea Markus resolved JBCACHE-1176.
------------------------------------

    Resolution: Done

Starting with 2.0 remove operations are executed to a single call to the DBMS. I've added logs (trace) that show the operations being executed whils removing the nodes from the database.

> Bad performance when deleting a large tree from JDBCCacheLoader 
> ----------------------------------------------------------------
>
>                 Key: JBCACHE-1176
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1176
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR1
>            Reporter: gmeroz
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> When using JDBCCacheLaoder and trying to delete the hole tree:
> using: cache.getCache().removeNode(Fqn.ROOT)
> it takes a long time which may cause transaction timeouts when running on application server.
> it seems that each node is deleted seperately instead of using one sql command.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:32:48 2007
From: jira-events at lists.jboss.org (Prabhat Jha (JIRA))
Date: Tue, 16 Oct 2007 10:32:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1756) port jacc
 contention workaround that was made for Intuit to 2.6.2
Message-ID: <20582814.1192545168988.JavaMail.jira@cloud.prod.atl2.jboss.com>

port jacc contention workaround that was made for Intuit to 2.6.2
-----------------------------------------------------------------

                 Key: JBPORTAL-1756
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1756
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Security
    Affects Versions: 2.6.2 Final
            Reporter: Prabhat Jha
         Assigned To: Sohil Shah


As agreed during today's portal QA call, please port jacc fix that was done for Intuit to 2.6.2. We will test to make sure everything works as expected and then make it mainstream in 2.6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:34:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 10:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1154) Introduce
 ability to mark
 nodes as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17495372.1192545243698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Mircea Markus reopened JBCACHE-1154:
------------------------------------

             
status should be resolved, not closed

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:36:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 10:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1154) Introduce
 ability to mark
 nodes as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6244037.1192545363465.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Mircea Markus resolved JBCACHE-1154.
------------------------------------

    Resolution: Done

resolved

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:40:08 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 16 Oct 2007 10:40:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13229065.1192545609361.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=comments#action_12382747 ] 
            
Andrew Rubinger commented on EJBTHREE-1066:
-------------------------------------------

Progress temporarily suspended while refactoring in metamodel is performed.

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:50:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 16 Oct 2007 10:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1174) Add further
	passivation docs
In-Reply-To: <8204338.1188232763535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15554735.1192546203794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1174?page=all ]

Brian Stansberry closed JBCACHE-1174.
-------------------------------------

    Fix Version/s: 2.1.0.CR1
                       (was: 2.1.0.GA)
       Resolution: Done

> Add further passivation docs
> ----------------------------
>
>                 Key: JBCACHE-1174
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1174
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.CR1
>
>
> Add discussion a la http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077805#4077805. I've already done this in my local checkout but can't figure out how to get the maven jdocbook stuff to run so I can validate.  This task is just a reminder to finish up once a more urgent need drives me to figure this stuff out.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:58:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:58:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1121) Investigate the
 suitability of not copying child maps into workspace
In-Reply-To: <14759070.1183724948890.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24856985.1192546684177.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1121?page=all ]

Manik Surtani updated JBCACHE-1121:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Investigate the suitability of not copying child maps into workspace
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1121
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1121
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Optimistic Locking
>    Affects Versions: 1.4.1.GA, 1.4.0.GA, 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Tue Oct 16 11:36:54 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 11:36:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6966050.1192549014983.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382789 ] 
            
Tim Fox commented on JBMESSAGING-1110:
--------------------------------------

This could be related to a jboss remoting issue where remoting incorrectly terminates a connection under load since it didn't receive a ping.

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 11:55:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 11:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1129) Specify version
 dependencies in component-info.xml
In-Reply-To: <1176722.1184107471596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17441905.1192550103413.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1129?page=all ]

Manik Surtani resolved JBCACHE-1129.
------------------------------------

    Resolution: Rejected

> Specify version dependencies in component-info.xml
> --------------------------------------------------
>
>                 Key: JBCACHE-1129
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Seems they are listed in pom.xml; need equivalent entries in component-info.xml.
> This adds fun, since we need to ensure consistency with the AS versions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:01:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 12:01:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1128) Automated
 integration testing to ensure compatibility of dependencies
In-Reply-To: <5459575.1184107351575.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <822587.1192550475150.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1128?page=all ]

Manik Surtani updated JBCACHE-1128:
-----------------------------------

               Summary: Automated integration testing to ensure compatibility of dependencies  (was: Add a full component-info.xml to source tree)
     Original Estimate: 1 week
    Remaining Estimate: 1 week
         Fix Version/s: 2.2.0.GA
                            (was: 2.1.0.GA)
                            (was: 2.1.0.CR1)
            Complexity: Medium

Deferring this to 2.2.0.

The purpose here is to ensure that the dependencies JBC ships with are compatible with versions shipped with JBoss AS.

E.g., (hypothetically speaking) JBC ships with JGroups 2.6.1 and JBoss AS 5 shipped with JGroups 2.6.0.  The JBC tests just run with 2.6.1 and before release we should certify it against libs shipped with AS 5.

Basically, an automated way to generate this page:

http://labs.jboss.org/jbosscache/compatibility/index.html

Should be as simple as an ant script, that pulls down:

1.  Srcs for JBC we hope to test
2.  Dependent libs from JBC's pom.xml
3.  Dependent libs from AS's component-info.xml that overlaps with libs from (2)
4.  Run test suite
5.  Repeat steps 1-4 for all versions of AS we need to test against
6.  Generate report based on output



> Automated integration testing to ensure compatibility of dependencies
> ---------------------------------------------------------------------
>
>                 Key: JBCACHE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.2.0.GA
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:15:04 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 16 Oct 2007 12:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-987) display non GMT+0
	time zones
In-Reply-To: <14779733.1181746286332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <603890.1192551304219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-987?page=comments#action_12382800 ] 
            
Ronald van Kuijk commented on JBPM-987:
---------------------------------------

@Tom,

No it does not. The seam convertDateTime does this for you when displaying it. On the server side (e.g. when posting) it is still in Zulu time. There are multiple solutions:
1: Take the seam s:convertDateTime component and port that to a j4j one
2: just use f:convertDateTime and create one component that looks up the users timezone
3: just use convertDateTime and configure somewhere what the timezone would be.

Only the last needs documentation. 2 is plain jsf as is 1 (but a little less)

And after that, add this tag to each field that requires a date

> display non GMT+0 time zones
> ----------------------------
>
>                 Key: JBPM-987
>                 URL: http://jira.jboss.com/jira/browse/JBPM-987
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: Jean-Louis Rastapoc
>         Assigned To: David Lloyd
>
> The web-console currently uses the default JSF timezone conversion and displays GMT+0.
> Other time zones should be read from the client or be configurable.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:38:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 16 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19159656.1192552683936.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Edson Tirelli reassigned JBRULES-1279:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:45:35 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 16 Oct 2007 12:45:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3351079.1192553136006.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Edson Tirelli updated JBRULES-1279:
-----------------------------------

    Fix Version/s: 4.0.2_SOA_4.2-CP1
                   4.0.3
                   4.1.0

> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:03:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 16 Oct 2007 13:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13115398.1192554183969.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Edson Tirelli resolved JBRULES-1279.
------------------------------------

    Resolution: Done

Thanks for reporting and providing test case.

This was indeed a serious regression introduced at revision #15532. It is now fixed and I added an integration test to make sure it will not happen again.

Please let us know if you face any other related problem.

> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1113) Post office
 and message updates at failover need to be transactional
In-Reply-To: <32831290.1192476003623.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4069029.1192555814461.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1113?page=all ]

Tim Fox updated JBMESSAGING-1113:
---------------------------------

    Fix Version/s: 1.4.0.SP1
      Description: 
At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.

If the failing over server is itself killed during this process, then the system can enter an inconsistent state.

Easy solution is to make sure the the postoffice db update is done *after* the merge.

  was:
At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.

If the failing over server is itself killed during this process, then the system can enter an inconsistent state.

Need to make sure all database updates are performed in a single transaction.

         Assignee: Tim Fox  (was: Ovidiu Feodorov)

> Post office and message updates at failover need to be transactional
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1113
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.
> If the failing over server is itself killed during this process, then the system can enter an inconsistent state.
> Easy solution is to make sure the the postoffice db update is done *after* the merge.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:34:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23022572.1192556043695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox updated JBMESSAGING-1112:
---------------------------------

          Summary: Consumption with highly concurrent clients lock a JBM server node.  (was: Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear")
    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:34:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13590499.1192556043907.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382835 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

I have fixed this in TRUNK by using a semaphore to prevent more than a max number of replication requests to occur concurrently to prevent overwhelming JGroups.

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:42:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:42:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1114) JBoss
 Remoting fails under load
Message-ID: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Remoting fails under load
-------------------------------

                 Key: JBMESSAGING-1114
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
            Priority: Critical
             Fix For: 1.4.0.SP1


JBoss Remoting fails with various different errors when under extreme load.

To replicate this, set up two clustered server nodes, using a MySQL database.

These can both be on the same machine, using ServiceBindingManager.

On a second machine run Ovidiu's messkit toolki, first to send some messages:

mess -stat send -size 10240 50000 

And then to receive them back using 50 concurrent consumers:

mess -stat -sessions 50 receive all

You will notice that JBoss Remoting fails with errors:

I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?

I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.

It also seems remoting is continually timing out and recreating connections - this could also be a source of error.

How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:46:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3611764.1192556763383.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox updated JBMESSAGING-1112:
---------------------------------

    Attachment: messkit.zip

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>         Attachments: messkit.zip
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 14:26:03 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Tue, 16 Oct 2007 14:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1073)
 SessionContext.getBusinessObject(...) throws IllegalStateException on
 @Service EJB
Message-ID: <27081964.1192559163555.JavaMail.jira@cloud.prod.atl2.jboss.com>

SessionContext.getBusinessObject(...) throws IllegalStateException on @Service EJB
----------------------------------------------------------------------------------

                 Key: EJBTHREE-1073
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1073
             Project: EJB 3.0
          Issue Type: Bug
          Components: EJB3 Extensions
    Affects Versions: AS 4.2.1.GA
            Reporter: Michael McKibben


Calling SessionContext.getBusinessObject(...) throws an IllegalStateException within a @Service EJB. This should behave like a Stateless/Stateful EJB no?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 15:16:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 15:16:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1113) Post office
 and message updates at failover need to be transactional
In-Reply-To: <32831290.1192476003623.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15023360.1192562165500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1113?page=all ]

Tim Fox closed JBMESSAGING-1113.
--------------------------------

    Resolution: Done

> Post office and message updates at failover need to be transactional
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1113
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.
> If the failing over server is itself killed during this process, then the system can enter an inconsistent state.
> Easy solution is to make sure the the postoffice db update is done *after* the merge.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 15:30:06 2007
From: jira-events at lists.jboss.org (Matthew Sandoz (JIRA))
Date: Tue, 16 Oct 2007 15:30:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-143) Load the icon of a
 paletteContribution entry from the plugin directory where it is defined
In-Reply-To: <28132773.1186761253835.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26630040.1192563006056.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-143?page=all ]

Matthew Sandoz updated GPD-143:
-------------------------------

    Attachment: PaletteRoot.java

I just ended up needing to do this as well - if you havent already fixed it this seems to work. I am also attaching this file to the issue

### Eclipse Workspace Patch 1.0
#P org.jbpm.gd.jpdl
Index: src/org/jbpm/gd/common/editor/PaletteRoot.java
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/PaletteRoot.java,v
retrieving revision 1.2
diff -u -r1.2 PaletteRoot.java
--- src/org/jbpm/gd/common/editor/PaletteRoot.java	7 Aug 2007 11:38:49 -0000	1.2
+++ src/org/jbpm/gd/common/editor/PaletteRoot.java	16 Oct 2007 19:25:06 -0000
@@ -21,6 +21,7 @@
  */
 package org.jbpm.gd.common.editor;
 
+import java.net.URL;
 import java.util.ArrayList;
 import java.util.HashMap;
 import java.util.List;
@@ -37,6 +38,7 @@
 import org.eclipse.gef.palette.ToolEntry;
 import org.eclipse.jface.resource.ImageDescriptor;
 import org.jbpm.gd.jpdl.Plugin;
+import org.osgi.framework.Bundle;
 
 
 public class PaletteRoot extends org.eclipse.gef.palette.PaletteRoot {
@@ -78,9 +80,9 @@
 					PaletteEntry entry;
 					CreationFactory factory = new CreationFactory(object, editor.getSemanticElementFactory(), editor.getNotationElementFactory());
 					if (isNode) {
-						entry = new CreationToolEntry(label, tooltip, factory, getIconDescriptor(icon), null);
+						entry = new CreationToolEntry(label, tooltip, factory, getIconDescriptor(entryElement), null);
 					} else {
-						entry = new ConnectionCreationToolEntry(label, tooltip, factory, getIconDescriptor(icon), null);
+						entry = new ConnectionCreationToolEntry(label, tooltip, factory, getIconDescriptor(entryElement), null);
 					}
 					entry.setId(entryName);
 					paletteGroup.add(entry);
@@ -90,8 +92,10 @@
 		}
 	}
 	
-	private ImageDescriptor getIconDescriptor(String icon) {
-		return ImageDescriptor.createFromURL(Plugin.getDefault().getBundle().getEntry("/" + icon));
+	private ImageDescriptor getIconDescriptor(IConfigurationElement element) {
+		Bundle bundle = Platform.getBundle(element.getDeclaringExtension().getNamespace());
+		URL location = bundle.getEntry("/" + element.getAttribute("icon"));
+		return ImageDescriptor.createFromURL(location);
 	}
 	
 	private void processPaletteContribution(IConfigurationElement configurationElement) {


> Load the icon of a paletteContribution entry from the plugin directory where it is defined
> ------------------------------------------------------------------------------------------
>
>                 Key: GPD-143
>                 URL: http://jira.jboss.com/jira/browse/GPD-143
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>         Attachments: PaletteRoot.java
>
>
> In PaletteRoot class, the icon of a palette entry is always loaded from org.jbpm.gd.jpdl plugin, even if the paletteContribution entry is defined in a dependent plugin.
> The information, where the palette entry element (entryElement in PaletteRoot.addControls) is defined, can be found in entryElement.getContributor().getName().
> So also the corresponding image can be loaded from the correct bundle.
> [ Sorry to only give a verbal description of the implementation. I would sign a corporate contributor's agreement, but I have problems with the procedure, e.g.
> - do we need a corporate jboss account for my boss to sign
> - if we sign with the "corporate" account, with which account I need to contribute then
> etc.
> So I would need some assistance here. Then you would get a real diff also.
> ]

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:42:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 16 Oct 2007 16:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2006933.1192567323610.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 103.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:42:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 16 Oct 2007 16:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25940469.1192567323911.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 104.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:42:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 16 Oct 2007 16:42:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4106651.1192567324101.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 105.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:52:03 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 16 Oct 2007 16:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-603) FLUSH: problems
 with TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10968731.1192567923491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12382877 ] 
            
Vladimir Blagojevic commented on JGRP-603:
------------------------------------------

Bela described the scenario to reproduce this issue:

- View is V2 {A,B,C}
- Member C has address C:7602
- Member C is killed and *immediately* restarted (before A can exclude it)
- Member C has the *same* address: C:7602
- On JOIN, A will return the *existing view* V2 because it sees that C is still a member !

Does C's FLUSH.down() unblock in such a case ? I don't think so, it only unblocks on reception of the STOP-FLUSH message ! However, this message is never received because the coord (A) never even starts the flush in this case !

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 17:37:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Tue, 16 Oct 2007 17:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1757) Update workflow
 chapter as it
 doesn't take into account the fact that the workflow service has been
 extracted... Should also document how to use the service in portlets.
Message-ID: <2067996.1192570623164.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update workflow chapter as it doesn't take into account the fact that the workflow service has been extracted... Should also document how to use the service in portlets.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1757
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1757
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:50:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4865) Validate the JBM
	clustered config
Message-ID: <13693139.1192585803269.JavaMail.jira@cloud.prod.atl2.jboss.com>

Validate the JBM clustered config
---------------------------------

                 Key: JBAS-4865
                 URL: http://jira.jboss.com/jira/browse/JBAS-4865
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For:  JBossAS-5.0.0.Beta3


This is just a link to a JBM task : JBMESSAGING-1093

I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:50:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4865) Validate the JBM
	clustered config
In-Reply-To: <13693139.1192585803269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21820092.1192585803628.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4865?page=all ]

Clebert Suconic updated JBAS-4865:
----------------------------------

    Component/s: JB5-Messaging

> Validate the JBM clustered config
> ---------------------------------
>
>                 Key: JBAS-4865
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4865
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This is just a link to a JBM task : JBMESSAGING-1093
> I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:54:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4865) Validate the JBM
	clustered config
In-Reply-To: <13693139.1192585803269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9738458.1192586043355.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4865?page=all ]

Clebert Suconic closed JBAS-4865.
---------------------------------

    Resolution: Done

> Validate the JBM clustered config
> ---------------------------------
>
>                 Key: JBAS-4865
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4865
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This is just a link to a JBM task : JBMESSAGING-1093
> I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:54:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1093) Verify/Update
 the "all" configuration on JBossHead
In-Reply-To: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20653264.1192586043510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1093?page=all ]

Clebert Suconic closed JBMESSAGING-1093.
----------------------------------------

    Resolution: Done

> Verify/Update the "all" configuration on JBossHead
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1093
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:54:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-726) Write/Ellect
 some
 Clustering tests to go into Integration Testsuite on ApplicationServer
In-Reply-To: <1288401.1168296267440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28549451.1192586043701.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-726?page=all ]

Clebert Suconic updated JBMESSAGING-726:
----------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121313

> Write/Ellect some Clustering tests to go into Integration Testsuite on ApplicationServer
> ----------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-726
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-726
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.2.0.Beta1
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: EAP 4.3 Integration, AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 23:30:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 16 Oct 2007 23:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1198)
 putForExternalRead not silent on remote node
Message-ID: <22737059.1192591803386.JavaMail.jira@cloud.prod.atl2.jboss.com>

putForExternalRead not silent on remote node
--------------------------------------------

                 Key: JBCACHE-1198
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1198
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani


Seeing WARN logging like this when using PFER with a replicating cache:

22:16:37,931  WARN pessimistic-shared:2839 - replication failure with method_call MethodName: _putForExternalRead; MethodIdInteger: 45; Args: (null, /test/com/foo/test/ENTITY/KEY, item, VALUE1) exception
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/test/com/foo/test/ENTITY/KEY, caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock=write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)
	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299)
	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3958)
	at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2826)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330)
	at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77)
	at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624)
	at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533)
	at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365)
	at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:744)
	at org.jgroups.JChannel.up(JChannel.java:1137)
	at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:999)
	at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1023)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.cache.lock.TimeoutException: write lock for /test/com/foo/test/ENTITY/KEY could not be acquired after 0 ms. Locks: Read lock owners: []
Write lock owner: GlobalTransaction:<192.168.1.145:35562>:1
 (caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock info: write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0))
	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244)
	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
	... 33 more

Issue seems to be that the logic in CacheImpl.putForExternalRead that makes the call a no-op if the node exists and sets the failSilently option otherwise never gets executed on the remote node.  Instead the call gets handled by _replicate which just passes the MethodCall into the interceptor chain without setting any options.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 00:11:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 17 Oct 2007 00:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7559882.1192594263424.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Andrew Rubinger reassigned EJBTHREE-1057:
-----------------------------------------

    Assignee: Andrew Rubinger

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 4.2.2.GA
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 00:32:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 17 Oct 2007 00:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-820) Fix race in
 ServerInvokerCallbackHandler.handleCallback()
Message-ID: <17208857.1192595523247.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix race in ServerInvokerCallbackHandler.handleCallback()
---------------------------------------------------------

                 Key: JBREM-820
                 URL: http://jira.jboss.com/jira/browse/JBREM-820
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: callbacks
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.4.0.Beta1 (Pinto)


org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback() calls  callBackClient.setSessionId(sessionId) without synchronization.  It's doing that so that the callback is sent to the client with a sessionId that matches the appropriate InvokerCallbackHandler on the client side.  However, I think that if two separate threads made the same call at the same time, callbackClient's sessionId could get messed up.

The solution is to call callBackClient.setSessionId(sessionId) once in init() right after the Client has been created.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:03:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4866) TECHREVIEW:
 Installation Guide - Zip Installation
Message-ID: <2871061.1192600983255.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide - Zip Installation
-------------------------------------------------

                 Key: JBAS-4866
                 URL: http://jira.jboss.com/jira/browse/JBAS-4866
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:05:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4867) TECHREVIEW:
 Installation Guide - Graphical Installation
Message-ID: <10698891.1192601103903.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide - Graphical Installation
-------------------------------------------------------

                 Key: JBAS-4867
                 URL: http://jira.jboss.com/jira/browse/JBAS-4867
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:05:04 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4868) TECHREVIEW:
 Installation Guide - Chapter:'Test Your Installation'
Message-ID: <33490414.1192601104115.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide -  Chapter:'Test Your Installation'
------------------------------------------------------------------

                 Key: JBAS-4868
                 URL: http://jira.jboss.com/jira/browse/JBAS-4868
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:05:04 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4869) TECHREVIEW:
 Installation Guide - Chapter:'Getting Started'
Message-ID: <23725770.1192601104378.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide -  Chapter:'Getting Started'
-----------------------------------------------------------

                 Key: JBAS-4869
                 URL: http://jira.jboss.com/jira/browse/JBAS-4869
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:07:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4866) TECHREVIEW:
 Installation Guide - Zip Installation
In-Reply-To: <2871061.1192600983255.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32206138.1192601223726.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4866?page=comments#action_12382906 ] 
            
Vinu S Renish commented on JBAS-4866:
-------------------------------------

Verify the following content in this chapter:
1. Zip download Filename - jboss-4.2.2.GA.zip
2. Zip file download location
3. Description

> TECHREVIEW: Installation Guide - Zip Installation
> -------------------------------------------------
>
>                 Key: JBAS-4866
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4866
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:11:18 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:11:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4867) TECHREVIEW:
 Installation Guide - Graphical Installation
In-Reply-To: <10698891.1192601103903.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8855243.1192601478637.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4867?page=comments#action_12382907 ] 
            
Vinu S Renish commented on JBAS-4867:
-------------------------------------

 Verify the following content in this chapter:
1. Do we have a GUI installer?
2. Installer Filename - jboss-4.2.2.GA.zip
3. Major Installation Steps
4. Shortcuts / XDG Menu applicable?


> TECHREVIEW: Installation Guide - Graphical Installation
> -------------------------------------------------------
>
>                 Key: JBAS-4867
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4867
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:13:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4868) TECHREVIEW:
 Installation Guide -  Chapter:'Test Your Installation'
In-Reply-To: <33490414.1192601104115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2914165.1192601583413.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4868?page=comments#action_12382908 ] 
            
Vinu S Renish commented on JBAS-4868:
-------------------------------------

Verify the following content in this chapter: 
1. Console output on server start up
2. Do we have a production profile? 
3. Image snapshot


> TECHREVIEW: Installation Guide -  Chapter:'Test Your Installation'
> ------------------------------------------------------------------
>
>                 Key: JBAS-4868
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4868
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:15:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4869) TECHREVIEW:
 Installation Guide -  Chapter:'Getting Started'
In-Reply-To: <23725770.1192601104378.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21233685.1192601703648.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4869?page=comments#action_12382909 ] 
            
Vinu S Renish commented on JBAS-4869:
-------------------------------------

Is there a link we can point to for supported Operating System/Databases etc?

> TECHREVIEW: Installation Guide -  Chapter:'Getting Started'
> -----------------------------------------------------------
>
>                 Key: JBAS-4869
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4869
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:07:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 03:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1071) Possible problem in
 concurrent signalling from multiple threads
Message-ID: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>

Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------

                 Key: JBPM-1071
                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
MySQL 5.0.22
            Reporter: Jiri Pechanec
         Assigned To: Tom Baeyens
            Priority: Critical
         Attachments: expl.tar.gz

Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database

The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13

Explanation of the outcome
4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:07:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 03:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1071) Possible problem in
 concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10436493.1192604823943.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]

Jiri Pechanec updated JBPM-1071:
--------------------------------

    Attachment: expl.tar.gz

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:09:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 03:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1280) Automatically
 import types into a package config if no config exists
Message-ID: <11072875.1192604943226.JavaMail.jira@cloud.prod.atl2.jboss.com>

Automatically import types into a package config if no config exists
--------------------------------------------------------------------

                 Key: JBRULES-1280
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1280
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE


based on what it finds in the jar.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:17:17 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 17 Oct 2007 03:17:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21552592.1192605437644.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382912 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

You need to deploy the juddi-service.sar from the jbossws/thirdparty directory.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 04:16:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 04:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1072) Concurrent
 JobExecutors can process the same job in parallel
Message-ID: <8119670.1192608963680.JavaMail.jira@cloud.prod.atl2.jboss.com>

Concurrent JobExecutors can process the same job in parallel
------------------------------------------------------------

                 Key: JBPM-1072
                 URL: http://jira.jboss.com/jira/browse/JBPM-1072
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
MySQL 5.0.22
            Reporter: Jiri Pechanec
         Assigned To: Tom Baeyens
         Attachments: expl.tar.gz

Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts 20 executor threads
2) Starts the process instance that will asynchronously execute action on the second node
4) The second node writes a record to the database

The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Success 0
Failure 0
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2
Action 2 1
Action 2 1
Action 2
Action 2 1

Explanation of the outcome
9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created)


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 04:16:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 04:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1072) Concurrent
 JobExecutors can process the same job in parallel
In-Reply-To: <8119670.1192608963680.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18039029.1192608963858.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1072?page=all ]

Jiri Pechanec updated JBPM-1072:
--------------------------------

    Attachment: expl.tar.gz

Test case is TestMultiJobExecutor

> Concurrent JobExecutors can process the same job in parallel
> ------------------------------------------------------------
>
>                 Key: JBPM-1072
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1072
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts 20 executor threads
> 2) Starts the process instance that will asynchronously execute action on the second node
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Success 0
> Failure 0
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2
> Action 2 1
> Explanation of the outcome
> 9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 05:18:19 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Wed, 17 Oct 2007 05:18:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <22446557.1192612699908.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]

Jeff Mesnil updated JBMESSAGING-375:
------------------------------------

    Attachment: patch-JBMESSAGING-375.txt

simpler patch: group ID binding is handled directly in RoundRobinDistributor

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 05:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 17 Oct 2007 05:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-467) Serialize container
 proxies out of vm
In-Reply-To: <21248201.1190887061041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29856113.1192613404389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-467?page=all ]

Kabir Khan reassigned JBAOP-467:
--------------------------------

    Assignee: Flavia Rainone  (was: Kabir Khan)

> Serialize container proxies out of vm
> -------------------------------------
>
>                 Key: JBAOP-467
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-467
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Flavia Rainone
>             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

        


From jira-events at lists.jboss.org  Wed Oct 17 05:30:06 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 17 Oct 2007 05:30:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3281188.1192613406528.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Kabir Khan reassigned JBAOP-480:
--------------------------------

    Assignee: Flavia Rainone

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 06:43:03 2007
From: jira-events at lists.jboss.org (Ian Priest (JIRA))
Date: Wed, 17 Oct 2007 06:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-178) ClassCastException
 using Process Designer 3.1.0SP1
Message-ID: <15484296.1192617783364.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException using Process Designer 3.1.0SP1
--------------------------------------------------

                 Key: GPD-178
                 URL: http://jira.jboss.com/jira/browse/GPD-178
             Project: JBoss jBPM GPD
          Issue Type: Bug
          Components: jpdl
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
         Environment: Windows XP, Java 1.6.0_02, Eclipse 3.3, suite_3.2.2 (which packages GPD 3.1.0SP1)
            Reporter: Ian Priest
         Assigned To: Koen Aers


Get a ClassCastException using the Process Designer to open the gpd.xml in the websales example provided with the 3.2.2 suite download.

The exception is (full stack trace to follow)

java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement

The problem seems to lie in class GenericElementXmlAdapter, which deals with the classes though the SemanticElement interface, which both classes do implement. The following class reproduces the runtime issue and demonstrates the faulty cast:

import org.jbpm.gd.common.model.GenericElement;
import org.jbpm.gd.common.model.SemanticElement;
import org.jbpm.gd.jpdl.model.ProcessDefinition;


public class Play {

	public static void main(String[] args) {
		
		ProcessDefinition pd = new ProcessDefinition();
		SemanticElement se = (SemanticElement)pd;
		GenericElement ge = (GenericElement)se;
	}
}

which gives a runtime error:

Exception in thread "main" java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
at Play.main(Play.java:15) 

See also the forum discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121355

Full stack trace:

!ENTRY org.eclipse.ui 4 0 2007-10-16 11:12:33.685
!MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
!STACK 0
java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2719)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169) 




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 07:10:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 17 Oct 2007 07:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <1253999.1192619403518.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12382954 ] 
            
Tim Fox commented on JBMESSAGING-375:
-------------------------------------

One thought here.

Would it be possible to have this functionality working across a cluster too?

I.e. all messages sent using a particular value of JMSXGroupid go to the same consumer on the cluster?

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 07:43:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 17 Oct 2007 07:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1198)
 putForExternalRead not silent on remote node
In-Reply-To: <22737059.1192591803386.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3382337.1192621383454.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1198?page=all ]

Manik Surtani updated JBCACHE-1198:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA

> putForExternalRead not silent on remote node
> --------------------------------------------
>
>                 Key: JBCACHE-1198
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1198
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Seeing WARN logging like this when using PFER with a replicating cache:
> 22:16:37,931  WARN pessimistic-shared:2839 - replication failure with method_call MethodName: _putForExternalRead; MethodIdInteger: 45; Args: (null, /test/com/foo/test/ENTITY/KEY, item, VALUE1) exception
> org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/test/com/foo/test/ENTITY/KEY, caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock=write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299)
> 	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
> 	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3958)
> 	at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2826)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330)
> 	at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77)
> 	at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624)
> 	at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533)
> 	at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365)
> 	at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:744)
> 	at org.jgroups.JChannel.up(JChannel.java:1137)
> 	at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:999)
> 	at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1023)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.cache.lock.TimeoutException: write lock for /test/com/foo/test/ENTITY/KEY could not be acquired after 0 ms. Locks: Read lock owners: []
> Write lock owner: GlobalTransaction:<192.168.1.145:35562>:1
>  (caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock info: write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0))
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
> 	... 33 more
> Issue seems to be that the logic in CacheImpl.putForExternalRead that makes the call a no-op if the node exists and sets the failSilently option otherwise never gets executed on the remote node.  Instead the call gets handled by _replicate which just passes the MethodCall into the interceptor chain without setting any options.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:09:06 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Wed, 17 Oct 2007 08:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-178) ClassCastException
 using Process Designer 3.1.0SP1
In-Reply-To: <15484296.1192617783364.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11992738.1192622946938.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-178?page=comments#action_12382964 ] 
            
Koen Aers commented on GPD-178:
-------------------------------

I cannot reproduce this issue. The gpd.xml is not supposed to open with the graphical process designer. Only the processdefinition.xml should do this. Does this happen with clean downloads and empty workspaces?

Regards,
Koen

> ClassCastException using Process Designer 3.1.0SP1
> --------------------------------------------------
>
>                 Key: GPD-178
>                 URL: http://jira.jboss.com/jira/browse/GPD-178
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>         Environment: Windows XP, Java 1.6.0_02, Eclipse 3.3, suite_3.2.2 (which packages GPD 3.1.0SP1)
>            Reporter: Ian Priest
>         Assigned To: Koen Aers
>
> Get a ClassCastException using the Process Designer to open the gpd.xml in the websales example provided with the 3.2.2 suite download.
> The exception is (full stack trace to follow)
> java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> The problem seems to lie in class GenericElementXmlAdapter, which deals with the classes though the SemanticElement interface, which both classes do implement. The following class reproduces the runtime issue and demonstrates the faulty cast:
> import org.jbpm.gd.common.model.GenericElement;
> import org.jbpm.gd.common.model.SemanticElement;
> import org.jbpm.gd.jpdl.model.ProcessDefinition;
> public class Play {
> 	public static void main(String[] args) {
> 		
> 		ProcessDefinition pd = new ProcessDefinition();
> 		SemanticElement se = (SemanticElement)pd;
> 		GenericElement ge = (GenericElement)se;
> 	}
> }
> which gives a runtime error:
> Exception in thread "main" java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> at Play.main(Play.java:15) 
> See also the forum discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121355
> Full stack trace:
> !ENTRY org.eclipse.ui 4 0 2007-10-16 11:12:33.685
> !MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> !STACK 0
> java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
> at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
> at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
> at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
> at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299)
> at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179)
> at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400)
> at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
> at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
> at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604)
> at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
> at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
> at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
> at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
> at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
> at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774)
> at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673)
> at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2719)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
> at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
> at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
> at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
> at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1169) 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:34:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Wed, 17 Oct 2007 08:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28310807.1192624443745.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4754?page=all ]

Rajesh Rajasekaran resolved JBAS-4754.
--------------------------------------

    Resolution: Done

Did a full run and tck1.4 is now at 100% for 4.2.2.GA

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:39:04 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 17 Oct 2007 08:39:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19768221.1192624744098.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]

Galder Zamarreno updated JBAS-4805:
-----------------------------------

    Workaround Description: 
+ Workaround for injecting ConnectionFactory instances - Inject JmsXA instead of ConnectionFactory

   @Resource(mappedName="java:/JmsXA", type=javax.jms.ConnectionFactory.class) 
   private ConnectionFactory factory;

+ Workarounds for injecting Queue/Topic instances:

1.- Not to inject Queue and instead, assuming the queue name is "queue/A" use the
following code to initialise it the first time you use the Queue instance variable:

String bindAddress = System.getProperty("jboss.bind.address") == null ? "localhost" : System.getProperty("jboss.bind.address");
InitialContext ic = new InitialContext();
Queue queueA = (Queue)ic.lookup("jnp://" + bindAddress + ":1100/queue/A");

2.- For this second option, let's assume the queue name is "queue/B". In this case,
you can add META-INF/jboss.xml to your EJB jar deployment, which looks like this:

<?xml version="1.0"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>InhaltPruefungVerwaltungBean</ejb-name>
<resource-ref>
<res-ref-name>queue/ref/B</res-ref-name>
<jndi-name>jnp://${jboss.bind.address:localhost}:1100/queue/B</jndi-name>
</resource-ref>
</session>
</enterprise-beans>
</jboss>

And inject the Queue in your EJB this way:

@Resource(mappedName="java:comp/env/queue/ref/B")
private Queue queueB;

  was:
A possible workaround (that the customer is trying out at the moment is):

in deploy/cluster-service.xml:

<mbean code="org.jboss.ha.jndi.HANamingService"
name="jboss:service=HAJNDI">
...
<!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
<attribute name="BindAddress">localhost</attribute> 


Updated with workarounds from support case.

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:41:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 08:41:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18278504.1192624865934.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12382973 ] 
            
Dimitris Andreadis commented on JBAS-4754:
------------------------------------------

Excellent! I'll do a final pass over the release notes and tag after that.

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 08:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4852) EJB3 web service
 endpoints ignore metadata in jboss.xml
In-Reply-To: <16146379.1192175643414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6357857.1192625823738.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4852?page=all ]

Dimitris Andreadis updated JBAS-4852:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

To the next release.

> EJB3 web service endpoints ignore metadata in jboss.xml
> -------------------------------------------------------
>
>                 Key: JBAS-4852
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4852
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For: JBossAS-4.2.3.GA
>
>
> This is related to JBWS-1813
> It needs to be decided whether jboss-4.2.2 can go out despite this issue.
> Currently, users are forced to use annotations on the bean.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:59:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4696) Arrange community
 documents for 4.2.2.GA
In-Reply-To: <25461197.1189416611004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23889102.1192625943859.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4696?page=all ]

Dimitris Andreadis updated JBAS-4696:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.2.2.GA)

I'm just unscheduling this issue, because it will continue after the release.

I'm about to tag the release today.

> Arrange community documents for 4.2.2.GA
> ----------------------------------------
>
>                 Key: JBAS-4696
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4696
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Michael Smith
>            Priority: Blocker
>
> We *must* produce community documents for AS.
> At the moment, the only 4.2.x documentation that exists is the EAP one.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 09:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9559732.1192626063672.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382978 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

I'm about to tag, so this needs closing, or if work is on-going move to the next release.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:19:06 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Wed, 17 Oct 2007 09:19:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10266724.1192627146489.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382992 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

The juddi-service.sar is already deployed in the 'all' config. This is just some classpath issue and we can move on with the release.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:41:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 17 Oct 2007 09:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
Message-ID: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>

Redelivery flags not updated in case of JBossMQ node failure
------------------------------------------------------------

                 Key: JBAS-4870
                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JMS service
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Adrian Brock
         Assigned To: Adrian Brock
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA


When the JBossMQ node fails with messages currently being delivered to the clients,
the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).

The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
(which it won't do if it has crashed).

A potential fix, is to update the status early before delivering the message to the client,
see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:47:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 09:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16879252.1192628823672.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis updated JBAS-4811:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 10:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 10:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4591) Create a generic way
 to createDestinations on MDB Container
In-Reply-To: <32782847.1186095349327.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8808884.1192629663303.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4591?page=all ]

Dimitris Andreadis updated JBAS-4591:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.4.0.CR1)

Unscheduling, as 4.4.0.CR1 version has been archived.

> Create a generic way to createDestinations on MDB Container
> -----------------------------------------------------------
>
>                 Key: JBAS-4591
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4591
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>
> We should provide a generic way to configure the MDB container to create destinations in other providers besidess JBossMQ.
> The Implementation I'm going to do will use a Property Name for the MBean responsible to create destinations and method names for the create methods.
> Also... we will support two signatures... one (createTopic(String Topicname) or createQueue(String queueName))
> or
> createTopic(String TopicName, String jndti) or createQueue(String queueName, String jndi)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:16:24 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 11:16:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1281) ExecutorService
 cannot be shared
Message-ID: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>

ExecutorService cannot be shared
--------------------------------

                 Key: JBRULES-1281
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2, 4.0.1
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0


Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:30:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 11:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1281) ExecutorService
 cannot be shared
In-Reply-To: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32779624.1192635003468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1281?page=all ]

Mark Proctor updated JBRULES-1281:
----------------------------------

    Attachment: UnshareExecutorService.patch

> ExecutorService cannot be shared
> --------------------------------
>
>                 Key: JBRULES-1281
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>         Attachments: UnshareExecutorService.patch
>
>
> Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:32:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 11:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1281) ExecutorService
 cannot be shared
In-Reply-To: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23642386.1192635123600.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1281?page=comments#action_12383049 ] 
            
Mark Proctor commented on JBRULES-1281:
---------------------------------------

commit to trunk:
commit -m "JBRULES-1281 ExecutorService cannot be shared
-Added cached reflection class resolve and object instantiator to ClassUtil.
-Made RuleBaseUpdateListenerFactory and ExecutorServiceFactory use ClassUtil.
-Now each new stateful or stateless session get's its own instance of ExecutorService." C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooRuleBase.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatefulSession.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatelessSession.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/RuleBaseConfiguration.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/ExecutorServiceFactory.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/RuleBaseUpdateListenerFactory.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/util/ClassUtils.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/RuleBaseConfiguration.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooRuleBase.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatefulSession.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatelessSession.java
    Adding         dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/ExecutorServiceFactory.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/RuleBaseUpdateListenerFactory.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/util/ClassUtils.java
    Transmitting file data ...
    Committed revision 15887.


> ExecutorService cannot be shared
> --------------------------------
>
>                 Key: JBRULES-1281
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>         Attachments: UnshareExecutorService.patch
>
>
> Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:40:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 11:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1199) Update
 InvalidatorInterceptorTest to use Node.isValid()
Message-ID: <2782171.1192635603222.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update InvalidatorInterceptorTest to use Node.isValid()
-------------------------------------------------------

                 Key: JBCACHE-1199
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For: 2.1.0.GA


InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node.  See the forum link.  Need to replace with a call to isValid() whenever that is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:48:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 11:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-130) Problems with
	reincarnation
Message-ID: <23412040.1192636084470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-130?page=all ]

Bela Ban updated JGRP-130:
--------------------------

    Fix Version/s: 2.5.2

Needs to be backported to 2.5.2

> Problems with reincarnation
> ---------------------------
>
>                 Key: JGRP-130
>                 URL: http://jira.jboss.com/jira/browse/JGRP-130
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6, 2.5.2
>
>         Attachments: tcp.xml
>
>
> Problems with reincarnation
> ===========================
> Author: Bela Ban
> Version: $Id$
> The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
> bind_port is set (not set by default).
> Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a
> higher port, say 5002. This depends on how many other processes requested a port in between the start and restart
> of the member.
> JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically)
> *increasing* across a single machine. If this is not the case, then the following problems can occur:
> 1. Restart:
> When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded,
> then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table),
> retransmission requests sent to the new P will fail.
> 2. Shunning:
> Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of
> those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have
> processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time,
> when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so
> they could assume each other's identity !
> Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a
> new process and in case #2, the list is process-wide, but not machine-wide.
> Again, these problems occur *only* when the OS reuses previously assigned ports.
> SOLUTION:
> A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we
> don't reuse previous addresses
> B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host.
> Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity.
> The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:48:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 11:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JGRP-130) Problems with
	reincarnation
Message-ID: <3012786.1192636084921.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-130?page=all ]

Bela Ban reopened JGRP-130:
---------------------------

             

> Problems with reincarnation
> ---------------------------
>
>                 Key: JGRP-130
>                 URL: http://jira.jboss.com/jira/browse/JGRP-130
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6, 2.5.2
>
>         Attachments: tcp.xml
>
>
> Problems with reincarnation
> ===========================
> Author: Bela Ban
> Version: $Id$
> The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
> bind_port is set (not set by default).
> Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a
> higher port, say 5002. This depends on how many other processes requested a port in between the start and restart
> of the member.
> JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically)
> *increasing* across a single machine. If this is not the case, then the following problems can occur:
> 1. Restart:
> When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded,
> then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table),
> retransmission requests sent to the new P will fail.
> 2. Shunning:
> Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of
> those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have
> processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time,
> when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so
> they could assume each other's identity !
> Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a
> new process and in case #2, the list is process-wide, but not machine-wide.
> Again, these problems occur *only* when the OS reuses previously assigned ports.
> SOLUTION:
> A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we
> don't reuse previous addresses
> B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host.
> Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity.
> The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:57:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 17 Oct 2007 11:57:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1121) Investigate the
 suitability of not copying child maps into workspace
In-Reply-To: <14759070.1183724948890.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30242184.1192636624706.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1121?page=all ]

Manik Surtani resolved JBCACHE-1121.
------------------------------------

    Resolution: Done

> Investigate the suitability of not copying child maps into workspace
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1121
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1121
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Optimistic Locking
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:07:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Wed, 17 Oct 2007 12:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Moved: (GPD-179) pages.xml doesn't work
 with pageflow editor
Message-ID: <6550650.1192637223887.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-179?page=all ]

Koen Aers moved JBIDE-642 to GPD-179:
-------------------------------------

              Project: JBoss jBPM GPD  (was: JBoss Tools)
                  Key: GPD-179  (was: JBIDE-642)
          Component/s: jpdl
                           (was: jbpm)
        Fix Version/s: jBPM jPDL Designer 3.1.1
                           (was: 2.0.1)
    Affects Version/s:     (was: 2.0.0.Beta3)
                           (was: 2.0.0.CR1)

> pages.xml doesn't work with pageflow editor
> -------------------------------------------
>
>                 Key: GPD-179
>                 URL: http://jira.jboss.com/jira/browse/GPD-179
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Max Andersen
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu.
> and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get 
> java.lang.NullPointerException
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> 	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:09:04 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Wed, 17 Oct 2007 12:09:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-179) pages.xml doesn't
 work with pageflow editor
Message-ID: <14500344.1192637344264.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-179?page=comments#action_12383077 ] 
            
Max Andersen commented on GPD-179:
----------------------------------

koen - please don't *move* the bugs because then we can't see them as outstanding issues for JBossTools/RHDS. Link to it instead please.

> pages.xml doesn't work with pageflow editor
> -------------------------------------------
>
>                 Key: GPD-179
>                 URL: http://jira.jboss.com/jira/browse/GPD-179
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Max Andersen
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu.
> and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get 
> java.lang.NullPointerException
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> 	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:32:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 12:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1200) Node removal with
 invalidation leaves child data accessible
Message-ID: <4642624.1192638724532.JavaMail.jira@cloud.prod.atl2.jboss.com>

Node removal with invalidation leaves child data accessible
-----------------------------------------------------------

                 Key: JBCACHE-1200
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1200
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
            Priority: Critical
             Fix For: 2.1.0.CR1


With invalidation, when a node that has children is removed, on remote caches the data in the children is still visible; e..g

cache1.put(childFqn, key, value);
cache1.removeNode(parentFqn);
// This assertion fails
assertNull(cache2.get(childFqn, key));

InvalidationInterceptorTest.testPessimisticNodeRemoval() and testOptimisticNodeRemoval() have been modified to show this issue.

This is a significant problem for the Hibernate/JBC integration

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:34:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 12:34:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-130) Problems with
	reincarnation
Message-ID: <32278397.1192638844330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-130?page=all ]

Bela Ban resolved JGRP-130.
---------------------------

    Resolution: Done

backported to 2.5.2

> Problems with reincarnation
> ---------------------------
>
>                 Key: JGRP-130
>                 URL: http://jira.jboss.com/jira/browse/JGRP-130
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.5.2, 2.6
>
>         Attachments: tcp.xml
>
>
> Problems with reincarnation
> ===========================
> Author: Bela Ban
> Version: $Id$
> The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
> bind_port is set (not set by default).
> Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a
> higher port, say 5002. This depends on how many other processes requested a port in between the start and restart
> of the member.
> JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically)
> *increasing* across a single machine. If this is not the case, then the following problems can occur:
> 1. Restart:
> When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded,
> then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table),
> retransmission requests sent to the new P will fail.
> 2. Shunning:
> Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of
> those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have
> processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time,
> when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so
> they could assume each other's identity !
> Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a
> new process and in case #2, the list is process-wide, but not machine-wide.
> Again, these problems occur *only* when the OS reuses previously assigned ports.
> SOLUTION:
> A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we
> don't reuse previous addresses
> B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host.
> Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity.
> The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:40:06 2007
From: jira-events at lists.jboss.org (Gunnar Grim (JIRA))
Date: Wed, 17 Oct 2007 12:40:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1074) Circular @EJB3
 references in session beans fail to deploy.
Message-ID: <7270653.1192639206697.JavaMail.jira@cloud.prod.atl2.jboss.com>

Circular @EJB3 references in session beans fail to deploy.
----------------------------------------------------------

                 Key: EJBTHREE-1074
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.1.GA
            Reporter: Gunnar Grim


The following circular references makes the application undeployable:

In ArchiveBrokerBean:

  @EJB 
  private SeriesBrokerLocal itsSeriesBroker;	

In SeriesBrokerBean

  @EJB 
  private ArchiveBrokerLocal itsArchiveBroker;	

Circular references like these work fine in Glassfish but JBoss shows the following error message:

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
  Depends On Me:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
  Depends On Me:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU



-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 12:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11399830.1192639683658.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

    Attachment: Dumper.patch

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 12:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10920215.1192639683964.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

        Fix Version/s: 4.0.2_SOA_4.2-CP1
                       4.0.3
                       4.1.0
                           (was: 4.0.2)
    Affects Version/s: 4.0.2

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:50:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 12:50:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22371207.1192639805158.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=comments#action_12383112 ] 
            
Mark Proctor commented on JBRULES-1252:
---------------------------------------

commit -m "JBRULES-1252 DrlDumper does not dump functions
-Fixed function dumper issues
-added tests for various other globals, imports etc.
-updated to add quotes to other attributes like date-effective." C:/dev/jbossrules/4.1.0/drools-compiler/src/main/java/org/drools/lang/DrlDumper.java C:/dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTest.java C:/dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTestHelper.java C:/dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.drl C:/dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.xml
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/main/java/org/drools/lang/DrlDumper.java
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTest.java
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTestHelper.java
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.drl
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.xml
    Transmitting file data ...
    Committed revision 15895.

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 13:28:14 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Wed, 17 Oct 2007 13:28:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-821) JBoss Remoting fails
	under load
Message-ID: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Remoting fails under load
-------------------------------

                 Key: JBREM-821
                 URL: http://jira.jboss.com/jira/browse/JBREM-821
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP1
            Reporter: Ovidiu Feodorov
         Assigned To: Trustin Lee
            Priority: Blocker


This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.

Phrasing belongs to Tim:

JBoss Remoting fails with various different errors when under extreme load.

To replicate this, set up two clustered server nodes, using a MySQL database.

These can both be on the same machine, using ServiceBindingManager.

On a second machine run Ovidiu's messkit toolki, first to send some messages:

mess -stat send -size 10240 50000

And then to receive them back using 50 concurrent consumers:

mess -stat -sessions 50 receive all

You will notice that JBoss Remoting fails with errors:

I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?

I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.

It also seems remoting is continually timing out and recreating connections - this could also be a source of error.

How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:15:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 17 Oct 2007 14:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBSER-97)
 RegularObjectPersister.readSlotWithFields to log number of fields being
 read
In-Reply-To: <32246194.1192448283370.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17856604.1192644903591.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBSER-97?page=all ]

Galder Zamarreno reassigned JBSER-97:
-------------------------------------

    Assignee: Galder Zamarreno  (was: Clebert Suconic)

> RegularObjectPersister.readSlotWithFields to log number of fields being read
> ----------------------------------------------------------------------------
>
>                 Key: JBSER-97
>                 URL: http://jira.jboss.com/jira/browse/JBSER-97
>             Project: JBoss Serialization
>          Issue Type: Task
>    Affects Versions: 1.0.3 GA
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>
> writeSlotWithFields logs the slot name and number of fields to be written.
> for debugging pupouses, readSlotWithFields could do with logging the number of fields written too, i.e.
> RegularObjectPersister.readSlotWithFields() to start like this:
>      short numberOfFields = (short)fieldsKey.length;
>       if (isDebug)
>       {
>          log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName() + " and " + numberOfFields + " fields");
>       }
> instead of:
>        if (isDebug)
>        {
>           log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName());
>        }
>        //final int numberOfFields = input.readShort();
>       short numberOfFields = (short)fieldsKey.length;

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:22:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 17 Oct 2007 14:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBSER-98) Write slot with
 fields only if both readObject and writeObject are missing
In-Reply-To: <1789794.1192530433263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16139517.1192645323336.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBSER-98?page=all ]

Galder Zamarreno reassigned JBSER-98:
-------------------------------------

    Assignee: Galder Zamarreno  (was: Clebert Suconic)

> Write slot with fields only if both readObject and writeObject are missing
> --------------------------------------------------------------------------
>
>                 Key: JBSER-98
>                 URL: http://jira.jboss.com/jira/browse/JBSER-98
>             Project: JBoss Serialization
>          Issue Type: Feature Request
>    Affects Versions: 1.0.3 GA
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>
> Over the last few weeks, I've been dealing with a funky support case which showed the following 
> stacktrace:
> ...
> Caused by: org.jboss.serial.exception.SerializationException: Excepted to be String
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1120)
> at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:71)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
> at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
> at org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
> at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
> at org.jboss.serial.io.MarshalledObjectForLocalCalls.get(MarshalledObjectForLocalCalls.java:60)
> at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> ... 28 more
> Caused by: java.lang.ClassCastException: org.jboss.serial.finalcontainers.IntegerContainer
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1116)
> ... 42 more 
> The cause of the issue was that the customer had a class where it had re-implemented 
> readObject(java.io.ObjectInputStream stream) but had not re-implemented 
> writeObject(java.io.ObjectOutputStream stream). This is obviously a programming error on their side,
> but it took a while to detect such stupid mistake.
> The problem within JBoss Serialization was that because this class didn't have a writeObject() 
> reimplementation, it was a writing the class as a slot with fields, but when it came to reading it, it 
> was reading the class as a slot with method because readObject had been reimplemented. The 
> next time a slot with fields was read, the fields were mixed up.
> To avoid these type of situations, I'd suggest that:
> - JBS only writes as fields if *both* writeObject and readObject are missing. Right now, can't see a 
> situation where you'd implement one and not the other, thoughts?

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:55:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 14:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
Message-ID: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>

OPTIMISTIC locking requires SyncCommitPhase to be true
------------------------------------------------------

                 Key: JBCACHE-1201
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Replication
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
             Fix For: 2.1.0.BETA1


When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:

tm.begin();
cache1.put(fqn, KEY, VALUE1);
tm.commit();
      
assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));

With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.

A simple sleep after the commit call will also make this test pass

My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.

The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.

Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:57:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 14:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17604160.1192647423382.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=comments#action_12383122 ] 
            
Brian Stansberry commented on JBCACHE-1201:
-------------------------------------------

This appears to not be an issue with INVALIDATION, although I'm not 100% certain of that.

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.BETA1
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:05:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1252) DrlDumper does not
 dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29337642.1192647904086.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor closed JBRULES-1252.
---------------------------------

    Resolution: Done

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:05:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1281) ExecutorService
 cannot be shared
In-Reply-To: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3979950.1192647904251.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1281?page=all ]

Mark Proctor closed JBRULES-1281.
---------------------------------

    Resolution: Done

> ExecutorService cannot be shared
> --------------------------------
>
>                 Key: JBRULES-1281
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: UnshareExecutorService.patch
>
>
> Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:07:08 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:07:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1277) BRDRLPersitence is
 not rendering OR's correctly
In-Reply-To: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7569022.1192648028851.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1277?page=all ]

Mark Proctor closed JBRULES-1277.
---------------------------------

    Resolution: Done

> BRDRLPersitence is not rendering OR's correctly
> -----------------------------------------------
>
>                 Key: JBRULES-1277
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2-CP1
>
>         Attachments: BRDRLPersistence.java, BRDRLPersistence.old
>
>
> Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:12:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1272) DSL : String index
 out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24800588.1192648323327.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Mark Proctor closed JBRULES-1272.
---------------------------------


> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.0.3, 4.1.0, FUTURE, 4.0.2_SOA_4.2-CP1
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:12:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:12:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10973978.1192648324200.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Mark Proctor closed JBRULES-1279.
---------------------------------


> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 16:30:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 16:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-605) Dynamically adjust
 min_threads in thread pools
Message-ID: <14206383.1192653003274.JavaMail.jira@cloud.prod.atl2.jboss.com>

Dynamically adjust min_threads in thread pools
----------------------------------------------

                 Key: JGRP-605
                 URL: http://jira.jboss.com/jira/browse/JGRP-605
             Project: JGroups
          Issue Type: Feature Request
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.7


This should be a function of 
- number of nodes
- number of CPUs
, as described in JCIP

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 16:41:03 2007
From: jira-events at lists.jboss.org (Diego Belfer (JIRA))
Date: Wed, 17 Oct 2007 16:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4871) TransactionIsolation
 is not reset when Connection is returned to the pool
Message-ID: <33190829.1192653663634.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionIsolation is not reset when Connection is returned to the pool
-------------------------------------------------------------------------

                 Key: JBAS-4871
                 URL: http://jira.jboss.com/jira/browse/JBAS-4871
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.0.5.GA
            Reporter: Diego Belfer


TransactionIsolation is not being reset when the JDBC connection is returned to the pool. Bug is indicated in the code. 
This was also reported in http://jira.jboss.com/jira/browse/JBAS-1123 and marked as closed but the bug is still there.

   public void cleanup() throws ResourceException
   {
      synchronized (handles)
      {
         for (Iterator i = handles.iterator(); i.hasNext(); )
         {
            WrappedConnection lc = (WrappedConnection)i.next();
            lc.setManagedConnection(null);
         }
         handles.clear();
      }
      //reset all the properties we know about to defaults.
      synchronized (stateLock)
      {
         jdbcAutoCommit = true;
         jdbcReadOnly = readOnly;
         if (jdbcTransactionIsolation != transactionIsolation)
         {
            try
            {
               con.setTransactionIsolation(jdbcTransactionIsolation); <-- BUG: It should be con.setTransactionIsolation(transactionIsolation);
               jdbcTransactionIsolation = transactionIsolation;
            }
            catch (SQLException e)
            {
               mcf.log.warn("Error resetting transaction isolation ", e);
            }
         }
      }
   }


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 16:52:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 16:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
Message-ID: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>

State transfer does not include optimistic node's DataVersion
-------------------------------------------------------------

                 Key: JBCACHE-1202
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani


Here's the object that's transferred; doesn't include the DataVersion

public class NodeData implements Externalizable
{
   private Fqn<?> fqn = null;
   private Map<?, ?> attrs = null;
}

A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 17:35:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 17 Oct 2007 17:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
Message-ID: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure Session Beans with Incomplete 2.1 View Fail Deployment
-------------------------------------------------------------

                 Key: EJBTHREE-1075
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 17:44:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 17:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19933662.1192657443787.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Brian Stansberry updated JBCACHE-1201:
--------------------------------------

        Fix Version/s:     (was: 2.1.0.BETA1)
    Affects Version/s: 2.1.0.BETA1

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 17:57:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 17:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-606) Use same properties
 for start_port/bind_port and end_port/port_range
Message-ID: <33207067.1192658223238.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use same properties for start_port/bind_port and end_port/port_range
--------------------------------------------------------------------

                 Key: JGRP-606
                 URL: http://jira.jboss.com/jira/browse/JGRP-606
             Project: JGroups
          Issue Type: Task
            Reporter: Bela Ban
         Assigned To: Bela Ban
            Priority: Minor
             Fix For: 2.7


In UDP, we use bind_port and port_range to define a range of valid ports.
In TCP, we use start_port and end_port

We should use
- bind_port (rather than start_port) to define the port to bind to
- end_port to define the range



-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 18:49:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Wed, 17 Oct 2007 18:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1758)
 PortletManagerBean$Comparator is not robust enough
Message-ID: <24053748.1192661343193.JavaMail.jira@cloud.prod.atl2.jboss.com>

PortletManagerBean$Comparator is not robust enough
--------------------------------------------------

                 Key: JBPORTAL-1758
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1758
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
    Affects Versions: 2.6.2 Final
            Reporter: Chris Laprun
         Assigned To: Chris Laprun
            Priority: Critical
             Fix For: 2.6.3 Final


In particular in a portlet doesn't have a display name then the comparator crashes.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 19:25:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Wed, 17 Oct 2007 19:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13974271.1192663503461.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383149 ] 
            
Ronald van Kuijk commented on JBPM-1071:
----------------------------------------

what exceptions were thrown? and what action was not performed? There has been lots of discussion on simultaneous access to node, actions and database. Can you please check  the JBPM-993 and JBPM-995 (and related) if that contains some more info?

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 20:08:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 20:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
Message-ID: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>

Problems uploading models etc. into the BRMS
--------------------------------------------

                 Key: JBRULES-1282
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.0.3, 4.1.0


There are 2 problems (this shows up mainly in WebKIT and safary browsers): 

1) the return content type for a successfull upload is text/plain when it should be test/html
2) if any form fields are not visible, they will not be submitted to the server. 


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 20:11:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 20:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3172314.1192666263518.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383152 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

Notify soa-p at redhat.com of change



> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 20:11:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 20:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25068376.1192666263671.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Michael Neale updated JBRULES-1282:
-----------------------------------

    Fix Version/s: 4.0.2_SOA_4.2-CP1
                   4.0.2_SOA.4.2-CP2

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 17 Oct 2007 21:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-822) Avoid deadlock when
 Connector
 shuts down while callback client invoker is in handleConnect()
Message-ID: <21914029.1192669983283.JavaMail.jira@cloud.prod.atl2.jboss.com>

Avoid deadlock when Connector shuts down while callback client invoker is in handleConnect()
--------------------------------------------------------------------------------------------

                 Key: JBREM-822
                 URL: http://jira.jboss.com/jira/browse/JBREM-822
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.4.0.Beta1 (Pinto)


Clebert Suconic has experienced a deadlock while shutting down the Application Server.  

The thread dump shows that the AS has called Connector.stop(), which leads to a call to the synchronized method org.jboss.remoting.MicroRemoteClientInvoker.disconnect() on the callback org.jboss.remoting.transport.bisocket.BisocketClientInvoker.  However, all this happens at the same time that a callback handler is being installed, which leads to a call to the synchronized method MicroRemoteClientInvoker.connect() on *the same* callback BisocketClientInvoker.  The BisocketClientInvoker is in BisocketClientInvoker.handleConnect(), where it is waiting (with, in the case of JBossMessaging, a timeout of 0) to get a control socket.  As a result, MicroRemoteClientInvoker.disconnect() is blocked and cannot execute.

This situation needs careful study.  Do MicroRemoteClientInvoker.connect() and MicroRemoteClientInvoker.disconnect() need to be fully synchronized?



-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:15:03 2007
From: jira-events at lists.jboss.org (Jonathan Duty (JIRA))
Date: Wed, 17 Oct 2007 21:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24690310.1192670103331.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=comments#action_12383153 ] 
            
Jonathan Duty commented on EJBTHREE-1031:
-----------------------------------------

As a production user of both ejb3 and jboss 4.2.1 can someone explain this issue?  Should this bug mean that 4.2.1 shouldn't be used in production or we may create SLSB out of control???

Thanks,
~Jonathan


> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:15:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 17 Oct 2007 21:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-822) Avoid deadlock when
 Connector
 shuts down while callback client invoker is in handleConnect()
In-Reply-To: <21914029.1192669983283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13290170.1192670103486.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-822?page=all ]

Ron Sigal updated JBREM-822:
----------------------------

    Attachment: connect_disconnect_deadlock_thread_dump

Attached file with thread dump.

> Avoid deadlock when Connector shuts down while callback client invoker is in handleConnect()
> --------------------------------------------------------------------------------------------
>
>                 Key: JBREM-822
>                 URL: http://jira.jboss.com/jira/browse/JBREM-822
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: connect_disconnect_deadlock_thread_dump
>
>
> Clebert Suconic has experienced a deadlock while shutting down the Application Server.  
> The thread dump shows that the AS has called Connector.stop(), which leads to a call to the synchronized method org.jboss.remoting.MicroRemoteClientInvoker.disconnect() on the callback org.jboss.remoting.transport.bisocket.BisocketClientInvoker.  However, all this happens at the same time that a callback handler is being installed, which leads to a call to the synchronized method MicroRemoteClientInvoker.connect() on *the same* callback BisocketClientInvoker.  The BisocketClientInvoker is in BisocketClientInvoker.handleConnect(), where it is waiting (with, in the case of JBossMessaging, a timeout of 0) to get a control socket.  As a result, MicroRemoteClientInvoker.disconnect() is blocked and cannot execute.
> This situation needs careful study.  Do MicroRemoteClientInvoker.connect() and MicroRemoteClientInvoker.disconnect() need to be fully synchronized?

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:42:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 17 Oct 2007 21:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27682190.1192671723473.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=comments#action_12383156 ] 
            
William DeCoste commented on EJBTHREE-1031:
-------------------------------------------

Under some loads, SLSB instances are not always removed, so there is a potential memory leak in 4.2.1. 4.2.2 is coming out shortly and has this issue resolved.

> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 23:12:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 23:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28690901.1192677123281.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383159 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

OMGWTFBBQ: there is also http://code.google.com/p/google-web-toolkit/issues/detail?id=1585

DAMN YOU! 3 bugs (one in my code, one safari quirk, and one on GWT) all conspire to make my week hell. I need a drink.

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 23:18:03 2007
From: jira-events at lists.jboss.org (Jonathan Duty (JIRA))
Date: Wed, 17 Oct 2007 23:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30669531.1192677483362.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=comments#action_12383160 ] 
            
Jonathan Duty commented on EJBTHREE-1031:
-----------------------------------------

Does this  typically with high or low loads?  We just want to know what to look for.

> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 00:19:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 18 Oct 2007 00:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22068422.1192681143234.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383161 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

http://www.webmasterworld.com/macintosh_webmaster/3300569.htm

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:21:14 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 02:21:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25268038.1192688474760.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383167 ] 
            
Jiri Pechanec commented on JBPM-1071:
-------------------------------------

Hi,
the exception throws is
org.jbpm.JbpmException: couldn't execute org.jbpm.command.SignalCommand at 715c2843
	at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73)
	at org.jpbm.exploratory.Signalist.run(Signalist.java:30)
Caused by: org.jbpm.JbpmException: couldn't signal token 'Token(/)' : node 'EndState(end-state1)' doesn't have a default transition
	at org.jbpm.graph.exe.Token.signal(Token.java:138)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
	at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$9af9b4e6.signal(<generated>)
	at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91)
	at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:71)
	... 1 more

Which means that other threads are isgnalling process when it is in the end state.
But this is not a problem I am trying to point out.
The problem is that the same node is executed 4 times from different threads and all changes made are successfully comitted.
IMHO the correct semantics is that only one thread executes each action (each node). The rest of threads will either throw something like concurrent access exception or will be used to signal in the next wait states.
According to content of the exception I can pretty accurately suppose that
4 threads executed Action 2, commited
3 threads executed transition to end state, probably committed
13 threads failed as there is no next transition
What I suppose is to have
1 thread executed Action 2, commited
3 thread executed Action 2, fail and rollback
1 thread executed transition to end state,  committed
2 threads executed transition to end state,  fail and rollback
13 threads failed as there is no next transition
or
1 thread executed Action 2, commited
1 thread executed transition to end state,  committed
18 threads failed as there is no next transition




> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:35:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 02:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4872) Invalid URI if the
 jboss.bind.address is IPv6
Message-ID: <37566.1192689303570.JavaMail.jira@cloud.prod.atl2.jboss.com>

Invalid URI if the jboss.bind.address is IPv6
---------------------------------------------

                 Key: JBAS-4872
                 URL: http://jira.jboss.com/jira/browse/JBAS-4872
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Remoting
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Takayoshi Kimura
         Assigned To: Ron Sigal


JBossRemoting uses jboss.bind.address in URI like the following:
socket://${jboss.bind.address}:4446/?datatype=invocation

However, if the jboss.bind.address is IPv6, it should be inside
of square brackets.

Invalid URI
socket://::1:4446/?datatype=invocation

Valid URI
socket://[::1]:4446/?datatype=invocation

To reproduce this issue:

Run JBoss instance by the following commend on IPv6 enabled system.
$ ./run.sh -c default -b ::1

Workaround:
Edit JBossRemoting URL not to use jboss.bind.address.

Note:
IPv6 address cannot be parsed with JBossRemoting 2.2.1.GA bundled in 4.2.1.GA. IPv6 parsing needs updated version of JBossRemoting.
http://jira.jboss.com/jira/browse/JBREM-645

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:45:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 02:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-823)
 ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value
 is IPv6
Message-ID: <9184117.1192689903468.JavaMail.jira@cloud.prod.atl2.jboss.com>

ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6
-----------------------------------------------------------------------------------

                 Key: JBREM-823
                 URL: http://jira.jboss.com/jira/browse/JBREM-823
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.0.0.Alpha1 (Otter)
            Reporter: Takayoshi Kimura
         Assigned To: Trustin Lee


IPv6 address contains ":" character, so it cannot be used in ObjectName.

2007-10-18 15:37:40,476 WARN  [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer.
javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
	at javax.management.ObjectName.construct(ObjectName.java:529)
	at javax.management.ObjectName.<init>(ObjectName.java:1304)
	at org.jboss.remoting.transport.Connector.init(Connector.java:402)
	at org.jboss.remoting.transport.Connector.create(Connector.java:760)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
	at $Proxy0.create(Unknown Source)
	at org.jboss.system.ServiceController.create(ServiceController.java:330)
	at org.jboss.system.ServiceController.create(ServiceController.java:273)
	at org.jboss.system.ServiceController.create(ServiceController.java:349)
	at org.jboss.system.ServiceController.create(ServiceController.java:273)
	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.create(Unknown Source)
	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy5.deploy(Unknown Source)
	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
	at org.jboss.Main.boot(Main.java:200)
	at org.jboss.Main$1.run(Main.java:508)
	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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:45:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 18 Oct 2007 02:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27825363.1192689903616.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383168 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

FOR THE SOA-P TEAM: OK, fix is in both trunk and 4.0.x.

The changes are from revision 15901 to 15906 on the 4.0.x branch. 

To get a cumulative patch (or svn merge):
svn diff -r 15901:15906 https://svn.labs.jboss.org/labs/jbossrules/branches/4.0.x/  > cumulative_patch.patch

etc.

-------
DETAILS OF FIX:
Was a problem effecting some browsers (notably webkit or khtml related ones) from 3 unrelated bugs all conspiring to make my life a living hell.
Meant it was not always possible to upload to the BRMS.
Now it should be fine on all (known) browsers.

This fix is not critical, without it, it will still work with Firefox (version 2) at least, and IE. 

-------

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:47:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 18 Oct 2007 02:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31663275.1192690023511.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Michael Neale updated JBRULES-1282:
-----------------------------------

    Attachment: cumulative_patch.patch

Here is a cumulative patch (its a bit big as the UI was changed).

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>         Attachments: cumulative_patch.patch
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 03:01:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 03:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4872) Invalid URI if the
 jboss.bind.address is IPv6
In-Reply-To: <37566.1192689303570.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6508105.1192690863316.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4872?page=comments#action_12383170 ] 
            
Takayoshi Kimura commented on JBAS-4872:
----------------------------------------

Another workaround:

Use-b [::1] instead of -b ::1. Somehow it works.

$ ./run.sh -b \[::1\]

> Invalid URI if the jboss.bind.address is IPv6
> ---------------------------------------------
>
>                 Key: JBAS-4872
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4872
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Takayoshi Kimura
>         Assigned To: Ron Sigal
>
> JBossRemoting uses jboss.bind.address in URI like the following:
> socket://${jboss.bind.address}:4446/?datatype=invocation
> However, if the jboss.bind.address is IPv6, it should be inside
> of square brackets.
> Invalid URI
> socket://::1:4446/?datatype=invocation
> Valid URI
> socket://[::1]:4446/?datatype=invocation
> To reproduce this issue:
> Run JBoss instance by the following commend on IPv6 enabled system.
> $ ./run.sh -c default -b ::1
> Workaround:
> Edit JBossRemoting URL not to use jboss.bind.address.
> Note:
> IPv6 address cannot be parsed with JBossRemoting 2.2.1.GA bundled in 4.2.1.GA. IPv6 parsing needs updated version of JBossRemoting.
> http://jira.jboss.com/jira/browse/JBREM-645

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 03:06:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 03:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-823)
 ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value
 is IPv6
In-Reply-To: <9184117.1192689903468.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17523669.1192691163409.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-823?page=all ]

Takayoshi Kimura updated JBREM-823:
-----------------------------------

    Attachment: JBREM-823.patch

Patch attached: Encode address during construct ObjectName.

> ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6
> -----------------------------------------------------------------------------------
>
>                 Key: JBREM-823
>                 URL: http://jira.jboss.com/jira/browse/JBREM-823
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.Alpha1 (Otter)
>            Reporter: Takayoshi Kimura
>         Assigned To: Trustin Lee
>         Attachments: JBREM-823.patch
>
>
> IPv6 address contains ":" character, so it cannot be used in ObjectName.
> 2007-10-18 15:37:40,476 WARN  [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer.
> javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
> 	at javax.management.ObjectName.construct(ObjectName.java:529)
> 	at javax.management.ObjectName.<init>(ObjectName.java:1304)
> 	at org.jboss.remoting.transport.Connector.init(Connector.java:402)
> 	at org.jboss.remoting.transport.Connector.create(Connector.java:760)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:349)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy4.create(Unknown Source)
> 	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy5.deploy(Unknown Source)
> 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
> 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
> 	at org.jboss.Main.boot(Main.java:200)
> 	at org.jboss.Main$1.run(Main.java:508)
> 	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

        


From jira-events at lists.jboss.org  Thu Oct 18 03:52:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 18 Oct 2007 03:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20994848.1192693923475.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383177 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

Well, we should see a successful testrun before we can release.
If you don't want to deploy the juddi-service.sar to default, you can also run the tests against all.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 04:53:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 18 Oct 2007 04:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1114) JBoss
 Remoting fails under load
In-Reply-To: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27627477.1192697583331.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=comments#action_12383187 ] 
            
Tim Fox commented on JBMESSAGING-1114:
--------------------------------------

I found out why this is happening (why the callback handler can't be found).   :

1. An invocation fails because remoting timed out waiting for a TCP connection to be returned to the pool. (Pool size to small).
2. In this case remoting throws a java.net.SocketException:

throw new SocketException("Can not obtain client socket connection from pool. " +
           "Have waited " + (System.currentTimeMillis() - start) +
           " milliseconds for available connection (" + usedPooled + "in use)");

3. JBM catches the exception and since it is a java.net.SocketException, assumes some fatal problem has happened with the connection, and falsely initiates failover to another node.

4. Before failing over JBM closes the failed connection.

5. This results in the JBR Callback Connector getting closed.

6. All this while callbacks are still arriving from the server, since that connection is actually still fine.

7. The connector closing process removes the callbackhandler from the callback ServerInvoker so any more callbacks arrive barf with not being able to find the handler.

So:

After increasing the client pool size I'm not getting these exceptions any more, but imho there are two issues here:

1) Why does remoting throw SocketException? - I would say this is inappropriate since the socket is fine - I would suggest some kind of org.jboss.remoting.RemotingException should be thrown?
This would allow JBM to catch it and not initiate failover in this case.
In the mean-time I will have to do some kind of text comparison:

if (exception.getMessage().startsWith("Can not obtain client....))
{
//don't do failover
}
else
{
//do failover
}
This will work for now but is ugly and brittle.

2) The connector close process is not clean. I would suggest the code should be changed so the server threads are shut down at the beginning of the connector close process.
I.e.
a) Wait for current invocations on that server invoker to complete - and don't allow any more.
b) Once all are complete shut it down.
(I believe we also have a deadlock on JBoss AS that Clebert discovered that was something due to connectors closing. I don't know if this is related?) 

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBMESSAGING-1114
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000 
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:06:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Thu, 18 Oct 2007 06:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17446147.1192701963467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani updated JBCACHE-1202:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA
       Complexity: High

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.3.0.GA, 1.4.0.GA, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3, 1.4.0.SP1, 1.4.1.GA, 1.3.0.SP4, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:08:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Thu, 18 Oct 2007 06:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22323022.1192702083562.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Manik Surtani updated JBCACHE-1201:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:10:03 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Thu, 18 Oct 2007 06:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1071) Possible problem in
 concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20471683.1192702203444.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]

Tom Baeyens updated JBPM-1071:
------------------------------

    Attachment: LockingTest.java

I attached a test LockingTest.  This test does basically the same as your test, but it fits in our overall test suite.

This test runs fine.  So I can't reproduce the problem.

The way that I check the optimistic locking is a bit different.  First, I spawn of x number of competing threads/transactions.  In each transaction, a comment is added that includes the name of the thread.

Later on, we check if exactly 1 thread managed to commit, while the other were rolled back.

What I think that you do different is that you don't use transactional resource to measure which transactions committed and which transactions rolled back.  A limitation of the current implementation is that you can't see if an optimistic failure rollback occured or not.

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz, LockingTest.java
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:16:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Thu, 18 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31612804.1192702563316.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani updated JBCACHE-1202:
-----------------------------------

    Priority: Critical  (was: Major)

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.3.0.GA, 1.4.0.GA, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3, 1.4.0.SP1, 1.4.1.GA, 1.3.0.SP4, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:21:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 18 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19041360.1192702863283.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12383202 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

Alex, this cant be true. 

I verified this the startup problem after a clean build on two different boxes. 
Heiko is seeing this as well.

Did you do: rm -rf thirdparty/*


[tdiesler at jbws trunk]$ svn info
Path: .
URL: https://svn.jboss.org/repos/jbossas/trunk
Repository Root: https://svn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 66231
Node Kind: directory
Schedule: normal
Last Changed Author: scott.stark at jboss.org
Last Changed Rev: 66229
Last Changed Date: 2007-10-18 07:51:39 +0200 (Thu, 18 Oct 2007)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:31:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1283) Unable to
	serialize rule base
Message-ID: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>

Unable to serialize rule base
-----------------------------

                 Key: JBRULES-1283
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Jiri Pechanec
         Assigned To: Mark Proctor
            Priority: Minor


When I am trying to serialize rulebase, I am getting the exception
Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at java.util.ArrayList.writeObject(ArrayList.java:569)
        at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
        at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
        at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
        at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
        at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
        at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:31:04 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:31:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1283) Unable to
	serialize rule base
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23534102.1192703464157.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=all ]

Jiri Pechanec updated JBRULES-1283:
-----------------------------------

    Component/s: Reteoo

> Unable to serialize rule base
> -----------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:31:04 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Thu, 18 Oct 2007 06:31:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11145231.1192703464437.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12383204 ] 
            
Alexey Loubyansky commented on JBAS-4864:
-----------------------------------------

After svn update I see it.

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:37:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3406905.1192703823280.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383206 ] 
            
Jiri Pechanec commented on JBPM-1071:
-------------------------------------

I will look at the code. But what pleas pay attantion to the fact that in my test I am also accessing to the database and all changes done in successful threads are committed.

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz, LockingTest.java
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:46:20 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:46:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15883845.1192704380200.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383207 ] 
            
Jiri Pechanec commented on JBPM-1071:
-------------------------------------

I have run your test in my environment and this is the result (I have run it not as junit test but as a standalone application)
More updates [org.jbpm.graph.exe.Comment at 3be0e954, org.jbpm.graph.exe.Comment at 2af6a882]
So in that assertEquals there are two results, not just one.
Sometimes there is only one, sometimes there are three

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz, LockingTest.java
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:59:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1300) Default a
 portlet window to maximized.
In-Reply-To: <24092633.1173097870945.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32799694.1192705143429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1300?page=all ]

Thomas Heute updated JBPORTAL-1300:
-----------------------------------

      Component/s: Portal Core
    Fix Version/s: 2.6.3 Final

> Default a portlet window to maximized.
> --------------------------------------
>
>                 Key: JBPORTAL-1300
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: David Roberts
>            Priority: Optional
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 07:01:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1619) Multiple
	maximized windows
In-Reply-To: <8587201.1185976549535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15562040.1192705263305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1619?page=all ]

Thomas Heute updated JBPORTAL-1619:
-----------------------------------

    Fix Version/s: 2.6.3 Final
         Assignee: Thomas Heute  (was: Julien Viet)

> Multiple maximized windows
> --------------------------
>
>                 Key: JBPORTAL-1619
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature.
> If you follow the next steps:
> 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized
> 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window.
> you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window.
> If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it).
> Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 07:03:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 07:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1300) Default a
 portlet window to maximized.
In-Reply-To: <24092633.1173097870945.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3550156.1192705383362.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1300?page=all ]

Thomas Heute reassigned JBPORTAL-1300:
--------------------------------------

    Assignee: Thomas Heute

> Default a portlet window to maximized.
> --------------------------------------
>
>                 Key: JBPORTAL-1300
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: David Roberts
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:02:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4567) Install
	jbossws-2.0.1.SP1
In-Reply-To: <13626450.1184838707453.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25807349.1192712523370.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4567?page=all ]

Dimitris Andreadis reopened JBAS-4567:
--------------------------------------

             
Re-opening the task, as we are back to a snapshot version.

> Install jbossws-2.0.1.SP1
> -------------------------
>
>                 Key: JBAS-4567
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4567
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:04:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4689) Upgrade JBoss
 messaging to 1.4.0.GA
In-Reply-To: <16306175.1189160291086.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25713946.1192712643491.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4689?page=all ]

Dimitris Andreadis reopened JBAS-4689:
--------------------------------------

             
re-open, we are back to a snapshot version.

> Upgrade JBoss messaging to 1.4.0.GA
> -----------------------------------
>
>                 Key: JBAS-4689
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4689
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Dimitris Andreadis
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> We are currently at 1.4.0.CR2

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:04:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 18 Oct 2007 09:04:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1283) Unable to
 serialize rule base ( NotSerializableException:
 org.drools.base.FireAllRulesRuleBaseUpdateListener)
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3516149.1192712644456.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=all ]

Mark Proctor updated JBRULES-1283:
----------------------------------

          Summary: Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)  (was: Unable to serialize rule base)
    Fix Version/s: 4.0.2_SOA_4.2-CP1
                   4.0.3
                   4.1.0

> Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:08:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 18 Oct 2007 09:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4567) Install jbossws-2.0.x
In-Reply-To: <13626450.1184838707453.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12980656.1192712883502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4567?page=all ]

Thomas Diesler updated JBAS-4567:
---------------------------------

    Summary: Install jbossws-2.0.x  (was: Install jbossws-2.0.1.SP1)

> Install jbossws-2.0.x
> ---------------------
>
>                 Key: JBAS-4567
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4567
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:12:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4714) Upgrade JBossRemoting
 to 2.2.2.SP2 (from 2.2.0.GA)
In-Reply-To: <17799303.1189663991032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14406232.1192713123347.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4714?page=all ]

Dimitris Andreadis closed JBAS-4714.
------------------------------------

    Resolution: Done

Closing it. We are running on remoting 2.2.2.SP2 since Oct/10th.

(Ron, unfortunately the SP2 release wasn't used for AS 4.2.2.GA)

> Upgrade JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)
> --------------------------------------------------
>
>                 Key: JBAS-4714
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4714
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The upgrade from Remoting 2.2.0.GA to 2.2.2.GA is occasioned largely by a set of features and fixes for JBossMessaging 1.4. 
> The further upgrade to 2.2.2.SP1 consists of fixes for JBREM-653 and JBREM-750.  The fix for JBREM-750 was supposed to go into 2.2.2.GA but was overlooked.  The fix for JBREM-653 is needed for ESB 4.2.1.
> These fixes have been applied to the remoting_2_2_0_GA branch from which 2.2.2.GA was released.  As soon as the related unit tests pass on cruisecontrol, the branch will be tagged remoting_2_2_2_SP1.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:14:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 18 Oct 2007 09:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1283) Unable to
 serialize rule base ( NotSerializableException:
 org.drools.base.FireAllRulesRuleBaseUpdateListener)
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16683222.1192713244587.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=comments#action_12383238 ] 
            
Mark Proctor commented on JBRULES-1283:
---------------------------------------

I've fixed for trunk and 4.0.x. raise the jira in the SOAP mailing list.

> Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:16:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 18 Oct 2007 09:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9997667.1192713363818.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Mark Proctor updated JBRULES-1282:
----------------------------------

    Fix Version/s:     (was: 4.0.2_SOA.4.2-CP2)

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>         Attachments: cumulative_patch.patch
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:16:04 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Thu, 18 Oct 2007 09:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12797008.1192713364389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4864?page=all ]

Alexey Loubyansky closed JBAS-4864.
-----------------------------------

    Resolution: Done

Fixed.

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:34:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30994347.1192714443317.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12383246 ] 
            
Dimitris Andreadis commented on JBAS-4688:
------------------------------------------

Pointing trunk to Beta2. I see the integration project currently at 5.0.0.Beta3.

Is an update to that necessary, as well?

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:40:11 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Thu, 18 Oct 2007 09:40:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17012592.1192714812233.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12383247 ] 
            
Jonathan Halliday commented on JBAS-4688:
-----------------------------------------

Yes. The change is in, it just needs releasing. My understanding from http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120481 was that Paul would handle the tagging for the release, but I may have misunderstood. 

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:05:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Thu, 18 Oct 2007 11:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-423) Fix microcontainer
 poms and metatdata in maven repository
Message-ID: <15025489.1192719903676.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix microcontainer poms and metatdata in maven repository
---------------------------------------------------------

                 Key: JBBUILD-423
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-423
             Project: JBoss Build System
          Issue Type: Task
          Components: Maven
            Reporter: Paul Gier
             Fix For: Maven Build - Maint 2007


The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:05:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Thu, 18 Oct 2007 11:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBBUILD-423) Fix
 microcontainer poms and metatdata in maven repository
In-Reply-To: <15025489.1192719903676.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26146717.1192719903834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-423?page=all ]

Paul Gier reassigned JBBUILD-423:
---------------------------------

    Assignee: Paul Gier

> Fix microcontainer poms and metatdata in maven repository
> ---------------------------------------------------------
>
>                 Key: JBBUILD-423
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-423
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 11:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4874) Track JBoss and
 thirdparty dependencies for JBossAS 4.2.3
Message-ID: <29949338.1192721463216.JavaMail.jira@cloud.prod.atl2.jboss.com>

Track JBoss and thirdparty dependencies for JBossAS 4.2.3
---------------------------------------------------------

                 Key: JBAS-4874
                 URL: http://jira.jboss.com/jira/browse/JBAS-4874
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Other
            Reporter: Dimitris Andreadis
             Fix For: JBossAS-4.2.3.GA


Use subtasks to track component updates in AS 4.2.3.GA

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 11:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4875) Upgrade jboss
 transactions to 4.2.3.SP7 (from 4.2.3.SP6)
Message-ID: <27966578.1192721823361.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6)
--------------------------------------------------------

                 Key: JBAS-4875
                 URL: http://jira.jboss.com/jira/browse/JBAS-4875
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: JB5-Transaction Manager
            Reporter: Dimitris Andreadis
         Assigned To: Mark Little
             Fix For: JBossAS-4.2.3.GA




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 11:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4875) Upgrade jboss
 transactions to 4.2.3.SP7 (from 4.2.3.SP6)
In-Reply-To: <27966578.1192721823361.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24614390.1192721823524.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4875?page=all ]

Dimitris Andreadis reassigned JBAS-4875:
----------------------------------------

    Assignee: Dimitris Andreadis  (was: Mark Little)

> Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6)
> --------------------------------------------------------
>
>                 Key: JBAS-4875
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4875
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.3.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:13:04 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 18 Oct 2007 12:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4863) NPE in
 ContainerConfigurationMetaDataWrapper
In-Reply-To: <22857669.1192523828772.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17898972.1192723984747.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4863?page=all ]

Scott M Stark resolved JBAS-4863.
---------------------------------

    Resolution: Done

The ContainerConfigurationMetaDataWrapper has been resolved

> NPE in ContainerConfigurationMetaDataWrapper
> --------------------------------------------
>
>                 Key: JBAS-4863
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4863
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> getContainerConfigurations returns null
>       configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
>             defaults.getContainerConfigurations());
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
>         at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:17:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 18 Oct 2007 12:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28525134.1192724223669.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4180?page=comments#action_12383290 ] 
            
Galder Zamarreno commented on JBAS-4180:
----------------------------------------

I have committed a simple UT for an HA Singleton with a Pojo bean injected 
without a JMX annotation that passes.

Still TODO: remove @JMX from HA singleton election policy tests and 
investigate why tests are failing.

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:23:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Thu, 18 Oct 2007 12:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4759) Upgrade jboss
 transactions to 4.2.3.SP6 (from 4.2.3.SP5)
In-Reply-To: <1093019.1190995301217.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19406993.1192724583682.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4759?page=comments#action_12383291 ] 
            
Jonathan Halliday commented on JBAS-4759:
-----------------------------------------

Unfortunately the JBOSSTS_4_2_3_SP6 tag in JBossTS project svn does not correctly reflect the content of the JBossTS 4.2.3.SP6 binaries on repository.jboss.com and in JBossAS 4.2.2.GA.

The tag was incorrectly created from the wrong branch, whilst the binaries were built from the correct one.

The good news is that the AS 4.2.2.GA therefore has the necessary transactions bug fixes.

The bad news is that recreating the source requires using the JBOSSTS_4_2_3_SP6_FOR_AS tag of the JBossTS svn, not the JBOSSTS_4_2_3_SP6  tag.

The binaries of SP6 on repository.jboss.com are now accompanied by a warning to this effect.

> Upgrade jboss transactions to 4.2.3.SP6 (from 4.2.3.SP5)
> --------------------------------------------------------
>
>                 Key: JBAS-4759
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4759
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:46:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 18 Oct 2007 12:46:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1107) Less noisy
 client-side failover
In-Reply-To: <13404207.1192220103325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3105332.1192725964801.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1107?page=comments#action_12383301 ] 
            
Tim Fox commented on JBMESSAGING-1107:
--------------------------------------

I agree.

Although AFAICT the only thing that logs at ERROR during failover is JBoss Remoting code.

We would need JBR to changes this and bring out a new release.

> Less noisy client-side failover
> -------------------------------
>
>                 Key: JBMESSAGING-1107
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.
> If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.
> Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. 
> The logging information should be naturally still available, but at DEBUG level.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:19:21 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:19:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-821) JBoss Remoting fails
	under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21278235.1192731561260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-821?page=all ]

Ron Sigal updated JBREM-821:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:21:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8806969.1192731663308.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383307 ] 
            
Ron Sigal commented on JBREM-821:
---------------------------------

Copying Tim Fox's comment from JBMESSAGING-1114:

I found out why this is happening (why the callback handler can't be found). :

1. An invocation fails because remoting timed out waiting for a TCP connection to be returned to the pool. (Pool size to small).
2. In this case remoting throws a java.net.SocketException:

throw new SocketException("Can not obtain client socket connection from pool. " +
           "Have waited " + (System.currentTimeMillis() - start) +
           " milliseconds for available connection (" + usedPooled + "in use)");

3. JBM catches the exception and since it is a java.net.SocketException, assumes some fatal problem has happened with the connection, and falsely initiates failover to another node.

4. Before failing over JBM closes the failed connection.

5. This results in the JBR Callback Connector getting closed.

6. All this while callbacks are still arriving from the server, since that connection is actually still fine.

7. The connector closing process removes the callbackhandler from the callback ServerInvoker so any more callbacks arrive barf with not being able to find the handler.

So:

After increasing the client pool size I'm not getting these exceptions any more, but imho there are two issues here:

1) Why does remoting throw SocketException? - I would say this is inappropriate since the socket is fine - I would suggest some kind of org.jboss.remoting.RemotingException should be thrown?
This would allow JBM to catch it and not initiate failover in this case.
In the mean-time I will have to do some kind of text comparison:

if (exception.getMessage().startsWith("Can not obtain client....))
{
//don't do failover
}
else
{
//do failover
}
This will work for now but is ugly and brittle.

2) The connector close process is not clean. I would suggest the code should be changed so the server threads are shut down at the beginning of the connector close process.
I.e.
a) Wait for current invocations on that server invoker to complete - and don't allow any more.
b) Once all are complete shut it down.
(I believe we also have a deadlock on JBoss AS that Clebert discovered that was something due to connectors closing. I don't know if this is related?)

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:25:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16548689.1192731903304.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383309 ] 
            
Ron Sigal commented on JBREM-821:
---------------------------------

Regarding issue 2) from Tim's note:  org.jboss.remoting.transport.socket.SocketServerInvoker.cleanup() should wait for all worker threads to finish processing before returning to SocketServerInvoker.stop(), which then calls ServerInvoker.stop().  The problem is that ServerInvoker.stop() removes all callback handlers, which could happen while a worker thread is still processing.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:29:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20316417.1192732143758.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383311 ] 
            
Ron Sigal commented on JBREM-821:
---------------------------------

Regarding the deadlock that Clebert discovered (JBREM-822):  I don't think it's related.  The deadlock occurs on the server side while JBossAS is shutting down.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:35:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-821) JBoss Remoting fails
	under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4664955.1192732503499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-821?page=all ]

Ron Sigal updated JBREM-821:
----------------------------

    Priority: Major  (was: Blocker)

Given that there is a workaround for the issues Tim has discovered, I've reduced the priority from Blocker to Major.  

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:37:05 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1114) JBoss
 Remoting fails under load
In-Reply-To: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5152785.1192732625206.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=comments#action_12383317 ] 
            
Ron Sigal commented on JBMESSAGING-1114:
----------------------------------------

I've added Tim's comments to JBREM-821 "JBoss Remoting fails under load".   I agree that issues 1) and 2) should be fixed.

Since there seems to be a workaround, I've scheduled JBREM-821 for Remoting release 2.4.0.Beta1 and reduced the priority to Major.  If any further related issues arise, of course, that can be readjusted.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBMESSAGING-1114
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000 
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:45:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Thu, 18 Oct 2007 14:45:03 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Created=3A_=28JBPORTAL-1?=
 =?utf-8?q?759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
Message-ID: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>

Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
-----------------------------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1759
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Server
    Affects Versions: 2.6.2 Final
         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
            Reporter: Johannes Fiala
         Assigned To: Julien Viet


Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.

E.g. Entering "http://localhost:8080/portal/?test=%FC"
throws the following exception:

HTTP Status 500 -
type Exception report
message description The server encountered an internal error () that prevented it from fulfilling this request.
exception java.lang.ArrayIndexOutOfBoundsException: 4
	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.


-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 15:04:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Thu, 18 Oct 2007 15:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5257557.1192734243464.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12383320 ] 
            
Koen Aers commented on GPD-169:
-------------------------------

Can someone please attach the processdefinition.xml and the gpd.xml file for a process that produces this behaviour.

Regards,
Koen

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 15:12:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 18 Oct 2007 15:12:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
Message-ID: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>

putForExternalRead replicates when INVALIDATION used
----------------------------------------------------

                 Key: JBCACHE-1203
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
             Fix For: 2.1.0.BETA1


If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.

The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 15:14:16 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 18 Oct 2007 15:14:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
In-Reply-To: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13750399.1192734856470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1203?page=all ]

Brian Stansberry updated JBCACHE-1203:
--------------------------------------

        Fix Version/s:     (was: 2.1.0.BETA1)
    Affects Version/s: 2.1.0.BETA1

> putForExternalRead replicates when INVALIDATION used
> ----------------------------------------------------
>
>                 Key: JBCACHE-1203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>
> If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.
> The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:26:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 16:26:03 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Commented=3A_=28JBPORTAL?=
 =?utf-8?q?-1759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15038924.1192739163437.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383337 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

Thanks for reporting this.

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 16:26:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 16:26:03 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Updated=3A_=28JBPORTAL-1?=
 =?utf-8?q?759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24291366.1192739163675.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=all ]

Julien Viet updated JBPORTAL-1759:
----------------------------------

    Fix Version/s: 2.6.3 Final

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 16:36:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 18 Oct 2007 16:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4876) Re-enable JGroups
 message bundling
Message-ID: <12319302.1192739763279.JavaMail.jira@cloud.prod.atl2.jboss.com>

Re-enable JGroups message bundling
----------------------------------

                 Key: JBAS-4876
                 URL: http://jira.jboss.com/jira/browse/JBAS-4876
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


 For 4.2.0 JGroups message bundling was disabled pending investigation of JGRP-497. That is fixed in JGroups 2.4.1.SP4. Message bundling improves performance, so we should re-enable it.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:54:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1760) JSR-301 JSF
 Portlet Bridge Integration
Message-ID: <18140018.1192740843453.JavaMail.jira@cloud.prod.atl2.jboss.com>

JSR-301 JSF Portlet Bridge Integration
--------------------------------------

                 Key: JBPORTAL-1760
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1760
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales


Integrate Implementation of 301 spec into JBP.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:59:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1761) Sun RI Example
Message-ID: <14752350.1192741143929.JavaMail.jira@cloud.prod.atl2.jboss.com>

Sun RI Example
--------------

                 Key: JBPORTAL-1761
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1761
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales


Create example app using maven and the Sun 1.2+ Reference Implementation

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:59:04 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1762) Myfaces Example
Message-ID: <30135268.1192741144057.JavaMail.jira@cloud.prod.atl2.jboss.com>

Myfaces Example
---------------

                 Key: JBPORTAL-1762
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1762
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:59:04 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1761) Sun RI Example
In-Reply-To: <14752350.1192741143929.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11535754.1192741144209.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1761?page=all ]

Wesley Hales reassigned JBPORTAL-1761:
--------------------------------------

    Assignee: Wesley Hales

> Sun RI Example
> --------------
>
>                 Key: JBPORTAL-1761
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1761
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>
> Create example app using maven and the Sun 1.2+ Reference Implementation

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:01:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1763) RichFaces Example
Message-ID: <18141880.1192741263399.JavaMail.jira@cloud.prod.atl2.jboss.com>

RichFaces Example
-----------------

                 Key: JBPORTAL-1763
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1763
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:01:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1764) Seam 2.x Example
Message-ID: <14612276.1192741263558.JavaMail.jira@cloud.prod.atl2.jboss.com>

Seam 2.x Example
----------------

                 Key: JBPORTAL-1764
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1764
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:03:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1686) Maven migration
	plan
In-Reply-To: <18408104.1189534271230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8269787.1192741383353.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1686?page=all ]

Wesley Hales resolved JBPORTAL-1686.
------------------------------------

    Resolution: Done

Created initial maven structure for common module to be referenced for future conversions.

> Maven migration plan
> --------------------
>
>                 Key: JBPORTAL-1686
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1686
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:05:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1689) Maven
	documentation
In-Reply-To: <31089433.1189534391507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2038625.1192741503435.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1689?page=all ]

Wesley Hales resolved JBPORTAL-1689.
------------------------------------

    Resolution: Done

Use common module for example and also reference blog http://jbossportal.blogspot.com/2007/10/migrating-to-maven-from-ant-part-1.html

> Maven documentation
> -------------------
>
>                 Key: JBPORTAL-1689
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1689
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>         Attachments: modules-common-structure.Jpg
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:07:03 2007
From: jira-events at lists.jboss.org (Frank Langelage (JIRA))
Date: Thu, 18 Oct 2007 17:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4877) Upgrade JSF to 1.2_05
Message-ID: <1154812.1192741623777.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade JSF to 1.2_05
---------------------

                 Key: JBAS-4877
                 URL: http://jira.jboss.com/jira/browse/JBAS-4877
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Frank Langelage


JSF 1.2_05 is out for a few days. Upgrade to this from 1.2_04_P02.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:15:34 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 17:15:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1765) Adapt the admin
 portlet to let the user set a default window state
Message-ID: <32743739.1192742134373.JavaMail.jira@cloud.prod.atl2.jboss.com>

Adapt the admin portlet to let the user set a default window state
------------------------------------------------------------------

                 Key: JBPORTAL-1765
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1765
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
            Reporter: Thomas Heute
         Assigned To: Wesley Hales
             Fix For: 2.6.3 Final


We'll need to be able to define which window (if any) of a page should be maximized when a window opens, we'll also need to define if a window must first be displayed as minimized.
The back end is not done 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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:27:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBPORTAL-1689) Maven
	documentation
In-Reply-To: <31089433.1189534391507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4789562.1192742823490.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1689?page=all ]

Wesley Hales reopened JBPORTAL-1689:
------------------------------------

             

> Maven documentation
> -------------------
>
>                 Key: JBPORTAL-1689
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1689
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>         Attachments: modules-common-structure.Jpg
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:27:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1689) Maven
	documentation
In-Reply-To: <31089433.1189534391507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20810119.1192742823718.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1689?page=comments#action_12383341 ] 
            
Wesley Hales commented on JBPORTAL-1689:
----------------------------------------

http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide

> Maven documentation
> -------------------
>
>                 Key: JBPORTAL-1689
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1689
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>         Attachments: modules-common-structure.Jpg
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:31:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1766) Portal
	Administration Icons
Message-ID: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>

Portal Administration Icons
---------------------------

                 Key: JBPORTAL-1766
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales


Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:31:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1766) Portal
	Administration Icons
In-Reply-To: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33374027.1192743063374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1766?page=all ]

Wesley Hales reassigned JBPORTAL-1766:
--------------------------------------

    Assignee: Wesley Hales

> Portal Administration Icons
> ---------------------------
>
>                 Key: JBPORTAL-1766
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>
> Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:53:04 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 17:53:04 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Commented=3A_=28JBPORTAL?=
 =?utf-8?q?-1759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22146406.1192744384163.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383344 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

I would like to know how this URL is generated. Has it been generated  by a PortletURL or did you manufacture it by hand ?
The correct litteral value for the umlaut char encoded for the web should be "%C3%BC" not "%FC" (x-www-formurlencoded with UTF-8). So your URL should be "http://localhost:8080/portal/?test=%C3%BC" 

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 17:55:07 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 17:55:07 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Commented=3A_=28JBPORTAL?=
 =?utf-8?q?-1759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22746590.1192744507950.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383345 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

However the bug should be resolved to detect that the input is wrong and it should be handled differently than a ArrayIndexOutOfBoundsException. I will consider this report as a bug in the detection of malformed input and correct it. If the URL you are giving me is manufactured by the portal, tell us how it was done with a new JIRA issue for it.

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 18:08:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 18:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1759) FastURLDecoder
 with malformed
 input %FC throws an ArrayIndexOutOfBoundsException instead of throwing
 MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9629210.1192745283393.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=all ]

Julien Viet updated JBPORTAL-1759:
----------------------------------

    Summary: FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException  (was: Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder)

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 18:10:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 18:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2951370.1192745403513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=all ]

Julien Viet resolved JBPORTAL-1759.
-----------------------------------

    Resolution: Done

fix in trunk of common module.

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 19:52:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 18 Oct 2007 19:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1059) Return a
 business interface from a home create method must not be allowed
In-Reply-To: <30915920.1191838939062.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10552969.1192751523266.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1059?page=all ]

Andrew Rubinger reassigned EJBTHREE-1059:
-----------------------------------------

    Assignee: Andrew Rubinger

> Return a business interface from a home create method must not be allowed
> -------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1059
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1059
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>
> EJB 3 4.6.8: The return type for a create<METHOD> method must be the session bean's remote interface type.
> Using the proxy as if it would be an EJBObject results in class cast exceptions.
> java.lang.ClassCastException: $Proxy9
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject(RemoteUnitTestCase.java:208)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 19:54:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 18 Oct 2007 19:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6511245.1192751643517.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=all ]

Andrew Rubinger reassigned EJBTHREE-1045:
-----------------------------------------

    Assignee: Andrew Rubinger

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 4.2.2.GA, AS 5.0.0.Beta3
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 21:07:14 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Thu, 18 Oct 2007 21:07:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1284)
 ClassCastException when using
 "<" constraint on field of type java.lang.Object containing data of type
 java.lang.Integer
Message-ID: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
------------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1284
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
         Environment: Windows XP, Eclipse 3.2
            Reporter: Justin Wick
         Assigned To: Mark Proctor


If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.

See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 21:13:07 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Thu, 18 Oct 2007 21:13:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1284)
 ClassCastException when using
 "<" constraint on field of type java.lang.Object containing data of type
 java.lang.Integer
In-Reply-To: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9601038.1192756387317.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1284?page=all ]

Justin Wick updated JBRULES-1284:
---------------------------------

    Attachment: DroolsTest.zip

A complete drools project with minimalist test code ready to be transplanted.

> ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1284
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: DroolsTest.zip
>
>
> If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.
> See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:47:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31550366.1192762023459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith updated JBAS-4818:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:48:05 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:48:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13074531.1192762085736.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith updated JBAS-4818:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

Revision 3

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:50:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6325606.1192762203368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Michael Smith updated JBAS-4820:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives  (was: TECH REVIEW: Installation Guide - Chapter 2 -  Directory Structure)

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:50:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12858643.1192762203507.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Michael Smith updated JBAS-4820:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-2.odt

Revision 2

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:52:07 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:52:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23718736.1192762327896.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

Michael Smith updated JBAS-4821:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer  (was: TECH REVIEW: Installation Guide - Chapter 3 -  The Default Server Configuration File Set)

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:52:08 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:52:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24548719.1192762328032.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

Michael Smith updated JBAS-4821:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-3.odt

Revision 2

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:54:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18285268.1192762443324.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download  (was: TECH REVIEW: Installation Guide - Chapter 4 -  Starting and Stopping JBoss)

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:54:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12863481.1192762443441.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-4.odt

REvision 2

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 -
Message-ID: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 5 - 
----------------------------------------------

                 Key: JBAS-4878
                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt

Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 -
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1196786.1192763103571.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

Michael Smith updated JBAS-4878:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-5.odt

> TECH REVIEW: Installation Guide - Chapter 5 - 
> ----------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5451276.1192763223558.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

Michael Smith updated JBAS-4878:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss  (was: TECH REVIEW: Installation Guide - Chapter 5 - )

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16006072.1192763223689.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

Michael Smith updated JBAS-4878:
--------------------------------

    Description: 
Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 

  was:
Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 


> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:09:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -
Message-ID: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 6 -  
-----------------------------------------------

                 Key: JBAS-4879
                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19788485.1192763463336.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Michael Smith updated JBAS-4879:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation  (was: TECH REVIEW: Installation Guide - Chapter 6 -  )

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25432603.1192763463467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Michael Smith updated JBAS-4879:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-6.odt

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:39:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
Message-ID: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
---------------------------------------------------------------

                 Key: JBAS-4880
                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt

Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:39:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8074111.1192765143641.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4880?page=all ]

Michael Smith updated JBAS-4880:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4880
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:39:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12095996.1192765143749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith closed JBAS-4818.
-------------------------------

    Resolution: Duplicate Issue

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:46:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - Getting Started
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3392716.1192765563375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

Michael Smith updated JBAS-4825:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-1.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started
> ----------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:48:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started Guide - Chapter 2. The JBoss Server - A Quick Tour
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9935628.1192765683407.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Michael Smith updated JBAS-4826:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-2.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:48:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24273123.1192765683566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Michael Smith updated JBAS-4826:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2   (was: TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour)

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:01:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8542299.1192766463459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Michael Smith updated JBAS-4827:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-3.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:03:14 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:03:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5133456.1192766594974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Michael Smith updated JBAS-4828:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application  (was: TECH REVIEW: Getting Started Guide - Chapter 4. The Duke's Bank Application)

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:03:15 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:03:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31086067.1192766595133.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Michael Smith updated JBAS-4828:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-4.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21940737.1192766703284.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Michael Smith updated JBAS-4829:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam  (was: TECH REVIEW: Getting Started Guide - Chapter 5. J2EE Web Services)

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18620203.1192766703427.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Michael Smith updated JBAS-4829:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-5.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <390452.1192766823532.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Michael Smith updated JBAS-4830:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases  (was: TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans)

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16271304.1192766823865.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Michael Smith updated JBAS-4830:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-6.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:09:06 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4831) TECH REVIEW: Getting
 Started Guide - Chapter 7. Container-Managed Persistence
In-Reply-To: <2964949.1192165535786.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5367118.1192766946482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4831?page=all ]

Michael Smith closed JBAS-4831.
-------------------------------

    Resolution: Out of Date

> TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4831
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4831
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-7.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:09:06 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4832) TECH REVIEW: Getting
 Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33008676.1192766946755.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4832?page=all ]

Michael Smith closed JBAS-4832.
-------------------------------

    Resolution: Out of Date

> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:09:06 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4833) TECH REVIEW: Getting
 Started Guide - Chapter 9. Using Hibernate
In-Reply-To: <12730012.1192165536058.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24487271.1192766946896.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4833?page=all ]

Michael Smith closed JBAS-4833.
-------------------------------

    Resolution: Out of Date

> TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
> ---------------------------------------------------------------
>
>                 Key: JBAS-4833
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4833
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-9.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:14:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Fri, 19 Oct 2007 00:14:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1285) Time Machine to
 allow setting of "now" effective current time in Rule
Message-ID: <30930954.1192767254713.JavaMail.jira@cloud.prod.atl2.jboss.com>

Time Machine to allow setting of "now" effective current time in Rule
---------------------------------------------------------------------

                 Key: JBRULES-1285
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1285
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0


This is needed for testing effective dating.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:58:14 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Fri, 19 Oct 2007 00:58:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
Message-ID: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>

java.net.SocketException: Too many open files
---------------------------------------------

                 Key: JBMESSAGING-1115
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Critical


When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.

2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
java.net.SocketException: Too many open files
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
        at java.net.ServerSocket.implAccept(ServerSocket.java:450)
        at java.net.ServerSocket.accept(ServerSocket.java:421)
        at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
        at java.lang.Thread.run(Thread.java:595)
2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 02:19:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 02:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33060066.1192774743243.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

Michael Smith updated JBAS-4825:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour  (was: TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started)

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 02:44:04 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Fri, 19 Oct 2007 02:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12342687.1192776244012.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

David Roberts updated GPD-169:
------------------------------

    Attachment: gpd.xml
                processdefinition.xml

I've attached the gpd.xml and the processdefinition.xml that caused me the initial problem. It has been updated quite a bit since the last time I had the problem. The node placement problem hasn't occured in a while, so I'm not sure what actually causes it. The same node placement problem happened on a completely different process two days ago. I haven't noticed any common ground though. And I can't seem to duplicate it when I want to, only hope that it doesn't happen.

However, the transition text positioning is always a problem. Try placing the text somewhere, and re-open the process. You'll notice that it doesn't save its position.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 02:48:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Fri, 19 Oct 2007 02:48:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1284)
 ClassCastException when
 using "<" constraint on field of type java.lang.Object containing data of
 type java.lang.Integer
In-Reply-To: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1486857.1192776494487.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1284?page=comments#action_12383376 ] 
            
Michael Neale commented on JBRULES-1284:
----------------------------------------

OK - yes well at compile time it decides to coerce to a string, yet gets a rude shock at runtime. 

not much more we can do at compile time for this, but at runtime I will see if we can do a better coercion.

> ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1284
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: DroolsTest.zip
>
>
> If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.
> See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 03:04:03 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Fri, 19 Oct 2007 03:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5334924.1192777443671.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12383377 ] 
            
David Roberts commented on GPD-169:
-----------------------------------

Okay I managed to reproduce the problem with the gpd.xml and processdefinition.xml I attached above, by doing either one of the following:

- On the graphical designer, delete the end node named "Offer Withdrawn". Then, add an end node in the same position and give it a transition line from "Withdrawn Notification" to "Offer Withdrawn", and save. Now close and re-open the processdefinition.xml in the designer, and all nodes will be messed up. Looking at the gpd.xml, the new end node has been placed at the bottom. This seems to cause the problem.

OR

- In the gpd.xml, take the line/node "Offer Withdrawn", and move it to the bottom of the gpd.xml, so it is the last node. Now close and open the processdefinition.xml with the graphical editor, the nodes will be messed up.

It seems that if an end node is at the bottom of the gpd.xml, it messes up the nodes? Well at least in this case.
Hope this helps...


> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:32:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10058969.1192782723368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

samson kittoli updated JBAS-4849:
---------------------------------

    Summary: TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel  (was: TECH REVIEW:  Server Configuration Guide - Chapter3 - Naming on JBoss)

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:32:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17790590.1192782723498.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli updated JBAS-4848:
---------------------------------

    Summary: TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss  (was: TECH REVIEW: Server Configuration Guide - Chapter4 - Connectors on JBoss)

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:32:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12903193.1192782723663.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

samson kittoli updated JBAS-4847:
---------------------------------

    Summary: TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss  (was: TECH REVIEW:  Server Configuration Guide - Chapter5 - Transactions on JBoss)

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:34:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15895283.1192782843754.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

samson kittoli updated JBAS-4846:
---------------------------------

    Summary: TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss  (was: TECH REVIEW:  Server Configuration Guide - Chapter6 - Messaging on JBoss)

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:34:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16212870.1192782843872.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

samson kittoli updated JBAS-4845:
---------------------------------

    Summary: TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss  (was: TECH REVIEW: Server Configuration Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.)

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:36:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28488085.1192790163319.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

samson kittoli updated JBAS-4851:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt

10-19-2007

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:49:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
Message-ID: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
----------------------------------------------------------------------

                 Key: JBAS-4881
                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:51:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
In-Reply-To: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31496818.1192791063329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4881?page=all ]

samson kittoli updated JBAS-4881:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4881
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:53:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4882) TECH REVIEW: Server
 Configuration Guide - Chapter9 - Web Services
Message-ID: <11998244.1192791183470.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services
-----------------------------------------------------------------

                 Key: JBAS-4882
                 URL: http://jira.jboss.com/jira/browse/JBAS-4882
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt

Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:53:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4882) TECH REVIEW: Server
 Configuration Guide - Chapter9 - Web Services
In-Reply-To: <11998244.1192791183470.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22490.1192791183809.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4882?page=all ]

samson kittoli updated JBAS-4882:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services
> -----------------------------------------------------------------
>
>                 Key: JBAS-4882
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4882
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:55:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:55:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
Message-ID: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
-------------------------------------------------------------------------

                 Key: JBAS-4883
                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:57:05 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:57:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
Message-ID: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
-------------------------------------------------------------------

                 Key: JBAS-4884
                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:59:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15132201.1192791543404.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

samson kittoli updated JBAS-4883:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:59:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
In-Reply-To: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17293184.1192791543819.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4884?page=all ]

samson kittoli updated JBAS-4884:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
> -------------------------------------------------------------------
>
>                 Key: JBAS-4884
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:01:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
Message-ID: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
---------------------------------------------------

                 Key: JBAS-4885
                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt

Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:01:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1445079.1192791663869.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

samson kittoli updated JBAS-4885:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:03:15 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:03:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30404471.1192791795518.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

samson kittoli updated JBAS-4844:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt, JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:03:15 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:03:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20527598.1192791795805.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

samson kittoli updated JBAS-4843:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:12:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 07:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20098208.1192792323341.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4688?page=all ]

Dimitris Andreadis closed JBAS-4688.
------------------------------------

    Resolution: Done

With the help of Paul we are using jboss-integration 5.0.0.Beta4.

JBossTS now at 4.3.0.Beta2.

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:14:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 19 Oct 2007 09:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1767) Add support for
 exporting full CMS content (multiple language)
Message-ID: <30770226.1192799643385.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add support for exporting full CMS content (multiple language)
--------------------------------------------------------------

                 Key: JBPORTAL-1767
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1767
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final
            Reporter: Mariusz Smykula
         Assigned To: Sohil Shah


Current, after migration all data in language other than default are lost. There is no solution for full data exporting.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:14:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 19 Oct 2007 09:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1767) Add support for
 exporting full CMS content (multiple language)
In-Reply-To: <30770226.1192799643385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18806098.1192799643637.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1767?page=all ]

Mariusz Smykula updated JBPORTAL-1767:
--------------------------------------

    Description: Currently after migration all data in language other than default are lost. There is no solution for full data exporting.  (was: Current, after migration all data in language other than default are lost. There is no solution for full data exporting.)

> Add support for exporting full CMS content (multiple language)
> --------------------------------------------------------------
>
>                 Key: JBPORTAL-1767
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1767
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>
> Currently after migration all data in language other than default are lost. There is no solution for full data exporting.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:18:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Fri, 19 Oct 2007 09:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3364889.1192799883436.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383431 ] 
            
Johannes Fiala commented on JBPORTAL-1759:
------------------------------------------

Julien, thank you for the quick analysis. 

The url has been manufactured manually, so I can correct it easily in my program (in fact it is a redirect url constructed manually).

However, if the user enters this url into the address field of the browser, my browsers (Mozilla Firefox 2.0.0.8/MS IE 6) transform this automatically x-www-formurlencoded with ISO-8859-1 (? becomes %FC), which would result in the error outlined above. With earlier versions of JBoss Portal 2.2.1SP3 and 2.6.1 GA this works correct as expected.

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Fri Oct 19 09:20:09 2007
From: jira-events at lists.jboss.org (Sergey Manukyan (JIRA))
Date: Fri, 19 Oct 2007 09:20:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1286) Incorrect
 information in section 2.5.7.3. Agenda Filters
Message-ID: <4085772.1192800009350.JavaMail.jira@cloud.prod.atl2.jboss.com>

Incorrect information in section 2.5.7.3. Agenda Filters
--------------------------------------------------------

                 Key: JBRULES-1286
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1286
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Manual
    Affects Versions: 4.0.2
            Reporter: Sergey Manukyan
         Assigned To: Mark Proctor


CORRECTION #1

Manual states :

To use a filter specify it while calling FireAllRules. The following example will filter out all rules ending with the text "Test":
workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );      

Should be:

To use a filter specify it while calling FireAllRules. The following example will only allow activation of rules ending with the text "Test". All others will be filtered out.:
workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );      

CORRECTION #2

Manual states :

RuleNameEndWithAgendaFilter

Should be :

RuleNameEndsWithAgendaFilter




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:26:16 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Fri, 19 Oct 2007 09:26:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26942602.1192800376995.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383437 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

it looks like your form is doing a get instead of a post, isn't it ?



> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Fri Oct 19 09:44:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 09:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1300) Default a
 portlet window to maximized.
In-Reply-To: <24092633.1173097870945.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21722347.1192801444222.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1300?page=all ]

Thomas Heute resolved JBPORTAL-1300.
------------------------------------

    Resolution: Done

> Default a portlet window to maximized.
> --------------------------------------
>
>                 Key: JBPORTAL-1300
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: David Roberts
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:14:03 2007
From: jira-events at lists.jboss.org (Francisco Reverbel (JIRA))
Date: Fri, 19 Oct 2007 10:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20791314.1192803243314.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4830?page=comments#action_12383443 ] 
            
Francisco Reverbel commented on JBAS-4830:
------------------------------------------

The title of the Oracle section ("Setting up an XADataSource with Oracle 9i") is inconsistent with the text, which states that "For this example, we've used Oracle 10g". The reference to 9i in the title shoud be either updated to 10g or, perhaps, removed (if the example does not change across Oracle versions in a significant way -- I think this is the case, but am not sure).



> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:14:03 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 19 Oct 2007 10:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <15122370.1192803243571.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]

Jeff Mesnil reassigned JBMESSAGING-375:
---------------------------------------

    Assignee: Jeff Mesnil  (was: Tim Fox)

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:16:03 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 19 Oct 2007 10:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <27447596.1192803363502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil reassigned JBMESSAGING-381:
---------------------------------------

    Assignee: Jeff Mesnil  (was: Tim Fox)

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:18:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 19 Oct 2007 10:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15158097.1192803483653.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12383444 ] 
            
Koen Aers commented on GPD-169:
-------------------------------

Thanks. This will most probably be helpful.

Cheers,
Koen

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:22:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7990827.1192803723765.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic reassigned JBMESSAGING-1099:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:22:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:22:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25222755.1192803724330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

        Fix Version/s: AS 5.0 Integration
                           (was: 1.4.0.SP1)
    Affects Version/s:     (was: 1.4.0.GA)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:24:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4886) Incorrect
 order/dependency shutting down MDBs
Message-ID: <32753121.1192803843327.JavaMail.jira@cloud.prod.atl2.jboss.com>

Incorrect order/dependency shutting down MDBs
---------------------------------------------

                 Key: JBAS-4886
                 URL: http://jira.jboss.com/jira/browse/JBAS-4886
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Clebert Suconic
         Assigned To: Weston Price
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:26:26 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:26:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4886) Incorrect
 order/dependency shutting down MDBs
In-Reply-To: <32753121.1192803843327.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31129014.1192803986370.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4886?page=all ]

Clebert Suconic updated JBAS-4886:
----------------------------------

    Description: 
Currently MDBs are being shutdown after the ServerPeer, what could cause communication error during the Connection closing, causing a waitForever in some interceptors.

We need to correctly set the dependency between MBeans

> Incorrect order/dependency shutting down MDBs
> ---------------------------------------------
>
>                 Key: JBAS-4886
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4886
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Clebert Suconic
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Currently MDBs are being shutdown after the ServerPeer, what could cause communication error during the Connection closing, causing a waitForever in some interceptors.
> We need to correctly set the dependency between MBeans

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:26:26 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:26:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1462211.1192803986740.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------

    Resolution: Rejected

After investigations this became a JBAS code... we opened JBAS-4886 for this.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:32:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 19 Oct 2007 10:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4886) Incorrect
 order/dependency shutting down MDBs
In-Reply-To: <32753121.1192803843327.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25387411.1192804323374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4886?page=all ]

Adrian Brock closed JBAS-4886.
------------------------------

    Resolution: Won't Fix

> Incorrect order/dependency shutting down MDBs
> ---------------------------------------------
>
>                 Key: JBAS-4886
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4886
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Clebert Suconic
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Currently MDBs are being shutdown after the ServerPeer, what could cause communication error during the Connection closing, causing a waitForever in some interceptors.
> We need to correctly set the dependency between MBeans

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:59:18 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 19 Oct 2007 10:59:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1534590.1192805958891.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=all ]

Carlo de Wolf updated EJBTHREE-1045:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 11:37:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 19 Oct 2007 11:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1284)
 ClassCastException when
 using "<" constraint on field of type java.lang.Object containing data of
 type java.lang.Integer
In-Reply-To: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29880.1192808223853.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1284?page=comments#action_12383469 ] 
            
Justin Wick commented on JBRULES-1284:
--------------------------------------

IMHO, if this is known to be a "bad" thing to do, the compiler should at least throw a warning saying so, if not a straight-out error.  Unless, of course, the runtime coercian could be made better.

Is there a reason runtime type coercion cannot say that literals are whatever type they would be in Java?  i.e. 50 is  an integer, 50l is a long, 50.0 is a double, "50" is a String, etc?

> ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1284
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: DroolsTest.zip
>
>
> If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.
> See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4887) Port beanshell
	deployer to VDF
Message-ID: <27777727.1192811463357.JavaMail.jira@cloud.prod.atl2.jboss.com>

Port beanshell deployer to VDF
------------------------------

                 Key: JBAS-4887
                 URL: http://jira.jboss.com/jira/browse/JBAS-4887
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Deployment services
            Reporter: Dimitris Andreadis
         Assigned To: Ales Justin
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:34:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:34:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3536) Spring Deployer
 lacks info on
 Spring compatibility, I get NoSuchMethodError....and try to find which
 Spring version to use...
In-Reply-To: <22456206.1156144632106.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <284185.1192811655479.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3536?page=all ]

Dimitris Andreadis updated JBAS-3536:
-------------------------------------

    Component/s: Spring integration
                     (was: Other)
       Assignee: Ales Justin

Assign to Ales to look at.

> Spring Deployer lacks info on Spring compatibility, I get NoSuchMethodError....and try to find which Spring version to use...
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-3536
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3536
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: WinXP, Spring-2.0-RC2,  JBOSS-AS-4.0.4-GA
>            Reporter: Morten Haavaldsen
>         Assigned To: Ales Justin
>
> I use the Spring Deployer and get NoSuchMethodError on Spring classes during deployment.
> I use the Spring Deployer 1.3 and it is the example(the fixed one as well) which gives the exception.
> So, the big question is: which Spring version is the deployer compatible with?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:36:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2040) Spring Deployer
Message-ID: <28754905.1192811763525.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2040?page=all ]

Dimitris Andreadis updated JBAS-2040:
-------------------------------------

    Component/s: Spring integration
                     (was: Deployment services)

> Spring Deployer
> ---------------
>
>                 Key: JBAS-2040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2040
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>            Priority: Optional
>
> Complete me for release notes.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:36:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2042) Spring deployer and
 coding standards
Message-ID: <912432.1192811763777.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2042?page=all ]

Dimitris Andreadis updated JBAS-2042:
-------------------------------------

    Component/s: Spring integration
                     (was: Other)

> Spring deployer and coding standards
> ------------------------------------
>
>                 Key: JBAS-2042
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2042
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>            Priority: Trivial
>
> The spring deployer follows incorrect coding standards.
> i.e. Kernigan and Ritchie
> Also, it should not use printStackTrace(), 
> nor should it use the horrible log.error and throw paradigm
> that just leads to a console full of annoying duplicate logging of errors.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:36:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:36:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2153) Spring-int tests
Message-ID: <21809673.1192811764037.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2153?page=all ]

Dimitris Andreadis updated JBAS-2153:
-------------------------------------

    Component/s: Spring integration
                     (was: Test Suite)

> Spring-int tests
> ----------------
>
>                 Key: JBAS-2153
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2153
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>
> Need some ant unit tests for spring-int such that we don't break it.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:38:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4666) MBean for new
	EjbDeployer
In-Reply-To: <29450369.1188919271355.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30852590.1192811883486.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4666?page=all ]

Dimitris Andreadis updated JBAS-4666:
-------------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was: JBossAS-5.0.0.GA)

> MBean for new EjbDeployer
> -------------------------
>
>                 Key: JBAS-4666
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4666
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>            Reporter: Adrian Brock
>             Fix For: JBossAS-5.0.0.CR1
>
>
> I've reinstated the MBean for the EJBDeployer since some tests were using it.
> This uses the @JMX annotation on the POJO.
> The new deployer looks to have some bits missing related to verification which it what this task is about resolving.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:38:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-24) Get OpenSaml2
 snapshot libraries into the JBoss Maven repository
In-Reply-To: <26707524.1164815335686.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19964589.1192811883675.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-24?page=all ]

Anil Saldhana updated SECURITY-24:
----------------------------------

    Summary: Get OpenSaml2 snapshot libraries into the JBoss Maven repository  (was: Get OpenSaml2 snapshot libraries into the JBoss repository)

> Get OpenSaml2 snapshot libraries into the JBoss Maven repository
> ----------------------------------------------------------------
>
>                 Key: SECURITY-24
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-24
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: OnDemand, Repository
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:38:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:38:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4130) Simple HelloWorld
 JSF 1.2 application does not work
In-Reply-To: <28586848.1172070275576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23312324.1192811884487.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4130?page=all ]

Dimitris Andreadis updated JBAS-4130:
-------------------------------------

    Component/s: JavaServerFaces
                     (was: Deployment services)
       Assignee: Stan Silvert  (was: Dimitris Andreadis)

Assign to Stan to look at

> Simple HelloWorld JSF 1.2 application does not work
> ---------------------------------------------------
>
>                 Key: JBAS-4130
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4130
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JavaServerFaces
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: Windows XP,  Suse 10.2
>            Reporter: sedat ciftci
>         Assigned To: Stan Silvert
>
>  I have faced with a problem while deploying my JSF 1.2 web application (sun impl) ( I build with Netbeans 5.5 Visual Web pack) to JBoss5 Beta. It works with Glassfish. In order to find the problem, I make a simple Hello world web application and try to deploy it to JBoss5Beta. However, I get the same exception.
> The first exception that I overcome is related with web-facesconfig_1_2.xsd. JBoss says that it can not resolve this schema. I solve this problem by putting this file into the jboss.jar/schema.
> The second exception that I cannot solve is although my projects managed-beans.xml file is well formed, JBoss throws such an exception:
> org.jboss.deployers.spi.DeploymentException: The xml JBoss5Ex.war/WEB-INF/managed-beans.xml is not well formed!
> at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:94)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:173)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88)
> at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59)
> at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
> at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
> at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
> at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:508)
> at java.lang.Thread.run(Thread.java:595)
> Note that JBoss5Ex.war is my web application. 
>  Here is the content of my managed-beans.xml file (starting after the #'s line):
> ######################################
> <?xml version="1.0" encoding="UTF-8"?>
> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd">
> <managed-bean>
> <managed-bean-name>SessionBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.SessionBean1</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>Page1</managed-bean-name>
> <managed-bean-class>jboss5ex.Page1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>ApplicationBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.ApplicationBean1</managed-bean-class>
> <managed-bean-scope>application</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>RequestBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.RequestBean1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> </faces-config>
> #################################################

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:40:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:40:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-1292) SFSB session
	replication
Message-ID: <12456485.1192812005257.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-1292?page=comments#action_12383478 ] 
            
Dimitris Andreadis commented on JBAS-1292:
------------------------------------------

Is this issue still current, or outdated?

> SFSB session replication
> ------------------------
>
>                 Key: JBAS-1292
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1292
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Bela Ban
>         Assigned To: Jason T. Greene
>   Original Estimate: 10 weeks
>  Remaining Estimate: 10 weeks
>
> - Issues: who instrument the user-specified object? Can it be done transparently?
>   - SFSB has states defined already and user declared it as "clusterable", can we
>     declare the fields object as "advisable" at runtime. Meaning, deployer will know
>     this bean is clusterable and it will "delegate" it to JBossAop to declare all
>     the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor
>     at run time. Check with Bill on this feature.
>   - Check modified field and do fine-grained replication only

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:47:11 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 12:47:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-24) Get OpenSaml2
 snapshot libraries into the JBoss Maven repository
In-Reply-To: <26707524.1164815335686.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26446090.1192812431385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-24?page=all ]

Anil Saldhana closed SECURITY-24.
---------------------------------

    Resolution: Done

Maven Repository has:

OpenSaml-2.0-alpha1:
maven2/opensaml/opensaml2/2.0-alpha1/

Opensaml2 openws:
maven2/opensaml/openws/1.0-alpha1/

Opensaml2 xmltooling:
maven2/opensaml/xmltooling/1.0-alpha1/

Commons-Codec:
maven2/org/apache/commons-codec/1.3/

Commons-SSL:
maven2/org/apache/commons/not-yet-commons-ssl/0.3.7

httpclient:
maven2/org/apache/httpclient/3.0.1/

joda-time:
maven2/net/sf/joda-time/1.4/

javolution:
maven2/org/javolution/4.1.0

Velocity-dep:
maven2/velocity/velocity-dep/1.5/



> Get OpenSaml2 snapshot libraries into the JBoss Maven repository
> ----------------------------------------------------------------
>
>                 Key: SECURITY-24
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-24
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: OnDemand, Repository
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:49:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 19 Oct 2007 12:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4888) Inject
 InvalidationManagerMBean into JGCacheInvalidationBridge
Message-ID: <29917340.1192812543460.JavaMail.jira@cloud.prod.atl2.jboss.com>

Inject InvalidationManagerMBean into JGCacheInvalidationBridge
--------------------------------------------------------------

                 Key: JBAS-4888
                 URL: http://jira.jboss.com/jira/browse/JBAS-4888
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For:  JBossAS-5.0.0.Beta3


Currently an ObjectName is injected, and startService() does a JMX lookup.  Just have the MC inject the service.

Will also remove the getter/setter from JGCacheInvalidationServiceMBean -- MC is doing the injection into a pojo service, and it doesn't need to be in an MBean interface for any other reason.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:49:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 19 Oct 2007 12:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4888) Inject
 InvalidationManagerMBean into JGCacheInvalidationBridge
In-Reply-To: <29917340.1192812543460.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11736107.1192812543600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4888?page=all ]

Brian Stansberry closed JBAS-4888.
----------------------------------

    Resolution: Done

> Inject InvalidationManagerMBean into JGCacheInvalidationBridge
> --------------------------------------------------------------
>
>                 Key: JBAS-4888
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4888
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Currently an ObjectName is injected, and startService() does a JMX lookup.  Just have the MC inject the service.
> Will also remove the getter/setter from JGCacheInvalidationServiceMBean -- MC is doing the injection into a pojo service, and it doesn't need to be in an MBean interface for any other reason.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:51:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:51:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18802649.1192812664232.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3885?page=all ]

Dimitris Andreadis reassigned JBAS-3885:
----------------------------------------

    Assignee: Dimitris Andreadis

> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:51:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:51:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28881920.1192812664658.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3885?page=comments#action_12383481 ] 
            
Dimitris Andreadis commented on JBAS-3885:
------------------------------------------

Yes, it's this line in \jbossas\jmx-remoting\src\main\org\jboss\mx\remoting\service\JMXConnectorServerService.java:

...
      if(bindAddress == null || bindAddress.equals("0.0.0.0"))
      {
         bindAddress = InetAddress.getLocalHost().getHostName();
      }

> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:53:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3508)
 org.jboss.test.aop.test.SimpleBeanUnitTestCase fails because "ejb" is not
 bound
In-Reply-To: <15145030.1155322695616.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1507060.1192812783435.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3508?page=all ]

Dimitris Andreadis updated JBAS-3508:
-------------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> org.jboss.test.aop.test.SimpleBeanUnitTestCase fails because "ejb" is not bound
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-3508
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3508
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: win xp
>            Reporter: Jaroslaw Kijanowski
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> org.jboss.test.aop.test.SimpleBeanUnitTestCase fails because "ejb" is not bound, because of missing files in META-INF.
> Solution:
> copy following xml files to:
> testsuite\src\resources\aop\simpleejb\META-INF
> ejb-jar.xml:
> **************************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
> <ejb-jar >
>    <description><![CDATA[No Description.]]></description>
>    <display-name>Generated by XDoclet</display-name>
>    <enterprise-beans>
>       <!-- Session Beans -->
>       <session >
>          <description><![CDATA[]]></description>
>          <ejb-name>test/Simple</ejb-name>
>          <home>org.jboss.test.aop.simpleejb.SimpleHome</home>
>          <remote>org.jboss.test.aop.simpleejb.Simple</remote>
>          <ejb-class>org.jboss.test.aop.simpleejb.SimpleBean</ejb-class>
>          <session-type>Stateless</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>      <!--
>        To add session beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called session-beans.xml that contains
>        the <session></session> markup for those beans.
>      -->
>       <!-- Entity Beans -->
>      <!--
>        To add entity beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called entity-beans.xml that contains
>        the <entity></entity> markup for those beans.
>      -->
>       <!-- Message Driven Beans -->
>      <!--
>        To add message driven beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called message-driven-beans.xml that contains
>        the <message-driven></message-driven> markup for those beans.
>      -->
>    </enterprise-beans>
>    <!-- Relationships -->
>    <!-- Assembly Descriptor -->
>    <assembly-descriptor >
>      <!--
>        To add additional assembly descriptor info here, add a file to your
>        XDoclet merge directory called assembly-descriptor.xml that contains
>        the <assembly-descriptor></assembly-descriptor> markup.
>      -->
>    <!-- finder permissions -->
>    <!-- transactions -->
>    <container-transaction >
>       <method >
>          <ejb-name>test/Simple</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Required</trans-attribute>
>     </container-transaction>
>    <!-- finder transactions -->
>    </assembly-descriptor>
> </ejb-jar>
> ************************************
> ************************************
> jboss.xml:
> ******************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
> <jboss>
>    <enterprise-beans>
>      <!--
>        To add beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called jboss-beans.xml that contains
>        the <session></session>, <entity></entity> and <message-driven></message-driven>
>        markup for those beans.
>      -->
>       <session>
>          <ejb-name>test/Simple</ejb-name>
>          <jndi-name>ejb/test/Simple</jndi-name>
>       </session>
>    </enterprise-beans>
>    <resource-managers>
>    </resource-managers>
> </jboss>

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:55:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-1402) Transaction Recovery
Message-ID: <14126009.1192812903783.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ]

Dimitris Andreadis reassigned JBAS-1402:
----------------------------------------

    Assignee: Adrian Brock

Adrian, can we close this whole task & subtasks out-of-date, or do we keep the JCA tasks as still current?

> Transaction Recovery
> --------------------
>
>                 Key: JBAS-1402
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1402
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.0.1 Final
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>
> Implement optional transaction recovery
> The simplest mechanism is to do this is with a local database
> using the last resource gambit where during its "prepare" it logs the XID in a table.
> If this last resource fails to commit, recovery will not find the transaction
> in the table which means it will rollback the whole transaction.
> This has limitations where a different local resource is required within the transaction
> but not this local database used as the recovery log.
> Another implementation is a local file. Though more complicated it should give superior
> performance. 
> But, it does not work well with the last resource gambit, e.g. you cannot tell
> whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation
> before the result is returned from the db.
> The other work required:
> 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier.
> Currently the RARs need the transaction manager at deployment time. The
> recovery service needs to be an external service depending upon both the
> tm and the managed connection factories.
> At least this will require a GUID for the XID so we can avoid duplicates between
> unrecovered XIDs and any new XIDs created before recovery is complete.
> 2) JBossMQ needs to implement XAResource.recover()

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3509)
 org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
In-Reply-To: <20759834.1155322935652.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13624554.1192813023811.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3509?page=all ]

Dimitris Andreadis updated JBAS-3509:
-------------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
> ----------------------------------------------------------------------
>
>                 Key: JBAS-3509
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3509
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: win xp
>            Reporter: Jaroslaw Kijanowski
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound because of missing xml files.
> Resolve:
> Copy following xml files to testsuite\src\resources\cache\META-INF
> ************
> ejb-jar.xml:
> ************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
> <ejb-jar >
>    <description><![CDATA[No Description.]]></description>
>    <display-name>Generated by XDoclet</display-name>
>    <enterprise-beans>
>       <!-- Session Beans -->
>       <session >
>          <description><![CDATA[]]></description>
>          <ejb-name>CacheObjectMeanTester</ejb-name>
>          <home>org.jboss.test.cache.bean.CacheObjectMeanTesterHome</home>
>          <remote>org.jboss.test.cache.bean.CacheObjectMeanTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.CacheObjectMeanTesterBean</ejb-class>
>          <session-type>Stateless</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[Proxy to the TreeCache MBean.]]></description>
>          <ejb-name>test/TreeCacheTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
>          <ejb-name>test/TreeCacheAopTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheAopTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheAopTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheAopTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[EJB proxy to the TreeCache MBean service.]]></description>
>          <ejb-name>test/TreeCacheMBeanTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheMBeanTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheMBeanTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheMBeanTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
>          <ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheAopMBeanTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>      <!--
>        To add session beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called session-beans.xml that contains
>        the <session></session> markup for those beans.
>      -->
>       <!-- Entity Beans -->
>      <!--
>        To add entity beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called entity-beans.xml that contains
>        the <entity></entity> markup for those beans.
>      -->
>       <!-- Message Driven Beans -->
>      <!--
>        To add message driven beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called message-driven-beans.xml that contains
>        the <message-driven></message-driven> markup for those beans.
>      -->
>    </enterprise-beans>
>    <!-- Relationships -->
>    <!-- Assembly Descriptor -->
>    <assembly-descriptor >
>      <!--
>        To add additional assembly descriptor info here, add a file to your
>        XDoclet merge directory called assembly-descriptor.xml that contains
>        the <assembly-descriptor></assembly-descriptor> markup.
>      -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- transactions -->
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheAopTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheMBeanTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <!-- finder transactions -->
>    </assembly-descriptor>
> </ejb-jar>
> ************
> ************
> jboss.xml
> ************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
> <jboss>
>    <enterprise-beans>
>      <!--
>        To add beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called jboss-beans.xml that contains
>        the <session></session>, <entity></entity> and <message-driven></message-driven>
>        markup for those beans.
>      -->
>       <session>
>          <ejb-name>CacheObjectMeanTester</ejb-name>
>          <jndi-name>test/CacheObjectMeanTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheTester</ejb-name>
>          <jndi-name>ejb/test/TreeCacheTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheAopTester</ejb-name>
>          <jndi-name>test/TreeCacheAopTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheMBeanTester</ejb-name>
>          <jndi-name>ejb/test/TreeCacheMBeanTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
>          <jndi-name>ejb/test/TreeCacheAopMBeanTester</jndi-name>
>       </session>
>    </enterprise-beans>
>    <resource-managers>
>    </resource-managers>
> </jboss>
> ***************

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:59:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17578747.1192813143841.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic reopened JBMESSAGING-1099:
------------------------------------------

             

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:59:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 12:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25678265.1192813144124.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

        Fix Version/s: 1.4.0.SP1
                           (was: AS 5.0 Integration)
    Affects Version/s: 1.4.0.GA

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:01:08 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 13:01:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1357) Support for massive
	mbean counts
Message-ID: <32854294.1192813268429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1357?page=all ]

Dimitris Andreadis closed JBAS-1357.
------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Scott M Stark)

Re-open if there is real interest for this.

> Support for massive mbean counts
> --------------------------------
>
>                 Key: JBAS-1357
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1357
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-4.0.1 Final
>            Reporter: Scott M Stark
>
> Creating thousands of mbeans seems to incur a very large overhead in memory that needs to be investigated.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:01:08 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 19 Oct 2007 13:01:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1287) Use of reserved
 word as bound variable in a pattern results as NPE
Message-ID: <13915114.1192813268603.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use of reserved word as bound variable in a pattern results as NPE
------------------------------------------------------------------

                 Key: JBRULES-1287
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1287
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, Eclipse IDE
    Affects Versions: 4.0.2
         Environment: Eclipse 3.2, Windows XP
            Reporter: Justin Wick
         Assigned To: Mark Proctor


example:

rule "This generates an NPE"
	when
		result : ReservedWordNPEFact(data < 15)
	then
		result.setData(new Integer(1));	 
end

At least in the eclipse IDE, this generates an NPE.  Change result to something like:


rule "This generates an NPE"
	when
		f: ReservedWordNPEFact(data < 15)
	then
		f.setData(new Integer(1));	 
end

and it goes away.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:03:04 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 19 Oct 2007 13:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1287) Use of reserved
 word as bound variable in a pattern results as NPE
In-Reply-To: <13915114.1192813268603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18926033.1192813384498.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1287?page=all ]

Justin Wick updated JBRULES-1287:
---------------------------------

    Attachment: ReservedWordNPE.zip

A sample project which generates aforementioned NPEs, designed to be easily integrated into a junit test

> Use of reserved word as bound variable in a pattern results as NPE
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1287
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1287
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE, Drl Parser/Builder
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2, Windows XP
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: ReservedWordNPE.zip
>
>
> example:
> rule "This generates an NPE"
> 	when
> 		result : ReservedWordNPEFact(data < 15)
> 	then
> 		result.setData(new Integer(1));	 
> end
> At least in the eclipse IDE, this generates an NPE.  Change result to something like:
> rule "This generates an NPE"
> 	when
> 		f: ReservedWordNPEFact(data < 15)
> 	then
> 		f.setData(new Integer(1));	 
> end
> and it goes away.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:05:05 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1768) sanitize captcha
 parameter setup
Message-ID: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>

sanitize captcha parameter setup
--------------------------------

                 Key: JBPORTAL-1768
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
             Project: JBoss Portal
          Issue Type: Patch
      Security Level: Public (Everyone can see)
    Affects Versions: 2.6.3 Final
            Reporter: Andrew Oliver
             Fix For: 2.6.3 Final
         Attachments: captcha.patch

The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:05:06 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:05:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16106534.1192813506098.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Andrew Oliver updated JBPORTAL-1768:
------------------------------------

    Attachment: captcha.patch

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:14:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 13:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
In-Reply-To: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13991648.1192814043276.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1203?page=all ]

Manik Surtani updated JBCACHE-1203:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA

> putForExternalRead replicates when INVALIDATION used
> ----------------------------------------------------
>
>                 Key: JBCACHE-1203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.
> The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:18:03 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24975348.1192814283687.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Andrew Oliver updated JBPORTAL-1768:
------------------------------------

    Attachment: captcha2.patch

both patches are needed.  this one is against the main jsf/register/register.xhtml, the other includes only files in common.  (stupid eclipse)

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:20:05 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:20:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1768) sanitize
 captcha parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26749.1192814405601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Andrew Oliver reassigned JBPORTAL-1768:
---------------------------------------

    Assignee: Emanuel Muckenhuber

patch is to admin, you seem to be the admin guy.

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:22:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 13:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28820097.1192814523809.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Thomas Heute updated JBPORTAL-1768:
-----------------------------------

    Affects Version/s: 2.6.2 Final
                           (was: 2.6.3 Final)

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.2 Final
>            Reporter: Andrew Oliver
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:22:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 13:22:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23679201.1192814524644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------

    Resolution: Done

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:30:14 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 13:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9392080.1192815014818.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Clebert Suconic updated JBMESSAGING-1096:
-----------------------------------------

    Summary: Remove references from the old Callback Manager on the documentation  (was: Document bisocket and remove references from the old Callback Manager on the documentation)

The bisocket is already documented... we just need to remove this old refeference on docs.

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:30:15 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 13:30:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10051438.1192815015037.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Clebert Suconic closed JBMESSAGING-1096.
----------------------------------------

    Resolution: Done

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:32:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Fri, 19 Oct 2007 13:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
Message-ID: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove svn m2_repo dir or at least clean it out
-----------------------------------------------

                 Key: JBRULES-1288
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.2
            Reporter: Geoffrey De Smet
         Assigned To: Geoffrey De Smet
             Fix For: 4.1.0


Both of the jars in trunk/m2_repo are obsolete:
- jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
- mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:34:06 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Fri, 19 Oct 2007 13:34:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12562613.1192815246689.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=comments#action_12383497 ] 
            
Geoffrey De Smet commented on JBRULES-1288:
-------------------------------------------

Gonna remove both jars tomorrow if no one objects.
I 'll leave the m2_repo dir intact, maybe you guys want to reuse it later.

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:55:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 13:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7802501.1192816503319.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=comments#action_12383502 ] 
            
Manik Surtani commented on JBCACHE-1202:
----------------------------------------

Added unit test o.j.c.statetransfer.DataVersionTransferTest and implemented a fix based on putting the data version in the attribs map.  

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:55:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 13:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22584512.1192816503522.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani resolved JBCACHE-1202.
------------------------------------

    Resolution: Done

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:35:07 2007
From: jira-events at lists.jboss.org (Emanuel Muckenhuber (JIRA))
Date: Fri, 19 Oct 2007 14:35:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11933833.1192818907170.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Emanuel Muckenhuber updated JBPORTAL-1768:
------------------------------------------

    Priority: Minor  (was: Major)

The first spot declaration of 'showCaptcha' makes indeed no sense because it's never used - most likely a relict when portletPreferences could not be resolved. The only idea behind putting the condition into the captcha.xml was to keep the registration page as simple as possible, because it should be editable by users. Anyway i will take a look at that again. Thanks

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.2 Final
>            Reporter: Andrew Oliver
>         Assigned To: Emanuel Muckenhuber
>            Priority: Minor
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:35:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:35:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-79) Principal Mapping
	Modules
In-Reply-To: <7883474.1190755242268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17358867.1192818907383.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-79?page=all ]

Anil Saldhana closed SECURITY-79.
---------------------------------

    Resolution: Done

> Principal Mapping Modules
> -------------------------
>
>                 Key: SECURITY-79
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-79
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.1-BETA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-GA
>
>
> We need Principal Mapping Modules via the Mapping Manager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:37:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (SECURITY-32) White Paper on
	Clustered SSO
In-Reply-To: <19027403.1173286522201.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17771888.1192819023384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-32?page=all ]

Anil Saldhana reassigned SECURITY-32:
-------------------------------------

    Assignee: Marcus Moyses  (was: Sakthi Samabsivam)

> White Paper on Clustered SSO
> ----------------------------
>
>                 Key: SECURITY-32
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-32
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Marcus Moyses
>             Fix For: NO_VERSION
>
>
> White paper on the Clustered SSO offering from JBoss.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
> http://wiki.jboss.org/wiki/Wiki.jsp?page=BuddyReplicationAndClusteredSSO
> This is important because many customers are using this along with http session replication.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:39:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-84) Update
 documentation for 2.0.1-GA Release
Message-ID: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update documentation for 2.0.1-GA Release
-----------------------------------------

                 Key: SECURITY-84
                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-GA


Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:41:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-85) Release Security
	V2.0.1-GA
Message-ID: <25608054.1192819263974.JavaMail.jira@cloud.prod.atl2.jboss.com>

Release Security V2.0.1-GA
--------------------------

                 Key: SECURITY-85
                 URL: http://jira.jboss.com/jira/browse/SECURITY-85
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: JBossSX, Security SPI
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-GA




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:53:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 14:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8810966.1192819983664.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani reopened JBCACHE-1202:
------------------------------------

             

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:53:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 14:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1202) State transfer
 and cache loading does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29603892.1192819983824.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani updated JBCACHE-1202:
-----------------------------------

    Summary: State transfer and cache loading does not include optimistic node's DataVersion  (was: State transfer does not include optimistic node's DataVersion)

> State transfer and cache loading does not include optimistic node's DataVersion
> -------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:53:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 14:53:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1202) State transfer
 and cache loading does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21605803.1192819984518.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=comments#action_12383505 ] 
            
Manik Surtani commented on JBCACHE-1202:
----------------------------------------

Moved to o.j.c.optimistic.DataVersionTransferTest and added o.j.c.optimistic.DataVersionPersistenceTest


> State transfer and cache loading does not include optimistic node's DataVersion
> -------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:57:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 14:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBBUILD-423) Fix microcontainer
 poms and metatdata in maven repository
In-Reply-To: <15025489.1192719903676.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11291940.1192820223382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-423?page=all ]

Paul Gier closed JBBUILD-423.
-----------------------------

    Resolution: Done

> Fix microcontainer poms and metatdata in maven repository
> ---------------------------------------------------------
>
>                 Key: JBBUILD-423
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-423
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:08:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 15:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBBUILD-414) Mavenize security
	project
In-Reply-To: <22840794.1188506058257.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10170128.1192820883707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-414?page=all ]

Paul Gier reassigned JBBUILD-414:
---------------------------------

    Assignee: Paul Gier

> Mavenize security project
> -------------------------
>
>                 Key: JBBUILD-414
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-414
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The pom of the security project should be updated to fit project standards.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:10:06 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 15:10:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBBUILD-418) Figure out why
 iiop and jmx do not build from the aggregate app server build.
In-Reply-To: <31763240.1189779072625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28270930.1192821007030.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBBUILD-418?page=comments#action_12383507 ] 
            
Paul Gier commented on JBBUILD-418:
-----------------------------------

The maven issue http://jira.codehaus.org/browse/MNG-2045 has been applied, and will be released with 2.0.8.
The app server maven builds will be dependent on the 2.0.8 release of maven.

> Figure out why iiop and jmx do not build from the aggregate app server build.
> -----------------------------------------------------------------------------
>
>                 Key: JBBUILD-418
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-418
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Currently the jmx and iiop modules build fine by themselves, but do not build correctly during the aggregate build with all the modules.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:10:07 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 15:10:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBBUILD-418) Figure out why iiop
 and jmx do not build from the aggregate app server build.
In-Reply-To: <31763240.1189779072625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <746009.1192821007482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-418?page=all ]

Paul Gier closed JBBUILD-418.
-----------------------------

    Resolution: Done

When maven 2.0.8 is released, it will become a requirement for the app server builds.

> Figure out why iiop and jmx do not build from the aggregate app server build.
> -----------------------------------------------------------------------------
>
>                 Key: JBBUILD-418
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-418
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Currently the jmx and iiop modules build fine by themselves, but do not build correctly during the aggregate build with all the modules.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:32:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 19 Oct 2007 15:32:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4889) jboss-vfs 2.0.0.beta5
Message-ID: <6891938.1192822322261.JavaMail.jira@cloud.prod.atl2.jboss.com>

jboss-vfs 2.0.0.beta5
---------------------

                 Key: JBAS-4889
                 URL: http://jira.jboss.com/jira/browse/JBAS-4889
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Kabir Khan
         Assigned To: Kabir Khan
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:32:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 19 Oct 2007 15:32:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4889) jboss-vfs 2.0.0.beta5
In-Reply-To: <6891938.1192822322261.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21218803.1192822322554.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4889?page=all ]

Kabir Khan updated JBAS-4889:
-----------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> jboss-vfs 2.0.0.beta5
> ---------------------
>
>                 Key: JBAS-4889
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4889
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:35:09 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 19 Oct 2007 15:35:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4889) jboss-vfs 2.0.0.beta5
In-Reply-To: <6891938.1192822322261.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20900959.1192822509239.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4889?page=all ]

Kabir Khan closed JBAS-4889.
----------------------------

    Resolution: Done

> jboss-vfs 2.0.0.beta5
> ---------------------
>
>                 Key: JBAS-4889
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4889
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:42:19 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 19 Oct 2007 15:42:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the
 legacy configuration that embeds xml parsing
Message-ID: <5246661.1192822939716.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12383509 ] 
            
Ron Sigal commented on JBREM-63:
--------------------------------

org.jboss.remoting.transport.remoting.Connector can now be configured by way of an org.jboss.remoting.ServerConfiguration.  ServerConfiguration holds four components:

1. transport (supplied by constructor)
2. invokerLocatorParameters:  the is a map of all parameter names and values that will go into the org.jboss.remoting.InvokerLocator
3. serverParameters: this is a map of parameter names and values that will be used by the server but will not go into the InvokerLocator
4. invocationHandlers: this is a map of invocation handlers.  The key is the subsystem, or comma separated list of subsystems.

Note that parameter values in invokerLocatorParameters override values in serverParameters, if a parameter appears in both.

ServerConfiguration may be used programmatically, but it is primarily intended to be constructed from a jboss-beans.xml file by a microcontainer and injected into a Connector.

Unit test:  org.jboss.test.remoting.transport.config.POJOConfigurationTestCase.

Waiting for cruisecontrol results.

> Get rid of the legacy configuration that embeds xml parsing
> -----------------------------------------------------------
>
>                 Key: JBREM-63
>                 URL: http://jira.jboss.com/jira/browse/JBREM-63
>             Project: JBoss Remoting
>          Issue Type: Task
>    Affects Versions: 1.0.1 beta
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:44:03 2007
From: jira-events at lists.jboss.org (krish p (JIRA))
Date: Fri, 19 Oct 2007 15:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
Message-ID: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>

Portlet disappears in IE 7.0 after it is maximized
--------------------------------------------------

                 Key: JBPORTAL-1769
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Portlet
    Affects Versions: 2.6.1 Final
         Environment: Windows XP, Internet Explorer 7.0
            Reporter: krish p
         Assigned To: Julien Viet


I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.

Essentially, this is the problem:
* Add a portlet on the page.
* Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).

After doing a fair bit of testing, I've narrowed down the test case to the following:
* This does NOT reproduce in Firefox and happens only in IE
* Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 

I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).

It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:46:34 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 19 Oct 2007 15:46:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3926) Move remoting
 transports out of conf/jboss-service.xml to a remoting-beans.xml
In-Reply-To: <7741264.1165442815973.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7419622.1192823194535.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3926?page=all ]

Ron Sigal updated JBAS-3926:
----------------------------

    Assignee: Ron Sigal  (was: Dimitris Andreadis)

> Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-3926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services, Remoting
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>
> We need to remove remoting transports out of conf/jboss-service.xml to a remoting-beans.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:50:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 19 Oct 2007 15:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3926) Move remoting
 transports out of conf/jboss-service.xml to a remoting-beans.xml
In-Reply-To: <7741264.1165442815973.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27189442.1192823403371.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3926?page=comments#action_12383510 ] 
            
Ron Sigal commented on JBAS-3926:
---------------------------------

This issue depends on JBREM-63 "Get rid of the legacy configuration that embeds xml parsing".  For JBREM-63, org.jboss.remoting.transport.Connector has been changed so that the <config> parameter used in *-service.xml files to configure a server may now be replaced by an org.jboss.remoting.ServerConfiguration object, constructed from a jboss-beans.xml file by the microcontainer.

The changes for JBREM-63 are scheduled to be released in Remoting 2.4.0.

A unit test is ready to be committed, once Remoting 2.4.0 is available.

> Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-3926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services, Remoting
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>
> We need to remove remoting transports out of conf/jboss-service.xml to a remoting-beans.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 16:01:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 16:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4694002.1192824063337.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=all ]

Thomas Heute updated JBPORTAL-1769:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 16:03:03 2007
From: jira-events at lists.jboss.org (krish p (JIRA))
Date: Fri, 19 Oct 2007 16:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19012294.1192824183352.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=comments#action_12383513 ] 
            
krish p commented on JBPORTAL-1769:
-----------------------------------

It is the maximize/minimize/restore event. One of them.. I wish I could have been more specific but the problem is quite intermittent and it is hard to nail down on the simplest reproducible test case..

For instance, I tried to reproduce this again, and I got a HTTP-500 error:

URL accessed: http://portal.demo.jboss.com/auth/portal/default/default/JSPPortletWindow?windowstate=normal

Error:

javax.servlet.ServletException: java.lang.NullPointerException
	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:406)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)


root cause 

java.lang.NullPointerException
	org.jboss.portal.core.impl.model.portal.PersistentPortalObjectContainer.getObjectNode(PersistentPortalObjectContainer.java:242)
	org.jboss.portal.core.impl.model.portal.AbstractPortalObjectContainer.getContext(AbstractPortalObjectContainer.java:100)
	org.jboss.portal.core.impl.model.portal.AbstractPortalObjectContainer.getContext(AbstractPortalObjectContainer.java:80)
	org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:72)
	org.jboss.portal.core.controller.Controller.handle(Controller.java:209)
	org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
	org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
	org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:380)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)



> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:52:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 15:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14715052.1192823523430.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=comments#action_12383511 ] 
            
Thomas Heute commented on JBPORTAL-1769:
----------------------------------------

Which event are you talking about ?
Can you detail "The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point" ?

I cannot reproduce the problem with the info you provided


> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 18:57:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 18:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBBUILD-414) Mavenize security
	project
In-Reply-To: <22840794.1188506058257.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33478366.1192834623238.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-414?page=all ]

Paul Gier closed JBBUILD-414.
-----------------------------

    Resolution: Done

Anil did most of the work mavenizing the security project.  So I just had to make a couple of minor changes.

> Mavenize security project
> -------------------------
>
>                 Key: JBBUILD-414
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-414
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The pom of the security project should be updated to fit project standards.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 19:33:18 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 19 Oct 2007 19:33:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29942082.1192836798418.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=comments#action_12383517 ] 
            
Tim Fox commented on JBMESSAGING-1115:
--------------------------------------

How large were the messages?

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 02:48:03 2007
From: jira-events at lists.jboss.org (Stale Pedersen (JIRA))
Date: Sat, 20 Oct 2007 02:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-265) Aspectize Java array
Message-ID: <3132734.1192862883768.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-265?page=all ]

Stale Pedersen closed JBAOP-265.
--------------------------------

    Resolution: Done

committed and tested

> Aspectize Java array
> --------------------
>
>                 Key: JBAOP-265
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-265
>             Project: JBoss AOP
>          Issue Type: Feature Request
>            Reporter: Ben Wang
>         Assigned To: Stale Pedersen
>             Fix For: 2.0.0.beta2
>
>
> For AOP, we haven't dealt with Java array. Is it possible to provide interception for array? This is required if we need to instrument Java Collection, for example, since they uses array list for internal fields.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 06:03:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5717050.1192874583877.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox reopened JBMESSAGING-1099:
----------------------------------

             
I am re-opening because Clebert's fix to ConsumerAspect is wrong and breaks failover.

Try running MergeQueueTest a few times to see it fail.

The problem with the fix is that it always closes the ClientConsumer in a finally block.

For failover a MessagingNetworkFailed exception would be thrown, and failover would eventually retry after failover.

But by then the ClientConsumer had been closed.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 06:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 06:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10939888.1192874943537.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                       (was: 1.4.0.SP1)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 06:36:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sat, 20 Oct 2007 06:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3389000.1192876563303.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=all ]

Geoffrey De Smet resolved JBRULES-1288.
---------------------------------------

    Resolution: Done

cleaned out

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 07:37:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 07:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6621978.1192880223321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox reopened JBMESSAGING-1096:
----------------------------------

      Assignee: Tim Fox  (was: Clebert Suconic)
             
No the bisocket is NOT already documented.

Re-opening.

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 08:21:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 08:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19304047.1192882863692.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox closed JBMESSAGING-1096.
--------------------------------

    Resolution: Done

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 08:21:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 08:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1114) JBoss Remoting
 fails under load
In-Reply-To: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30461631.1192882863865.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=all ]

Tim Fox closed JBMESSAGING-1114.
--------------------------------

    Resolution: Done

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBMESSAGING-1114
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000 
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Sat Oct 20 09:20:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 09:20:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1199) Update
 InvalidatorInterceptorTest to use Node.isValid()
In-Reply-To: <2782171.1192635603222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15690723.1192886414171.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1199?page=all ]

Manik Surtani updated JBCACHE-1199:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Update InvalidatorInterceptorTest to use Node.isValid()
> -------------------------------------------------------
>
>                 Key: JBCACHE-1199
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node.  See the forum link.  Need to replace with a call to isValid() whenever that is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:36:07 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:36:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1289) BRMS gives
 unusable error messages when validating DSL based rules
Message-ID: <12543965.1192890967500.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS gives unusable error messages when validating DSL based rules
------------------------------------------------------------------

                 Key: JBRULES-1289
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1289
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


The error messages that are shown when you click "Validate" when editing a business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small typo and misspell the name of an attribute (a very likely thing for a BRMS user to do), and click the Validate button, the error I get back is a big stack trace starting with "java.lang.RuntimeException: SNO: Conversion failed at org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere in that stack trace is anything that gives a hint that
the error is just a typo of an attribute name.

Contrast this with the rather helpful error message I get if I make the same typo when editing a DRL rule: "Unable to create Field Extractor for 'overtimHours'". (The error is that I misspelled overtimeHours). 

The BRMS needs to give the same type of helpful error message on validation errors when editing a DSL rule.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:42:03 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1290) BRMS does not
 allow rule names to contain an apostrophe character ( ' )
Message-ID: <25881085.1192891323312.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS does not allow rule names to contain an apostrophe character ( ' )
-----------------------------------------------------------------------

                 Key: JBRULES-1290
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1290
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


Rules with apostrophe characters are rejected by the BRMS. For example the rule name "Set employee's wage" works outside BRMS, but does not work in BRMS.

If you attempt to enter a rule through the BRMS containing an apostrophe,the error stack trace says "An error occurred executing the action.
Details
com.google.gwt.user.client.rpc.SerializableException:
javax.jcr.RepositoryException: failed to resolve path Set employee's relative to /drools:repository/drools:package_area/com.example/assets: Invalid name: Set employee's wage: Invalid name: Set employee's wage at
org.drools.brms.server.ServiceImplementation.createNewRule(ServiceImplementation.java:166)..."

If you attempt to import a .drl file with a rule that has an apostrophe in the title, you'll get this error message
(including the <pre> tags): "Unable to import into the package. [<pre>Unable to process import: javax.jcr.RepositoryException: failed
to resolve path Set employee's wage relative to /drools:repository/drools:package_area/com.soi/assets: Invalid name: Set employee's  wage: Invalid name: Set employee's wage</pre>]".

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:44:03 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1291) BRMS does not
 allow import of .dslr files
Message-ID: <26814116.1192891443260.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS does not allow import of .dslr files
-----------------------------------------

                 Key: JBRULES-1291
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1291
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


The documentation (section 6.7.3) says that .drl files that use a DSL should be renamed to .dslr to work better in the IDE. The BRMS does not allow importing of .dslr files. Renaming the file back to .drl works.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:46:03 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1292) BRMS ignores
 "initial
 description" entered when creating new "Business rule using a DSL (text
 editor)" rule
Message-ID: <7897053.1192891563924.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS ignores "initial description" entered when creating new "Business rule using a DSL (text editor)" rule
-----------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1292
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1292
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


When creating a new rule asset through the BRMS using the type "Business rule using a DSL (text editor)", the initial description you put in is ignored. You always get the description "A dsl is a language mapping from a domain specific language to the rule language."

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:41:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 12:41:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1202) State transfer
 and cache loading does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21251551.1192898466524.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani resolved JBCACHE-1202.
------------------------------------

    Resolution: Done

> State transfer and cache loading does not include optimistic node's DataVersion
> -------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:43:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 12:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1188)
 UnversionedNode.isValid - out
 of sync (deleted/remotely deleted nodes)
In-Reply-To: <1073686.1190216951047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7602284.1192898583342.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1188?page=all ]

Manik Surtani updated JBCACHE-1188:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA
                       (was: 2.2.0.GA)
         Assignee: Manik Surtani  (was: Mircea Markus)

> UnversionedNode.isValid - out of sync (deleted/remotely deleted nodes)
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1188
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1188
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>         Environment: all
>            Reporter: Mircea Markus
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> considering the scenario:
> thread1: 
> node = cache.get("a/b/c");
> thread2(possibly running on another node/JVM):
> cache.remove("a/b/c");
> thread1: 
> node.getAttribute("attr1");//at this point the node is not longer in the cache. we should allow user to check this through isValid
> node.getAttribute("attr2");

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:47:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 12:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1198)
 putForExternalRead not silent on remote node
In-Reply-To: <22737059.1192591803386.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23708711.1192898823482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1198?page=all ]

Manik Surtani resolved JBCACHE-1198.
------------------------------------

    Resolution: Done

> putForExternalRead not silent on remote node
> --------------------------------------------
>
>                 Key: JBCACHE-1198
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1198
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Seeing WARN logging like this when using PFER with a replicating cache:
> 22:16:37,931  WARN pessimistic-shared:2839 - replication failure with method_call MethodName: _putForExternalRead; MethodIdInteger: 45; Args: (null, /test/com/foo/test/ENTITY/KEY, item, VALUE1) exception
> org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/test/com/foo/test/ENTITY/KEY, caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock=write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299)
> 	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
> 	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3958)
> 	at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2826)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330)
> 	at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77)
> 	at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624)
> 	at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533)
> 	at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365)
> 	at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:744)
> 	at org.jgroups.JChannel.up(JChannel.java:1137)
> 	at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:999)
> 	at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1023)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.cache.lock.TimeoutException: write lock for /test/com/foo/test/ENTITY/KEY could not be acquired after 0 ms. Locks: Read lock owners: []
> Write lock owner: GlobalTransaction:<192.168.1.145:35562>:1
>  (caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock info: write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0))
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
> 	... 33 more
> Issue seems to be that the logic in CacheImpl.putForExternalRead that makes the call a no-op if the node exists and sets the failSilently option otherwise never gets executed on the remote node.  Instead the call gets handled by _replicate which just passes the MethodCall into the interceptor chain without setting any options.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:51:03 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Sat, 20 Oct 2007 12:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27928854.1192899063310.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Shigeru Chiba resolved JASSIST-37.
----------------------------------

    Resolution: Done

I have implemented initializers for boolean, byte, short, char.

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 13:04:03 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Sat, 20 Oct 2007 13:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25850183.1192899843299.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Shigeru Chiba closed JASSIST-37.
--------------------------------


and the initializer for float.

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 13:16:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 13:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23550129.1192900563609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Manik Surtani updated JBCACHE-1201:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097198
               Complexity: High

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 15:30:03 2007
From: jira-events at lists.jboss.org (Stan Silvert (JIRA))
Date: Sat, 20 Oct 2007 15:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4130) Simple HelloWorld
 JSF 1.2 application does not work
In-Reply-To: <28586848.1172070275576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31381363.1192908603339.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4130?page=comments#action_12383554 ] 
            
Stan Silvert commented on JBAS-4130:
------------------------------------

I tried creating a simple JSF app with visual web pack and I got this error:

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed
 to resolve schema nsURI=http://java.sun.com/JSF/Configuration location=null
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:203)

Is that the first one you saw?  Exactly which file did you put in jboss.jar to get past the problem?

It is strange that you would have a problem with that schema definition in your managed-beans.xml.  The faces-config.xml in the hellojsf-correted.war at the bottom of this page uses the exact same definition and it deploys without errors:
http://wiki.jboss.org/wiki/Wiki.jsp?page=HelloJSF

Also, I noticed that visual web pack creates a J2EE 1.4 JSF application.  It includes the jsf-impl.jar, jsf-api.jar, and jstl.jar.  You don't want to have these in your WAR on JBoss 5 because they might interfere with the versions already present in the JBoss 5 distribution.

Stan

> Simple HelloWorld JSF 1.2 application does not work
> ---------------------------------------------------
>
>                 Key: JBAS-4130
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4130
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JSF
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: Windows XP,  Suse 10.2
>            Reporter: sedat ciftci
>         Assigned To: Stan Silvert
>
>  I have faced with a problem while deploying my JSF 1.2 web application (sun impl) ( I build with Netbeans 5.5 Visual Web pack) to JBoss5 Beta. It works with Glassfish. In order to find the problem, I make a simple Hello world web application and try to deploy it to JBoss5Beta. However, I get the same exception.
> The first exception that I overcome is related with web-facesconfig_1_2.xsd. JBoss says that it can not resolve this schema. I solve this problem by putting this file into the jboss.jar/schema.
> The second exception that I cannot solve is although my projects managed-beans.xml file is well formed, JBoss throws such an exception:
> org.jboss.deployers.spi.DeploymentException: The xml JBoss5Ex.war/WEB-INF/managed-beans.xml is not well formed!
> at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:94)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:173)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88)
> at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59)
> at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
> at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
> at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
> at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:508)
> at java.lang.Thread.run(Thread.java:595)
> Note that JBoss5Ex.war is my web application. 
>  Here is the content of my managed-beans.xml file (starting after the #'s line):
> ######################################
> <?xml version="1.0" encoding="UTF-8"?>
> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd">
> <managed-bean>
> <managed-bean-name>SessionBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.SessionBean1</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>Page1</managed-bean-name>
> <managed-bean-class>jboss5ex.Page1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>ApplicationBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.ApplicationBean1</managed-bean-class>
> <managed-bean-scope>application</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>RequestBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.RequestBean1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> </faces-config>
> #################################################

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 17:38:09 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sat, 20 Oct 2007 17:38:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1230) Not able to run
 drools if
 core-3.2.3.v_686_R32x.jar is not specified in the classpath
In-Reply-To: <27431141.1190987681381.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19450071.1192916289129.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1230?page=comments#action_12383558 ] 
            
Mark Proctor commented on JBRULES-1230:
---------------------------------------

I assume this jira is for when you are compiling and all rules are using he MVEL dialect, but it's still complaining about janino or jdt? If janino is configured it should definitely not still require jdt core.

> Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath
> -------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1230
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1230
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions:  4.0.0.GA
>         Environment: Windows XP, Dell Optiplex GX 270
>            Reporter: Krishnan Sivaramakrishna Iyer
>         Assigned To: Mark Proctor
>            Priority: Blocker
>
> hi all,
> In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies
> documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_DEPENDENCIES.txt
> , it seems I am in the compiler option
> The only jars I am including are as follows :-
> drools-compiler-4.0.0.jar
> drools-core-4.0.0.jar
> drools-decisiontables-4.0.0.jar
> drools-jsr94-4.0.0.jar
> antlr-runtime-3.0.jar
> mvel14-1.2rc1.jar
> core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I
> don't specify this, it does not work ?.]
> I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also
> expects the core to be included. Any help is appreciated.
> TIA,
> Krishnan. 
> Comments from Edson Tirelli 
> Krishnan,
>     You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix.
>     []s
>     Edson

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 04:18:08 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Sun, 21 Oct 2007 04:18:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5109102.1192954688224.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383571 ] 
            
Johannes Fiala commented on JBPORTAL-1759:
------------------------------------------

Yes, exactly - I'm issuing a GET-request (manually by editing the url address input of the browser). In this case browsers seem to neglect the correct utf-8 encoding of the url before doing the url encoding).

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Sun Oct 21 09:36:03 2007
From: jira-events at lists.jboss.org (Wolfgang Knauf (JIRA))
Date: Sun, 21 Oct 2007 09:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4361)
 java.util.logging.FileHandler.formatter cannot be changed to
 java.util.logging.SimpleFormatter
In-Reply-To: <24133361.1177358310492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10845202.1192973763667.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4361?page=all ]

Wolfgang Knauf closed JBAS-4361.
--------------------------------

    Resolution: Rejected

Yes, you are right, there was a space. I'm ashamed of not seeing it !

> java.util.logging.FileHandler.formatter cannot be changed to java.util.logging.SimpleFormatter
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4361
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4361
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.0.CR2
>         Environment: JDK is 1.5.0_11-b03
>            Reporter: Wolfgang Knauf
>         Assigned To: Scott M Stark
>            Priority: Minor
>
> I tried to create a plain text log output with this logging.properties file:
> handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler
> .level= INFO
> java.util.logging.FileHandler.pattern = c:/temp/logfile.log 
> java.util.logging.FileHandler.level = INFO
> java.util.logging.FileHandler.limit = 50000
> java.util.logging.FileHandler.count = 1
> java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter 
> java.util.logging.ConsoleHandler.level = INFO
> java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
> I startup the server with this commandline:
> run.bat -c default -Djava.util.logging.config.file=c:/temp/logging.properties
> The log file is placed in c:\temp\logfile.log and contains my output, but it is in XML, not in Simple format. Console output is in SimpleFormat as expected.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 10:00:09 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Sun, 21 Oct 2007 10:00:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30844363.1192975209028.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383581 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

I did have juddi-service.sar deployed in the earlier runs.
The following tests pass when juddi-service.sar is deployed under the DEFAULT config in an EXPLODED form ONLY, which is the way i have configured hudson now.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBossWS-2.0.1.SP2-testsuite-AS4.2.x/
org.jboss.test.ws.jaxws.samples.jaxr.scout.publish.JaxrDeleteOrganizationTestCase
org.jboss.test.ws.jaxws.samples.jaxr.scout.publish.JaxrSaveOrganizationTestCase
org.jboss.test.ws.jaxws.samples.jaxr.scout.query.JaxrBusinessQueryTestCase

In the earlier runs the tests failed, when i ran against the ALL config with juddi-service deployed, because the tests were still looking for juddi-service under the DEFAULT config.

When i ran the tests using the DEFAULT config with juddi-service.sar deployed in an UNEXPLODED form the tests still failed because it could not find the scout.jar which was inside the sar.

In both the cases the error was java.lang.ClassNotFoundException: org.apache.ws.scout.registry.ConnectionFactoryImpl

I'm not sure if this is a bad test or potential bug, Thomas could you take a look?
I would like to change the hudson job to run in one of the last 2 ways mentioned above so no bugs are missed.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 11:35:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Sun, 21 Oct 2007 11:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4945690.1192980903327.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383592 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

Shouldn't the tests be such so they run on a out-of-the box AS? Or if they require a different configuration, create it, as part of the test?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 12:48:04 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 21 Oct 2007 12:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14785160.1192985284434.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=all ]

Geoffrey De Smet reopened JBRULES-1288:
---------------------------------------

             
it broke the build:
https://hudson.jboss.org/hudson/job/drools/919/testReport/

mvel is not mvel14, apparently it's a different flavor of the same version - this is probably the problem

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 15:09:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 21 Oct 2007 15:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1541355.1192993743424.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=all ]

Geoffrey De Smet resolved JBRULES-1288.
---------------------------------------

    Resolution: Partially Completed

Revert the changes for mvel, as mvel != mvel14.

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 00:34:03 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Mon, 22 Oct 2007 00:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (BPEL-281) apache ant support
Message-ID: <19912563.1193027643410.JavaMail.jira@cloud.prod.atl2.jboss.com>

apache ant support
------------------

                 Key: BPEL-281
                 URL: http://jira.jboss.com/jira/browse/BPEL-281
             Project: JBoss jBPM BPEL
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Engine
            Reporter: Alejandro Guizar
         Assigned To: Alejandro Guizar
             Fix For: jBPM BPEL 1.1 GA


The web console provides a user interface to perform the following tasks.

1. Database administration
2. Process deployment
3. Partner registration

For integration purposes, the ability to invoke the above tasks from an Ant script is highly desirable.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:08:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1116) Fail-over
 does not complete if a node different from the "active" one fails
Message-ID: <10435351.1193029683486.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fail-over does not complete if a node different from the "active" one fails
---------------------------------------------------------------------------

                 Key: JBMESSAGING-1116
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Critical
             Fix For: 1.4.0.SP1


This is how to replicate it:

- Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A
- Start consuming concurrently using 50 parallel consumers over a connection to node A
- Kill node B

The consumption rate drop to 0 and never recovers.
Trying to close the connection on the client-side never completes.
Trying to shut down node A fails, need to eventually kill it.



-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:30:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26204852.1193031003430.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1109:
-----------------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)

I have not seen this anymore with r3237, while testing it by sending/receiving in parallel over 50-100 sessions. Probably safe to close. I will re-open if I see it again.

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:30:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6275279.1193031003696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1110:
-----------------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)

I have not seen this anymore with r3237, while testing it by sending/receiving in parallel over 50-100 sessions. Probably safe to close. I will re-open if I see it again.

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:32:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27563489.1193031123444.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1112:
-----------------------------------------


I have not seen this anymore with r3237, while testing it by sending/receiving in parallel over 50-100 sessions. Probably safe to close. I will re-open if I see it again.

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>         Attachments: messkit.zip
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:32:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1116) Consuming
 client grinds to
 a halt if a node different from the "active" one fails
In-Reply-To: <10435351.1193029683486.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10348228.1193031123653.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1116?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1116:
-----------------------------------------

    Summary: Consuming client grinds to a halt if a node different from the "active" one fails  (was: Fail-over does not complete if a node different from the "active" one fails)

> Consuming client grinds to a halt if a node different from the "active" one fails
> ---------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1116
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> This is how to replicate it:
> - Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A
> - Start consuming concurrently using 50 parallel consumers over a connection to node A
> - Kill node B
> The consumption rate drop to 0 and never recovers.
> Trying to close the connection on the client-side never completes.
> Trying to shut down node A fails, need to eventually kill it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:27:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1283) Unable to
 serialize rule base ( NotSerializableException:
 org.drools.base.FireAllRulesRuleBaseUpdateListener)
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22677479.1193034423320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=all ]

Mark Proctor closed JBRULES-1283.
---------------------------------

    Resolution: Done

> Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2_SOA_4.2-CP01, 4.0.3, 4.1.0
>
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:44:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1282) Problems uploading
 models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8013541.1193035443257.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Mark Proctor closed JBRULES-1282.
---------------------------------

    Resolution: Done

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.2_SOA_4.2-CP01, 4.0.3, 4.1.0
>
>         Attachments: cumulative_patch.patch
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1230) Not able to run
 drools if
 core-3.2.3.v_686_R32x.jar is not specified in the classpath
In-Reply-To: <27431141.1190987681381.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9747500.1193035683517.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1230?page=comments#action_12383643 ] 
            
Mark Proctor commented on JBRULES-1230:
---------------------------------------

btw you know you actually need to remove the java dialect to avoid this? Otherwise whether you use the java dialect in a rule or not, the java dialect plugin is initialised and thus the need for the dependency.

> Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath
> -------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1230
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1230
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions:  4.0.0.GA
>         Environment: Windows XP, Dell Optiplex GX 270
>            Reporter: Krishnan Sivaramakrishna Iyer
>         Assigned To: Mark Proctor
>            Priority: Blocker
>
> hi all,
> In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies
> documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_DEPENDENCIES.txt
> , it seems I am in the compiler option
> The only jars I am including are as follows :-
> drools-compiler-4.0.0.jar
> drools-core-4.0.0.jar
> drools-decisiontables-4.0.0.jar
> drools-jsr94-4.0.0.jar
> antlr-runtime-3.0.jar
> mvel14-1.2rc1.jar
> core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I
> don't specify this, it does not work ?.]
> I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also
> expects the core to be included. Any help is appreciated.
> TIA,
> Krishnan. 
> Comments from Edson Tirelli 
> Krishnan,
>     You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix.
>     []s
>     Edson

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:50:14 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:50:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16016287.1193035814662.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12383644 ] 
            
Mark Proctor commented on JBRULES-1273:
---------------------------------------

we cannot progress this without the code being attached to the jira.

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Mark Proctor
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 03:31:03 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Mon, 22 Oct 2007 03:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-37) include snap to grid
In-Reply-To: <30030403.1168963978540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3323630.1193038263980.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-37?page=comments#action_12383648 ] 
            
David Roberts commented on GPD-37:
----------------------------------

I would love the designer to be able to simply straighten transition lines with the click of a mouse. I spend so much time trying to straighten transition lines before I deploy, and sometimes it takes me 5 minutes just to get one line to look straight. And when you have about 20 lines to neaten up, it takes forever. Then any changes to the flow, and you have to do it again. Trying to move a line ever so slightly to straighten it is near impossible, you have to move it quite a distance first, then drag it back and hope it is straight. Perhaps just right clicking on a transition line, and selecting "straighten" or "snap to grid" would save many hours of frustration for many people im sure.

> include snap to grid
> --------------------
>
>                 Key: GPD-37
>                 URL: http://jira.jboss.com/jira/browse/GPD-37
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> While designing processes, it would be a lot easier if there is some kind of 'snap to grid'. You can then have easier manual allignment etc. Besides that, the images look better
> - transitions should snap to the grid to
> - transitions should be perpendicular at least if there are more than three points in the line 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 04:36:03 2007
From: jira-events at lists.jboss.org (Rainer Langbehn (JIRA))
Date: Mon, 22 Oct 2007 04:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27790668.1193042163548.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12383653 ] 
            
Rainer Langbehn commented on JBRULES-1273:
------------------------------------------

Hi Mark,

some refactoring was necessary and I prepared some examples. I will attach the code shortly.

Bye

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Mark Proctor
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:03:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <293608.1193047383385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis updated JBAS-4811:
-------------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
                       (was: JBossAS-4.2.3.GA)

Setting release version back to 2.2.2.GA

I've also recreated the tag:
https://svn.jboss.org/repos/jbossas/tags/JBoss_4_2_2_GA/

All the testsuites pass, as far as I can see.

Rajesh, can we release today (Oct/22nd) ?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:16:03 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4832) TECH REVIEW:
 Getting Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17896578.1193048163399.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4832?page=comments#action_12383656 ] 
            
Luc Texier commented on JBAS-4832:
----------------------------------

What does "Out of Date" mean for this task?

Clearly this document requires some work although it should be included in the installation guide. Installing a datasource in JBossAS is a typical task

> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:50:03 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 06:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33255918.1193050203327.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12383660 ] 
            
Luc Texier commented on JBAS-4819:
----------------------------------

The JBoss Support Team will review these documents and make the appropriate changes accordingly



> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:52:03 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 06:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4832) TECH REVIEW:
 Getting Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9937495.1193050323350.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4832?page=comments#action_12383661 ] 
            
Luc Texier commented on JBAS-4832:
----------------------------------

Oh I see, this has been moved to Chapter 6. Please discard my last comment.


> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 06:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30826986.1193050443417.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12383662 ] 
            
Dimitris Andreadis commented on JBAS-4819:
------------------------------------------

Luc, this is fantastic news :-)

> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 07:58:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 07:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4890) EJBAccessException:
 Caller unauthorized
Message-ID: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJBAccessException: Caller unauthorized
---------------------------------------

                 Key: JBAS-4890
                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Anil Saldhana




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 07:59:26 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 07:59:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4890) EJBAccessException:
 Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29035286.1193054366260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4890?page=all ]

Thomas Diesler updated JBAS-4890:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED

13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.ejb.EJBAccessException: Caller unauthorized
        at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)



> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:03:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Mon, 22 Oct 2007 08:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1022) 3.2.1 Admin Console:
 Any user sees all users tasks
In-Reply-To: <6696155.1184871647115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25666160.1193054583522.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1022?page=all ]

Ronald van Kuijk updated JBPM-1022:
-----------------------------------

        Fix Version/s: jBPM jPDL 3.2.3
    Affects Version/s: jBPM jPDL 3.2.2

more and more people have a 'problem' with this. Although it is currently as designed (at least intended by the person who created the console) I think the term 'bug' is correct, since it is totally unexpected behaviour by lots of people and  therefore  I put 3.2.3 as a 'fix version' . Any work on this being done?

> 3.2.1 Admin Console: Any user sees all users tasks 
> ---------------------------------------------------
>
>                 Key: JBPM-1022
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1022
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions:  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>            Reporter: Burr Sutter
>         Assigned To: Tom Baeyens
>            Priority: Blocker
>             Fix For: jBPM jPDL 3.2.3
>
>
> In the current Admin Console, any given user will see all other users tasks.  Plus a user can "take" another person's assigned tasks even when they are not an "administrator".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:05:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 08:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4890)
 EJBAccessException: Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9056083.1193054703338.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4890?page=comments#action_12383667 ] 
            
Thomas Diesler commented on JBAS-4890:
--------------------------------------

The authorization comming from tomcat seems to be ok

Subject:
	Principal: kermit
	Principal: Roles(members:friend)


> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:13:03 2007
From: jira-events at lists.jboss.org (Burr Sutter (JIRA))
Date: Mon, 22 Oct 2007 08:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin
 Console: Any user sees all users tasks
In-Reply-To: <6696155.1184871647115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20034816.1193055183403.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12383669 ] 
            
Burr Sutter commented on JBPM-1022:
-----------------------------------

Do you believe the jBPM userbase considers this console to be something they can deploy into a production setting? Or is it still considered to be a sample/demo tool for interacting with quickly prototyped process definitions?




> 3.2.1 Admin Console: Any user sees all users tasks 
> ---------------------------------------------------
>
>                 Key: JBPM-1022
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1022
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions:  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>            Reporter: Burr Sutter
>         Assigned To: Tom Baeyens
>            Priority: Blocker
>             Fix For: jBPM jPDL 3.2.3
>
>
> In the current Admin Console, any given user will see all other users tasks.  Plus a user can "take" another person's assigned tasks even when they are not an "administrator".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:26:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 22 Oct 2007 08:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9255070.1193055963357.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383670 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

I am waiting on Thomas's comment on the above. The way we are running the JBossWS testsuite could be hiding a potential bug.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:45:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 22 Oct 2007 08:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32062198.1193057103468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Tim Fox closed JBMESSAGING-1110.
--------------------------------

    Resolution: Done

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:45:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 22 Oct 2007 08:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23947477.1193057103825.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox closed JBMESSAGING-1112.
--------------------------------

    Resolution: Done

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>         Attachments: messkit.zip
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:47:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 22 Oct 2007 08:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5296993.1193057223555.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Tim Fox closed JBMESSAGING-1109.
--------------------------------

    Resolution: Done

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:49:04 2007
From: jira-events at lists.jboss.org (David Bala?ic (JIRA))
Date: Mon, 22 Oct 2007 08:49:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-698) Exception
 serialization issue when remotely accessing stateless session bean
In-Reply-To: <23517647.1157576669733.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18554030.1193057344675.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-698?page=comments#action_12383671 ] 
            
David Bala?ic commented on EJBTHREE-698:
----------------------------------------

I have the same problem (on version 4.0.4GA , JDK 1.5.0_12  Windows XP).

And (fanfares...) I found a workaround.
If the exception is ClassNotFoundException: [Lcom.foo.Bar;

then just add a line in the client before the remote call :

import com.foo.Bar;
...

Bar [] dummy = { new Bar() };
remObj.yourRemoteCall(x,y,z);


It seems the JVM "forgets" to load (or create, array classes can not be loaded...) the class definition for "array of SomeClass", to that line of code "forces" it to do so before the call (when the definition is then required/used).

> Exception serialization issue when remotely accessing stateless session bean
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-698
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-698
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: David Green
>
> Accessing a remote EJB (Session bean) results in exception.  Stack trace follows:
> 13:54:39,546 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> 	at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
> 	at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> 	at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
> 	at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
> 	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
> 	at org.jboss.remoting.Client.invoke(Client.java:525)
> 	at org.jboss.remoting.Client.invoke(Client.java:488)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> 	at $Proxy0.postNotification(Unknown Source)
> 	at com.hgea.hch.service.HchClientDelegate.postNotification(HchClientDelegate.java:99)
> 	at com.hgea.hch.client.RemoteHchClientTest.testRemotePostNotification(RemoteHchClientTest.java:38)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
> 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672)
> 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:03:03 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Mon, 22 Oct 2007 09:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22437634.1193058183334.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4880?page=all ]

Colin Mondesir reassigned JBAS-4880:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4880
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:05:31 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 09:05:31 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7807529.1193058331654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Luc Texier reassigned JBAS-4830:
--------------------------------

    Assignee: Luc Texier

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:19:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 09:19:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6546069.1193059145145.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383672 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

C'mon guys, this really looks like a non-issue to me.

Since the 'all' configuration of jboss contains an unexploded juddi-service.sar with scout.jar inside, the test classpath should be changed to look there for the libraries. Or even look for scout.jar in the client libraries directory, it is there, too.

So either make this modification and re-tag jbossws-2.0.1.SP2, or hack the hudson build (like Rajesh has done already AFAIK) and fix it later in jbossws.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:21:03 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 22 Oct 2007 09:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1073) Allow mail attribute
 'to' resolve EL Expressions
Message-ID: <18645462.1193059263442.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow mail attribute 'to' resolve EL Expressions
------------------------------------------------

                 Key: JBPM-1073
                 URL: http://jira.jboss.com/jira/browse/JBPM-1073
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
            Reporter: Fady Matar
         Assigned To: Tom Baeyens
             Fix For: jBPM jPDL 3.2.3


Allow the attribute 'to' in the mail module to resolve EL expressions. Currently the 'to' attribute only encodes hard coded emails

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:37:35 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 09:37:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28573803.1193060255589.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383677 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

There is a switch where this is configurable.

jboss.server.instance=default

I also think this is a non-issue


> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 09:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14593321.1193060583401.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383680 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I looked at you hudson script. I think this looks ok and we really don't have a hidden issue.
AFAIK, you can close this issue.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:48:14 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 22 Oct 2007 09:48:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3700243.1193060894428.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383681 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

Since you had a look at the hudson script, currently i unzip the juddi-service.sar in the default/deploy directory.
unzip thirdparty/juddi-service.sar -d $WORKSPACE/$DIST_NAME/server/default/deploy/juddi-service.sar/

instead if i just copy the sar, the tests fail.
cp thirdparty/juddi-service.sar $WORKSPACE/$DIST_NAME/server/default/deploy/

Do you know why that happens?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:00:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 22 Oct 2007 10:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-180) Problems with delete
	of start state
Message-ID: <4703392.1193061603580.JavaMail.jira@cloud.prod.atl2.jboss.com>

Problems with delete of start state
-----------------------------------

                 Key: GPD-180
                 URL: http://jira.jboss.com/jira/browse/GPD-180
             Project: JBoss jBPM GPD
          Issue Type: Bug
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
            Reporter: Koen Aers
         Assigned To: Koen Aers
             Fix For: jBPM jPDL Designer 3.1.1




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:00:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 22 Oct 2007 10:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-180) Problems with delete
	of start state
In-Reply-To: <4703392.1193061603580.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16544696.1193061603979.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-180?page=all ]

Koen Aers updated GPD-180:
--------------------------

    Component/s: jpdl

> Problems with delete of start state
> -----------------------------------
>
>                 Key: GPD-180
>                 URL: http://jira.jboss.com/jira/browse/GPD-180
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 10:11:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24984284.1193062267870.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383684 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

Because-most probably- the test puts server/default/deployjuddi-service.sar/scout.jar in the classpath. If you don't unzip, it cannot see it.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:09 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 10:11:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19871460.1193062269815.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4823?page=comments#action_12383685 ] 
            
Luc Texier commented on JBAS-4823:
----------------------------------

 The JBoss Support Team will review these documents and make the appropriate changes accordingly 

> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:10 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 10:11:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15749551.1193062270009.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383686 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I  don't unfortunately, Maybe you should talk to Dimitris on whether this is a general issue that needs to get looked in to for 4.2.3

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:10 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 10:11:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6275726.1193062270171.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12383687 ] 
            
Luc Texier commented on JBAS-4819:
----------------------------------

You're welcome Big Daddy...



> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:19:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1729) AjaxInterceptor
 with a different context root
In-Reply-To: <13290468.1191167861321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18376798.1193062743767.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1729?page=all ]

Thomas Heute updated JBPORTAL-1729:
-----------------------------------

    Assignee: Thomas Heute

> AjaxInterceptor with a different context root
> ---------------------------------------------
>
>                 Key: JBPORTAL-1729
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1729
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.1 Final
>         Environment: fedora 7, eclipse europa, java 5 update 12
>            Reporter: Luca Stancapiano
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>         Attachments: patch_AjaxInterceptor.zip
>
>
> about org.jboss.portal.core.controller.ajax.AjaxInterceptor class
> row 75:
> pageProps.put(DynaConstants.RESOURCE_BASE_URL, "/portal-ajax/dyna");
> It uses a static hard coded link to use portal-ajax application , but if we need to change context root, it points to the same link and so in some cases there can to be redirect problems.
> In my case, I have two portal instances on two different hosts and through mod_jk I redirect the first instance using /portal* path and the second with /two_portal* path.
> I cannot o use /portal-ajax path from the second host because mod_jk see that path and it redirects to the first portal instance, then I need to use a different path else I pay a unnecessary connection.
> To resolve this problem I added a property TargetContextPath (as for org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor class) into AjaxInterceptor and substituted it to /portal-ajax/ link.
> private String targetContextPath = "/portal-ajax";
>    public String getTargetContextPath()
>    {
>       return targetContextPath;
>    }
>    public void setTargetContextPath(String context)
>    {
>       targetContextPath = context;
>    }
> it can to be configured through AjaxInterceptor MBean into META-INF/jboss-service.xml. Here there is an example:
>    <mbean
>       code="org.jboss.portal.core.controller.ajax.AjaxInterceptor"
>       name="portal:service=Interceptor,type=Command,name=Ajax"
>       xmbean-dd=""
>       xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
>       <xmbean/>
>       <attribute name="TargetContextPath">/portal-ajax</attribute>
>    </mbean>

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:21:31 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:21:31 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1730)
 IdentityServiceControllerImpl
 : unregister existing MBean service before to re register them
In-Reply-To: <4337065.1191178121268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23295407.1193062891885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=all ]

Thomas Heute updated JBPORTAL-1730:
-----------------------------------

    Assignee: Thomas Heute

> IdentityServiceControllerImpl : unregister existing MBean service before to re register them
> --------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1730
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
> the Identity Beans are registered as JMX MBeans.
> When redeploying the service, an exception is thrown, as the services are yet deployed.
> javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
> Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
> // Unregister the former service is if it is yet there.
> // This to avoid the exception when redeploying this service
> if (getServer().isRegistered(
> 		new ObjectName(module.getServiceName()))) {
> 	getServer().unregisterMBean(
> 			new ObjectName(module.getServiceName()));
> }
> Thanks,

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:29:05 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:29:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1765) Adapt the
 admin portlet to let the user set a default window state
In-Reply-To: <32743739.1192742134373.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23107729.1193063345568.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1765?page=comments#action_12383694 ] 
            
Thomas Heute commented on JBPORTAL-1765:
----------------------------------------

The back end is done ;)

One constraint is that only 1 window can be set as maximized.
But several windoes can be set as minimized.

> Adapt the admin portlet to let the user set a default window state
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1765
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1765
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Thomas Heute
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> We'll need to be able to define which window (if any) of a page should be maximized when a window opens, we'll also need to define if a window must first be displayed as minimized.
> The back end is not done 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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:33:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1770) Display icons in
 portlets list and provide icons for portlets
Message-ID: <25521218.1193063583429.JavaMail.jira@cloud.prod.atl2.jboss.com>

Display icons in portlets list and provide icons for portlets
-------------------------------------------------------------

                 Key: JBPORTAL-1770
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1770
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
            Reporter: Thomas Heute
         Assigned To: Wesley Hales
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:37:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 22 Oct 2007 10:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24212646.1193063823354.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383697 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

Since this is mostly an issue on the test side i am going to ignore this issue for this release.
Also since Thomas is not able to reproduce this, there is no point waiting here.

Not sure what the status of this issue should say, I will leave it to Dimitris.
Going ahead with the release.

I am also reverting the hudson job to the earlier way in which the error can be reproduced.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:43:14 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 10:43:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25129739.1193064194873.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383701 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

Rajesh, there is no web service specific error. Please leave it as it is. Otherwise we won't be able to detect regression.

That a class from a jar from inside a sar cannot be loaded is a general AS issue.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:51:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4891) Cannot unmarshall
	qname elements
Message-ID: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot unmarshall qname elements
--------------------------------

                 Key: JBAS-4891
                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:53:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Mon, 22 Oct 2007 10:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-424) Look into
 combining default pom and jdk14 poms.
Message-ID: <26016287.1193064783660.JavaMail.jira@cloud.prod.atl2.jboss.com>

Look into combining default pom and jdk14 poms.
-----------------------------------------------

                 Key: JBBUILD-424
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-424
             Project: JBoss Build System
          Issue Type: Task
          Components: Maven
            Reporter: Paul Gier
             Fix For: Maven Build - Maint 2007


Having separate pom files (default and jdk14) is causing some problems with releases.  Maybe the poms can be combined using profiles so that we don't have to keep two separate poms up to date.
I had some issues when attempting to use profiles before:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=115157

But I think that I can get around those issues now.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:55:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:55:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1766) Portal
	Administration Icons
In-Reply-To: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12144902.1193064904402.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1766?page=all ]

Thomas Heute updated JBPORTAL-1766:
-----------------------------------

      Component/s: Portal Core Admin
    Fix Version/s: 2.6.3 Final

> Portal Administration Icons
> ---------------------------
>
>                 Key: JBPORTAL-1766
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:55:04 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 22 Oct 2007 10:55:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9846939.1193064904617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris reassigned JBAS-4820:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:55:06 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBPORTAL-1770) Display icons in
 portlets list and provide icons for portlets
Message-ID: <15162837.1193064906366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1770?page=all ]

Thomas Heute deleted JBPORTAL-1770:
-----------------------------------


> Display icons in portlets list and provide icons for portlets
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1770
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1770
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Heute
>         Assigned To: Wesley Hales
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:59:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Mon, 22 Oct 2007 10:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-425) Fix maven bug in
	release plugin
Message-ID: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix maven bug in release plugin
-------------------------------

                 Key: JBBUILD-425
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
             Project: JBoss Build System
          Issue Type: Task
          Components: Maven
            Reporter: Paul Gier
         Assigned To: Paul Gier
             Fix For: Maven Build - Maint 2007


There is an issue when using a test-jar in during a release.
http://jira.codehaus.org/browse/MRELEASE-285 

This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:18:14 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 11:18:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24302861.1193066294981.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Thomas Diesler updated JBAS-4891:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
jboss descriptors cannot have qname elements like this 

  <service-ref>
    <service-ref-name>SecurePort1</service-ref-name>
    <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
    ...
  </service-ref>


Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
        at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)


> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:30:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 11:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31797832.1193067003476.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383723 ] 
            
Thomas Diesler commented on JBAS-4891:
--------------------------------------

Please note, we used to have qname elements defined like this

  <service-ref>
    <service-ref-name>SecurePort1</service-ref-name>
    <service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</service-qname>
    ...
  </service-ref>

which gave this exception 

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Characters are not allowed here
        at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal(CharactersHandler.java:118)
        at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHandler.unmarshal(RtCharactersHandler.java:64)
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1044)
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:266)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:374)
        at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)





> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:32:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28021019.1193067124438.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383725 ] 
            
Thomas Diesler commented on JBAS-4891:
--------------------------------------

Standard descriptors like web.xml also contain <service-qname> elements. 
IMHO we should use the same syntax in our descriptors that is used in the standard descriptors

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:37:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 11:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3555144.1193067425725.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Manik Surtani updated JBCACHE-1201:
-----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.CR1)

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:37:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 11:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16142883.1193067425865.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=comments#action_12383728 ] 
            
Manik Surtani commented on JBCACHE-1201:
----------------------------------------

as per discussion on the forum, deferring this to 2.2.0, potentially may not fix this at all.


> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:39:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 22 Oct 2007 11:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13143893.1193067543279.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris reassigned JBAS-4822:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:42:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 22 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9233610.1193067723767.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris updated JBAS-4820:
-------------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-2.odt

This chapter is fairly self explanatory (Chapter 2. Installation Alternatives) I just added suggestions that might make more obvious to users, where and how they can get each of the alternatives. And if they will be able to get it (subscription restrictions)

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:15:03 2007
From: jira-events at lists.jboss.org (Bernd Ruecker (JIRA))
Date: Mon, 22 Oct 2007 12:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-181) NullPointerException
 when opening processdefinition with additional elements
Message-ID: <5111725.1193069703312.JavaMail.jira@cloud.prod.atl2.jboss.com>

NullPointerException when opening processdefinition with additional elements
----------------------------------------------------------------------------

                 Key: GPD-181
                 URL: http://jira.jboss.com/jira/browse/GPD-181
             Project: JBoss jBPM GPD
          Issue Type: Bug
          Components: jpdl
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
         Environment: Eclipse Europa
            Reporter: Bernd Ruecker
         Assigned To: Koen Aers


When I add in a processdefinition an element for the simulation, the process deisgner raises a NullPointerException when opening the changed processdefinition.

This is the element I add:
	<task-node name="quick test">
		<task name="quick test" swimlane="clerk"></task>
		<resource-needed pool='test-equipment' amount='1' />
		<transition to="extended technical test" name="no defect"></transition>
		<transition to="Refund" name="defect approved"></transition>
	</task-node>

Without the "resource-needed" element everything works fine, with that element I get the following exception:

java.lang.NullPointerException
	at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.TaskNodeDomAdapter.doModelAdd(Unknown Source)
	at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.TaskNodeDomAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.ProcessDefinitionDomAdapter.doModelAdd(Unknown Source)
	at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.ProcessDefinitionDomAdapter.initialize(Unknown Source)
	at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
	at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
	at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
	at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
	at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
	at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2547)
	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644)
	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603)
	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:285)
	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:138)
	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:194)
	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:175)
	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268)
	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244)
	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:316)
	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:613)
	at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
	at org.eclipse.core.runtime.Platform.run(Platform.java:857)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:193)
	at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818)
	at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
	at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183)
	at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
	at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
	at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
	at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1169)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:17:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:17:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
In-Reply-To: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15033235.1193069824567.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4834?page=all ]

Brian Stansberry reassigned JBAS-4834:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Clustering Guide - TRACKER
> ---------------------------------------
>
>                 Key: JBAS-4834
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>
> Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:17:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:17:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18718683.1193069824753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Brian Stansberry reassigned JBAS-4835:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:17:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:17:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11923622.1193069824928.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

Brian Stansberry reassigned JBAS-4836:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10812236.1193069943534.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

Brian Stansberry reassigned JBAS-4837:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20459241.1193069943695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

Brian Stansberry reassigned JBAS-4838:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26916039.1193069943864.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Brian Stansberry reassigned JBAS-4839:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16137377.1193069944028.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Brian Stansberry reassigned JBAS-4840:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31007168.1193069944226.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry reassigned JBAS-4841:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:50:03 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Mon, 22 Oct 2007 12:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-158) Non-existent
 manifest Class-Path refs produce vfs IllegalStateException
In-Reply-To: <7022011.1173599806886.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10731954.1193071803396.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-158?page=comments#action_12383746 ] 
            
Max Andersen commented on JBMICROCONT-158:
------------------------------------------

Any known workarounds around this ?! 

I'm getting this too when I'm trying to run unittests directly from the IDE where these jars might not yet be packaged up but just be on the global classpath.

> Non-existent manifest Class-Path refs produce vfs IllegalStateException
> -----------------------------------------------------------------------
>
>                 Key: JBMICROCONT-158
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-158
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>    Affects Versions:  JBossMC_2_0_0 Beta3
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> When the structure deployers parse a top-level jboss-test-entity.jar with a manifest like:
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.5.0_09-b01 (Sun Microsystems Inc.)
> Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx
>  .jar junit.jar deploy.jar
> it fails with:
> Caused by: java.lang.IllegalStateException: JarHandler at 28271403[path= context=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar
> real=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar] has no parent.
>         at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:116)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.processContext(DefaultStructureBuilder.java:131)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.populateContext(DefaultStructureBuilder.java:89)
> The invalid references should at most produce debug level warnings.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1150) Drools 4.0 BRMS
 not working with geronimo-jetty6-jee5-2.0.1
In-Reply-To: <25850901.1188508878448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <294557.1193072643925.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1150?page=all ]

Fernando Meyer reassigned JBRULES-1150:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Drools 4.0 BRMS not working with geronimo-jetty6-jee5-2.0.1
> -----------------------------------------------------------
>
>                 Key: JBRULES-1150
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1150
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>         Environment: geronimo-jetty6-jee5-2.0.1
> drools-4.0.1.SNAPSHOT-brms
>            Reporter: Bhagwath Vadyala
>         Assigned To: Fernando Meyer
>         Attachments: drools-error-screenshot.doc, jetty_2007_09_04.log, screenshot-1.jpg
>
>
> I am trying to test and see whether Drools 4.0 BRMS works with Geronimo-jetty6-jee5-2.0.1 or not.
> Drools BRMS version which I am using is drools-4.0.1.SNAPSHOT-brms.
> It deploys fine in Geronimo but when I open the BRMS error message I am getting is HTTP ERROR:404.
> Please let me know whether we can make Drools 4.0 work with Geronimo-jetty 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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:04 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1251) Cannot remove a
 category if it was used in an archived rule
In-Reply-To: <29917794.1191583443584.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24506412.1193072644644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1251?page=all ]

Fernando Meyer reassigned JBRULES-1251:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Cannot remove a category if it was used in an archived rule
> -----------------------------------------------------------
>
>                 Key: JBRULES-1251
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1251
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> The BRMS manual says you can delete a category if it is not in use by any current version of a rule. However, if you archive a rule that uses a category X, say, then you cannot remove category X in the Admin section, even if no other rules in the repository use category X. You get the following error message:
> "The category still has some assets linked to it. You will need to remove the links so you can delete the cateogory"
> (PS not the spelling mistake cateogory in the error message)
> Either the manual (Section 9.4.2.2) should be updated with a warning that you cannot remove a category used by archived rules, or is there is a bug in the remove category functionality for archived assets, as you can remove categories which are only used in old versions of a rule?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:04 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1250) Allow option to
 completely remove an asset from the repository
In-Reply-To: <16475001.1191582723288.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19502074.1193072644832.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1250?page=all ]

Fernando Meyer reassigned JBRULES-1250:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Allow option to completely remove an asset from the repository
> --------------------------------------------------------------
>
>                 Key: JBRULES-1250
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1250
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> If you use the archive feature to remove a rule or package from the BRMS it is not really seen as gone, as if you attempt to create a new rule or package with the same name as the archived rules or package then you get an error saying that the rule or package already exists (looking at the  source code, the repository does not care if an item is archived or not, so it will always throw an error if an asset with an existing name is created).
> I'm assuming this is the designed behaviour and not a bug (I've asked about this a couple of times on the user list and got no replies to the contrary).
> However, it would be very useful to be able to remove a rule or package so that you can then recreate it (e.g by importing new versions from a drl file). At present, you have to laboriously rename the rules and packages you want to remove, so that when they are archived their names do not clash with the new versions of the rules and packages you want to import or recreate. Perhaps all that is involved in implementing this new remove feature is to just automatically rename the package and its rules before archiving it?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:05 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1249) Allow repository
 location to be specified in BRMS web client
In-Reply-To: <26599863.1191582367386.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31953539.1193072645068.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1249?page=all ]

Fernando Meyer reassigned JBRULES-1249:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Allow repository location to be specified in BRMS web client
> ------------------------------------------------------------
>
>                 Key: JBRULES-1249
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1249
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> At present, any custom location of the repository is set in a components.xml file inside the WEB-INF directory of the BRMS war file. It would be better if the user could specify the location using the BRMS web client itself, rather than have to unzip, modify and zip up the WAR file. Perhaps this functionality could be added to the Admin section of the BRMS.
> One advantage of this is that users could also then work with multiple repositories (e.g. for different projects). In effect there would be an option to create a new repository (specified by a directory given by the user), open an existing repository and close a repository.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:05 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Mon, 22 Oct 2007 13:04:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBBUILD-425) Fix maven bug in
 release plugin
In-Reply-To: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1163556.1193072645182.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBBUILD-425?page=comments#action_12383756 ] 
            
Paul Gier commented on JBBUILD-425:
-----------------------------------

Looks like this issue is related to a more general maven issue that affects a few plugins:
http://jira.codehaus.org/browse/MNG-2277

> Fix maven bug in release plugin
> -------------------------------
>
>                 Key: JBBUILD-425
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> There is an issue when using a test-jar in during a release.
> http://jira.codehaus.org/browse/MRELEASE-285 
> This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:05 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1242) Archived package
 assets cannot be restored
In-Reply-To: <10651989.1191324483301.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29420141.1193072645461.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1242?page=all ]

Fernando Meyer reassigned JBRULES-1242:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Archived package assets cannot be restored
> ------------------------------------------
>
>                 Key: JBRULES-1242
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1242
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets?
> The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of  archived assets.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:22 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1289) BRMS gives
 unusable error messages when validating DSL based rules
In-Reply-To: <12543965.1192890967500.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6622936.1193072782517.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1289?page=all ]

Fernando Meyer reassigned JBRULES-1289:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS gives unusable error messages when validating DSL based rules
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1289
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1289
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> The error messages that are shown when you click "Validate" when editing a business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small typo and misspell the name of an attribute (a very likely thing for a BRMS user to do), and click the Validate button, the error I get back is a big stack trace starting with "java.lang.RuntimeException: SNO: Conversion failed at org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere in that stack trace is anything that gives a hint that
> the error is just a typo of an attribute name.
> Contrast this with the rather helpful error message I get if I make the same typo when editing a DRL rule: "Unable to create Field Extractor for 'overtimHours'". (The error is that I misspelled overtimeHours). 
> The BRMS needs to give the same type of helpful error message on validation errors when editing a DSL rule.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:22 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1290) BRMS does not
 allow rule names to contain an apostrophe character ( ' )
In-Reply-To: <25881085.1192891323312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17618685.1193072782722.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1290?page=all ]

Fernando Meyer reassigned JBRULES-1290:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS does not allow rule names to contain an apostrophe character ( ' )
> -----------------------------------------------------------------------
>
>                 Key: JBRULES-1290
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1290
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> Rules with apostrophe characters are rejected by the BRMS. For example the rule name "Set employee's wage" works outside BRMS, but does not work in BRMS.
> If you attempt to enter a rule through the BRMS containing an apostrophe,the error stack trace says "An error occurred executing the action.
> Details
> com.google.gwt.user.client.rpc.SerializableException:
> javax.jcr.RepositoryException: failed to resolve path Set employee's relative to /drools:repository/drools:package_area/com.example/assets: Invalid name: Set employee's wage: Invalid name: Set employee's wage at
> org.drools.brms.server.ServiceImplementation.createNewRule(ServiceImplementation.java:166)..."
> If you attempt to import a .drl file with a rule that has an apostrophe in the title, you'll get this error message
> (including the <pre> tags): "Unable to import into the package. [<pre>Unable to process import: javax.jcr.RepositoryException: failed
> to resolve path Set employee's wage relative to /drools:repository/drools:package_area/com.soi/assets: Invalid name: Set employee's  wage: Invalid name: Set employee's wage</pre>]".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:22 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1291) BRMS does not
 allow import of .dslr files
In-Reply-To: <26814116.1192891443260.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12973559.1193072782997.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1291?page=all ]

Fernando Meyer reassigned JBRULES-1291:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS does not allow import of .dslr files
> -----------------------------------------
>
>                 Key: JBRULES-1291
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1291
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> The documentation (section 6.7.3) says that .drl files that use a DSL should be renamed to .dslr to work better in the IDE. The BRMS does not allow importing of .dslr files. Renaming the file back to .drl works.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:23 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1292) BRMS ignores
 "initial
 description" entered when creating new "Business rule using a DSL (text
 editor)" rule
In-Reply-To: <7897053.1192891563924.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9800977.1193072783195.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1292?page=all ]

Fernando Meyer reassigned JBRULES-1292:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS ignores "initial description" entered when creating new "Business rule using a DSL (text editor)" rule
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1292
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1292
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> When creating a new rule asset through the BRMS using the type "Business rule using a DSL (text editor)", the initial description you put in is ignored. You always get the description "A dsl is a language mapping from a domain specific language to the rule language."

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:23 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14617490.1193072783631.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=all ]

Fernando Meyer reassigned JBRULES-1273:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Fernando Meyer
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:10:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Mon, 22 Oct 2007 13:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBPORTAL-1766) Portal
	Administration Icons
In-Reply-To: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23641218.1193073003250.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1766?page=all ]

Wesley Hales closed JBPORTAL-1766.
----------------------------------

    Resolution: Done

> Portal Administration Icons
> ---------------------------
>
>                 Key: JBPORTAL-1766
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:12:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 13:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1293) Backport for
	Eclipse 3.3
Message-ID: <12660311.1193073123217.JavaMail.jira@cloud.prod.atl2.jboss.com>

Backport for Eclipse 3.3
------------------------

                 Key: JBRULES-1293
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1293
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.3


We now how two parallel eclipse projects for 4.0.x.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:14:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 13:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1294) Upgrade to MVEL
	1.2.10
Message-ID: <16163147.1193073243211.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade to MVEL 1.2.10
----------------------

                 Key: JBRULES-1294
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1294
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: All
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.3




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:16:03 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Mon, 22 Oct 2007 13:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1117) Request for
 feature to
 close connections on server side by ip address and by connection id
Message-ID: <5418814.1193073363722.JavaMail.jira@cloud.prod.atl2.jboss.com>

Request for feature to close connections on server side by ip address and by connection id
------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1117
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1117
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: Configuration and Management
    Affects Versions: 1.4.0.GA
            Reporter: Jay Howell
         Assigned To: Tim Fox


Several customers have asked for a management method to drop client connections from the server by ip address and by client id.

So there would be two cases.
By ipaddress - this would stop the pinger and also close all connections associated with that client ip address.  Only one pinger exists for an ip address, so this would require closging of the pinger connection also.
By clientid - this would close the pinger thread only if there are no other connections present.

In each of the cases, clients should get an asynchronous onException call.  

The person writing the client will have to have this in mind.  If a client has 1000 connections and the connection logic on the client reconnects.  When the server drops the ip address, then that machine will try to reconnect all 1000 clients.  I really depends on how the connection pooling on the client works.  

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:16:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 22 Oct 2007 13:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1295) DSL Mapping files
 does not support comments and empty lines
Message-ID: <8445563.1193073363982.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL Mapping files does not support comments and empty lines
-----------------------------------------------------------

                 Key: JBRULES-1295
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1295
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.0.3, 4.1.0


Hi Mark,

I encountered a problem in DROOLS 4.0.2 (I was upgrading from 3.x). The 
problem consists in the fact that the DSL syntax has changed, now it 
does not accept empty lines, and lines continuing on the new line i.e.:

# this is ok
#
<--- Error, empty line
[then] name = java expression 1 \
java expression 2 <--- Error, it does not recognize anymore "\"

Now, I have a very large DSL file (sorry, I cannot disclose it) and I'm 
lazy enough not to edit that one, so instead I patched DROOLs with the 
following code (see the attached files). The code I added is a bit ugly 
(I'm in a hurry, always in a hurry :( ) I have done some basic tests, 
but since they are linked to the files that I cannot disclose (once 
again, sorry for that) they are not added here.

Anyway, here's the patch. Feel free to modify the code.
.java - my current version
.old - the svn extracted one
.diff - unified diff

I would have also some comments about the class loaders, but I will need 
to confirm that before making any comment.

Hope it will be included (in this form or another) in the next release.

Best Regards,
Radu

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:20:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 22 Oct 2007 13:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1295) DSL Mapping files
 does not support comments and empty lines
In-Reply-To: <8445563.1193073363982.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16970865.1193073603366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1295?page=all ]

Edson Tirelli closed JBRULES-1295.
----------------------------------

    Resolution: Done

Fixed.

> DSL Mapping files does not support comments and empty lines
> -----------------------------------------------------------
>
>                 Key: JBRULES-1295
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1295
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3, 4.1.0
>
>
> Hi Mark,
> I encountered a problem in DROOLS 4.0.2 (I was upgrading from 3.x). The 
> problem consists in the fact that the DSL syntax has changed, now it 
> does not accept empty lines, and lines continuing on the new line i.e.:
> # this is ok
> #
> <--- Error, empty line
> [then] name = java expression 1 \
> java expression 2 <--- Error, it does not recognize anymore "\"
> Now, I have a very large DSL file (sorry, I cannot disclose it) and I'm 
> lazy enough not to edit that one, so instead I patched DROOLs with the 
> following code (see the attached files). The code I added is a bit ugly 
> (I'm in a hurry, always in a hurry :( ) I have done some basic tests, 
> but since they are linked to the files that I cannot disclose (once 
> again, sorry for that) they are not added here.
> Anyway, here's the patch. Feel free to modify the code.
> .java - my current version
> .old - the svn extracted one
> .diff - unified diff
> I would have also some comments about the class loaders, but I will need 
> to confirm that before making any comment.
> Hope it will be included (in this form or another) in the next release.
> Best Regards,
> Radu

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:36:03 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Mon, 22 Oct 2007 13:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-158) Non-existent
 manifest Class-Path refs produce vfs IllegalStateException
In-Reply-To: <7022011.1173599806886.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15727809.1193074563770.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-158?page=comments#action_12383763 ] 
            
Max Andersen commented on JBMICROCONT-158:
------------------------------------------

note: it seems like this happen even without any manifest.mf. 

Only way I could work around it was to remove the ejb-jar.xml file.

> Non-existent manifest Class-Path refs produce vfs IllegalStateException
> -----------------------------------------------------------------------
>
>                 Key: JBMICROCONT-158
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-158
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>    Affects Versions:  JBossMC_2_0_0 Beta3
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> When the structure deployers parse a top-level jboss-test-entity.jar with a manifest like:
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.5.0_09-b01 (Sun Microsystems Inc.)
> Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx
>  .jar junit.jar deploy.jar
> it fails with:
> Caused by: java.lang.IllegalStateException: JarHandler at 28271403[path= context=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar
> real=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar] has no parent.
>         at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:116)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.processContext(DefaultStructureBuilder.java:131)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.populateContext(DefaultStructureBuilder.java:89)
> The invalid references should at most produce debug level warnings.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:00:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 22 Oct 2007 14:00:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1076) Ensure new
 metamodel and annotations/xml line up
Message-ID: <1082073.1193076005069.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure new metamodel and annotations/xml line up
------------------------------------------------

                 Key: EJBTHREE-1076
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1076
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
            Priority: Critical


End game here is to ensure the external API is correct before Beta 3.  Must ensure that all EJB3 annotations map to cooresponding representations in XML and the new metamodel.

Create a document to track the mappings, place on the Wiki.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:05:06 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Mon, 22 Oct 2007 14:05:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1118) Sucker
 connection created back to itself doesn't need to be created
Message-ID: <1544433.1193076306087.JavaMail.jira@cloud.prod.atl2.jboss.com>

Sucker connection created back to itself doesn't need to be created
-------------------------------------------------------------------

                 Key: JBMESSAGING-1118
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
            Reporter: Jay Howell
         Assigned To: Tim Fox
            Priority: Minor


The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment.  So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker.

while (iter.hasNext())
		{
			Map.Entry entry = (Map.Entry)iter.next();
			
			Integer nid = (Integer)entry.getKey();
			
			ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue();
			
			if (connections.get(nid) == null)
			{
				try
				{
   				ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword);
   				
   				log.trace(this + " created connection info " + info);
   				
   				connections.put(nid, info);
   				
   				info.start();
   						         							         			
				}
				catch (Exception e)
				{
					log.error("Failed to start connection info ", e);
				}
			}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:15:21 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 22 Oct 2007 14:15:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22156702.1193076921549.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=comments#action_12383771 ] 
            
Andrew Rubinger commented on EJBTHREE-1045:
-------------------------------------------

BindingUtils does not provide context as to which attempt to bind resulted in a CCE; a message describing the node that resulted in the failure cannot be constructed.

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:19:05 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Mon, 22 Oct 2007 14:19:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin
 Console: Any user sees all users tasks
In-Reply-To: <6696155.1184871647115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25634380.1193077145913.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12383772 ] 
            
Ronald van Kuijk commented on JBPM-1022:
----------------------------------------

Burr,

Completele depends on what you regard as the jbpm userbase. Really newbies (often java/web newbies as at the same time) think it can/will/should do everything. More advanced users do not and regard it as an admin console (production quality in the end) and for rapid prototyping.


> 3.2.1 Admin Console: Any user sees all users tasks 
> ---------------------------------------------------
>
>                 Key: JBPM-1022
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1022
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions:  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>            Reporter: Burr Sutter
>         Assigned To: Tom Baeyens
>            Priority: Blocker
>             Fix For: jBPM jPDL 3.2.3
>
>
> In the current Admin Console, any given user will see all other users tasks.  Plus a user can "take" another person's assigned tasks even when they are not an "administrator".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:48:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 22 Oct 2007 14:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
Message-ID: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>

We should ignore nonPersistentMessages on failover
--------------------------------------------------

                 Key: JBMESSAGING-1119
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: 1.4.0.GA
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For: 1.4.0.SP1


There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 15:08:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 15:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1242) Archived package
 assets cannot be restored
In-Reply-To: <10651989.1191324483301.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18105545.1193080083640.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1242?page=all ]

Fernando Meyer closed JBRULES-1242.
-----------------------------------

    Resolution: Rejected

It isn't a bug, 
there's an open ticket for that, It just wasn't finished yet 

> Archived package assets cannot be restored
> ------------------------------------------
>
>                 Key: JBRULES-1242
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1242
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets?
> The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of  archived assets.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 15:43:15 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 22 Oct 2007 15:43:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1074) Circular @EJB3
 references in session beans fail to deploy.
In-Reply-To: <7270653.1192639206697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29611582.1193082195540.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1074?page=comments#action_12383800 ] 
            
Andrew Rubinger commented on EJBTHREE-1074:
-------------------------------------------

@IgnoreDependency on one of the injected members should break the cyclic dependency.

> Circular @EJB3 references in session beans fail to deploy.
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1074
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Gunnar Grim
>
> The following circular references makes the application undeployable:
> In ArchiveBrokerBean:
>   @EJB 
>   private SeriesBrokerLocal itsSeriesBroker;	
> In SeriesBrokerBean
>   @EJB 
>   private ArchiveBrokerLocal itsArchiveBroker;	
> Circular references like these work fine in Glassfish but JBoss shows the following error message:
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
>   Depends On Me:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
>   Depends On Me:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 17:05:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 22 Oct 2007 17:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7096699.1193087103878.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4180?page=comments#action_12383808 ] 
            
Galder Zamarreno commented on JBAS-4180:
----------------------------------------

Second set of HA singleton election tests added based on 
Pojo bean HA singletons which passed successfully.

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 17:07:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 22 Oct 2007 17:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <236998.1193087223641.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4180?page=all ]

Galder Zamarreno resolved JBAS-4180.
------------------------------------

    Resolution: Done

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 17:36:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 22 Oct 2007 17:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1771) Add support for
 event listener binding to windows in admin interface
Message-ID: <33127050.1193088963161.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add support for event listener binding to windows in admin interface
--------------------------------------------------------------------

                 Key: JBPORTAL-1771
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1771
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
    Affects Versions: 2.6.2 Final, 2.8 Final
            Reporter: Chris Laprun
         Assigned To: Chris Laprun
            Priority: Minor
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:09:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 19:09:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12586920.1193094555268.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis updated JBAS-4811:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

Ok, so I'm just re-scheduling this for 4.2.3. Or if the same tests need to run for EAP4.3, we will face this issue again there.

I don't know what the test does exactly, so I cannot tell if this is something we need to fix in AS.

Thomas should be able to describe the failure better, and open a bug report, if this is really an AS problem.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:09:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 19:09:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1188)
 UnversionedNode.isValid - out
 of sync (deleted/remotely deleted nodes)
In-Reply-To: <1073686.1190216951047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1520478.1193094555529.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1188?page=all ]

Manik Surtani resolved JBCACHE-1188.
------------------------------------

    Resolution: Done

> UnversionedNode.isValid - out of sync (deleted/remotely deleted nodes)
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1188
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1188
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>         Environment: all
>            Reporter: Mircea Markus
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> considering the scenario:
> thread1: 
> node = cache.get("a/b/c");
> thread2(possibly running on another node/JVM):
> cache.remove("a/b/c");
> thread1: 
> node.getAttribute("attr1");//at this point the node is not longer in the cache. we should allow user to check this through isValid
> node.getAttribute("attr2");

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:19:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 22 Oct 2007 19:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1077) @RunAsPrincipal
 not propagated
Message-ID: <13923257.1193095143282.JavaMail.jira@cloud.prod.atl2.jboss.com>

@RunAsPrincipal not propagated
------------------------------

                 Key: EJBTHREE-1077
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1077
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.1.GA
            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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 19:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1199) Update
 InvalidatorInterceptorTest to use Node.isValid()
In-Reply-To: <2782171.1192635603222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21212154.1193097543333.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1199?page=all ]

Manik Surtani resolved JBCACHE-1199.
------------------------------------

    Resolution: Done

> Update InvalidatorInterceptorTest to use Node.isValid()
> -------------------------------------------------------
>
>                 Key: JBCACHE-1199
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node.  See the forum link.  Need to replace with a call to isValid() whenever that is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 19:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1200) Node removal with
 invalidation leaves child data accessible
In-Reply-To: <4642624.1192638724532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19139948.1193097543460.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1200?page=all ]

Manik Surtani resolved JBCACHE-1200.
------------------------------------

    Resolution: Done

> Node removal with invalidation leaves child data accessible
> -----------------------------------------------------------
>
>                 Key: JBCACHE-1200
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1200
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1
>
>
> With invalidation, when a node that has children is removed, on remote caches the data in the children is still visible; e..g
> cache1.put(childFqn, key, value);
> cache1.removeNode(parentFqn);
> // This assertion fails
> assertNull(cache2.get(childFqn, key));
> InvalidationInterceptorTest.testPessimisticNodeRemoval() and testOptimisticNodeRemoval() have been modified to show this issue.
> This is a significant problem for the Hibernate/JBC integration

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 21:05:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 21:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1296) Drools Release
	4.0.3
Message-ID: <4893834.1193101503300.JavaMail.jira@cloud.prod.atl2.jboss.com>

Drools Release 4.0.3
--------------------

                 Key: JBRULES-1296
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1296
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 21:21:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 21:21:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
In-Reply-To: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18448216.1193102467827.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1203?page=all ]

Manik Surtani resolved JBCACHE-1203.
------------------------------------

    Resolution: Done

most of the failures were broken tests; although one glaring problem was in the way invalidation markers were created in CacheImpl.invalidate()



> putForExternalRead replicates when INVALIDATION used
> ----------------------------------------------------
>
>                 Key: JBCACHE-1203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.
> The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 21:36:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 22 Oct 2007 21:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1285) Time Machine to
 allow setting of "now" effective current time in Rule
In-Reply-To: <30930954.1192767254713.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16007487.1193103363366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1285?page=all ]

Michael Neale closed JBRULES-1285.
----------------------------------

    Resolution: Done

> Time Machine to allow setting of "now" effective current time in Rule
> ---------------------------------------------------------------------
>
>                 Key: JBRULES-1285
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1285
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>
> This is needed for testing effective dating.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 22:04:03 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Mon, 22 Oct 2007 22:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4821) TECH REVIEW:
 Installation Guide
 - Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14899601.1193105043323.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

cheng dan reassigned JBAS-4821:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 22:54:14 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 22 Oct 2007 22:54:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1771) Add support for
 event listener binding to windows in admin interface
In-Reply-To: <33127050.1193088963161.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10409249.1193108054540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1771?page=all ]

Chris Laprun resolved JBPORTAL-1771.
------------------------------------

    Resolution: Done

> Add support for event listener binding to windows in admin interface
> --------------------------------------------------------------------
>
>                 Key: JBPORTAL-1771
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1771
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>    Affects Versions: 2.8 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>            Priority: Minor
>             Fix For: 2.6.3 Final, 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 22:54:14 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 22 Oct 2007 22:54:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-824) Allow server to shut
 down connections from specified clients
Message-ID: <17720506.1193108054695.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow server to shut down connections from specified clients
------------------------------------------------------------

                 Key: JBREM-824
                 URL: http://jira.jboss.com/jira/browse/JBREM-824
             Project: JBoss Remoting
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Trustin Lee
             Fix For: 3.0.0.Alpha1 (Otter)


>From Jay Howell:  

Several customers have asked for a management method to drop client connections from the server by ip address and by client id.

So there would be two cases.
   By ipaddress - this would stop the pinger and also close all connections associated with that client ip address. Only one pinger exists for an ip address, so this would require closing of the pinger connection also.
   By clientid - this would close the pinger thread only if there are no other connections present.

In each of the cases, clients should get an asynchronous onException call. 

This facility would be necessary to support JBMESSAGING-1117.




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 23:40:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Mon, 22 Oct 2007 23:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4892) WebService ignores
 java.rmi.server.codebase system property
Message-ID: <6431871.1193110803625.JavaMail.jira@cloud.prod.atl2.jboss.com>

WebService ignores java.rmi.server.codebase system property
-----------------------------------------------------------

                 Key: JBAS-4892
                 URL: http://jira.jboss.com/jira/browse/JBAS-4892
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Takayoshi Kimura


server/src/main/org/jboss/web/WebService.java

The trailing semicolon of if statement is a bug.

      String codebase = getCodebase(); // This returns system property value
      if (codebase == null); // HERE
      {
         codebase = "http://" + getHost() + ":" + getPort() + "/";
         System.setProperty("java.rmi.server.codebase", codebase);
      }
      log.info("Using RMI server codebase: " + codebase);


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:05:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 00:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
Message-ID: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>

JvmRouteValve (UseJK) for non session replication setup
-------------------------------------------------------

                 Key: JBAS-4893
                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Takayoshi Kimura


Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:05:04 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 00:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
In-Reply-To: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11114976.1193112304022.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ]

Takayoshi Kimura updated JBAS-4893:
-----------------------------------

    Component/s: Clustering

> JvmRouteValve (UseJK) for non session replication setup
> -------------------------------------------------------
>
>                 Key: JBAS-4893
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Takayoshi Kimura
>
> Currently JBoss doesn't install JvmRouteValve for non session
> replication setup. However, it's still useful in the following
> scenario:
> * 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
> * A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
> * The node AAA crashed
> * The request goes node BBB, lost session, recreate another
> * The node AAA recovered
> * The request comes back to the node AAA, lost session again
> Enabling JvmRouteValve can prevent last failure.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:05:04 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 00:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
In-Reply-To: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7168357.1193112304358.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ]

Takayoshi Kimura updated JBAS-4893:
-----------------------------------

    Description: 
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.


  was:
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.



> JvmRouteValve (UseJK) for non session replication setup
> -------------------------------------------------------
>
>                 Key: JBAS-4893
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Takayoshi Kimura
>
> Currently JBoss doesn't install JvmRouteValve for non session
> replication setup. However, it's still useful in the following
> scenario:
> * 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
> * A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
> * The node AAA crashed
> * The request goes node BBB, lost session, recreate another
> * The node AAA recovered
> * The request comes back to the node AAA, lost session again
> Enabling JvmRouteValve can prevent last failure.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:11:23 2007
From: jira-events at lists.jboss.org (Santiago Erquicia (JIRA))
Date: Tue, 23 Oct 2007 00:11:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (BPEL-282) Engine runs process
 instances in serie instead of in parallel
Message-ID: <7870750.1193112683491.JavaMail.jira@cloud.prod.atl2.jboss.com>

Engine runs process instances in serie instead of in parallel
-------------------------------------------------------------

                 Key: BPEL-282
                 URL: http://jira.jboss.com/jira/browse/BPEL-282
             Project: JBoss jBPM BPEL
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Engine
    Affects Versions: jBPM BPEL 1.1 beta 3
         Environment: RHEL
            Reporter: Santiago Erquicia
         Assigned To: Alejandro Guizar


We are stress testing a BPEL process and we found out that the engine runs all the requests it receives in serie. That means that if there are two or more concurrent users of the system, one has to wait till the first process instance stops at some point (wait state) so the other request can be processed.

On our test environment, we are calling a web service which is also calling another web service. The are connection problems with the second one, so from time to time the web service just times out. This means that a concurrent user has to wait for that time out, and whatever is left of that process instance, in order to be processed.

On our JMeter test, the throughput keeps stable even if there number of request is bigger than the throughput of the BPEL engine. The result is that the time for response of each process request increases indefinitely if the usage is bigger than the throughput. This obviously doesn't scale at all for the processing requirement we are considering.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 02:18:08 2007
From: jira-events at lists.jboss.org (Magesh Kumar B (JIRA))
Date: Tue, 23 Oct 2007 02:18:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1772) Security fixes
 for JBoss Portal 2.6.2
Message-ID: <24917505.1193120288270.JavaMail.jira@cloud.prod.atl2.jboss.com>

Security fixes for JBoss Portal 2.6.2
-------------------------------------

                 Key: JBPORTAL-1772
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1772
             Project: JBoss Portal
          Issue Type: Support Patch
      Security Level: Public (Everyone can see)
          Components: Portal Security
    Affects Versions: 2.6.2 Final
            Reporter: Magesh Kumar B
         Assigned To: Julien Viet


The patch contains fixes for the following issues:

[JBPORTAL-1741] PortalURL security not honoured
[JBPORTAL-1481] Reimplement portal security interface without JACC

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:02:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 23 Oct 2007 04:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14560763.1193126521916.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383840 ] 
            
Scott M Stark commented on JBAS-4891:
-------------------------------------

There is a usage of such qname type elments in the EjbJar3xUnitTestCase.java, and this is parsing correctly.
https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/test/java/org/jboss/test/metadata/ejb/EjbJar3xUnitTestCase.java
https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/test/resources/org/jboss/test/metadata/ejb/EjbJar3x_testServiceRefs.xml

<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
    version="3.0"
    id="ejb-jar-service-refs">
    <enterprise-beans>
        <session id="session1">
            <description>A secured trival echo session bean</description>
            <ejb-name>StatelessSession1</ejb-name>
            <home>org.jboss.test.security.interfaces.StatelessSessionHome</home>
            <remote>org.jboss.test.security.interfaces.StatelessSession</remote>
            <local-home>org.jboss.test.security.interfaces.StatelessSessionLocalHome</local-home>
            <local>org.jboss.test.security.interfaces.StatelessSessionLocal</local>
            <ejb-class>org.jboss.test.security.ejb.StatelessSessionBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
            <service-ref id="session1-service-ref">
                <!-- JNDI name bound to the service interface in the client's environment context -->
                <service-ref-name>session1/Hello</service-ref-name>
                <!-- service interface class -->
                <service-interface>org.jboss.test.security.interfaces.HelloWorldService</service-interface>
                <service-ref-type>org.jboss.test.security.interfaces.HelloWorldRef</service-ref-type>
                <!-- placeholder for published WSDL file -->
                <wsdl-file>session1-wsdl-file</wsdl-file>
                <!-- Java<->XML mapping file -->
                <jaxrpc-mapping-file>META-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file>
                <service-qname xmlns:session1="http://www.jboss.org">session1:Session1Qname</service-qname>
                <port-component-ref>
                    <!-- service endpoint interface class -->
                    <service-endpoint-interface>org.jboss.test.security.interfaces.HelloEndPoint</service-endpoint-interface>
                </port-component-ref>
                <handler-chains>
                    <handler-chain id="session1-chain1">
                        <service-name-pattern>*</service-name-pattern>
                        <handler id="sesion1-chain1-handler1">
                            <handler-name>session1.Handler1</handler-name>
                            <handler-class>session1.Handler1</handler-class>
                            <init-param>
                                <param-name>param1</param-name>
                                <param-value>value1</param-value>
                            </init-param>
                            <soap-header xmlns:session1="http://www.jboss.org">session1:soap-header</soap-header>
                            <soap-role>session1:soap-role</soap-role>
                            <port-name>session1:soap-role</port-name>
                        </handler>
                    </handler-chain>
                </handler-chains>
            </service-ref>
        </session>

What is an example descriptor that is failing?


> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:16:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 04:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4892) WebService ignores
 java.rmi.server.codebase system property
In-Reply-To: <6431871.1193110803625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14770622.1193127361571.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4892?page=comments#action_12383842 ] 
            
Dimitris Andreadis commented on JBAS-4892:
------------------------------------------

I believe this is the very first bug recorded against 4.2.2.GA - that was fast!

> WebService ignores java.rmi.server.codebase system property
> -----------------------------------------------------------
>
>                 Key: JBAS-4892
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4892
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Takayoshi Kimura
>
> server/src/main/org/jboss/web/WebService.java
> The trailing semicolon of if statement is a bug.
>       String codebase = getCodebase(); // This returns system property value
>       if (codebase == null); // HERE
>       {
>          codebase = "http://" + getHost() + ":" + getPort() + "/";
>          System.setProperty("java.rmi.server.codebase", codebase);
>       }
>       log.info("Using RMI server codebase: " + codebase);

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:22:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 04:22:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4892) WebService ignores
 java.rmi.server.codebase system property
In-Reply-To: <6431871.1193110803625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9241861.1193127725972.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4892?page=all ]

Dimitris Andreadis updated JBAS-4892:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA

> WebService ignores java.rmi.server.codebase system property
> -----------------------------------------------------------
>
>                 Key: JBAS-4892
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4892
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Takayoshi Kimura
>             Fix For: JBossAS-4.2.3.GA
>
>
> server/src/main/org/jboss/web/WebService.java
> The trailing semicolon of if statement is a bug.
>       String codebase = getCodebase(); // This returns system property value
>       if (codebase == null); // HERE
>       {
>          codebase = "http://" + getHost() + ":" + getPort() + "/";
>          System.setProperty("java.rmi.server.codebase", codebase);
>       }
>       log.info("Using RMI server codebase: " + codebase);

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1015)
 ServiceDelegateWrapper should
 delegate MBeanRegistration and NotificationEmitter calls
In-Reply-To: <27468169.1184596608426.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20307811.1193127843630.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1015?page=all ]

Carlo de Wolf updated EJBTHREE-1015:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls
> --------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1015
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1015
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: EJB3 Extensions
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>             Fix For: Branch_4_2
>
>
> ServiceDelegateWrapper should delegate MBeanRegistration 
> and NotificationEmitter calls to EJB3 Services if users made
> their EJB3 services implement these interfaces.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-896) Specifying an
 interceptor-order in ejb-jar.xml also creates a new instance of the
 interceptor
In-Reply-To: <33054938.1172680808955.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18888117.1193127843801.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-896?page=all ]

Carlo de Wolf updated EJBTHREE-896:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor
> ---------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-896
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-896
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: interceptor2
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> Trying to override the order of interceptors in xml from the one specified via annotations in the beans, will lead to duplicate invocations on the interceptors.
> @Interceptors({AnnotatedClassInterceptor3.class, XMLClassInterceptor3.class})
> @Stateless(name="OrderedSLSB")
> public class OrderedSLSB implements OrderedSLSBRemote
> {
> ...
> }
>       <interceptor-binding>
>          <ejb-name>OrderedSLSB</ejb-name>
>          <interceptor-order>
> 	         <interceptor-class>org.jboss.ejb3.test.interceptors2.AnnotatedClassInterceptor3</interceptor-class>
> 	         <interceptor-class>org.jboss.ejb3.test.interceptors2.XMLClassInterceptor3</interceptor-class>
> 	         <interceptor-class>org.jboss.ejb3.test.interceptors2.DefaultInterceptor</interceptor-class>
>          </interceptor-order>
>       </interceptor-binding>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-884) META-INF/orm.xml
 should be
 read for both the main persistence jar and all the explicit jars
In-Reply-To: <22344968.1171895871850.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21497694.1193127843955.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-884?page=all ]

Carlo de Wolf updated EJBTHREE-884:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> META-INF/orm.xml should be read for both the main persistence jar and all the explicit jars
> -------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-884
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-884
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Emmanuel Bernard
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> See http://opensource.atlassian.com/projects/hibernate/browse/EJB-259
> I've fixed the issue in HEM, but it worth having a testcase in the container's code base to be safe

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27598616.1193127843451.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Carlo de Wolf updated EJBTHREE-1057:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: Branch_4_2
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-872) Unable to call
	EJB Remotely
In-Reply-To: <14581634.1171301790240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5033701.1193127844426.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-872?page=all ]

Carlo de Wolf updated EJBTHREE-872:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Unable to call EJB Remotely
> ---------------------------
>
>                 Key: EJBTHREE-872
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-872
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: EJB3 Extensions
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: two separate, non clustered jbosses
>            Reporter: Henning Vogt
>             Fix For: Branch_4_2
>
>
> See also the linked bug for detailed descripton.
> Calling a remote SLSB does not work, if the equally named SLSB is deployed on the calling JBoss.
> See also:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96098
> and
> http://jira.jboss.com/jira/browse/EJBTHREE-823
> and numerous other topics on this.
> In my opinion, ther should be an easier way to do this, instead of writing your own interceptor, patching JBoss or the like.
> Also, in a non clustered environment, if you give a hostname to the InitialContext(), you should get the remote server session beans,
> regardless of possibly locally deployed equally named stateless sessionbeans.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-856) Use Buddy
 Replication for clustered SFSBs
In-Reply-To: <24225310.1170195680226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8545308.1193127844753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-856?page=all ]

Carlo de Wolf updated EJBTHREE-856:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Use Buddy Replication for clustered SFSBs
> -----------------------------------------
>
>                 Key: EJBTHREE-856
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-856
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> Optimize the replicated SFSB cache for use with Buddy Replication.  Basically means checking cache calls to ensure unwanted data gravitations do not occur. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-835) revet to
 Hibernate's PersistenceXmlLoader
In-Reply-To: <26261978.1168895332931.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8521309.1193127845286.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-835?page=all ]

Carlo de Wolf updated EJBTHREE-835:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> revet to Hibernate's PersistenceXmlLoader
> -----------------------------------------
>
>                 Key: EJBTHREE-835
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-835
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> The default PersistenceUnitTransactionType is JTA in Java EE and RESOURCE_LOCAL in Java SE.  Currently HEM returns RESOURCE_LOCAL no matter what.  HEM is fixed but until it revs in JBoss head, I have copied the persistence.xml parsing to EJB3 project.
> Please remove org.jboss.ejb3.entity.PersistenceXmlLoader from SVN when HEM revs and revert to Hibernate 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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-832) HEM using
 JBossCache raise a CCE
In-Reply-To: <4453734.1168404686743.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6329831.1193127845499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-832?page=all ]

Carlo de Wolf updated EJBTHREE-832:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> HEM using JBossCache raise a CCE
> --------------------------------
>
>                 Key: EJBTHREE-832
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-832
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: EJB 3.0 RC9 - Patch 1
>            Reporter: Emmanuel Bernard
>         Assigned To: William DeCoste
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> Acording to Gavin
> In persistence.xml:
>          <property name="hibernate.cache.provider_class"
> value="org.hibernate.cache.OptimisticTreeCacheProvider"/>
> And I got:
> 00:39:56,421 INFO  [SettingsFactory] Cache provider:
> org.hibernate.cache.OptimisticTreeCacheProvider
> 00:39:56,421 WARN  [ServiceController] Problem starting service
> persistence.units:ear=jboss-seam-registration.ear,jar=jboss-seam-registr
> ation.jar,unitName=userDatabase
> java.lang.RuntimeException: java.lang.NoClassDefFoundError:
> org/jboss/cache/TransactionManagerLookup
> 	at
> org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrappe
> r.java:108)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
> ort.java:289)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
> Support.java:245)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
> .java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy190.start(Unknown Source)
> 	at
> org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96
> )
> 	at
> org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:
> 467)
> 	at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:317)
> 	at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
> ort.java:289)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
> Support.java:245)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
> .java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.start(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.
> java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea
> nOperationInterceptor.java:142)
> 	at
> org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.ja
> va:97)
> 	at
> org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorSe
> rviceMBeanSupport.java:238)
> 	at
> org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterce
> ptor.java:92)
> 	at
> org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.sta
> rt(SubDeployerInterceptorSupport.java:188)
> 	at
> org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerIntercepto
> r.java:95)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.start(Unknown Source)
> 	at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
> 	at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
> 	at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
> 	at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.
> java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea
> nOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)
> 	at
> org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc
> anner.java:421)
> 	at
> org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan
> ner.java:634)
> 	at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS
> can(AbstractDeploymentScanner.java:263)
> 	at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loo
> p(AbstractDeploymentScanner.java:274)
> 	at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run
> (AbstractDeploymentScanner.java:225)
> Caused by: java.lang.NoClassDefFoundError:
> org/jboss/cache/TransactionManagerLookup
> 	at java.lang.Class.getDeclaredConstructors0(Native Method)
> 	at java.lang.Class.privateGetDeclaredConstructors(Unknown
> Source)
> 	at java.lang.Class.getConstructor0(Unknown Source)
> 	at java.lang.Class.newInstance0(Unknown Source)
> 	at java.lang.Class.newInstance(Unknown Source)
> 	at
> org.hibernate.cfg.SettingsFactory.createCacheProvider(SettingsFactory.ja
> va:358)
> 	at
> org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:232
> )
> 	at
> org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1933)
> 	at
> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1
> 216)
> 	at
> org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Config
> uration.java:688)
> 	at
> org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFacto
> ry(HibernatePersistence.java:127)
> 	at
> org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDep
> loyment.java:264)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrappe
> r.java:102)
> 	... 92 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-789) build.xml and
 component-info.xml - version numbers and imports need to be updated
In-Reply-To: <1955110.1163617421727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4283985.1193127845711.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-789?page=all ]

Carlo de Wolf updated EJBTHREE-789:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> build.xml and component-info.xml - version numbers and imports need to be updated
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-789
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-789
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Vladimir Ralev
>            Priority: Critical
>             Fix For: Branch_4_2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repository-zip target's comp-version, like this (use appropriate version string):
> <target name="repository-zip" depends="jars"
>     description="Create the repository.jboss.com jboss/ejb3 component contents">
>     <!-- The binary component version -->
>     <property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />
>     <!-- Pack the ejb3.deployer -->
>     <zip destfile="${build.lib}/ejb3-deployer.zip">
>       <zipfileset dir="${build.lib}">
>         <include name="ejb3.deployer/**" />
>       </zipfileset>
>     </zip>
>     <!-- Create a zip file with the component structure -->
>     <zip destfile="${build.lib}/jboss-ejb3-repo.zip">
>       <!-- The component-info.xml -->
>       <zipfileset dir="${build.etc}" prefix="${comp-version}">
>         <include name="component-info.xml" />
>       </zipfileset>
>       <!-- The bin/ejb3.deployer -->
>       <zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer">
>         <include name="ejb3-deployer.zip" />
>       </zipfileset>
>       <!-- The lib client jars -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/lib">
>         <include name="hibernate-client.jar" />
>         <include name="jboss-ejb3-client.jar" />
>       </zipfileset>
>       <!-- The resources deploy descriptors -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/resources">
>         <include name="ejb3-clustered-sfsbcache-service.xml" />
>         <include name="ejb3-entity-cache-service.xml" />
>         <include name="ejb3-interceptors-aop.xml" />
>       </zipfileset>
>     </zip>
>   </target>
> and ejb3\src\etc\component-info.xml (the version attribute):
> <project name="jboss/ejb3-component-info">
>    <component id="jboss/ejb3"
>               licenseType="lgpl"
>               version="1.0.0.CR9-jboss4.0.5"
>               description="The EJB3 deployer for integration with jboss-4.0.x">
>       <artifact id="ejb3-clustered-sfsbcache-service.xml"/>
>       <artifact id="ejb3-entity-cache-service.xml"/>
>       <artifact id="ejb3-interceptors-aop.xml"/>
>       <artifact id="ejb3.deployer" />
>       <artifact id="hibernate-client.jar"/>
>       <artifact id="jboss-ejb3-client.jar"/>
>       <import componentref="javassist">
>         <compatible version="3.2.0.CR1"/>
>         <compatible version="3.2.0.CR2"/>
>       </import>
>       <import componentref="hibernate-annotations">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="hibernate-entitymanager">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="jboss/remoting">
>         <compatible version="1.4.1_final"/>
>         <compatible version="1.4.2.GA"/>
>       </import>
>       <import componentref="jboss/aop">
>       	<compatible version="1.5.1.GA"/>
>         <compatible version="1.5.2.GA"/> <--------------- IS 1.5.2.GA COMPATIBLE?
>       </import>
>       <export>
>          <include input="hibernate-client.jar"/>
>          <include input="jboss-ejb3-client.jar"/>
>       </export>
>    </component>
> </project>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-772) Add JBoss EULA
In-Reply-To: <26119208.1162412921868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20033634.1193127845850.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-772?page=all ]

Carlo de Wolf updated EJBTHREE-772:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Add JBoss EULA
> --------------
>
>                 Key: EJBTHREE-772
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-772
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Rajesh Rajasekaran
>             Fix For: Branch_4_2
>
>         Attachments: JBossORG-EULA.txt
>
>
> Attached is the JBossORG-EULA.txt 
> 1. The eula should be checked into the project's source tree.
> 2. The project's build should include the EULA in project
> distributables, ie, whatever is the unit of publish: zip, tgz, etc.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext
 Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26539940.1193127846430.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf updated EJBTHREE-757:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-754) isCallerInRole
 checks should go through JACC layer (if JACC is configured)
In-Reply-To: <22848821.1161361841680.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12908346.1193127846679.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-754?page=all ]

Carlo de Wolf updated EJBTHREE-754:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> isCallerInRole checks should go through JACC layer (if JACC is configured)
> --------------------------------------------------------------------------
>
>                 Key: EJBTHREE-754
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-754
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: Security
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Anil Saldhana
>         Assigned To: Scott M Stark
>             Fix For: Branch_4_2
>
>
> Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to Scott.
> The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has configured jacc.  I am not sure what the best way to tell the xxxContext layer to use jacc helper if user desires.  Maybe a simple system property may do it.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-744) EJB3 JACC Layer
	Container Task
In-Reply-To: <25454643.1160761721812.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25816642.1193127846974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-744?page=all ]

Carlo de Wolf updated EJBTHREE-744:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> EJB3 JACC Layer Container Task
> ------------------------------
>
>                 Key: EJBTHREE-744
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-744
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: Security
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: Branch_4_2
>
>
> Container Task for validation of the ejb3 jacc layer for correct permissions creation and checking, as per JACC 1.1 specification.
> In the future, the EJB3 security layer needs alignment with the security spi.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-661) Security:
 Deploying a bean
 without mandatory org.jboss.ejb3.security.SecurityDomain results in a
 NullPointerException
In-Reply-To: <7251726.1153836311374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7228111.1193127847283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-661?page=all ]

Carlo de Wolf updated EJBTHREE-661:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-661
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-661
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: EJB 3.0 RC7 - FD
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> When setting up security in a EJB3 bean, it is mandatory adding the 
> org.jboss.ejb3.security.SecurityDomain tag. Failure to do so results 
> on a NullPointerException. 
> AS should log a more meaningful message rather than a 
> NullPointerException.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-564) Inconsistent
 results in ConsumerUnitTestCase
Message-ID: <18824322.1193127847523.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-564?page=all ]

Carlo de Wolf updated EJBTHREE-564:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Inconsistent results in ConsumerUnitTestCase
> --------------------------------------------
>
>                 Key: EJBTHREE-564
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-564
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>            Reporter: Scott M Stark
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> If I run the ConsumerUnitTestCase multiple times I start seeing failures due to method invocation order it seems.
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>     [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 16.344 sec
> BUILD SUCCESSFUL
> Total time: 21 seconds
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>     [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 14.359 sec
>     [junit] Test org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase FAILED
> BUILD SUCCESSFUL
> Total time: 19 seconds
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>     [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 14.86 sec
>     [junit] Test org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase FAILED
> BUILD SUCCESSFUL
> Total time: 19 seconds
>   <testcase classname="org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase" name="testDeploymentDescriptorQueueXA" time="2.032">
>     <failure message="expected:&lt;...1&gt; but was:&lt;...2&gt;" type="junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: expected:&lt;...1&gt; but was:&lt;...2&gt;
> 	at org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA(ConsumerUnitTestCase.java:151)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> </failure>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-509) EJB 3.0
 persistense manager
 unit name is not comming up when deploying entity bean
Message-ID: <298911.1193127847852.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-509?page=all ]

Carlo de Wolf updated EJBTHREE-509:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> EJB 3.0 persistense manager unit name is not comming up when deploying entity bean
> ----------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-509
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-509
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: EJB3 Extensions
>    Affects Versions: EJB 3.0 RC5 - PFD
>         Environment: linux, jboss 4.0.2
>            Reporter: Amit Chauhan
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> trying to implement the tutorial example provided at http://docs.jboss.org/ejb3/app-servers/tutorials/entity/entity.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-477) Implement
 @WebServiceRef and <service-ref>
Message-ID: <2522300.1193127848053.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-477?page=all ]

Carlo de Wolf updated EJBTHREE-477:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Implement @WebServiceRef and <service-ref>
> ------------------------------------------
>
>                 Key: EJBTHREE-477
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-477
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Bill Burke
>         Assigned To: William DeCoste
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> This will be fun!!!!
> Take a look at code in EJB 2.1 container.  DO NOT USE THAT CODE DIRECTLY.  I want to start removing dependencies on that code.  You can also work with WS team on this too.  This should be a HIG PRIORITY task.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-421) Put
 FlushMode.NEVER back on
 track through @FlushMode, at least in a proprietary manner
Message-ID: <31463159.1193127848210.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-421?page=all ]

Carlo de Wolf updated EJBTHREE-421:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Put FlushMode.NEVER back on track through @FlushMode, at least in a proprietary manner
> --------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-421
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-421
>             Project: EJB 3.0
>          Issue Type: Feature Request
>            Reporter: Emmanuel Bernard
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-344) Deployment should
 fail for resource injection to both field and method
Message-ID: <960141.1193127848563.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-344?page=all ]

Carlo de Wolf updated EJBTHREE-344:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Deployment should fail for resource injection to both field and method
> ----------------------------------------------------------------------
>
>                 Key: EJBTHREE-344
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-344
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: org.jboss.ejb3.test.naming.unit.BadInjectionsUnitTestCase
>            Reporter: Scott M Stark
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> I belive the indicated BadInjectionsUnitTestCase should be failing to deploy due to the attempt to inject an env-entry via both a field and method annotation. The ejb-jar.xml key env-entry value is not being injected via either mechanism it appears.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-342) Unify
 configuration file names and bootstrap
Message-ID: <16654022.1193127848752.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-342?page=all ]

Carlo de Wolf updated EJBTHREE-342:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Unify configuration file names and bootstrap
> --------------------------------------------
>
>                 Key: EJBTHREE-342
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-342
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Christian Bauer
>         Assigned To: Bill Burke
>             Fix For: Branch_4_2
>
>
> The microcontainer can be booted with StandaloneBootstrap, and it searches for jboss-beans.xml in / and META-INF.
> The E-EJB3 container is booted with EJB3StandaloneBootstrap, which searches for embedded-jboss-beans.xml in / and supports a "basepath" argument.
> Unify these two bootstrap classes. Wishlist:
> - sensible default name for the configuration file ("jboss-beans.xml" sounds good)
> - searches in default locations (/ and META-INF)
> - supports parameters to completely override not only the "basepath", but the full location of the configuration file
> The EJB3StandaloneBootstrap should _extend_ the StandaloneBootstrap, not reimplement it. The current situation makes documentation and explanation unecessarily difficult.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-322) implement
	discarding rules
Message-ID: <26444459.1193127849280.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-322?page=all ]

Carlo de Wolf updated EJBTHREE-322:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> implement discarding rules
> --------------------------
>
>                 Key: EJBTHREE-322
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-322
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC1, EJB 3.0 RC2, EJB 3.0 RC3
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>             Fix For: Branch_4_2
>
>
> we are not discarding EJB instances where appropriate.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-305) Port EJB 2.1
 tests to EJB 3.0 where appropriate
Message-ID: <10404831.1193127849461.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-305?page=all ]

Carlo de Wolf updated EJBTHREE-305:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Port EJB 2.1 tests to EJB 3.0 where appropriate
> -----------------------------------------------
>
>                 Key: EJBTHREE-305
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-305
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: EJB 3.0 RC4 - PFD
>            Reporter: Bill Burke
>         Assigned To: William DeCoste
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-217) The container
 should Instruments Hibernate classes
Message-ID: <8063433.1193127849990.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-217?page=all ]

Carlo de Wolf updated EJBTHREE-217:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> The container should Instruments Hibernate classes
> --------------------------------------------------
>
>                 Key: EJBTHREE-217
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-217
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: EJB3 Extensions
>    Affects Versions: EJB 3.0 Beta 1
>            Reporter: Emmanuel Bernard
>         Assigned To: Bill Burke
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> Right now, the user has to instrument Hibernate classes itself through a InstrumentAnt task to enable some features such as property level lazy loading
> It'd be cool if the container execute the same job at class load time in an automatic manner.
> http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#performance-fetching-lazyproperties

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-197) Deploy Hibernate
 MBean statistics in the EJB 3 Deployer
Message-ID: <29882948.1193127850160.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-197?page=all ]

Carlo de Wolf updated EJBTHREE-197:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Deploy Hibernate MBean statistics in the EJB 3 Deployer
> -------------------------------------------------------
>
>                 Key: EJBTHREE-197
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-197
>             Project: EJB 3.0
>          Issue Type: Feature Request
>            Reporter: Michael Yuan
>             Fix For: Branch_4_2
>
>
> I discussed this with Emmanuel and Steve over email. They both thought it should be fairly easy to add. The JBoss Network team needs this feature to develop profiling and monitoring tools for EJB 3 (see the linked issue).
> Can we have this feature in the JavaOne release of the product? I can demo it in the trail blazer.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-191) servlet
 initialization happens before EJB startup
Message-ID: <10910092.1193127850373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-191?page=all ]

Carlo de Wolf updated EJBTHREE-191:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> servlet initialization happens before EJB startup
> -------------------------------------------------
>
>                 Key: EJBTHREE-191
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-191
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Bill Burke
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-127) Create Docbook
	for @Consumer
Message-ID: <12882820.1193127850514.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-127?page=all ]

Carlo de Wolf updated EJBTHREE-127:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Create Docbook for @Consumer
> ----------------------------
>
>                 Key: EJBTHREE-127
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-127
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-27) Allowed methods
Message-ID: <21286672.1193127850744.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-27?page=all ]

Carlo de Wolf updated EJBTHREE-27:
----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Allowed methods
> ---------------
>
>                 Key: EJBTHREE-27
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-27
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>             Fix For: Branch_4_2
>
>
> EJB specification has semanatics for what methods can be called when.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-712) Support EJBContext
 injection through ejb-jar.xml
In-Reply-To: <24653724.1158847561251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22925182.1193128083129.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-712?page=all ]

Carlo de Wolf closed EJBTHREE-712.
----------------------------------


> Support EJBContext injection through ejb-jar.xml
> ------------------------------------------------
>
>                 Key: EJBTHREE-712
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-712
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA, AS 5.0.0.Beta3, AS 4.2.1.GA, AS 4.2.0 GA
>
>
> Spec says you use <resource-env-ref> to do injection of EJBContext into a bean.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21832578.1193128083798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Carlo de Wolf closed EJBTHREE-785.
----------------------------------


> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-786) String remove()
	method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4332572.1193128084753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Carlo de Wolf closed EJBTHREE-786.
----------------------------------


> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-815) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
In-Reply-To: <995728.1166795738121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27402274.1193128085338.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-815?page=all ]

Carlo de Wolf closed EJBTHREE-815.
----------------------------------


> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-815
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-815
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> Testcase: testQuerySingleResultExceptions took 0.058 sec
>         Caused an ERROR
> javax.persistence.NoResultException: No entity found for query
> javax.ejb.EJBException: javax.persistence.NoResultException: No entity found for query
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: javax.persistence.NoResultException: No entity found for query
>         at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:82)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySingleResultExceptions(ExceptionTestBean.java:269)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySingleResultExceptions(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySingleResultExceptions(EntityExceptionTestCa
> se.java:96)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-816) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
In-Reply-To: <23148785.1166796163032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30594639.1193128085648.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-816?page=all ]

Carlo de Wolf closed EJBTHREE-816.
----------------------------------


> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-816
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-816
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> Testcase: testQuerySetHintAndParameter took 0.035 sec
>         Caused an ERROR
> java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
> javax.ejb.EJBException: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterDescriptor(ParameterMetadata.java:55)
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterExpectedType(ParameterMetadata.java:61)
>         at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:397)
>         at org.hibernate.impl.AbstractQueryImpl.setParameter(AbstractQueryImpl.java:369)
>         at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:234)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySetHintAndParameter(ExceptionTestBean.java:311)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySetHintAndParameter(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySetHintAndParameter(EntityExceptionTestCase.
> java:103)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-817) test failure -
 org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
In-Reply-To: <25680060.1166796342815.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4279110.1193128085853.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-817?page=all ]

Carlo de Wolf closed EJBTHREE-817.
----------------------------------


> test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-817
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-817
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> Testcase: testRuntimeException took 2.058 sec
>         FAILED
> expected:<1> but was:<0>
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
>         at org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase.testRuntimeException(MDBUnitTestCase.java:292)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-818) test failure -
 org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
In-Reply-To: <1942068.1166797118725.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18831694.1193128086062.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-818?page=all ]

Carlo de Wolf closed EJBTHREE-818.
----------------------------------


> test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-818
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-818
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> Testcase: testRollback took 5.05 sec
>         FAILED
> null
> junit.framework.AssertionFailedError
>         at org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase.testRollback(MDBUnitTestCase.java:128)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-819) test failure -
 org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
In-Reply-To: <4167073.1166798501804.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33229555.1193128086295.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-819?page=all ]

Carlo de Wolf closed EJBTHREE-819.
----------------------------------


> test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-819
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-819
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> Testcase: testSSLBindings took 35.731 sec
>         Caused an ERROR
> Could not dereference object
> javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.remoting.CannotConnectException: Can not 
> get connection to server.  Problem establishing socket connection.]
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase.testSSLBindings(SSLUnitTestCase.java:68)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server.  Problem establishing socket connection.
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:267)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:48)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
>         at $Proxy1.createProxy(Unknown Source)
>         at org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:52)
>         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
>         at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
>         ... 25 more
> Caused by: java.lang.reflect.InvocationTargetException
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createClientSocket(SocketClientInvoker.java:518)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.getConnection(SocketClientInvoker.java:485)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:263)
>         ... 38 more
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:742)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:678)
>         at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
>         at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2213)
>         at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
>         at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)
>         at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:761)
>         at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
>         at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
>         at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:83)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
>         ... 45 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>         at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-838) test failure -
 org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
In-Reply-To: <8353072.1169064476539.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29568391.1193128086522.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-838?page=all ]

Carlo de Wolf closed EJBTHREE-838.
----------------------------------


> test failure - org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> -------------------------------------------------------------------
>
>                 Key: EJBTHREE-838
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-838
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: [java.version: 1.5.0_08]
> [java.vendor: BEA Systems, Inc.]
> [java.vm.version: R27.1.0-109-73164-1.5.0_08-20061129-1418-linux-ia32]
> [java.vm.name: BEA JRockit(R)]
> [java.vm.info: compiled mode]
> [os.name: Linux]
> [os.arch: i386]
> [os.version: 2.6.9-42.0.3.ELsmp]
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> Test:        testStackTrace
> Type:        failure
> Exception:   junit.framework.AssertionFailedError
> junit.framework.AssertionFailedError
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testStackTrace(RemoteUnitTestCase.java:250)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-865) test failure -
 org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with
 Sun 1.5.0_11
In-Reply-To: <12695397.1170729619498.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3918439.1193128086785.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-865?page=all ]

Carlo de Wolf closed EJBTHREE-865.
----------------------------------


> test failure - org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with Sun 1.5.0_11 
> -------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-865
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-865
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: Boss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.webservices.unit.WsUnitTestCase
> Test:        testDeployment
> Type:        error
> Exception:   org.jboss.deployment.DeploymentException
> Message:     Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ej
> b3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.tes
> t.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> org.jboss.deployment.DeploymentException: Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> 	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:991)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:471)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.processWebMethod(JSR181MetaDataBuilder.java:568)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:193)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75)
> 	at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy30.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	... 53 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: org.jboss.ws.jaxrpc.ParameterWrapping$WrapperType
> 	at javassist.CtClassType.getClassFile2(CtClassType.java:204)
> 	at javassist.CtClassType.getConstructorsCache(CtClassType.java:892)
> 	at javassist.CtClassType.getDeclaredConstructors(CtClassType.java:878)
> 	at javassist.CtNewClass.inheritAllConstructors(CtNewClass.java:87)
> 	at javassist.CtNewClass.toBytecode(CtNewClass.java:63)
> 	at javassist.CtClass.toBytecode(CtClass.java:1181)
> 	at javassist.ClassPool.toClass(ClassPool.java:883)
> 	at javassist.ClassPool.toClass(ClassPool.java:846)
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:467)
> 	... 67 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-866) test failure -
 org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) -
 with Sun 1.5.0_11
In-Reply-To: <31270078.1170729763045.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11969895.1193128087059.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-866?page=all ]

Carlo de Wolf closed EJBTHREE-866.
----------------------------------


> test failure -  org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) - with Sun 1.5.0_11 
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-866
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-866
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase
> Test:        testEJBServlet
> Type:        error
> Exception:   java.io.IOException
> Message:     Expected reply code:200, actual=500
> Expected reply code:200, actual=500
> java.io.IOException: Expected reply code:200, actual=500
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:140)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:109)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:97)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:83)
> 	at org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase.testEJBServlet(EarServletUnitTestCase.java:49)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30824092.1193128087507.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf closed EJBTHREE-883.
----------------------------------


> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33446589.1193128087731.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf closed EJBTHREE-900.
----------------------------------


> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-938) Expired messages
 are being delivered
In-Reply-To: <22096346.1175683086452.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28696158.1193128087923.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-938?page=all ]

Carlo de Wolf closed EJBTHREE-938.
----------------------------------


> Expired messages are being delivered
> ------------------------------------
>
>                 Key: EJBTHREE-938
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-938
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: mdb unit test
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** ExpirationTestMDB onMessage 1 in org.jboss.ejb3.test.mdb.ExpirationTestMDB at 27977433
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** now = 1175680736566
> 2007-04-04 11:58:56,567 INFO  [STDOUT] *** message = SpyTextMessage {
> Header {
>    jmsDestination  : QUEUE.expirationtest
>    jmsDeliveryMode : 1
>    jmsExpiration   : 1175680735655
>    jmsPriority     : 4
>    jmsMessageID    : ID:436-11756807355552
>    jmsTimeStamp    : 1175680735555
>    jmsCorrelationID: null
>    jmsReplyTo      : null
>    jmsType         : null
>    jmsRedelivered  : false
>    jmsProperties   : {foo=bar, currentTest=testExpiration, null=null}
>    jmsPropReadWrite: false
>    msgReadOnly     : true
>    producerClientId: ID:436
> }
> Body {
>    text            :expire on server
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-986) EJB3 Remoting cause
 BindException on load
In-Reply-To: <23095690.1181134458736.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14079418.1193128088603.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-986?page=all ]

Carlo de Wolf closed EJBTHREE-986.
----------------------------------


> EJB3 Remoting cause BindException on load
> -----------------------------------------
>
>                 Key: EJBTHREE-986
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-986
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: JBoss 4.2.0 GA, JDK 1.5.0_08-b03, Windows XP SP2
>            Reporter: Yvan Borgne
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>         Attachments: ejb3-interceptors-aop.xml, InvokeRemoteInterceptor.java
>
>
> After a lot of call (>3000) to an EJB3 SLSB this exception is throwed :
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://127.0.0.1:3873/]
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy0.bar(Unknown Source)
> 	at client.Test.main(Test.java:22)
> Caused by: java.net.BindException: Address already in use: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:516)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy0.bar(Unknown Source)
> 	at client.Test.main(Test.java:22)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
> 	... 10 more
> Jboss server and test client are on the same host.
> For each call, a new TCP connection is opened, with a different local port. So there is also a performance problem.
> Here is a simple code to reproduce :
> -- EJB3 remote Interface --
> package ejb;
> import javax.ejb.Remote;
> @Remote
> public interface Foo {
>   public void bar();
> }
> -- EJB3 Implementation --
> package ejb;
> import javax.ejb.Stateless;
> @Stateless
> public class FooBean implements Foo {
>   public void bar() {
>   }
> }
> -- client --
> package client;
> import java.util.Properties;
> import javax.naming.Context;
> import javax.naming.InitialContext;
> import ejb.Foo;
> public class Test {
>   public static void main(String[] args) {
>     try {
>       Properties env = new Properties();
>       env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
>       env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
>       env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
>       env.put("jnp.disableDiscovery", "true");
>       Context context = new InitialContext(env);
>       Foo foo = (Foo)context.lookup("FooBean/remote");
>       while(true) {
>         foo.bar();
>       }
>     } catch (Exception e) {
>       e.printStackTrace();
>     }
>   }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1003) implement
 @PoolClass for MDBs
 (minSession/maxSession does not control MDB instances)
In-Reply-To: <20325323.1183404117628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24350606.1193128088735.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1003?page=all ]

Carlo de Wolf closed EJBTHREE-1003.
-----------------------------------


> implement @PoolClass for MDBs (minSession/maxSession does not control MDB instances)
> ------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1003
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1003
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA, Branch_4_4
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1006) EJB3 is way too
 performant on Amstrad 6218
In-Reply-To: <16542105.1183721932962.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32969984.1193128088917.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1006?page=all ]

Carlo de Wolf closed EJBTHREE-1006.
-----------------------------------


> EJB3 is way too performant on Amstrad 6218
> ------------------------------------------
>
>                 Key: EJBTHREE-1006
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1006
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: AS 4.2.1.GA
>         Environment: Amstrad 6128
>            Reporter: Dimitris Andreadis
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> Hi,
> I've just managed to install the latest EJB3 on Amstrad 6128, and it's way too fast, I cannot play my EJB3 based games.
> Could you please add a configuration parameter to make it slower?
> Thanks :)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1025) @Local and
 @Remote on a bean class must have values
In-Reply-To: <2543807.1186060789285.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8795364.1193128089815.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1025?page=all ]

Carlo de Wolf closed EJBTHREE-1025.
-----------------------------------


> @Local and @Remote on a bean class must have values
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1025
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1025
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> From the API doc:
> "When used on the bean class, declares the local business interface(s) for a session bean. When used on an interface, designates that interface as a local business interface. In this case, no value() is provided."
> Thus the following is an illegal construct:
> @Stateless
> @Local
> @Remote
> public class OrderServiceBean implements OrderService {...}

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22536357.1193128089996.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=all ]

Carlo de Wolf closed EJBTHREE-1031.
-----------------------------------


> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1032) inconsistent
 results for
 CreateCount, AvailableCount, CurrentSize for StrictMaxPool SLSBs
In-Reply-To: <32360816.1187381960564.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8581101.1193128090384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1032?page=all ]

Carlo de Wolf closed EJBTHREE-1032.
-----------------------------------


> inconsistent results for CreateCount, AvailableCount, CurrentSize for StrictMaxPool SLSBs
> -----------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1032
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1032
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - Patch 1, AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1055) WebServiceContext
 is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22059062.1193128090601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf closed EJBTHREE-1055.
-----------------------------------


> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:00:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4894) port-component
	element not mapped
Message-ID: <7117396.1193130001476.JavaMail.jira@cloud.prod.atl2.jboss.com>

port-component element not mapped
---------------------------------

                 Key: JBAS-4894
                 URL: http://jira.jboss.com/jira/browse/JBAS-4894
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:04:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4894) port-component
	element not mapped
In-Reply-To: <7117396.1193130001476.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23237332.1193130241530.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4894?page=all ]

Thomas Diesler updated JBAS-4894:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
I can't find the port-component element mapped to the metadata model.

   <xsd:complexType name="generic-beanType">
      <xsd:sequence>
         <xsd:group ref="javaee:descriptionGroup"/>
         <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
         <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
         <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
         <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
         <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
         <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
      </xsd:sequence>
   </xsd:complexType>


> port-component element not mapped
> ---------------------------------
>
>                 Key: JBAS-4894
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4894
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I can't find the port-component element mapped to the metadata model.
>    <xsd:complexType name="generic-beanType">
>       <xsd:sequence>
>          <xsd:group ref="javaee:descriptionGroup"/>
>          <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
>          <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
>          <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
>          <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
>          <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
>          <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>       </xsd:sequence>
>    </xsd:complexType>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:06:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28494714.1193130365566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Thomas Diesler reassigned JBAS-4891:
------------------------------------

    Assignee: Thomas Diesler  (was: Alexey Loubyansky)

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:06:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17765485.1193130365779.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383844 ] 
            
Thomas Diesler commented on JBAS-4891:
--------------------------------------

Let me see if this applies to jboss descriptors only ...

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:10:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4894) port-component
	element not mapped
Message-ID: <33061446.1193130601470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4894?page=all ]

Thomas Diesler deleted JBAS-4894:
---------------------------------


> port-component element not mapped
> ---------------------------------
>
>                 Key: JBAS-4894
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4894
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>
> I can't find the port-component element mapped to the metadata model.
>    <xsd:complexType name="generic-beanType">
>       <xsd:sequence>
>          <xsd:group ref="javaee:descriptionGroup"/>
>          <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
>          <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
>          <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
>          <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
>          <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
>          <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>       </xsd:sequence>
>    </xsd:complexType>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:41:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Tue, 23 Oct 2007 05:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16503831.1193132461535.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

cheng dan reassigned JBAS-4878:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:54:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 05:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1069) persistance.xml
 with <jar-file> looks for jar file in the wrong place
In-Reply-To: <20172525.1192434603555.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22829547.1193133241746.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1069?page=all ]

Dimitris Andreadis updated EJBTHREE-1069:
-----------------------------------------

        Fix Version/s:     (was: AS 4.2.0 GA)
    Affects Version/s: AS 4.2.0 GA

> persistance.xml with <jar-file> looks for jar file in the wrong place
> ---------------------------------------------------------------------
>
>                 Key: EJBTHREE-1069
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1069
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: JBoss AS 4.2.0.GA (Hibernate 3.3.1.GA)
>            Reporter: Magnus Sandberg
>
> When using <jar-file> references in persistance.xml the Ejb3Configuration does not look for the jar relative to the jar with the persistance.xml but relative to from where jboss is started.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:56:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 05:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-905)
 SessionContext.getEJBLocalObject & SessionContext.getEJBObject() fail on
 @PostConstruct
In-Reply-To: <25443719.1173215483466.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4903002.1193133361431.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-905?page=all ]

Dimitris Andreadis updated EJBTHREE-905:
----------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.0 GA)

> SessionContext.getEJBLocalObject & SessionContext.getEJBObject() fail on @PostConstruct
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-905
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-905
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> Either call creates a new bean instance via jndi lookup. Call to getEJBLocalObject() in @PostConstruct causes infinite loop.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:03:01 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Tue, 23 Oct 2007 06:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26651825.1193133781467.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4812?page=comments#action_12383852 ] 
            
Dominik Pospisil commented on JBAS-4812:
----------------------------------------

This is NOT reproducible with current head of JBoss Cache branch 1.4.X.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:19:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 06:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18196278.1193134741459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4880?page=all ]

Colin Mondesir resolved JBAS-4880.
----------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
       Resolution: Done

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4880
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>             Fix For: JBossAS-4.2.2.GA
>
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:21:01 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 23 Oct 2007 06:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-182) adding same node type
 twice to superstate causes exception
Message-ID: <26171474.1193134861402.JavaMail.jira@cloud.prod.atl2.jboss.com>

adding same node type twice to superstate causes exception
----------------------------------------------------------

                 Key: GPD-182
                 URL: http://jira.jboss.com/jira/browse/GPD-182
             Project: JBoss jBPM GPD
          Issue Type: Bug
          Components: jpdl
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
            Reporter: Koen Aers
         Assigned To: Koen Aers
             Fix For: jBPM jPDL Designer 3.1.1


create empty process diagram
add superstate
add first node
add second node

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:23:07 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 23 Oct 2007 06:23:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1619) Multiple
	maximized windows
In-Reply-To: <8587201.1185976549535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28131812.1193134987568.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1619?page=all ]

Thomas Heute resolved JBPORTAL-1619.
------------------------------------

    Resolution: Done

> Multiple maximized windows
> --------------------------
>
>                 Key: JBPORTAL-1619
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature.
> If you follow the next steps:
> 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized
> 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window.
> you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window.
> If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it).
> Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:23:07 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 23 Oct 2007 06:23:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1619) Multiple
	maximized windows
In-Reply-To: <8587201.1185976549535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15413067.1193134987961.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1619?page=comments#action_12383859 ] 
            
Thomas Heute commented on JBPORTAL-1619:
----------------------------------------

Thanks for the report

> Multiple maximized windows
> --------------------------
>
>                 Key: JBPORTAL-1619
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature.
> If you follow the next steps:
> 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized
> 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window.
> you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window.
> If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it).
> Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4895) JAXB based
	ServiceRef meta data
Message-ID: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>

JAXB based ServiceRef meta data
-------------------------------

                 Key: JBAS-4895
                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9936548.1193136001699.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler updated JBAS-4895:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: All service-ref based clients fail. See [JBWS-1842]

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail. See [JBWS-1842]

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:42:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5957301.1193136121478.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler updated JBAS-4895:
---------------------------------

    Description: All service-ref based clients fail.  (was: All service-ref based clients fail. See [JBWS-1842])

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:46:16 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 06:46:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4824) TECH REVIEW:
 Getting Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22426067.1193136376081.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Colin Mondesir reassigned JBAS-4824:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:52:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13387331.1193136721765.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Thomas Diesler reassigned JBAS-4891:
------------------------------------

    Assignee: Scott M Stark  (was: Thomas Diesler)

The problem seems to be related jboss descriptors that use a dtd. Generally, dtd based descriptors don't seem to support namespace attributes.

Currently schemas are not available for jboss-client.xml, jboss-web.xml that can also contain <service-qname> elements

Another point is backwards compatiblity. Folks might have AS-4.2 descriptors that use dtd based descriptors with qname elements. 

If we go back to supporting the <service-qname>{http://some-namespace}Foo</service-qname> syntax, we would have different syntaxes in the standard vs. the proprietary descriptors.

What do you think?   

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:58:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4896) NPE in
	JBossMetaDataWrapper
Message-ID: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in JBossMetaDataWrapper
---------------------------

                 Key: JBAS-4896
                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:00:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 07:00:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19459601.1193137202687.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4896?page=all ]

Thomas Diesler updated JBAS-4896:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

<jboss>
  <webservices>
    <context-root>/jaxrpc-enventry</context-root>
  </webservices>
</jboss>

Caused by: java.lang.NullPointerException
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.wireOverrides(JBossMetaDataWrapper.java:247)
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:67)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)

   protected void wireOverrides()
   {
      JBossEnterpriseBeansMetaData beans = primary.getEnterpriseBeans();
      beans.setJBossMetaData(this);
   }



> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:06:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 07:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23193100.1193137561863.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4896?page=comments#action_12383876 ] 
            
Thomas Diesler commented on JBAS-4896:
--------------------------------------

BTW, I cannot build the metadata project. I suppose this is a repository issue, but

http://wiki.jboss.org/wiki/Wiki.jsp?page=Maven does not tell me how to configure this, or does it?


[tdiesler at tdvaio trunk]$ mvn
[INFO] Scanning for projects...
Downloading: http://repo1.maven.org/maven2/org/jboss/jboss-parent/3/jboss-parent-3.pom
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.jboss
ArtifactId: jboss-parent
Version: 3

Reason: Unable to download the artifact from any repository

  org.jboss:jboss-parent:pom:3

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:08:11 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 23 Oct 2007 07:08:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
In-Reply-To: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3008990.1193137691952.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1195?page=all ]

Mircea Markus resolved JBCACHE-1195.
------------------------------------

    Resolution: Done

updated tutorial and updated scripts so that it runs as expcted

> Fix tutorial for 2.1.0 series
> -----------------------------
>
>                 Key: JBCACHE-1195
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.
> Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:19:12 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 23 Oct 2007 07:19:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1153) Introduce a
 concept of structural nodes
In-Reply-To: <6252571.1185539387065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12960401.1193138352260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1153?page=all ]

Mircea Markus updated JBCACHE-1153:
-----------------------------------

            Fix Version/s: 2.2.0.GA
                               (was: 2.1.0.GA)
                               (was: 2.1.0.CR1)
    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121724

opened a topic on the forum and posponed to 2.2 GA
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121724

> Introduce a concept of structural nodes
> ---------------------------------------
>
>                 Key: JBCACHE-1153
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1153
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.2.0.GA
>
>
> Structural nodes should not be taken into consideration when processing regions for eviction.
> Typically are nodes that do not contain data (and are not intended to contain data), but are used to build tree structure.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:31:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 07:31:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4824) TECH REVIEW: Getting
 Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11807696.1193139061544.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Colin Mondesir updated JBAS-4824:
---------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Appendix.odt

Added a note about the Enterprise JavaBeans book from O'Reilly.

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt, JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:36:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 23 Oct 2007 07:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16108737.1193139361854.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Galder Zamarreno reassigned JBAS-4841:
--------------------------------------

    Assignee: Galder Zamarreno  (was: Brian Stansberry)

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Galder Zamarreno
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:48:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 07:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4824) TECH REVIEW:
 Getting Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28514600.1193140081495.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Colin Mondesir resolved JBAS-4824.
----------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
       Resolution: Done

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>             Fix For: JBossAS-4.2.2.GA
>
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt, JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:50:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 07:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4842) TECH REVIEW: Server
 Configuration Guide - TRACKER
In-Reply-To: <22836378.1192169103482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17772822.1193140201511.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4842?page=comments#action_12383889 ] 
            
Dimitris Andreadis commented on JBAS-4842:
------------------------------------------

Samson, in the respective subtasks, I see the wrong document attached to the tasks (e.g. the microkernel task has the naming document). Can you please check?

>  TECH REVIEW: Server Configuration Guide - TRACKER
> --------------------------------------------------
>
>                 Key: JBAS-4842
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4842
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 08:06:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 08:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27466405.1193141161601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris updated JBAS-4820:
-------------------------------------


Graphical Installer : (should it be identified that this is available via https://network.jboss.com ie. for subsribed users only)
ZIP download : (should it be made clear that the zip is available via both the  https://network.jboss.com with subscription, alternatively    
                              via http://labs.jboss.com/jbossas/downloads/)
RPM download (should identified that this is available via the Jboss RHN channel -http://rhn.redhat.com - for subsription users only)

I think the location where each can be quickly retrieved from is quite important for users.



> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 08:08:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 08:08:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4841612.1193141281829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris resolved JBAS-4820.
--------------------------------------

    Resolution: Done

Attached document with proposed changes

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 08:28:01 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 23 Oct 2007 08:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-182) adding same node type
 twice to superstate causes exception
In-Reply-To: <26171474.1193134861402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16761338.1193142481395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-182?page=all ]

Koen Aers closed GPD-182.
-------------------------

    Resolution: Done

> adding same node type twice to superstate causes exception
> ----------------------------------------------------------
>
>                 Key: GPD-182
>                 URL: http://jira.jboss.com/jira/browse/GPD-182
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> create empty process diagram
> add superstate
> add first node
> add second node

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:12 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1553) Improve google
 gadgets support
In-Reply-To: <16476033.1184001151561.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9619241.1193144953016.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1553?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1553:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Improve google gadgets support
> ------------------------------
>
>                 Key: JBPORTAL-1553
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1553
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final, 2.6 Final
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>            Priority: Optional
>             Fix For: 2.8 Final
>
>
> Parent task - Improve support for google gadgets support. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:13 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1556) Use
 'gmodules.com/ig/gadgetsettings?url=' to render google settings window
In-Reply-To: <20813385.1184001871617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12256857.1193144953579.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1556?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1556:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Use 'gmodules.com/ig/gadgetsettings?url=' to render google settings window
> --------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1556
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1556
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:14 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1558) do not append
 default parameters values when rendering gadget
In-Reply-To: <18480515.1184002116059.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4617533.1193144954373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1558?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1558:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> do not append default parameters values when rendering gadget
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1558
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1558
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:14 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1573) google
 directory query shows only 10 results
In-Reply-To: <26006578.1184166151558.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16762341.1193144954589.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1573?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1573:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> google directory query shows only 10 results
> --------------------------------------------
>
>                 Key: JBPORTAL-1573
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1573
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final, 2.6 Final
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> At the moment in Google Gadgets query against gadgets directory has hard coded limitation to to show only 10 results

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:13:02 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:13:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1561) google widget
 preferences cannot be updated after window creation
In-Reply-To: <25873473.1184018208231.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28243249.1193145182184.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1561?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1561:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> google widget preferences cannot be updated after window creation
> -----------------------------------------------------------------
>
>                 Key: JBPORTAL-1561
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1561
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final, 2.6 Final
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>            Priority: Minor
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> 1) add a google widget window to the page
> 2) go to AdminPortlet, navigate and click on the portlet window you added
> 3) there is edit window with widget preferences 
> 4) changing values and hitting 'update' does nothing

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:15:04 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1613) Refactor
 Content framework and Widget support
In-Reply-To: <24952500.1185448967039.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18248981.1193145304061.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1613?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1613:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Refactor Content framework and Widget support
> ---------------------------------------------
>
>                 Key: JBPORTAL-1613
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1613
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final
>            Reporter: Chris Laprun
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.8 Final
>
>
> There are several interfaces that are either duplicated or not used (when they could be: WidgetProvider is not used, ContentPortlet is under-used...).
> Several definition of edit_content mode all over the place when the definition from ContentPortlet could be used.
> Overall clean-up seems required.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:15:04 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1534) Integrate
	netvibes widgets
In-Reply-To: <31207655.1183717973218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23928202.1193145304308.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1534?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1534:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Integrate netvibes widgets
> --------------------------
>
>                 Key: JBPORTAL-1534
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1534
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>            Priority: Optional
>             Fix For: 2.8 Final
>
>
> Integrate netvibes widgets into portal- similar way google gadgets are.
> http://dev.netvibes.com/doc/howto/widget_export

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:27:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 23 Oct 2007 09:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-315) Break locks for
	state transfer
Message-ID: <24844759.1193146021921.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-315?page=all ]

Manik Surtani updated JBCACHE-315:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)

Postponing pending virtual synchrony enhancements in JGroups 2.6

> Break locks for state transfer
> ------------------------------
>
>                 Key: JBCACHE-315
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-315
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.2.0.GA
>
>
> State transfer needs to acquire a lock on the root to make sure all existing TXs have been completed. However, when a TX takes more time than the lock acquisition timeout, state transfer will fail.
> Therefore, we need to forcefully acquire the locks for the state transfer by force-releasing the existing locks, and rolling back all TXs that held those locks.
> This will ensure that state transfer always succeeds, at the expense of some rolled back TXs.
> We need to investigate how this works with optimistic locking

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:27:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 09:27:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30744775.1193146022464.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Colin Mondesir reassigned JBAS-4828:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:31:16 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 23 Oct 2007 09:31:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-905) Integrate Clover
 code coverage into hudson builds
In-Reply-To: <10530221.1166036318578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18463243.1193146276546.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-905?page=all ]

Manik Surtani updated JBCACHE-905:
----------------------------------

          Summary: Integrate Clover code coverage into hudson builds  (was: Perform code coverage analysis and add missing unit tests)
    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)
         Assignee: Manik Surtani  (was: Hany Mesha)

This was done manually in the past; changing it so it is done automatically by Hudson.

> Integrate Clover code coverage into hudson builds
> -------------------------------------------------
>
>                 Key: JBCACHE-905
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-905
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> Using a code coverage tool like Clover:
> 1) Analyse current test suite on Branch_JBossCache_1_4_0
> 2) Put up results on a wiki page
> 3) Link wiki page to this JIRA task as well as the JBossCache wiki page
> 4) Analyse gaps in the test suite and either document (on the wiki) as being too simple/obvious to test or create a unit test for this.
> Once 2.0.0 reaches CR1, perform the same on HEAD (or Branch_JBossCache_2_0_0 by then...)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:33:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 09:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7585931.1193146381646.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris reassigned JBAS-4879:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:52:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 23 Oct 2007 09:52:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4890)
 EJBAccessException: Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21397401.1193147525504.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4890?page=comments#action_12383917 ] 
            
Anil Saldhana commented on JBAS-4890:
-------------------------------------

Thomas,
  I have been waiting for some stabilization of the metamodel (which probably has happened). So I will start taking a look at this now.  We will get it done soon, in time for your Nov.1 release. :)

Anil

> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:01 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1343) Create an Ant
 task to execute a TestDriver
In-Reply-To: <15137397.1177097730166.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15576179.1193148421868.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1343?page=all ]

Julien Viet updated JBPORTAL-1343:
----------------------------------

    Assignee: Boleslaw Dawidowicz  (was: Matt Wringe)

> Create an Ant task to execute a TestDriver
> ------------------------------------------
>
>                 Key: JBPORTAL-1343
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1343
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.8 Final
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> An org.jboss.portal.common.test.driver.TestDriver is executed in Ant though the usage of the org.jboss.portal.common.test.junit.JUnitAdapter which adaps the TestDriver protocol to junit.
> It has several limitations :
> - the way to pass parameters to the test driver is convoluted and basically an hack (that works)
> - it is not possible to filter the set of tests returned by the TestDriver easily which force many times to create subclasses in order to execute each test separately

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:02 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1349) Test the test
	framework
In-Reply-To: <24874214.1177099050255.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11794439.1193148422030.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1349?page=all ]

Julien Viet updated JBPORTAL-1349:
----------------------------------

    Assignee: Julien Viet  (was: Matt Wringe)

> Test the test framework
> -----------------------
>
>                 Key: JBPORTAL-1349
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1349
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>             Fix For: 2.8 Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> The test framework should be itself tested.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:02 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1344) Unify the remote
 driver framework with different protocols
In-Reply-To: <19632390.1177097970204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26245713.1193148422182.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1344?page=all ]

Julien Viet updated JBPORTAL-1344:
----------------------------------

    Assignee: Julien Viet  (was: Matt Wringe)

> Unify the remote driver framework with different protocols
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-1344
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1344
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>             Fix For: 2.8 Final
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The framework extending the test driver framework for remoteness has 2 protocols (using the Bridge pattern) : HTTP and Web.
> It is possible to unify the two protocols using an handler mechanism that creates the next command to execute in the protocol based on a chain of responsibility.
> The benefit is to have tests that have interactions using both protocols.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:02 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1346) Improve the
 parameter value handling
In-Reply-To: <29834057.1177098390300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30150423.1193148422707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1346?page=all ]

Julien Viet resolved JBPORTAL-1346.
-----------------------------------

    Resolution: Out of Date

Since it is handled differently by the new framework

> Improve the parameter value handling
> ------------------------------------
>
>                 Key: JBPORTAL-1346
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1346
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Matt Wringe
>             Fix For: 2.8 Final
>
>
> we have :
> MonoValuedTestParameterValue extends TestParameterValue
> MultiValuedTestParameterValue extends TestParameterValue
> and 
> TestParameterValue { public abstract Object getValue(); }
> the method getValue() should not be here : a value is either mono valued or multi valued and both have nothing in common, the code client of that needs to deal with both of them explicitely.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:09:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 23 Oct 2007 10:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16550202.1193148541843.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4812?page=all ]

Brian Stansberry updated JBAS-4812:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121968

That's good to know.  Opened a forum thread for further discussion on why this happened before you shut down any nodes.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:28:01 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Tue, 23 Oct 2007 10:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3350856.1193149682000.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4812?page=all ]

Dominik Pospisil updated JBAS-4812:
-----------------------------------

    Attachment: ejb3-buddy-JBASS-4812.tgz

Attaching test log with such case.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy-JBASS-4812.tgz, ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:30:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4898) class-loading not
 found as a child of jboss-web
Message-ID: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>

class-loading not found as a child of jboss-web
-----------------------------------------------

                 Key: JBAS-4898
                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:34:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4898) class-loading not
 found as a child of jboss-web
In-Reply-To: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6620327.1193150041514.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4898?page=all ]

Thomas Diesler updated JBAS-4898:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test


<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <class-loading>
    <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
  </class-loading>
</jboss-web>


Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)


> class-loading not found as a child of jboss-web
> -----------------------------------------------
>
>                 Key: JBAS-4898
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
>   <class-loading>
>     <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
>   </class-loading>
> </jboss-web>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:42:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:42:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
Message-ID: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failed to resolve schema nsURI= location=null
---------------------------------------------

                 Key: JBAS-4899
                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:42:06 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:42:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
In-Reply-To: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19180715.1193150526557.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Thomas Diesler reassigned JBAS-4899:
------------------------------------

    Assignee: Thomas Diesler  (was: Alexey Loubyansky)

> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:48:11 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:48:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
In-Reply-To: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21603603.1193150891981.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Thomas Diesler updated JBAS-4899:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

         Assignee: Alexey Loubyansky  (was: Thomas Diesler)

> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:55:01 2007
From: jira-events at lists.jboss.org (Stale Pedersen (JIRA))
Date: Tue, 23 Oct 2007 10:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-453)
 maven-jbossaop-plugin requires
 artifact maven-jbossaop-plugin on compile classpath
In-Reply-To: <31000254.1186523875263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3305414.1193151301860.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-453?page=comments#action_12383932 ] 
            
Stale Pedersen commented on JBAOP-453:
--------------------------------------

sorry for the late response (some other issues that had higher priority before the beta release).
yes, as it is now you have to specify the dependency in the plugin and project if there is a class you inherit thats outside of the project scope. 
but afaik this is the only case where its needed and i cant see the big problem of specifing it twice as there shouldnt be many cases you need this for... 
though i can add an option that would add all project dependencies if its set, but as default i believe it shouldnt be.

> maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath
> ----------------------------------------------------------------------------------
>
>                 Key: JBAOP-453
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-453
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: maven 2
>            Reporter: Anders Andersen
>         Assigned To: Stale Pedersen
>
> In order to use the plugin I have to add the following dependencies to the client artifact dependency list.
>     <dependency>
>       <groupId>org.jboss.maven.plugins</groupId>
>       <artifactId>maven-jbossaop-plugin</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-aop</artifactId>
>       <version>2.0.0.alpha2</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-common</artifactId>
>       <version>4.0.2</version>
>     </dependency>
>     <dependency>
>       <groupId>concurrent</groupId>
>       <artifactId>concurrent</artifactId>
>       <version>1.3.4</version>
>     </dependency>
> This is relative wrong, because all maven internal artifacts ends up being nested dependent om the runtime artifact.
> See lists below.
> I think the statement
>       cl.addArguments(new String[] { "-cp", createClassPathList(project.getArtifacts())});
> is wrong.
> I tried to include only project.getPluginArtifacts(), but it gave me a NPE
> So I am not 100% sure what the code solution should be
> but it is not good to having maven artifacts in the resulting dependency list of the client-artifact
> list: (resulting depenency list)
> The ** marked should not be there
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.jar
> /Users/aka/.m2/repository/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-opends/2.6.1-SNAPSHOT/portal-test-opends-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/isorelax/isorelax/20020414/isorelax-20020414.jar
> /Users/aka/.m2/repository/jgroups/jgroups-all/2.2.7/jgroups-all-2.2.7.jar
> /Users/aka/.m2/repository/jboss/jboss-common/4.0.2/jboss-common-4.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-xml-binding/5.0.0.Alpha/jboss-xml-binding-5.0.0.Alpha.jar
> /Users/aka/.m2/repository/jboss/jboss-cache/1.2.2/jboss-cache-1.2.2.jar
> /Users/aka/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar
> /Users/aka/.m2/repository/jboss/jboss-j2se/200504122039/jboss-j2se-200504122039.jar
> /Users/aka/.m2/repository/jboss/jbossha/4.0.2/jbossha-4.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-minimal/4.0.2/jboss-minimal-4.0.2.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-common-client/4.0.4.GA/jboss-common-client-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server/2.6.1-SNAPSHOT/portal-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-saaj/4.0.4.GA/jboss-saaj-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-system/4.0.4.GA/jboss-system-4.0.4.GA.jar
> /Users/aka/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar
> /Users/aka/.m2/repository/org/jboss/portal/core/portal-core/2.6.1-SNAPSHOT/portal-core-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/javassist/3.4.ga/javassist-3.4.ga.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test/2.6.1-SNAPSHOT/portal-test-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/format/portal-format/2.6.1-SNAPSHOT/portal-format-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.jar
> /Users/aka/.m2/repository/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar
> /Users/aka/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> /Users/aka/.m2/repository/jboss/jboss-system/4.0.2/jboss-system-4.0.2.jar
> /Users/aka/.m2/repository/javax/mail/mail/1.4/mail-1.4.jar
> /Users/aka/.m2/repository/hibernate/hibernate/3.2.0/hibernate-3.2.0.jar
> /Users/aka/.m2/repository/jboss/jboss-j2ee/4.0.4.GA/jboss-j2ee-4.0.4.GA.jar
> /Users/aka/.m2/repository/jaxen/jaxen/1.0-FCS/jaxen-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server-test-framework/2.6.1-SNAPSHOT/portal-server-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-project/2.0.2/maven-project-2.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-microcontainer/4.0.4.GA/jboss-microcontainer-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common/2.6.1-SNAPSHOT/portal-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/selenium/selenium-java-client-driver/0.0/selenium-java-client-driver-0.0.jar
> /Users/aka/.m2/repository/javax/portlet/portlet-api/1.0/portlet-api-1.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/theme/portal-theme/2.6.1-SNAPSHOT/portal-theme-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.jar
> /Users/aka/.m2/repository/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss/4.0.4.GA/jboss-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
> /Users/aka/.m2/repository/wsdl4j/wsdl4j/1.5.1/wsdl4j-1.5.1.jar
> /Users/aka/.m2/repository/concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/jboss/jboss-backport-concurrent/2.1.0.GA/jboss-backport-concurrent-2.1.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jbosssx/4.0.4.GA/jbosssx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> /Users/aka/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> /Users/aka/.m2/repository/trove/trove/1.1-beta-5/trove-1.1-beta-5.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/2.0.0.alpha2/jboss-aop-2.0.0.alpha2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-model/2.0.2/maven-model-2.0.2.jar
> /Users/aka/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar
> /Users/aka/.m2/repository/log4j/log4j/1.2.8/log4j-1.2.8.jar
> /Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet/2.6.1-SNAPSHOT/portal-portlet-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/jboss-aspect-library/1.5/jboss-aspect-library-1.5.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-server/portal-portlet-server/2.6.1-SNAPSHOT/portal-portlet-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jmx/4.0.4.GA/jboss-jmx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-impl/1.1.1/myfaces-impl-1.1.1.jar
> /Users/aka/.m2/repository/org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/jboss-aop/1.5.0.GA/jboss-aop-1.5.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common-junit/2.6.1-SNAPSHOT/portal-common-junit-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-profile/2.0.2/maven-profile-2.0.2.jar
> /Users/aka/.m2/repository/org/visigoths/freemaker/freemarker/2.3.9/freemarker-2.3.9.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-agent/2.6.1-SNAPSHOT/portal-test-agent-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-dependency/4.0.4.GA/jboss-dependency-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-federation/portal-portlet-federation/2.6.1-SNAPSHOT/portal-portlet-federation-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/msv/msv/20020414/msv-20020414.jar
> /Users/aka/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
> /Users/aka/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
> /Users/aka/.m2/repository/slide/webdavlib/2.0/webdavlib-2.0.jar
> **/Users/aka/.m2/repository/org/jboss/maven/plugins/maven-jbossaop-plugin/1.0-SNAPSHOT/maven-jbossaop-plugin-1.0-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/web/portal-web/2.6.1-SNAPSHOT/portal-web-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-api/1.1.1/myfaces-api-1.1.1.jar
> /Users/aka/.m2/repository/org/jboss/portal/wsrp/portal-wsrp-gen/2.6.1-SNAPSHOT/portal-wsrp-gen-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/jems/portal-jems/2.6.1-SNAPSHOT/portal-jems-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/registration/portal-registration/2.6.1-SNAPSHOT/portal-registration-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jaxrpc/4.0.4.GA/jboss-jaxrpc-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/security/portal-security/2.6.1-SNAPSHOT/portal-security-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/api/portal-api/2.6.1-SNAPSHOT/portal-api-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar
> /Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> /Users/aka/.m2/repository/dom4j/dom4j/1.4/dom4j-1.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/identity/portal-identity/2.6.1-SNAPSHOT/portal-identity-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/explode-common/2.6.1-SNAPSHOT/explode-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet-test-framework/2.6.1-SNAPSHOT/portal-portlet-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.2/plexus-utils-1.4.2.jar
> /Users/aka/.m2/repository/jboss/jnpserver/3.2.3/jnpserver-3.2.3.jar
> /Users/aka/.m2/repository/opends/opends/0.0/opends-0.0.jar

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:22:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 23 Oct 2007 11:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-607) SEQUENCER: incorrect
 ordering on concurrent sends
Message-ID: <30774057.1193152921433.JavaMail.jira@cloud.prod.atl2.jboss.com>

SEQUENCER: incorrect ordering on concurrent sends
-------------------------------------------------

                 Key: JGRP-607
                 URL: http://jira.jboss.com/jira/browse/JGRP-607
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.4.1 SP5, 2.5.2, 2.6


The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:38:01 2007
From: jira-events at lists.jboss.org (Michael Newcomb (JIRA))
Date: Tue, 23 Oct 2007 11:38:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
Message-ID: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>

FLUSH not safe in simultaneous flush situation
----------------------------------------------

                 Key: JGRP-608
                 URL: http://jira.jboss.com/jira/browse/JGRP-608
             Project: JGroups
          Issue Type: Feature Request
    Affects Versions: 2.6
            Reporter: Michael Newcomb
         Assigned To: Bela Ban


I'm running into a few problems when multiple members request a FLUSH at the same time.

I am still in the process of analyzing the situation, but here are a few problems:

private void handleStartFlush(Message msg, FlushHeader fh) {
  byte oldPhase = flushPhase.transitionToFirstPhase();
  if(oldPhase == FlushPhase.START_PHASE){
    sendBlockUpToChannel();
    onStartFlush(msg.getSrc(), fh);
  }else if(oldPhase == FlushPhase.FIRST_PHASE){
    Address flushRequester = msg.getSrc();
    Address coordinator = null;
    synchronized(sharedLock){
      if(flushCoordinator != null)
        coordinator = flushCoordinator;
      else
        coordinator = flushRequester;
    }

After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().

IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().

The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.

Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.

If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.

So the following code handles that situation...

private void handleStartFlush(Message msg, FlushHeader fh) {
  ...
  }else if(oldPhase == FlushPhase.FIRST_PHASE){
    ...
    if(flushRequester.compareTo(coordinator) < 0){
      rejectFlush(fh.viewID, coordinator);
      ...
      synchronized(sharedLock){
        flushCoordinator = flushRequester;
      }
    }

If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.

I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.

I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:42:07 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 23 Oct 2007 11:42:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6722102.1193154127588.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Bela Ban reassigned JGRP-608:
-----------------------------

    Assignee: Vladimir Blagojevic  (was: Bela Ban)

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:42:07 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 23 Oct 2007 11:42:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30784152.1193154127794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Bela Ban updated JGRP-608:
--------------------------

    Fix Version/s: 2.6
         Priority: Critical  (was: Major)

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:46:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 11:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17425028.1193154361707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris updated JBAS-4822:
-------------------------------------


HI,
a few point made in this chapter:

1. There are 3 links under the Chapter header are these really necessary? The chapter is only 2 pages long
2. It is mentioned in 4.1 that the ZIP can be downloaded from http://labs.jboss.com/jbossas/downloads/ but the same document in chapter 2 it is talking about installation types for the EAP. Should we explain that this is also available from https://network.jboss.com?
3.  4.3.  Post Installation Security Configuration 
        - I found that both JMX & Web Console do not actually, in 4.2.2 ,require authentication when the installation guide says they do
        - It is mentioned that no user accounts exist, but the JBossAdmin account is present
        - The section in creating accounts/authentication is not straight forward to a new user (I propose new structure and addition of 
           enabling <security-domain> JAAS, not mentioned)

I hope this is of help

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:46:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 11:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25691630.1193154361872.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris updated JBAS-4822:
-------------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-4.odt

Attached file

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:48:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 11:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24468325.1193154481707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris resolved JBAS-4822.
--------------------------------------

    Resolution: Done

done

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:50:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 11:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12741129.1193154601976.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler reassigned JBAS-4895:
------------------------------------

    Assignee: Scott M Stark  (was: Thomas Diesler)

JBossServiceReferencesMetaData is probably missing. Please see dependent issue

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:54:12 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 23 Oct 2007 11:54:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16894414.1193154852237.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-608?page=comments#action_12383943 ] 
            
Vladimir Blagojevic commented on JGRP-608:
------------------------------------------

Michael,

I was aware of the these problems but as we were in the process of simplifying flush (JGRP-598) I never got around to verify how concurrent flush works with a revised FLUSH version. Would you please verify FLUSH.java version 1.75 that I checked in this morning and see if you still experience these problems.

Vladimir

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:09:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4900) cannot redeploy
 after deployment error
Message-ID: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>

cannot redeploy after deployment error
--------------------------------------

                 Key: JBAS-4900
                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:13:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21402911.1193155981597.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Thomas Diesler updated JBAS-4900:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"

This forces a restart of the appserver between debugging sessions.

Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
        at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
        at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
        at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
        at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
        at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
        at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
        at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
        at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
        at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
        ... 62 more
18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
...
18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS MISSING DEPLOYERS: Name

vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.



         Assignee: Adrian Brock

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:13:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4390989.1193155981764.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Thomas Diesler updated JBAS-4900:
---------------------------------

    Priority: Critical  (was: Major)

I put this on critical because its a major time killer.

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:30:01 2007
From: jira-events at lists.jboss.org (Michael Newcomb (JIRA))
Date: Tue, 23 Oct 2007 12:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18096460.1193157001626.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-608?page=comments#action_12383946 ] 
            
Michael Newcomb commented on JGRP-608:
--------------------------------------

I will check it out.

Upon initial inspection:

470         if(!flushInProgress){
471             flushInProgress = true;
472             sendBlockUpToChannel();
473             onStartFlush(msg.getSrc(), fh);

You might want to use an AtomicBoolean for flushInProgress and use flushInProgress.compareAndSet(false, true) as your test. As it is, it might lead to more problems because of multiple blocks going up the channel.

I do see the second problem of not notifying the winning requestor that his flush is going to be accepted has been fixed by calling onStartFlush().

484             if(flushRequester.compareTo(coordinator) < 0){
485                 rejectFlush(fh.viewID, coordinator);
486                 if(log.isDebugEnabled()){
487                     log.debug("Rejecting flush at " + localAddress
488                               + " to current flush coordinator "
489                               + coordinator
490                               + " and switching flush coordinator to "
491                               + flushRequester);
492                 }
493                 onStartFlush(flushRequester, fh);

However, the situation still exists where the flushCoordinator may not be set by the winner of the initial flushInProgress = true and another flush requestor could execute the following and flushCoordinator wasn't set yet.

477             synchronized(sharedLock){
478                 if(flushCoordinator != null)
479                     coordinator = flushCoordinator;
480                 else
481                     coordinator = flushRequester;
482             }

So, in that sense you really can't even use a boolean, you need to execute some code that sets the flushCoordinator (and other onStartFlush stuff)while checking to see if a flush is in progress (all in a protected section of code).


> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:32:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
Message-ID: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>

Reverse paths are not allowed (containing a . or ..)
----------------------------------------------------

                 Key: JBAS-4901
                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:36:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28983543.1193157361523.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Thomas Diesler updated JBAS-4901:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
This change breaks backward compatibility

IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd

To be lees strict, this should be valid

vf.findChild("foo/bar/../file.txt")

and this not

vf.findChild("foo/bar/../../../file.txt")

         Assignee: Adrian Brock

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:44:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4902) nested jar not
	deployed
Message-ID: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>

nested jar not deployed
-----------------------

                 Key: JBAS-4902
                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:46:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27013291.1193157961749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4902?page=all ]

Thomas Diesler updated JBAS-4902:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
A nested jar inside an ear is not deployed 

2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear

[tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
META-INF/
META-INF/MANIFEST.MF
jaxws-jbws1813.jar
META-INF/application.xml

<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
  
  <module>
    <java>jaxws-jbws1813.jar</java>
  </module>
  
</application>

[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
    [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

         Assignee: Scott M Stark

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:46:02 2007
From: jira-events at lists.jboss.org (Clint Popetz (JIRA))
Date: Tue, 23 Oct 2007 12:46:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26445797.1193157962929.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=comments#action_12383952 ] 
            
Clint Popetz commented on EJBTHREE-785:
---------------------------------------

Did this fix make it into 4.2.2 GA as indicated?  Because I'm still seeing the problem with 4.2.2 that I thought was this bug, i.e. an EJB with no interfaces, but which contains an ancestor that implements an interface marked @Local:


@Local
public interface anInterface {  } 

public abstract class BaseClass implements anInterface { }

@Stateless 
public class SubClass extends BaseClass { }

still yields:

java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface: SubClass

Though the stack trace is now different:

        at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:115)
        at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.getBusinessInterfaces(EJB3InterceptorsFactory.java:172)
        at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.isBusinessMethod(EJB3InterceptorsFactory.java:122)

leading me to believe that the code in question has been updated.

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:58:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 23 Oct 2007 12:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7043033.1193158681532.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Scott M Stark updated JBAS-4895:
--------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097985

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:06:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8051977.1193159161649.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=comments#action_12383957 ] 
            
Dimitris Andreadis commented on EJBTHREE-1062:
----------------------------------------------

Is there any intention of fixing this in AS 4.2.3 ?

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:16:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 13:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4903) EJB 2.1 view cannot
	be realized
Message-ID: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJB 2.1 view cannot be realized
-------------------------------

                 Key: JBAS-4903
                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:18:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 13:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4903) EJB 2.1 view cannot
	be realized
In-Reply-To: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10381561.1193159881536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4903?page=all ]

Thomas Diesler updated JBAS-4903:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test

19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
        at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
        at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
        at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
        at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)

@WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
@WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
@SOAPBinding(style = SOAPBinding.Style.RPC)
@Remote(EJB3RemoteInterface.class)
@RemoteHome(EJB3RemoteHome.class)
@RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
@Stateless(name = "FooBean01")
public class EJB3Bean01 implements EJB3RemoteInterface
{
   @WebMethod
   public String echo(String input)
   {
      return input;
   }
}


         Assignee: Carlo de Wolf

> EJB 2.1 view cannot be realized
> -------------------------------
>
>                 Key: JBAS-4903
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test
> 19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
> 19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
> 19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
> 19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
> java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
>         at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
>         at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
>         at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)
> @WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
> @WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> @Remote(EJB3RemoteInterface.class)
> @RemoteHome(EJB3RemoteHome.class)
> @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
> @Stateless(name = "FooBean01")
> public class EJB3Bean01 implements EJB3RemoteInterface
> {
>    @WebMethod
>    public String echo(String input)
>    {
>       return input;
>    }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:28:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 23 Oct 2007 13:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12589274.1193160481739.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4896?page=comments#action_12383960 ] 
            
Scott M Stark commented on JBAS-4896:
-------------------------------------

See http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenSettings for setting up the jboss repositories

> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:34:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27809378.1193160841493.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

Dimitris Andreadis reassigned JBAS-4850:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21479335.1193160961604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

Dimitris Andreadis updated JBAS-4850:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt

Attach the corrected document.

The biggest change was to remove references to the 'production' config.

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32397458.1193160961777.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4850?page=comments#action_12383962 ] 
            
Dimitris Andreadis commented on JBAS-4850:
------------------------------------------

Should I close the issue now?

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:43:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12282842.1193161383918.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

Dimitris Andreadis resolved JBAS-4850.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:45:01 2007
From: jira-events at lists.jboss.org (janssk1 (JIRA))
Date: Tue, 23 Oct 2007 13:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3040) Add
 jboss-ws4ee.sar to docs/examples/ws4ee
Message-ID: <4756350.1193161501448.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3040?page=comments#action_12383963 ] 
            
janssk1 commented on JBAS-3040:
-------------------------------

This docs/examples/ws4ee dir is not available in 4.0.5.GA.
Quite annoying..

> Add jboss-ws4ee.sar to docs/examples/ws4ee
> ------------------------------------------
>
>                 Key: JBAS-3040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3040
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>             Fix For: JBossAS-4.0.4.CR2
>
>
> The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:50:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 13:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4856) Issues related to
 the new metadata model
In-Reply-To: <28485098.1192452063304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11694371.1193161801918.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4856?page=all ]

Thomas Diesler updated JBAS-4856:
---------------------------------

    Summary: Issues related to the new metadata model  (was: Fix web service issues related to the new metadata model)

> Issues related to the new metadata model
> ----------------------------------------
>
>                 Key: JBAS-4856
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4856
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:54:06 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-3040) Add jboss-ws4ee.sar
 to docs/examples/ws4ee
Message-ID: <15415745.1193162046320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3040?page=all ]

Dimitris Andreadis reopened JBAS-3040:
--------------------------------------

             

> Add jboss-ws4ee.sar to docs/examples/ws4ee
> ------------------------------------------
>
>                 Key: JBAS-3040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3040
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:54:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-3040) Add jboss-ws4ee.sar to
 docs/examples/ws4ee
Message-ID: <4578148.1193162047212.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3040?page=all ]

Dimitris Andreadis closed JBAS-3040.
------------------------------------

    Fix Version/s:     (was: JBossAS-4.0.4.CR2)
       Resolution: Won't Fix

Re-open to indicate that this was actually not done.

> Add jboss-ws4ee.sar to docs/examples/ws4ee
> ------------------------------------------
>
>                 Key: JBAS-3040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3040
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 14:35:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 23 Oct 2007 14:35:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <376426.1193164501589.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-608?page=comments#action_12383974 ] 
            
Vladimir Blagojevic commented on JGRP-608:
------------------------------------------

Yes you are right. flushCoordinator and flushInProgress should be in the same protected section of the code. 



> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 15:32:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 23 Oct 2007 15:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7447181.1193167921511.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=comments#action_12383989 ] 
            
Andrew Rubinger commented on EJBTHREE-1062:
-------------------------------------------

Will leave the decision to merge w/ Branch_4_2 between Dimitris and Carlo; was not ported initially as not indicated in "Fix Versions". 

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:09:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 23 Oct 2007 16:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4890) EJBAccessException:
 Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25630264.1193170141476.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4890?page=all ]

Anil Saldhana updated JBAS-4890:
--------------------------------

    JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098040

Thomas, I have added a thread for further discussion.

> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 16:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8238710.1193171761572.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis updated JBAS-4848:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt

Attach the reviewed file.

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 16:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16086461.1193171761961.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis reassigned JBAS-4848:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:36:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 16:36:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12297441.1193171762229.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis resolved JBAS-4848.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:07:06 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 23 Oct 2007 18:07:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1296) Drools Release
	4.0.3
In-Reply-To: <4893834.1193101503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13553479.1193177226375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1296?page=all ]

Fernando Meyer closed JBRULES-1296.
-----------------------------------

    Resolution: Done

> Drools Release 4.0.3
> --------------------
>
>                 Key: JBRULES-1296
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1296
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:11:01 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
Message-ID: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow simple configuration of jbpm-mail.war.
--------------------------------------------

                 Key: JBPM-1074
                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
             Project: JBoss jBPM
          Issue Type: Feature Request
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Jboss AS
            Reporter: Chris Sweeney
         Assigned To: Tom Baeyens


Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:11:01 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
In-Reply-To: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16400254.1193177461844.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1074?page=comments#action_12384005 ] 
            
Chris Sweeney commented on JBPM-1074:
-------------------------------------

I've attached the two files that need to be modified...

> Allow simple configuration of jbpm-mail.war.
> --------------------------------------------
>
>                 Key: JBPM-1074
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Jboss AS
>            Reporter: Chris Sweeney
>         Assigned To: Tom Baeyens
>
> Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:15:01 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
In-Reply-To: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24436158.1193177701469.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1074?page=all ]

Chris Sweeney updated JBPM-1074:
--------------------------------

    Attachment: web.xml
                InboxServlet.java

Path is jpdl/dist/src/test/resources/webapp/WEB-INF/web.xml
and
jpdl/dist/src/test/java/org/jbpm/mail/InboxServlet.java

> Allow simple configuration of jbpm-mail.war.
> --------------------------------------------
>
>                 Key: JBPM-1074
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Jboss AS
>            Reporter: Chris Sweeney
>         Assigned To: Tom Baeyens
>         Attachments: InboxServlet.java, web.xml
>
>
> Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:19:11 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:19:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
In-Reply-To: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30678301.1193177951724.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1074?page=all ]

Chris Sweeney updated JBPM-1074:
--------------------------------

    Attachment: jbpm-mail.war

This is a  version that doesn't refresh the page automatically and listens on port 2525 (better for selenium testing).

> Allow simple configuration of jbpm-mail.war.
> --------------------------------------------
>
>                 Key: JBPM-1074
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Jboss AS
>            Reporter: Chris Sweeney
>         Assigned To: Tom Baeyens
>         Attachments: InboxServlet.java, jbpm-mail.war, web.xml
>
>
> Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 19:26:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 23 Oct 2007 19:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-807) Allow assignment of
 jBPM variables via EL evaluation
In-Reply-To: <31566747.1166470838937.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16747366.1193181961845.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-807?page=all ]

Ronald van Kuijk updated JBPM-807:
----------------------------------

    Fix Version/s: jBPM jPDL 3.2.3

I used seam before, I used jBPM before, but now I started using them both in one project. This feature would be really helpful. It has no 'fix version' so I put 3.2.3 on it, but not sure it is realistic. 3.3. might be. 

> Allow assignment of jBPM variables via EL evaluation
> ----------------------------------------------------
>
>                 Key: JBPM-807
>                 URL: http://jira.jboss.com/jira/browse/JBPM-807
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>            Reporter: Gavin King
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value.
> What I want is to be able to say:
> <assign variable="orderId" value="#{order.id}"/>
> when a transition occurs.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 19:50:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 23 Oct 2007 19:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-807) Allow assignment of
 jBPM variables via EL evaluation
In-Reply-To: <31566747.1166470838937.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14919659.1193183401769.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-807?page=comments#action_12384015 ] 
            
Ronald van Kuijk commented on JBPM-807:
---------------------------------------

The reason I want this is that I cannot find a good example within seam where processvariables are set. So I thought of writing a jbpm actionhandler specifically for a process that can do this.

> Allow assignment of jBPM variables via EL evaluation
> ----------------------------------------------------
>
>                 Key: JBPM-807
>                 URL: http://jira.jboss.com/jira/browse/JBPM-807
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>            Reporter: Gavin King
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value.
> What I want is to be able to say:
> <assign variable="orderId" value="#{order.id}"/>
> when a transition occurs.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 20:52:10 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 20:52:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <399395.1193187130172.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-713?page=all ]

Ron Sigal updated JBREM-713:
----------------------------

    Assignee: Ron Sigal  (was: Tom  Elrod)

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 20:59:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Tue, 23 Oct 2007 20:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32085567.1193187541608.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

samson kittoli reopened JBAS-4850:
----------------------------------

             
re-opened to allow any further contributions.

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:01:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Tue, 23 Oct 2007 21:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22479020.1193187661468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli reopened JBAS-4848:
----------------------------------

             
re-opened to allow any further contribution.

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:06:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 21:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20429685.1193187961413.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384020 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

With a couple of small changes to org.jboss.remoting.transport.coyote.CoyoterInvoker, org.jboss.remoting.transport.coyote.ssl.RemotingSSLImplementation, and org.jboss.remoting.transport.coyote.ssl.RemotingSSLSupport, the http transport works with either the tomcat jars or jbossweb.jar.

Update build.xml so that tests.functional and tests.functional.core run all http related tests with both jbossweb.jar and tomcat jars.

Added jbossweb/jbossweb.jar to lib directory.  jbossweb.jar is version 2.0.0.GA.

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:12:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 21:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-825) Verify that
 CoyoteInvoker works with Apache Portable Runtime
Message-ID: <16554394.1193188321512.JavaMail.jira@cloud.prod.atl2.jboss.com>

Verify that CoyoteInvoker works with Apache Portable Runtime
------------------------------------------------------------

                 Key: JBREM-825
                 URL: http://jira.jboss.com/jira/browse/JBREM-825
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Trustin Lee


The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars.  When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:

21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
	at org.jboss.remoting.Client.invoke(Client.java:1632)
	at org.jboss.remoting.Client.invoke(Client.java:548)
	at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at junit.framework.TestCase.runTest(TestCase.java:154)
	at junit.framework.TestCase.runBare(TestCase.java:127)
	at junit.framework.TestResult$1.protect(TestResult.java:106)
	at junit.framework.TestResult.runProtected(TestResult.java:124)
	at junit.framework.TestResult.run(TestResult.java:109)
	at junit.framework.TestCase.run(TestCase.java:118)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at junit.framework.TestSuite.run(TestSuite.java:203)
	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
	... 31 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:12:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 21:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-825) Verify that
 CoyoteInvoker works with Apache Portable Runtime
In-Reply-To: <16554394.1193188321512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10562101.1193188321631.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-825?page=all ]

Ron Sigal updated JBREM-825:
----------------------------

    Assignee:     (was: Trustin Lee)

> Verify that CoyoteInvoker works with Apache Portable Runtime
> ------------------------------------------------------------
>
>                 Key: JBREM-825
>                 URL: http://jira.jboss.com/jira/browse/JBREM-825
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>
> The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars.  When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:
> 21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
> 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
> 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
> 	at org.jboss.remoting.Client.invoke(Client.java:1632)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> 	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
> 	... 31 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:18:01 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 21:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
In-Reply-To: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9631690.1193188681443.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ]

Takayoshi Kimura updated JBAS-4893:
-----------------------------------

    Description: 
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another, JSESSIONID won't be changed
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.


  was:
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.



> JvmRouteValve (UseJK) for non session replication setup
> -------------------------------------------------------
>
>                 Key: JBAS-4893
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Takayoshi Kimura
>
> Currently JBoss doesn't install JvmRouteValve for non session
> replication setup. However, it's still useful in the following
> scenario:
> * 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
> * A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
> * The node AAA crashed
> * The request goes node BBB, lost session, recreate another, JSESSIONID won't be changed
> * The node AAA recovered
> * The request comes back to the node AAA, lost session again
> Enabling JvmRouteValve can prevent last failure.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:16:06 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:16:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28276950.1193202966325.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

cheng dan updated JBAS-4821:
----------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-3.odt

Since there is no graphical installer for 4.2.2 available now, I tested this chapter with enterprise-installer-4.2.0-2.CP01.ep1.3.jar from CSP.
1. The installer file name is not exactly.
2. During installation, language choose step is not shown.
3. Release notes step is missing in doc. 



> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:20:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4821) TECH REVIEW:
 Installation Guide
 - Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23065425.1193203201783.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

cheng dan resolved JBAS-4821.
-----------------------------

    Resolution: Done

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:31:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10477631.1193203863555.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

samson kittoli updated JBAS-4849:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:33:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32173606.1193203981407.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4849?page=comments#action_12384037 ] 
            
samson kittoli commented on JBAS-4849:
--------------------------------------

correct document attached.

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:35:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:35:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24966671.1193204101446.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

samson kittoli updated JBAS-4847:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:37:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30861959.1193204221817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

samson kittoli updated JBAS-4846:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt

transactions on JBoss file attached.

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:37:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26733902.1193204221988.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

samson kittoli updated JBAS-4845:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt

messaging on JBoss file attached

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt, JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:48:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13068076.1193204881679.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

cheng dan updated JBAS-4878:
----------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-5.odt

In linux, if JAVA_HOME didn't set, the GUI uninstaller doesn't work.
The GUI uninstaller invoke "/bin/sh -c '$JAVA_HOME/bin/java -jar /home/cdan/EnterprisePlatform-4.2.0.GA_CP01_Release/Uninstaller/uninstaller.jar'"

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt, JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:48:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10330210.1193204881875.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

cheng dan resolved JBAS-4878.
-----------------------------

    Resolution: Done

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt, JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 02:59:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 02:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17874501.1193209141907.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli resolved JBAS-4848.
----------------------------------

    Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:01:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 03:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19921518.1193209261486.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

samson kittoli resolved JBAS-4850.
----------------------------------

    Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:16:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 24 Oct 2007 03:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-607) SEQUENCER:
 incorrect ordering on concurrent sends
In-Reply-To: <30774057.1193152921433.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20855061.1193210161605.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-607?page=comments#action_12384051 ] 
            
Bela Ban commented on JGRP-607:
-------------------------------

The bug is that, when we don't send seqnos in order, then the receiver will always keep the highest seqno, e.g. when we send
1 2 4 3, then - when 4 is received - the highest seqno will be 4 (regardless of whether there is a gap since we haven't yet received 3), and when 3 is finally received, it will get discarded.
Solution: maintain the highest received and highest delivered seqno (SeqnoTable)

Even if we synchronized down(), this wouldn't help, as 3 and 4 will get sent out in order, but a message loss of 3 might still cause receivers to receive 4 first and then the (retransmitted) 3.

> SEQUENCER: incorrect ordering on concurrent sends
> -------------------------------------------------
>
>                 Key: JGRP-607
>                 URL: http://jira.jboss.com/jira/browse/JGRP-607
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6, 2.4.1 SP5, 2.5.2
>
>
> The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:30:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 24 Oct 2007 03:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9673603.1193211001591.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=comments#action_12384052 ] 
            
Carlo de Wolf commented on EJBTHREE-1075:
-----------------------------------------

Error message must contain 'EJBTHREE-1075'.

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:30:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 24 Oct 2007 03:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7930100.1193211001794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=all ]

Carlo de Wolf updated EJBTHREE-1075:
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                       (was: HEAD)

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 04:13:12 2007
From: jira-events at lists.jboss.org (Jo Geraerts (JIRA))
Date: Wed, 24 Oct 2007 04:13:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1075)
 org.hibernate.hql.ast.QuerySyntaxException in
 org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds)
Message-ID: <19469021.1193213592540.JavaMail.jira@cloud.prod.atl2.jboss.com>

org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds)
----------------------------------------------------------------------------------------------------------

                 Key: JBPM-1075
                 URL: http://jira.jboss.com/jira/browse/JBPM-1075
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2,  jBPM jPDL 3.2.1, jBPM jPDL 3.2, jBPM jPDL 3.2 beta 2, jBPM 3.1.4
         Environment: java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)


            Reporter: Jo Geraerts
         Assigned To: Tom Baeyens


I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries. 

So we end up in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds) with the same List ( with 0 entries)

I get this Exception:

10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
ubtree [
      select distinct ti
      from org.jbpm.taskmgmt.exe.PooledActor pooledActor
           join pooledActor.taskInstances ti
      where pooledActor.actorId in (  )
        and ti.actorId is null
        and ti.isSuspended != true
        and ti.isOpen = 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

        


From jira-events at lists.jboss.org  Wed Oct 24 04:23:05 2007
From: jira-events at lists.jboss.org (Jo Geraerts (JIRA))
Date: Wed, 24 Oct 2007 04:23:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1075)
 org.hibernate.hql.ast.QuerySyntaxException in
 org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
In-Reply-To: <19469021.1193213592540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24147192.1193214185680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1075?page=all ]

Jo Geraerts updated JBPM-1075:
------------------------------

        Summary: org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)  (was: org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds))
    Description: 
I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds)  with a List with 0 entries. 

So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)

I get this Exception:

10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
ubtree [
      select distinct ti
      from org.jbpm.taskmgmt.exe.PooledActor pooledActor
           join pooledActor.taskInstances ti
      where pooledActor.actorId in (  )
        and ti.actorId is null
        and ti.isSuspended != true
        and ti.isOpen = true
  ]




  was:
I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries. 

So we end up in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds) with the same List ( with 0 entries)

I get this Exception:

10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
ubtree [
      select distinct ti
      from org.jbpm.taskmgmt.exe.PooledActor pooledActor
           join pooledActor.taskInstances ti
      where pooledActor.actorId in (  )
        and ti.actorId is null
        and ti.isSuspended != true
        and ti.isOpen = true
  ]





I reported the wrong functions.... Time for some more coffee i guess

> org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1075
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1075
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2, jBPM 3.1.4, jBPM jPDL 3.2 beta 2,  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>         Environment: java version "1.5.0_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
>            Reporter: Jo Geraerts
>         Assigned To: Tom Baeyens
>
> I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds)  with a List with 0 entries. 
> So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)
> I get this Exception:
> 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
> ubtree [
>       select distinct ti
>       from org.jbpm.taskmgmt.exe.PooledActor pooledActor
>            join pooledActor.taskInstances ti
>       where pooledActor.actorId in (  )
>         and ti.actorId is null
>         and ti.isSuspended != true
>         and ti.isOpen = 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

        


From jira-events at lists.jboss.org  Wed Oct 24 04:27:01 2007
From: jira-events at lists.jboss.org (Jo Geraerts (JIRA))
Date: Wed, 24 Oct 2007 04:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1075)
 org.hibernate.hql.ast.QuerySyntaxException in
 org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
In-Reply-To: <19469021.1193213592540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22938906.1193214421698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1075?page=all ]

Jo Geraerts updated JBPM-1075:
------------------------------

    Attachment: patch

I think this patch will fix the issue.

Sorry, it's a little verbose  but i couldnt get eclipse to make it some smaller.





> org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1075
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1075
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2, jBPM 3.1.4, jBPM jPDL 3.2 beta 2,  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>         Environment: java version "1.5.0_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
>            Reporter: Jo Geraerts
>         Assigned To: Tom Baeyens
>         Attachments: patch
>
>
> I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds)  with a List with 0 entries. 
> So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)
> I get this Exception:
> 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
> ubtree [
>       select distinct ti
>       from org.jbpm.taskmgmt.exe.PooledActor pooledActor
>            join pooledActor.taskInstances ti
>       where pooledActor.actorId in (  )
>         and ti.actorId is null
>         and ti.isSuspended != true
>         and ti.isOpen = 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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:23:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13625960.1193217781788.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris updated JBAS-4879:
-------------------------------------


Chapter 6. Testing your Installation

- This geared too much towards the EAP (from what I am informed it should cover all users subscrived  & community)
- Based on that the text that appears as a result of starting the server is not representative of both as there is no "production" configuration in the community release
- Also, it goes on to explain that "production" server configuration is the default one that can be started by ./run.sh or ./rub.bat again
 non representative of both type of users. 
- I feel explaining how to start each of the configurations and then that production is only part of the EAP as well as that it will be the default one for EAP installations whilst "default" would be the default configuration fon non-EAP would be more useful
- Finally, maybe due to editor or version of editor I am unable to see figure 6.1

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt, JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:23:02 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20088643.1193217782040.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris updated JBAS-4879:
-------------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-6.odt

File Attached

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt, JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:23:02 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11076814.1193217782399.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris resolved JBAS-4879.
--------------------------------------

    Resolution: Done

Done

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt, JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:26:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5368537.1193217961474.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris reassigned JBAS-4826:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 06:24:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 06:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1034) Allow JMS
 administered objects to be created programmatically
In-Reply-To: <9067157.1186598389285.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14757411.1193221445744.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1034?page=all ]

Tim Fox updated JBMESSAGING-1034:
---------------------------------

        Summary: Allow JMS administered objects to be created programmatically  (was: Allow connection factories to be created programmatically)
    Description: We should allow connection factories, queues and topics to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI.  (was: We should allow connection factories to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI.)

> Allow JMS administered objects to be created programmatically
> -------------------------------------------------------------
>
>                 Key: JBMESSAGING-1034
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1034
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> We should allow connection factories, queues and topics to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 06:50:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 06:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-726) Create
 clustering tests for integration test suite
In-Reply-To: <1288401.1168296267440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22493791.1193223001513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-726?page=all ]

Tim Fox updated JBMESSAGING-726:
--------------------------------

              Summary: Create clustering tests for integration test suite  (was: Write/Ellect some Clustering tests to go into Integration Testsuite on ApplicationServer)
    Affects Version/s:     (was: 1.2.0.Beta1)

The AS integration test suite currently doesn't contain any JMS clustering tests.

Need to write some clustering and failover tests.

Should contain at least distributed queue, distributed topic.

Producer and consumer failover with different ack modes, transacted, auto_ack, dups_ok

> Create clustering tests for integration test suite
> --------------------------------------------------
>
>                 Key: JBMESSAGING-726
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-726
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: EAP 4.3 Integration, AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 06:56:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 06:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as
 that is being removed from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14149555.1193223361438.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Tim Fox closed JBMESSAGING-1102.
--------------------------------

    Resolution: Done

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:07:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23786202.1193224021672.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=comments#action_12384089 ] 
            
Tim Fox commented on JBMESSAGING-1084:
--------------------------------------

We currently have some dependencies on JBoss AS security implementation - need to moev this to AS codebase

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:14:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <33398962.1193224444665.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ]

Tim Fox updated JBMESSAGING-406:
--------------------------------

        Summary: Persistence refactoring  (was: Enabled local persistent storage per node)
    Description: 
Need to refactor persistence so each node has its own storage.

We should provide at least three local persistence manager configs:

1) JDBC local pm that works out of the box with HSQL - not recommended for production.

2) BDB based pm that customers need to download - recommended for best performance.

Should optimise for the SAN use case.

Need to consider whether we need to support replication for failover too.

  was:
Implement non shared file based persistent store.

Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this.

Also look at HOWL. http://howl.objectweb.org/


> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:18:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:18:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor
	client side model
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27792930.1193224682140.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

        Summary: Refactor client side model  (was: Refactor AOP usage)
    Description: 
Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.

Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.

We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

The classes should be chosen to represent generic messaging, not just JMS (e.g. no need for a producer).

We also need to have an extension point so customers can add their own vanilla interceptors.

  was:
Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.

Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.

We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.


> Refactor client side model
> --------------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.
> The classes should be chosen to represent generic messaging, not just JMS (e.g. no need for a producer).
> We also need to have an extension point so customers can add their own vanilla interceptors.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:20:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:20:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18286507.1193224811635.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=comments#action_12384090 ] 
            
Tim Fox commented on JBMESSAGING-544:
-------------------------------------

The scope of this task should be extended to analsye the current wire format and alter as necessary.

A client and server side abstraction should be created allowing messages to be sent from either client or server and handlers regisstered to receive messages asynchronously.

Both synchronous and one way sends should be supported

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:22:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20795905.1193224921499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=all ]

Tim Fox updated JBMESSAGING-544:
--------------------------------

    Assignee: Jeff Mesnil  (was: Tim Fox)

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:29:01 2007
From: jira-events at lists.jboss.org (Rainer Langbehn (JIRA))
Date: Wed, 24 Oct 2007 07:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27539266.1193225341781.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=all ]

Rainer Langbehn updated JBRULES-1273:
-------------------------------------

    Attachment: maven-drools-plugins.zip

Hi Fernando,
please take a look at the attached code.

Bye
Rainer

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Fernando Meyer
>         Attachments: maven-drools-plugins.zip
>
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:16:02 2007
From: jira-events at lists.jboss.org (Vijesh (JIRA))
Date: Wed, 24 Oct 2007 08:16:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCLUSTER-187) Local instead of
 remote lookup happens when bean is clustered
Message-ID: <22932880.1193228162122.JavaMail.jira@cloud.prod.atl2.jboss.com>

Local instead of remote lookup happens when bean is clustered
-------------------------------------------------------------

                 Key: JBCLUSTER-187
                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-187
             Project: JBoss Clustering
          Issue Type: Bug
      Security Level: Public (Everyone can see)
         Environment: Linux/Widows 
            Reporter: Vijesh
         Assigned To: Brian Stansberry



1) Two different ejb 2.1 applications. Let's call them A1 and A2
2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.

The issue.

When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.

Expected behaviour:

In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2

Jboss; 4.0.5
jdk: 1.5_05
ejb; 2.1
stateless beans


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:16:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:16:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-373) Different
 persistance destinations for different JMS destinations
Message-ID: <28864420.1193228162331.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-373?page=all ]

Tim Fox closed JBMESSAGING-373.
-------------------------------

    Resolution: Rejected

Rejected since JBM 2 will use local storage

> Different persistance destinations for different JMS destinations
> -----------------------------------------------------------------
>
>                 Key: JBMESSAGING-373
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-373
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.0.0, 1.0.1.CR1
>            Reporter: Milena
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> We need to store the messages from different queues into a different tables, ot at least to separate them somehow.
> This is not possible with the current JBOSS Messaging as I was told.
> The motivation behind is that since we have a very high load on some of the queues, the persistance table appears a bottleneck for the rest of the messaging.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:18:01 2007
From: jira-events at lists.jboss.org (Vijesh (JIRA))
Date: Wed, 24 Oct 2007 08:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCLUSTER-187) Local instead of
 remote
 lookup happens when bean is clustered (in server to server calls)
In-Reply-To: <22932880.1193228162122.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26164995.1193228281589.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCLUSTER-187?page=all ]

Vijesh updated JBCLUSTER-187:
-----------------------------

        Summary: Local instead of remote lookup happens when bean is clustered (in server to server calls)  (was: Local instead of remote lookup happens when bean is clustered)
    Description: 
1) Two different ejb 2.1 applications. Let's call them A1 and A2
2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.

The issue.

When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.

Expected behaviour:

In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2

Jboss; 4.0.5
jdk: 1.5_05
ejb; 2.1
stateless beans


  was:

1) Two different ejb 2.1 applications. Let's call them A1 and A2
2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.

The issue.

When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.

Expected behaviour:

In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2

Jboss; 4.0.5
jdk: 1.5_05
ejb; 2.1
stateless beans



> Local instead of remote lookup happens when bean is clustered (in server to server calls)
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-187
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-187
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: Linux/Widows 
>            Reporter: Vijesh
>         Assigned To: Brian Stansberry
>
> 1) Two different ejb 2.1 applications. Let's call them A1 and A2
> 2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
> 3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
> 4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.
> The issue.
> When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
> But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.
> Expected behaviour:
> In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2
> Jboss; 4.0.5
> jdk: 1.5_05
> ejb; 2.1
> stateless beans

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:18:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-314) Extend
 messaging core to be fully functioning
Message-ID: <3239503.1193228281817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ]

Tim Fox updated JBMESSAGING-314:
--------------------------------

               Summary: Extend messaging core to be fully functioning  (was: Ensure Messaging core has no dependencies on the JMS facade)
     Original Estimate:     (was: 2 days)
    Remaining Estimate:     (was: 2 days)
           Description: The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients.  (was: Messaging core still has some dependencies on the jms facade. These should be factored out.)

> Extend messaging core to be fully functioning
> ---------------------------------------------
>
>                 Key: JBMESSAGING-314
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:20:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-815) Extra message
 created if server fails when send and ACK are synchronized
In-Reply-To: <5708755.1170803906788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13573254.1193228401885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ]

Tim Fox closed JBMESSAGING-815.
-------------------------------

    Resolution: Duplicate Issue

> Extra message created if server fails when send and ACK are synchronized
> ------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-815
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-815
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.0.1.SP3
>            Reporter: Clebert Suconic
>             Fix For: 2.0.0 Beta 1
>
>
> MultiThreadFailoverTest::testFailureOnSendReceiveSynchronized fails for this bug
> This test poisons the server to wait consumer and sender to be in a same point before crashing it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:20:02 2007
From: jira-events at lists.jboss.org (Trustin Lee (JIRA))
Date: Wed, 24 Oct 2007 08:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3524353.1193228402369.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12384094 ] 
            
Trustin Lee commented on JBREM-821:
-----------------------------------

I agree with Tim that throwing a SocketException when the connection pool is exhausted doesn't make sense.  However, changing Remoting to throw RemotingException might potentially break backward compatibility although I am not sure.  Ron could clarify this.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:31:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor
	client side model
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5210259.1193229063010.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Refactor client side model
> --------------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.
> The classes should be chosen to represent generic messaging, not just JMS (e.g. no need for a producer).
> We also need to have an extension point so customers can add their own vanilla interceptors.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:31:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <1812724.1193229063131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ]

Tim Fox updated JBMESSAGING-406:
--------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:33:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-25) Microcontainer
	integration
Message-ID: <10579808.1193229181696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ]

Tim Fox updated JBMESSAGING-25:
-------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Andy Taylor
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:33:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29754436.1193229181948.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=all ]

Tim Fox updated JBMESSAGING-544:
--------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:08:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Wed, 24 Oct 2007 09:08:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4145904.1193231282109.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4828?page=comments#action_12384100 ] 
            
Colin Mondesir commented on JBAS-4828:
--------------------------------------

In section 4.4.1 is says: "you need to first of all edit the build.xml file and edit the value of jboss-dist to reflect the location where the JBoss Application Server is installed. "

In the version of the JSF-EJB3 application I have downloaded there is no "jboss-dist" in build.xml.
...
<project name="HelloWorld"
         default="main" basedir=".">
    
  <description>Hello World</description>
  <property name="projname" value="jsfejb3" />

  <property file="../build.properties"/>
  <property name="jboss.deploy"
    location="${jboss.home}/server/default/deploy"/>
...




Inaddition the build fails unless you create a "lib" directory under ".../gettingstarted/jsfejb3":
...
Buildfile: build.xml

compile:
    [javac] Compiling 4 source files to /home/cmondesir/gettingstarted/jsfejb3/build/classes

BUILD FAILED
/home/cmondesir/gettingstarted/jsfejb3/build.xml:43: /home/cmondesir/gettingstarted/jsfejb3/lib not found.
...



Otherwise all the instructions work and the application runs as described.



> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:20:06 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Wed, 24 Oct 2007 09:20:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4827) TECH REVIEW:
 Getting Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23876605.1193232006707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir reassigned JBAS-4827:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:50:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 24 Oct 2007 09:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4904) Improve error
 message when binding fails
Message-ID: <21830480.1193233801646.JavaMail.jira@cloud.prod.atl2.jboss.com>

Improve error message when binding fails
----------------------------------------

                 Key: JBAS-4904
                 URL: http://jira.jboss.com/jira/browse/JBAS-4904
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Naming
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Andrew Rubinger
         Assigned To: Scott M Stark
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA


Upon attempt to bind an a subcontext to an address already bound by an object, the following exception occurs:

java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context 
at org.jboss.util.naming.Util.createSubcontext(Util.java:69) 
at org.jboss.util.naming.Util.rebind(Util.java:125) 
at org.jboss.util.naming.Util.rebind(Util.java:113)

Error message should be in form "Can't bind subContext/obj, because subContext is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:52:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 24 Oct 2007 09:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3876232.1193233921801.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=comments#action_12384111 ] 
            
Andrew Rubinger commented on EJBTHREE-1045:
-------------------------------------------

Linked dependency

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:54:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Wed, 24 Oct 2007 09:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6621366.1193234041717.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Vladimir Blagojevic resolved JGRP-608.
--------------------------------------

    Resolution: Done

Commit set:
FLUSH.java 1.76


> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:54:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Wed, 24 Oct 2007 09:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-598) Simplify FLUSH
In-Reply-To: <10363312.1190795201069.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6211567.1193234041986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-598?page=all ]

Vladimir Blagojevic resolved JGRP-598.
--------------------------------------

    Resolution: Done

Resolved on 2.6 branch.
Commit set:
FLUSH.java 1.76


Need to be back ported to 2.5.

> Simplify FLUSH
> --------------
>
>                 Key: JGRP-598
>                 URL: http://jira.jboss.com/jira/browse/JGRP-598
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.4, 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> #1 Superfluous FLUSH-COMPLETED phase ?
> --------------------------------------
> It seems we don't need the FLUSH-COMPLETED phase, it is sufficient for
> the FLUSH leader to do a START-FLUSH and wait for all FLUSH-OK
> messages. Why ? Because the reconciliation protocol will reconcile
> messages before the view installation (or state transfer).
> Example: {A,B,C}. E sends message M and then crashes. Only C receives
> M.
> - A does a START-FLUSH
> - B and C send a FLUSH-OK back to A. This means that all multicasts
> from B will be seen by A *before* B's FLUSH-OK is received, and all
> multicasts from C will be seen by A before C's FLUSH-OK is received by
> A. HOWEVER, C will not necessarily send M to A before sending the
> FLUSH-OK message. This is only done through the reconciliation
> protocol !
> - FLUSH-COMPLETED can be removed, the digest that's part of
> FLUSH-COMPLETED has to moved to FKLUSH-OK phase.
> - FLUSH-OK is unicast *not* multicast.
> #2 Superfluous STOP-FLUSH-OK phase ?
> ------------------------------------
> Why do we need the acks here ? JGroups guarantees the STOP-FLUSH
> message is delivered to all non-faulty members, so why wait fr the
> STOP-FLUSH-OK ? 
> If we make STOP-FLUSH *OOB* (JGRP-337), then this should work ! We can
> get rid of STOP-FLUSH-OK !! Just send STOP-FLUSH as OOB multicast.
> Note: this requires the concurrent stack, so possibly check for
> concurrent stack. Throw an exception if concurrent stack is not
> present when FLUSH is used. So, these changes cannot be applied to
> 2.4, only to 2.5 and 2.6.
> #3 Timeouts
> -----------
> - ClientGmsImpl: has a hard coded timeout of 4 secs
> - CoordGmsImpl also has a timeout for block()
> - If we *need* timeouts, we should get them from the FLUSH protocol !
> CoorsGmsImpl.startFlush() should *not* have a timeout, this should be
> in FLUSH itself. startFlush() should block forever, until it gets the ack
> #4 Spurious FLUSH-OK in the diagram
> -----------------------------------
> In the JOIN diagram, probably also in the state transfer diagram

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 10:09:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 24 Oct 2007 10:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4905) Resolve EJB3 / Web
 Service integration issues
Message-ID: <10015790.1193234941460.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve EJB3 / Web Service integration issues
---------------------------------------------

                 Key: JBAS-4905
                 URL: http://jira.jboss.com/jira/browse/JBAS-4905
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Thomas Diesler
             Fix For: JBossAS-4.2.3.GA


This is a container for relevant ejb3/jbossws integration issues

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 10:58:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Wed, 24 Oct 2007 10:58:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5679608.1193237882036.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4828?page=comments#action_12384134 ] 
            
Colin Mondesir commented on JBAS-4828:
--------------------------------------

index.xhtml has a header like this: <h2>Seam POJO</h2>.
Should it not be something like <h2>JSF-EJB3 example</h2>.

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 10:58:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 10:58:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
Message-ID: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
------------------------------------------------------------------------------------

                 Key: JBAS-4906
                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Clustering, XML services
    Affects Versions: JBossAS-4.2.2.GA,  JBossAS-5.0.0.Beta3
            Reporter: Galder Zamarreno
         Assigned To: Brian Stansberry
            Priority: Minor


For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
docs/examples/binding-manager/sample-bindings.xml 

i.e.

ports-default

<service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config portName="Port" hostName="BindAddress">
<attribute name="RmiPort">1101</attribute>
<attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
<attribute name="AutoDiscoveryGroup">1102</attribute>
</delegate-config>
<binding port="1100" host="${jboss.bind.address}"/>
</service-config> 
....

ports-01

<service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config portName="Port" hostName="BindAddress">
<attribute name="RmiPort">1201</attribute>
<attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
<attribute name="AutoDiscoveryGroup">1202</attribute>
</delegate-config>
<binding port="1200" host="${jboss.bind.address}"/>
</service-config> 
...


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:11:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 11:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16320412.1193238662323.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384140 ] 
            
Brian Stansberry commented on JBAS-4906:
----------------------------------------

How would autodiscovery work if different servers are using different multicast addresses and ports?

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:11:02 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 24 Oct 2007 11:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1204) Investogate
 shutdown hook usage in an MBeanServer environment
Message-ID: <5831751.1193238662428.JavaMail.jira@cloud.prod.atl2.jboss.com>

Investogate shutdown hook usage in an MBeanServer environment
-------------------------------------------------------------

                 Key: JBCACHE-1204
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1204
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.CR1, 2.1.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:15:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 24 Oct 2007 11:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1205) Data shipped with
 NodeModified
 events different on different ccache instances in the cluster
Message-ID: <24023938.1193238901431.JavaMail.jira@cloud.prod.atl2.jboss.com>

Data shipped with NodeModified events different on different ccache instances in the cluster
--------------------------------------------------------------------------------------------

                 Key: JBCACHE-1205
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1205
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.CR1, 2.1.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:28:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 24 Oct 2007 11:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4903) EJB 2.1 view cannot
	be realized
In-Reply-To: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16314490.1193239681604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4903?page=all ]

Andrew Rubinger reassigned JBAS-4903:
-------------------------------------

    Assignee: Andrew Rubinger  (was: Carlo de Wolf)

> EJB 2.1 view cannot be realized
> -------------------------------
>
>                 Key: JBAS-4903
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Andrew Rubinger
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test
> 19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
> 19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
> 19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
> 19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
> java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
>         at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
>         at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
>         at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)
> @WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
> @WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> @Remote(EJB3RemoteInterface.class)
> @RemoteHome(EJB3RemoteHome.class)
> @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
> @Stateless(name = "FooBean01")
> public class EJB3Bean01 implements EJB3RemoteInterface
> {
>    @WebMethod
>    public String echo(String input)
>    {
>       return input;
>    }
> }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:45:12 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 11:45:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-835) revet to
 Hibernate's PersistenceXmlLoader
In-Reply-To: <26261978.1168895332931.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29840031.1193240712432.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-835?page=comments#action_12384148 ] 
            
Dimitris Andreadis commented on EJBTHREE-835:
---------------------------------------------

Is this fixed in HEAD? We use HEM 3.3.1.GA there.

> revet to Hibernate's PersistenceXmlLoader
> -----------------------------------------
>
>                 Key: EJBTHREE-835
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-835
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> The default PersistenceUnitTransactionType is JTA in Java EE and RESOURCE_LOCAL in Java SE.  Currently HEM returns RESOURCE_LOCAL no matter what.  HEM is fixed but until it revs in JBoss head, I have copied the persistence.xml parsing to EJB3 project.
> Please remove org.jboss.ejb3.entity.PersistenceXmlLoader from SVN when HEM revs and revert to Hibernate 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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:49:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 11:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-789) build.xml and
 component-info.xml - version numbers and imports need to be updated
In-Reply-To: <1955110.1163617421727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17601904.1193240941698.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-789?page=comments#action_12384150 ] 
            
Dimitris Andreadis commented on EJBTHREE-789:
---------------------------------------------

Is this issue still current for Branch_4_2 ???

> build.xml and component-info.xml - version numbers and imports need to be updated
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-789
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-789
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Vladimir Ralev
>            Priority: Critical
>             Fix For: Branch_4_2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repository-zip target's comp-version, like this (use appropriate version string):
> <target name="repository-zip" depends="jars"
>     description="Create the repository.jboss.com jboss/ejb3 component contents">
>     <!-- The binary component version -->
>     <property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />
>     <!-- Pack the ejb3.deployer -->
>     <zip destfile="${build.lib}/ejb3-deployer.zip">
>       <zipfileset dir="${build.lib}">
>         <include name="ejb3.deployer/**" />
>       </zipfileset>
>     </zip>
>     <!-- Create a zip file with the component structure -->
>     <zip destfile="${build.lib}/jboss-ejb3-repo.zip">
>       <!-- The component-info.xml -->
>       <zipfileset dir="${build.etc}" prefix="${comp-version}">
>         <include name="component-info.xml" />
>       </zipfileset>
>       <!-- The bin/ejb3.deployer -->
>       <zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer">
>         <include name="ejb3-deployer.zip" />
>       </zipfileset>
>       <!-- The lib client jars -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/lib">
>         <include name="hibernate-client.jar" />
>         <include name="jboss-ejb3-client.jar" />
>       </zipfileset>
>       <!-- The resources deploy descriptors -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/resources">
>         <include name="ejb3-clustered-sfsbcache-service.xml" />
>         <include name="ejb3-entity-cache-service.xml" />
>         <include name="ejb3-interceptors-aop.xml" />
>       </zipfileset>
>     </zip>
>   </target>
> and ejb3\src\etc\component-info.xml (the version attribute):
> <project name="jboss/ejb3-component-info">
>    <component id="jboss/ejb3"
>               licenseType="lgpl"
>               version="1.0.0.CR9-jboss4.0.5"
>               description="The EJB3 deployer for integration with jboss-4.0.x">
>       <artifact id="ejb3-clustered-sfsbcache-service.xml"/>
>       <artifact id="ejb3-entity-cache-service.xml"/>
>       <artifact id="ejb3-interceptors-aop.xml"/>
>       <artifact id="ejb3.deployer" />
>       <artifact id="hibernate-client.jar"/>
>       <artifact id="jboss-ejb3-client.jar"/>
>       <import componentref="javassist">
>         <compatible version="3.2.0.CR1"/>
>         <compatible version="3.2.0.CR2"/>
>       </import>
>       <import componentref="hibernate-annotations">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="hibernate-entitymanager">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="jboss/remoting">
>         <compatible version="1.4.1_final"/>
>         <compatible version="1.4.2.GA"/>
>       </import>
>       <import componentref="jboss/aop">
>       	<compatible version="1.5.1.GA"/>
>         <compatible version="1.5.2.GA"/> <--------------- IS 1.5.2.GA COMPATIBLE?
>       </import>
>       <export>
>          <include input="hibernate-client.jar"/>
>          <include input="jboss-ejb3-client.jar"/>
>       </export>
>    </component>
> </project>

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:49:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 11:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1120) Data channel
 from
 MultiplexerChannelFactory prevents state transfers from other users of the
 shared channel
Message-ID: <2574382.1193240941938.JavaMail.jira@cloud.prod.atl2.jboss.com>

Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel
-----------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1120
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core Distributed Support
    Affects Versions: 1.4.0.GA
            Reporter: Brian Stansberry
         Assigned To: Tim Fox


JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang.

Problem is JBM's MultiplexerChannelFactory creates the data channel as follows:

public Channel createDataChannel() throws Exception
{
      return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
         new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE);
}

The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service.  JBM never calls getState(), so it *must not* pass Boolean.TRUE.  Valid usages are:

public Channel createDataChannel() throws Exception
{
      String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"};
      return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
         new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature);
}

or 

public Channel createDataChannel() throws Exception
{
      return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
         new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE);
}

The former invokes a convenience method that delegates to the latter.

Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState().  If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.)

When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState().

I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:53:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 11:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28721789.1193241181708.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384151 ] 
            
Galder Zamarreno commented on JBAS-4906:
----------------------------------------

I made the assumption that the customer was running these nodes in different 
clusters, although looking at the case again, this is not clear.

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:55:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 24 Oct 2007 11:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33368623.1193241301915.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12384152 ] 
            
Fernando Meyer commented on JBRULES-1273:
-----------------------------------------

Hi Rainer, I'm taking a look in your code!! :) 
regards 



> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Fernando Meyer
>         Attachments: maven-drools-plugins.zip
>
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 11:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2471582.1193241421745.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384155 ] 
            
Brian Stansberry commented on JBAS-4906:
----------------------------------------

Running the nodes in different clusters is not the standard usage of ServiceBindingManager.  We can't break the standard usage for this use case. Perhaps a wiki document explaining how to do this would be appropriate.

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:03:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 12:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30343710.1193241783025.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris updated JBAS-4826:
-------------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-2.odt

Comments in the document attached

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:03:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 12:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21974561.1193241783219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384159 ] 
            
Galder Zamarreno commented on JBAS-4906:
----------------------------------------

+1

Not standard usage is enough to reject it.

I'm double checking with the customer to get a better 
understanding of their use case. Should have done it 
before :$

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:03:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 12:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20519737.1193241783403.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris resolved JBAS-4826.
--------------------------------------

    Resolution: Done

Done

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:07:12 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Wed, 24 Oct 2007 12:07:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27731147.1193242032392.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

Shelly McGowan reassigned JBAS-4885:
------------------------------------

    Assignee: Shelly McGowan

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:07:12 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Wed, 24 Oct 2007 12:07:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25810647.1193242032204.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

Shelly McGowan reassigned JBAS-4844:
------------------------------------

    Assignee: Shelly McGowan

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt, JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:09:01 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Wed, 24 Oct 2007 12:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4843) TECH REVIEW: Server
 Configuration Guide - AppendixB - Use Alternative
 Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <784079.1193242141519.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

Shelly McGowan reassigned JBAS-4843:
------------------------------------

    Assignee: Shelly McGowan

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:11:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 24 Oct 2007 12:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1204) Investogate
 shutdown hook usage in an MBeanServer environment
In-Reply-To: <5831751.1193238662428.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24681982.1193242261406.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1204?page=all ]

Manik Surtani resolved JBCACHE-1204.
------------------------------------

    Resolution: Done

> Investogate shutdown hook usage in an MBeanServer environment
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1204
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1204
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:11:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 12:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4829) TECH REVIEW:
 Getting Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9003905.1193242261578.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Stelios Koussouris reassigned JBAS-4829:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:15:01 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Wed, 24 Oct 2007 12:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBBUILD-425) Fix maven bug in
	release plugin
In-Reply-To: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25446440.1193242501449.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-425?page=all ]

Paul Gier updated JBBUILD-425:
------------------------------

    Comment: was deleted

> Fix maven bug in release plugin
> -------------------------------
>
>                 Key: JBBUILD-425
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> There is an issue when using a test-jar in during a release.
> http://jira.codehaus.org/browse/MRELEASE-285 
> This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:19:01 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Wed, 24 Oct 2007 12:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBBUILD-425) Fix maven bug in
 release plugin
In-Reply-To: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3907471.1193242741490.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBBUILD-425?page=comments#action_12384163 ] 
            
Paul Gier commented on JBBUILD-425:
-----------------------------------

This issue is caused by a bug in the maven jar plugin (http://jira.codehaus.org/browse/MJAR-75).  The current version of the jar plugin sets the wrong artifact type.  The issue is already fixed, but not released.  A version of the jar plugin with the patch should be added to the jboss repository so that it can be used by the projects that need it.

> Fix maven bug in release plugin
> -------------------------------
>
>                 Key: JBBUILD-425
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> There is an issue when using a test-jar in during a release.
> http://jira.codehaus.org/browse/MRELEASE-285 
> This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:48:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 12:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5104839.1193244481831.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

Dimitris Andreadis updated JBAS-4849:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt)

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:53:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 12:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-609) Javadoc
	JChannelFactory
Message-ID: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>

Javadoc JChannelFactory
-----------------------

                 Key: JGRP-609
                 URL: http://jira.jboss.com/jira/browse/JGRP-609
             Project: JGroups
          Issue Type: Task
    Affects Versions: 2.5.1
            Reporter: Brian Stansberry
         Assigned To: Bela Ban


org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:00:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30940829.1193245203471.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

Dimitris Andreadis updated JBAS-4849:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt

Attached the reviewed file, really minor corrections.

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:00:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30965944.1193245203811.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

Dimitris Andreadis resolved JBAS-4849.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done
         Assignee: Dimitris Andreadis

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:02:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:02:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4608715.1193245335030.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis updated JBAS-4848:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt)

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:06:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29626567.1193245561612.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis updated JBAS-4847:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt)

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:06:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16272103.1193245561829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis reassigned JBAS-4847:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:10:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2657363.1193245802030.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis updated JBAS-4847:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt

Attached reviewed doc. Tiny changes.

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:10:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33252523.1193245802368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis resolved JBAS-4847.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:12:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9241460.1193245921477.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis updated JBAS-4846:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt)

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:12:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18226516.1193245921629.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis reassigned JBAS-4846:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:23:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15161788.1193246581567.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis updated JBAS-4846:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt

Attach reviewed doc. Explain that JBoss TS (JTA) is now the default transaction manager.

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:23:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8528339.1193246581856.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis resolved JBAS-4846.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:48:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 13:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1078)
 EJB3InterceptorsFactory.createPerJoinpoint() should log String
 representation of Array, not Array reference
Message-ID: <5384765.1193248081989.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJB3InterceptorsFactory.createPerJoinpoint() should log String representation of Array, not Array reference
-----------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1078
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1078
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3
            Reporter: Galder Zamarreno


EJB3InterceptorsFactory.createPerJoinpoint()

InterceptorInfo[] infos = container.getInterceptorRepository().getBusinessInterceptors(container, method);
...
log.debug("Bound interceptors for joinpoint: " + method + " - " + infos);

The log message is meaningless. It will print an array reference.

This should be instead:

log.debug("Bound interceptors for joinpoint: " + method + " - " + Arrays.toString(infos));

InterceptorInfo implements toString()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:48:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 13:48:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1078)
 EJB3InterceptorsFactory.createPerJoinpoint() should log String
 representation of Array, not Array reference
In-Reply-To: <5384765.1193248081989.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6269592.1193248082365.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1078?page=all ]

Galder Zamarreno reassigned EJBTHREE-1078:
------------------------------------------

    Assignee: Carlo de Wolf

> EJB3InterceptorsFactory.createPerJoinpoint() should log String representation of Array, not Array reference
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1078
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1078
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 5.0.0.Beta3, AS 4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> EJB3InterceptorsFactory.createPerJoinpoint()
> InterceptorInfo[] infos = container.getInterceptorRepository().getBusinessInterceptors(container, method);
> ...
> log.debug("Bound interceptors for joinpoint: " + method + " - " + infos);
> The log message is meaningless. It will print an array reference.
> This should be instead:
> log.debug("Bound interceptors for joinpoint: " + method + " - " + Arrays.toString(infos));
> InterceptorInfo implements toString()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:16:04 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 24 Oct 2007 14:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4907) JDK logging levels
 don't match our standard levels
Message-ID: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>

JDK logging levels don't match our standard levels
--------------------------------------------------

                 Key: JBAS-4907
                 URL: http://jira.jboss.com/jira/browse/JBAS-4907
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: David Lloyd
         Assigned To: Scott M Stark
             Fix For:  JBossAS-5.0.0.Beta3


The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.

Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:18:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 24 Oct 2007 14:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4907) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12273488.1193249881463.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4907?page=all ]

David Lloyd updated JBAS-4907:
------------------------------

    Attachment: JBAS-4907.patch

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBAS-4907
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4907
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: David Lloyd
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:20:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 14:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1079)
 Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or
 jboss.xml was included in the deployment
Message-ID: <15539969.1193250002098.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or jboss.xml was included in the deployment
---------------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1079
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1079
             Project: EJB 3.0
          Issue Type: Feature Request
    Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3
            Reporter: Galder Zamarreno
         Assigned To: Carlo de Wolf


Ejb3HandlerFactory.getInstance() could do with some DEBUG logging to 
indicate whether an ejb-jar.xml and/or jboss.xml was included in the 
deployment or not.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:20:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 14:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1079)
 Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or
 jboss.xml was included in the deployment
In-Reply-To: <15539969.1193250002098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16153257.1193250002329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1079?page=all ]

Galder Zamarreno updated EJBTHREE-1079:
---------------------------------------

    Issue Type: Task  (was: Feature Request)

> Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or jboss.xml was included in the deployment
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1079
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1079
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: AS 5.0.0.Beta3, AS 4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> Ejb3HandlerFactory.getInstance() could do with some DEBUG logging to 
> indicate whether an ejb-jar.xml and/or jboss.xml was included in the 
> deployment or not.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:04:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 24 Oct 2007 15:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4907) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7872899.1193252641772.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4907?page=comments#action_12384202 ] 
            
David Lloyd commented on JBAS-4907:
-----------------------------------

Forgot to add - if you want me to NOT apply this, say so in the next day or two.  Otherwise I'll do it.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBAS-4907
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4907
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: David Lloyd
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:10:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 24 Oct 2007 15:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Moved: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26092302.1193253001615.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

Scott M Stark moved JBAS-4907 to JBCOMMON-39:
---------------------------------------------

              Project: JBoss Common  (was: JBoss Application Server)
                  Key: JBCOMMON-39  (was: JBAS-4907)
          Component/s: common-logging-jdk
                           (was: Logging)
        Fix Version/s: 2.2.3.GA
                           (was:  JBossAS-5.0.0.Beta3)
    Affects Version/s: 2.2.2.GA
                           (was: JBossAS-5.0.0.Beta2)

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: Scott M Stark
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:10:02 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 24 Oct 2007 15:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCOMMON-39) JDK logging
 levels don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16934860.1193253002252.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

Scott M Stark reassigned JBCOMMON-39:
-------------------------------------

    Assignee: David Lloyd  (was: Scott M Stark)

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:18:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1121) Allow command
 line configuration of ServerPeerID
Message-ID: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow command line configuration of ServerPeerID
------------------------------------------------

                 Key: JBMESSAGING-1121
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Brian Stansberry
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration, EAP 4.3 Integration


The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.

Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:21:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4908) Update
 sample-bindings.xml to
 reflect use of -beans.xml instead of -service.xml for clustering services.
Message-ID: <1718009.1193253661440.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update sample-bindings.xml to reflect use of -beans.xml instead of -service.xml for clustering services.
--------------------------------------------------------------------------------------------------------

                 Key: JBAS-4908
                 URL: http://jira.jboss.com/jira/browse/JBAS-4908
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Critical
             Fix For: JBossAS-5.0.0.CR1


The current file assumes things like HA-JNDI are mbeans.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:23:06 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Wed, 24 Oct 2007 15:23:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14425624.1193253786971.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384204 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1121:
----------------------------------------------

If you configure it as: 

 <attribute name="ServerPeerID">${server.peer.id}</attribute>

and then define "server.peer.id" system property with -Dserver.peer.id=77 (or whatever) , it works.






> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:27:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 24 Oct 2007 15:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-818) Release
	2.2.2.GA_CP01
In-Reply-To: <12204903.1192079883249.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16599076.1193254021717.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-818?page=comments#action_12384205 ] 
            
Ron Sigal commented on JBREM-818:
---------------------------------

Branch remoting_2_2_2_GA_CP has been tagged remoting_2_2_2_CP01.

> Release 2.2.2.GA_CP01
> ---------------------
>
>                 Key: JBREM-818
>                 URL: http://jira.jboss.com/jira/browse/JBREM-818
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA_CP01
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:29:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4909) Remove
 JBMESSAGING-1120 workaround in JChannelFactory
Message-ID: <25619793.1193254141623.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove JBMESSAGING-1120 workaround in JChannelFactory
-----------------------------------------------------

                 Key: JBAS-4909
                 URL: http://jira.jboss.com/jira/browse/JBAS-4909
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions:  JBossAS-5.0.0.Beta3
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For: JBossAS-5.0.0.CR1


As a workaround to JBMESSAGING-1120, in org.jboss.ha.framework.server.JChannelFactory I disabled the ability to call set register_for_state_transfer to true when creating a multiplexer channel.  This JIRA is a reminder to remove the workaround once a fixed JBM release is integrated.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:33:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10942191.1193254381473.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384208 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

Right; this JIRA is a request to have the official property name defined and that system property substitution syntax added in the standard file that's integrated into the AS.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:58:13 2007
From: jira-events at lists.jboss.org (Michal Bali (JIRA))
Date: Wed, 24 Oct 2007 15:58:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
Message-ID: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>

DroolsCompilerAntTask.java should reset threadContextLoader to original value
-----------------------------------------------------------------------------

                 Key: JBRULES-1297
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Michal Bali


DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:02:01 2007
From: jira-events at lists.jboss.org (Michal Bali (JIRA))
Date: Wed, 24 Oct 2007 16:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
In-Reply-To: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7255356.1193256121416.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1297?page=all ]

Michal Bali updated JBRULES-1297:
---------------------------------

    Attachment: droolsAntClasspathFixPatch.txt

This patch should be applied on DroolsCompilerAntTask.java
It modifies the main execute() method to call loader.resetThreadContextLoader();
I can write some tests if needed.

> DroolsCompilerAntTask.java should reset threadContextLoader to original value
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-1297
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Bali
>         Attachments: droolsAntClasspathFixPatch.txt
>
>
> DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:10:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-113) support qname syntax
 {nsURI}localPart
Message-ID: <29512214.1193256601419.JavaMail.jira@cloud.prod.atl2.jboss.com>

support qname syntax {nsURI}localPart
-------------------------------------

                 Key: JBXB-113
                 URL: http://jira.jboss.com/jira/browse/JBXB-113
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Bug
    Affects Versions: JBossXB-1.0.0.SP1, JBossXB-2.0.0.CR4
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-2.0.0.CR5


Currently QName values in XML are supposed to follow syntax [prefix:]localPart. When the nsURI is not registered then the QName should be marshalled as {nsURI}localPart.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:12:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBXB-113) support qname syntax
 {nsURI}localPart
In-Reply-To: <29512214.1193256601419.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11688129.1193256721490.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-113?page=all ]

Alexey Loubyansky updated JBXB-113:
-----------------------------------

    Fix Version/s: JBossXB-1.0.0.SP2

> support qname syntax {nsURI}localPart
> -------------------------------------
>
>                 Key: JBXB-113
>                 URL: http://jira.jboss.com/jira/browse/JBXB-113
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4, JBossXB-1.0.0.SP1
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5, JBossXB-1.0.0.SP2
>
>
> Currently QName values in XML are supposed to follow syntax [prefix:]localPart. When the nsURI is not registered then the QName should be marshalled as {nsURI}localPart.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:12:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-113) support qname syntax
 {nsURI}localPart
In-Reply-To: <29512214.1193256601419.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18835227.1193256721617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-113?page=all ]

Alexey Loubyansky closed JBXB-113.
----------------------------------

    Resolution: Done

> support qname syntax {nsURI}localPart
> -------------------------------------
>
>                 Key: JBXB-113
>                 URL: http://jira.jboss.com/jira/browse/JBXB-113
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4, JBossXB-1.0.0.SP1
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5, JBossXB-1.0.0.SP2
>
>
> Currently QName values in XML are supposed to follow syntax [prefix:]localPart. When the nsURI is not registered then the QName should be marshalled as {nsURI}localPart.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:14:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 24 Oct 2007 16:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-817) Release 2.2.2.SP2
In-Reply-To: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23687507.1193256841613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-817?page=all ]

Ron Sigal closed JBREM-817.
---------------------------

    Resolution: Done

This release was targeted for JBossAS 5.0.0.Beta3, which is currently using it.

> Release 2.2.2.SP2
> -----------------
>
>                 Key: JBREM-817
>                 URL: http://jira.jboss.com/jira/browse/JBREM-817
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:18:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 24 Oct 2007 16:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4890) EJBAccessException:
 Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32637170.1193257083576.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4890?page=all ]

Anil Saldhana closed JBAS-4890.
-------------------------------

    Resolution: Done

Fixed. With the following rollback:
====================================
asaldhana~/jboss-5.0/jboss-head/tomcat/src/main/org/jboss/web/tomcat/security>svn ci -m "JBAS-4890: rollback change made by Scott during JBAS-4506 with RunAsIdentity push"
Sending        security\RunAsListener.java
Transmitting file data .
Committed revision 66397.
====================================


The test should pass now:
=================
asaldhana~/jbossws/stack/native/jbossws-native-2.0.2>ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase one-test
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 19.657 sec

BUILD SUCCESSFUL
Total time: 21 seconds
===================

> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:22:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26600700.1193257321714.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12384224 ] 
            
Alexey Loubyansky commented on JBAS-4891:
-----------------------------------------

I just added support for {nsURI}localPart syntax.

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 17:04:11 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 24 Oct 2007 17:04:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6097854.1193259851645.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=comments#action_12384230 ] 
            
Thomas Heute commented on JBPORTAL-1769:
----------------------------------------

I played again hard on the demo box, with IE 7.0.6000.16546 without experiening anything odd.
I added a portlet on the default page and hit the maximize/minimize/normal buttons for a while. Nothing.

> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 17:44:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 17:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1206) Improve cloning of
 configuration elements
Message-ID: <5658005.1193262241644.JavaMail.jira@cloud.prod.atl2.jboss.com>

Improve cloning of configuration elements
-----------------------------------------

                 Key: JBCACHE-1206
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1206
             Project: JBoss Cache
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA, 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For: 2.1.0.CR1


Ensure it's a deep clone operation; no shared references to subcomponents or any other mutable elements should come out of cloning a parent component.

Implement "public XYZ clone()" wherever possible, where XYZ is the type of the class (i.e. don't just rely on superclass' "public ConfigurationComponent clone()").

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 18:01:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 18:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1206) Improve cloning of
 configuration elements
In-Reply-To: <5658005.1193262241644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1181902.1193263261457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1206?page=all ]

Brian Stansberry closed JBCACHE-1206.
-------------------------------------

    Resolution: Done

> Improve cloning of configuration elements
> -----------------------------------------
>
>                 Key: JBCACHE-1206
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1206
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.CR1
>
>
> Ensure it's a deep clone operation; no shared references to subcomponents or any other mutable elements should come out of cloning a parent component.
> Implement "public XYZ clone()" wherever possible, where XYZ is the type of the class (i.e. don't just rely on superclass' "public ConfigurationComponent clone()").

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 18:15:01 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 24 Oct 2007 18:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1080) create tutorial
 for customizing ejb3-interceptors-aop.xml
Message-ID: <571489.1193264101537.JavaMail.jira@cloud.prod.atl2.jboss.com>

create tutorial for customizing ejb3-interceptors-aop.xml
---------------------------------------------------------

                 Key: EJBTHREE-1080
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1080
             Project: EJB 3.0
          Issue Type: Task
          Components: Documentation
            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

        


From jira-events at lists.jboss.org  Wed Oct 24 19:45:05 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Wed, 24 Oct 2007 19:45:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
In-Reply-To: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5844955.1193269505321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Jay Howell updated JBAS-4870:
-----------------------------

    Help Desk Ticket Reference: https://na1.salesforce.com/50030000003MjZr

I added the case number from salesforce.

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 22:28:02 2007
From: jira-events at lists.jboss.org (Cloves Almeida (JIRA))
Date: Wed, 24 Oct 2007 22:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-2) process monitoring
 and statistics capabilities (BAM)
Message-ID: <17717249.1193279282776.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12384251 ] 
            
Cloves Almeida commented on JBPM-2:
-----------------------------------

Is this still a BLOCKING issue? If not, could it please be marked Closed?

Those red issues really scary admins trying to use jBPM in production.

> process monitoring and statistics capabilities (BAM)
> ----------------------------------------------------
>
>                 Key: JBPM-2
>                 URL: http://jira.jboss.com/jira/browse/JBPM-2
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>         Environment: N/A
>            Reporter: Ronald van Kuijk
>            Priority: Blocker
>
> JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=49900689
> 1.  jBPM should store the duration and start date of a state/process in the logs
> 2.  Write some detailed info on wiki
> 3.  Show processinstance and data
> 4.  day/week/month overviews
> 5.  near realtime data per process
> 6.  produce graphs of day/week/month overviews
> Some more ideas i got from a requirements document...
> -  Number of cases processed in through a particular process definition
> -  Number of cases flowing through a particular activity
> -  Longest work item delay by activity
> -  Workitems awaiting a particular task
> -  Workitems in a specific worklist claimed and/or completed by a particular user
> -  Longest end-to-end delay
> -  Mean time to approve by activity by participant
> -  Mean end-to-end completion time.
> as background info, here's what the competition says about BAM:
> http://appian.com/AppianEnt/Analytics/analytics.html
> http://www.webmethods.com/meta/default/folder/0000005936
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduction/htm/ebiz_intro_story_piew.asp
> http://www.tibco.com/software/business_optimization/activity_monitoring.jsp?m=c1
> http://www.vitria.com/products/platform/bam.html
> http://looselycoupled.com/glossary/BAM

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 23:40:11 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 24 Oct 2007 23:40:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1298) Package wizard
 for package configuration
Message-ID: <33096746.1193283611576.JavaMail.jira@cloud.prod.atl2.jboss.com>

Package wizard for package configuration
----------------------------------------

                 Key: JBRULES-1298
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1298
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE


this is mainly for updating models and imports. Shoudl be a wizard that uploads and VALIDATES the model (and offers to import found classes). Similar when importing DRL. Could be a wizard from the package config screen, or it could be part of the model asset screen (probably former is better). 

This has been causing some confusion. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 23:44:01 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 24 Oct 2007 23:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1299) better handling
 of error when dependent class not in jar file
Message-ID: <4996155.1193283841519.JavaMail.jira@cloud.prod.atl2.jboss.com>

better handling of error when dependent class not in jar file
-------------------------------------------------------------

                 Key: JBRULES-1299
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1299
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 00:35:11 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 00:35:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17106469.1193286911723.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Scott M Stark resolved JBAS-4891.
---------------------------------

    Resolution: Done

jbossas trunk is using the jbossxb snapshot that supports this

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 00:37:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 00:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23603767.1193287021659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Scott M Stark resolved JBAS-4895.
---------------------------------

    Resolution: Done

The current jboss-metadata 1.0.0.snapshot (rev 1563) contains the complete standard and jboss service-ref mappings.


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:14:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 01:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
In-Reply-To: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21428636.1193289241565.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Scott M Stark resolved JBAS-4899.
---------------------------------

    Resolution: Done

The latest jbossxb snapshot (rev 1654) will pass in the root element local name as the schemaLocation if no other schemaLocation could be found. This allows one to map the root element name to a binding class as jbossas does in its metadata-beans.xml:

   <bean name="SchemaResolverConfig"
      class="org.jboss.xb.binding.sunday.unmarshalling.SchemaResolverConfig">
      <!-- schemaLocation to JBossXBuilder binding classes -->
      <property name="bindingClassesByLocations">
         <map keyClass="java.lang.String" valueClass="java.lang.String">
            <entry>
               <key>jboss</key>
               <value>org.jboss.metadata.ejb.jboss.JBoss50DTDMetaData</value>
            </entry>            
...


> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:16:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 01:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11765802.1193289361636.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4896?page=all ]

Scott M Stark resolved JBAS-4896.
---------------------------------

    Resolution: Done

The document parses correctly with the current jbossxb/jboss-metadata snapshots. See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testNoDoctype test.


> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:23:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 01:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21598628.1193289781478.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Scott M Stark updated JBAS-4900:
--------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098649

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:54:01 2007
From: jira-events at lists.jboss.org (Magesh Kumar B (JIRA))
Date: Thu, 25 Oct 2007 01:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1481) Reimplement
 portal security interface without JACC
In-Reply-To: <14757028.1181561891881.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2295689.1193291641537.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1481?page=all ]

Magesh Kumar B reassigned JBPORTAL-1481:
----------------------------------------

    Assignee: Sohil Shah

> Reimplement portal security interface without JACC
> --------------------------------------------------
>
>                 Key: JBPORTAL-1481
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1481
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6 CR3
>            Reporter: Julien Viet
>         Assigned To: Sohil Shah
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 02:13:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 02:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1156) Configuration
	profiles
In-Reply-To: <12193835.1185540767196.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14173054.1193292781666.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1156?page=comments#action_12384259 ] 
            
Brian Stansberry commented on JBCACHE-1156:
-------------------------------------------

A pretty reasonable version of what I'm thinking about is now in package org.jboss.cache.registry. I'm trying to keep this simple, since in many ways it's not a true JBC concern. I'd just do it in the AS, but it's needed for standalone Hibernate, which can't depend on the AS. I'll likely want to use the same interfaces for session mgmt stuff in the AS, so I don't want this stuff in Hibernate, since session mgmt has nothing to do with Hibernate. So, putting it in JBC makes the most sense.

Given the above, I thought the best approach to take was to define a couple basic interfaces that provide the API needed by Hibernate.  Then do a basic impl that meets the needs of standalone Hibernate. If I decide I want to do more complex stuff inside the AS, I can can expand upon this in the AS codebase.

This is pretty much ready to be resolved, other than I might think of a couple more unit tests.

> Configuration profiles
> ----------------------
>
>                 Key: JBCACHE-1156
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1156
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Requested by both AS clustering and Hibernate.
> The ability to use a specialised ConfigurationFactory that gives you a pre-configured cache for specific purposes.  E.g., CacheFactory.getAsyncReplicatedCache("myJGroupsMuxStackName")
> To be done as a subclass of DefaultCacheFactory (ProfileCacheFactory?)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 02:13:01 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 25 Oct 2007 02:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1299) better handling of
 error when dependent class not in jar file
In-Reply-To: <4996155.1193283841519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23402410.1193292781794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1299?page=all ]

Michael Neale closed JBRULES-1299.
----------------------------------

    Resolution: Done

> better handling of error when dependent class not in jar file
> -------------------------------------------------------------
>
>                 Key: JBRULES-1299
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1299
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder, drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 02:21:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 02:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
In-Reply-To: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5043343.1193293261446.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1194?page=all ]

Brian Stansberry closed JBCACHE-1194.
-------------------------------------

    Resolution: Done

> DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
> ---------------------------------------------------------------
>
>                 Key: JBCACHE-1194
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.4.1.SP5
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Critical
>             Fix For: 1.4.1.SP6
>
>
> It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4766.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:00:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 03:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-596) Document JOIN&state
 transfer, for JChannel and in the Multiplexer
In-Reply-To: <25358775.1190275215454.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8752391.1193295601497.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-596?page=all ]

Bela Ban resolved JGRP-596.
---------------------------

    Resolution: Done

> Document JOIN&state transfer, for JChannel and in the Multiplexer
> -----------------------------------------------------------------
>
>                 Key: JGRP-596
>                 URL: http://jira.jboss.com/jira/browse/JGRP-596
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 2.6
>
>
> JOIN&STATE transfer needs to get documented in doc/manual/en/modules/api.xml. We also need to add documentation for the same for the multiplexer

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:25:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 03:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JGRP-609) Javadoc
	JChannelFactory
In-Reply-To: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18675501.1193297101636.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-609?page=all ]

Bela Ban reassigned JGRP-609:
-----------------------------

    Assignee: Vladimir Blagojevic  (was: Bela Ban)

> Javadoc JChannelFactory
> -----------------------
>
>                 Key: JGRP-609
>                 URL: http://jira.jboss.com/jira/browse/JGRP-609
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5.1
>            Reporter: Brian Stansberry
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6, 2.5.2
>
>
> org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:25:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 03:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-609) Javadoc
	JChannelFactory
In-Reply-To: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29039435.1193297101797.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-609?page=all ]

Bela Ban updated JGRP-609:
--------------------------

    Fix Version/s: 2.5.2
                   2.6

> Javadoc JChannelFactory
> -----------------------
>
>                 Key: JGRP-609
>                 URL: http://jira.jboss.com/jira/browse/JGRP-609
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5.1
>            Reporter: Brian Stansberry
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6, 2.5.2
>
>
> org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:55:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 03:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging
 levels don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9614064.1193298901419.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384266 ] 
            
Dimitris Andreadis commented on JBCOMMON-39:
--------------------------------------------

Can you explain again what the problem is? Is there a forum thread discussing it?

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:59:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Thu, 25 Oct 2007 03:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32213940.1193299141494.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4823?page=all ]

cheng dan reassigned JBAS-4823:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:01:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Thu, 25 Oct 2007 04:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7241297.1193299261560.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4823?page=all ]

cheng dan reassigned JBAS-4823:
-------------------------------

    Assignee:     (was: cheng dan)

> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:01:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Thu, 25 Oct 2007 04:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4825) TECH REVIEW:
 Getting Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21013941.1193299261733.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

cheng dan reassigned JBAS-4825:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:21:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 04:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-607) SEQUENCER: incorrect
 ordering on concurrent sends
In-Reply-To: <30774057.1193152921433.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26584855.1193300461515.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-607?page=all ]

Bela Ban resolved JGRP-607.
---------------------------

    Resolution: Done

Fixed according to solution in CVS head, and 2.5 and 2.4 branches

> SEQUENCER: incorrect ordering on concurrent sends
> -------------------------------------------------
>
>                 Key: JGRP-607
>                 URL: http://jira.jboss.com/jira/browse/JGRP-607
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.4.1 SP5, 2.5.2, 2.6
>
>
> The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:26:19 2007
From: jira-events at lists.jboss.org (Magesh Kumar B (JIRA))
Date: Thu, 25 Oct 2007 04:26:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1481) Reimplement
 portal security interface without JACC
In-Reply-To: <14757028.1181561891881.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1372982.1193300779167.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1481?page=all ]

Magesh Kumar B resolved JBPORTAL-1481.
--------------------------------------

    Fix Version/s: 2.6.3 Final
       Resolution: Done

Merged from Security Branch JBoss_Portal_2_6_2_SecurityPatch to current working JBoss_Portal_Branch_2_6

> Reimplement portal security interface without JACC
> --------------------------------------------------
>
>                 Key: JBPORTAL-1481
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1481
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6 CR3
>            Reporter: Julien Viet
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:15:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 05:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4910) NPE in
	AbstractMappedMetaData
Message-ID: <32126662.1193303701492.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in AbstractMappedMetaData
-----------------------------

                 Key: JBAS-4910
                 URL: http://jira.jboss.com/jira/browse/JBAS-4910
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:19:06 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 05:19:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4910) NPE in
	AbstractMappedMetaData
In-Reply-To: <32126662.1193303701492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16322013.1193303947019.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4910?page=all ]

Thomas Diesler updated JBAS-4910:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefClientTestCase one-test

Caused by: java.lang.NullPointerException
        at org.jboss.metadata.javaee.support.AbstractMappedMetaData.addAll(AbstractMappedMetaData.java:188)
        at org.jboss.metadata.javaee.spec.MessageDestinationsMetaData.merge(MessageDestinationsMetaData.java:66)
        at org.jboss.metadata.client.jboss.JBossClientMetaData.merge(JBossClientMetaData.java:316)
        at org.jboss.ejb3.deployers.JBossClientParsingDeployer.createMetaData(JBossClientParsingDeployer.java:63)
        at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)

To reproduce this, you need to enable the test in src/resources/test-excludes-jboss500.txt
         Assignee: Scott M Stark

> NPE in AbstractMappedMetaData
> -----------------------------
>
>                 Key: JBAS-4910
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4910
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefClientTestCase one-test
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.javaee.support.AbstractMappedMetaData.addAll(AbstractMappedMetaData.java:188)
>         at org.jboss.metadata.javaee.spec.MessageDestinationsMetaData.merge(MessageDestinationsMetaData.java:66)
>         at org.jboss.metadata.client.jboss.JBossClientMetaData.merge(JBossClientMetaData.java:316)
>         at org.jboss.ejb3.deployers.JBossClientParsingDeployer.createMetaData(JBossClientParsingDeployer.java:63)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> To reproduce this, you need to enable the test in src/resources/test-excludes-jboss500.txt

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:25:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 25 Oct 2007 05:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1720) Profile /
 enhance error message : DatePropertyAccessor
In-Reply-To: <16243687.1190700172066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9524850.1193304301883.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1720?page=all ]

Thomas Heute updated JBPORTAL-1720:
-----------------------------------

    Assignee: Thomas Heute

> Profile / enhance error message : DatePropertyAccessor 
> -------------------------------------------------------
>
>                 Key: JBPORTAL-1720
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1720
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> Line 552
> catch (ParseException e)
>          {
>             throw new IllegalArgumentException();
>          }
> Some more information on the error will be helpfull, espcially for integration of legacy user datasource.
> Like it is done for the boolean property accessor
> something like :
> catch (ParseException e)
>          {
>             throw new IllegalArgumentException("Can't convert the date in the user profile. value=[" + value + "].", e);
>          }

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:43:12 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Thu, 25 Oct 2007 05:43:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17139263.1193305392784.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris reopened JBAS-4826:
--------------------------------------

             
Reviewed wrong doc. I will review now the later of the 2 docs originally attached

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:47:01 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 05:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4911)
 MSSQLValidConnectionChecker
 throws exception with MS SQL Server 2005 JDBC driver
Message-ID: <20099656.1193305621823.JavaMail.jira@cloud.prod.atl2.jboss.com>

MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
--------------------------------------------------------------------------------

                 Key: JBAS-4911
                 URL: http://jira.jboss.com/jira/browse/JBAS-4911
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JCA service
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Luc Texier
         Assigned To: Weston Price


After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource

<datasources>
  <local-tx-datasource>
    <jndi-name>DefaultDS</jndi-name>
    <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
    <user-name>sa</user-name>
    <password>jboss</password>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>

    <metadata>
       <type-mapping>MS SQLSERVER2000</type-mapping>
    </metadata>
  </local-tx-datasource>
</datasources>


during start-up, the following exception is throwed 


2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:56:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 05:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
In-Reply-To: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30525369.1193306161635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Adrian Brock updated JBAS-4870:
-------------------------------

    Attachment: testredelivery.zip

It's quite hard to write an ant unit test for this problem, because it can
only be reproduced with a server crash (rather than a clean shutdown of the server).

Attached is a simple ant project to test whether the redelivery flags are set correctly,
but it requires manual steps (step 4 below) to run the test.

1) Start JBoss
> ./run.sh
2) Send a message
> ant send
3) Receive the message in Client Acknowledge mode, but don't acknowledge (or close the session, etc. which is the same thing).
> ant receive
4) Crash the server (don't use control-c)
> kill -9 <jboss-pid>
5) Restart the server
> ./run.sh
7) Re-receive the message
> ant receive

You should see the redelivery count updated (before this fix you don't)

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>         Attachments: testredelivery.zip
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:00:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Thu, 25 Oct 2007 06:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29680425.1193306403613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris resolved JBAS-4826.
--------------------------------------

    Resolution: Done

I have completed the review and have nothing against this chapter. Please. ignore my previous attachment.

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:02:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
In-Reply-To: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17796079.1193306521609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Adrian Brock closed JBAS-4870.
------------------------------

    Resolution: Done

This has been fixed.

Since this is a corner case and the fix means we have to update all persistent messages
in the database before delivering the message (i.e. whether the message gets redelivered or not)
I've added an option to the destination manager so it can be reverted to the old behaviour.

<!-- Only update redelivery status of a persistent message in the database when a NACK is received -->
<attribute name="LazyRedeliveryUpdate">true</attribute>

The default is false.

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>         Attachments: testredelivery.zip
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:15:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-211) Support ..
 notion in vfs paths
Message-ID: <9963001.1193307301447.JavaMail.jira@cloud.prod.atl2.jboss.com>

Support .. notion in vfs paths
------------------------------

                 Key: JBMICROCONT-211
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-211
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: VFS
    Affects Versions: JBossMC-2.0.0.Beta4
            Reporter: Adrian Brock


If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
currently the PathTokenizer will report an error if the path contains a . or ..

It should still through an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:17:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10165918.1193307421654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Adrian Brock updated JBAS-4901:
-------------------------------

    Assignee:     (was: Adrian Brock)

I don't see how this can be backwards compatibility issue since the VFS has never supported
the .. notation.

We've discussed supporting it in the past, but nothing was ever done.
I've raised a feature request for it.

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:17:01 2007
From: jira-events at lists.jboss.org (Ovidiu Nichifor (JIRA))
Date: Thu, 25 Oct 2007 06:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1773) Unable to
 destroy instance customization
Message-ID: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>

Unable to destroy instance customization
----------------------------------------

                 Key: JBPORTAL-1773
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core
    Affects Versions: 2.6.1 Final
         Environment: Fedora Core 7
JVM 1.5.0_12
JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
JBoss Potal 2.6.1.GA

            Reporter: Ovidiu Nichifor
         Assigned To: Julien Viet


Create & place a window on a region of an ordinary page of your personal dashboard.
Make sure it is visible on your dashboard.
Destroy that window.
Recreate the window with the same name, content type, instance, page parent, region and order as before.

An error will appear in the console:
12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null

It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.

Sample:

`JBP_PORTLET_STATE`
PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL

`JBP_INSTANCE_PER_USER`
PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4

Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.

Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:19:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8262554.1193307541751.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir updated JBAS-4827:
---------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-3-1.odt

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3-1.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5752323.1193307662095.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir updated JBAS-4827:
---------------------------------

    Attachment:     (was: JBASS-422-Getting_Started_Guide-Chapter-3-1.odt)

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1402) Transaction Recovery
Message-ID: <21458831.1193307662555.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ]

Adrian Brock closed JBAS-1402.
------------------------------

    Resolution: Out of Date
      Assignee:     (was: Adrian Brock)

This issue can be closed.

The JCA issues still need resolving with some api for the a generic TM to get XAResources
during recovery. 

There is a thread about this in the JCA forum, but I'm not sure if any
JIRA issues were created beyond what is mentioned here.

I'll close the ones here and re-raise the issue in the JCA forum.

> Transaction Recovery
> --------------------
>
>                 Key: JBAS-1402
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1402
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.0.1 Final
>            Reporter: Adrian Brock
>
> Implement optional transaction recovery
> The simplest mechanism is to do this is with a local database
> using the last resource gambit where during its "prepare" it logs the XID in a table.
> If this last resource fails to commit, recovery will not find the transaction
> in the table which means it will rollback the whole transaction.
> This has limitations where a different local resource is required within the transaction
> but not this local database used as the recovery log.
> Another implementation is a local file. Though more complicated it should give superior
> performance. 
> But, it does not work well with the last resource gambit, e.g. you cannot tell
> whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation
> before the result is returned from the db.
> The other work required:
> 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier.
> Currently the RARs need the transaction manager at deployment time. The
> recovery service needs to be an external service depending upon both the
> tm and the managed connection factories.
> At least this will require a GUID for the XID so we can avoid duplicates between
> unrecovered XIDs and any new XIDs created before recovery is complete.
> 2) JBossMQ needs to implement XAResource.recover()

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1405) Padding should be a
	JCA option
Message-ID: <12240979.1193307662725.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1405?page=all ]

Adrian Brock closed JBAS-1405.
------------------------------

    Resolution: Out of Date

> Padding should be a JCA option
> ------------------------------
>
>                 Key: JBAS-1405
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1405
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> There should be a JCA switch that wraps any method of XAResource that takes an Xid and pads the Xid if needed by the JCA resource.  Some XAResources like Oracle need padding, others may have problems with padding.  It is stupid to have this switch on the XidFactory only.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21978028.1193307662956.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir updated JBAS-4827:
---------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-3.odt

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1406) XidFactory should
	never pad Xids
Message-ID: <8899110.1193307781887.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1406?page=all ]

Adrian Brock closed JBAS-1406.
------------------------------

    Resolution: Out of Date

> XidFactory should never pad Xids
> --------------------------------
>
>                 Key: JBAS-1406
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1406
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1407) recover flags should
 be a JCA option
Message-ID: <13947702.1193307782036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1407?page=all ]

Adrian Brock closed JBAS-1407.
------------------------------

    Resolution: Out of Date

> recover flags should be a JCA option
> ------------------------------------
>
>                 Key: JBAS-1407
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1407
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> The XAResource managed by JCA should be wrapped and calls to XAResource.recover should ignore passed in flags and use a configurable set of flags to pass into the XAResource.  This is important because some XAResources are finicky about what flags are passed to them in recover().

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4827) TECH REVIEW:
 Getting Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22653667.1193307782467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir resolved JBAS-4827.
----------------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1408) JCA layer should
 register Recoverables
Message-ID: <26974760.1193307782595.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1408?page=all ]

Adrian Brock closed JBAS-1408.
------------------------------

    Resolution: Out of Date

> JCA layer should register Recoverables
> --------------------------------------
>
>                 Key: JBAS-1408
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1408
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> JCA layer should provide a generic mechanism to register Recoverables with the RecoveryManager.  See http://www.jboss.org/wiki/Wiki.jsp?page=TransactionRecovery
> for more details.
> The way this will work is that the wrapper class for ManagedConnectionFactory will look at the metadata for creating the recoverable Subject and the metadata for the XAResource.recover() flags so that it can create a JCARecoverable class isntance to register with the recovery manager.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1409) JCA should have
	recovery config
Message-ID: <13697520.1193307782727.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1409?page=all ]

Adrian Brock closed JBAS-1409.
------------------------------

    Resolution: Out of Date

> JCA should have recovery config
> -------------------------------
>
>                 Key: JBAS-1409
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1409
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> See here:
> http://www.jboss.org/wiki/Wiki.jsp?page=TransactionRecovery
> JCA adapter should register a Recoverable with the RecoveryManager.  There should be additional switches on witch Subject or SecurityDomain should be used for recovery.  Regular XA connections may not have permission to do recovery and the app developer may not want to allow app connections to do recovery.
> Additionally, different XAResources may need different recovery switches that are passed to XAResource.recover()  For instance Informix needs only TMSTARTRSCAN while Oracle may need both TMENDRSCAN.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1410) check resources
	available
Message-ID: <2822383.1193307782857.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1410?page=all ]

Adrian Brock closed JBAS-1410.
------------------------------

    Resolution: Out of Date

> check resources available
> -------------------------
>
>                 Key: JBAS-1410
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1410
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>
> Write in the TX Log header all REcoverable IDs that are needed to recover that particular file.  If not all resources are available log error message and don't remove file.  Save it for later.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1418) test not all
	resources available
Message-ID: <6449221.1193307782986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1418?page=all ]

Adrian Brock closed JBAS-1418.
------------------------------

    Resolution: Out of Date

> test not all resources available
> --------------------------------
>
>                 Key: JBAS-1418
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1418
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1419) test when resource
	hot-deployed
Message-ID: <31433096.1193307783131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1419?page=all ]

Adrian Brock closed JBAS-1419.
------------------------------

    Resolution: Out of Date

> test when resource hot-deployed
> -------------------------------
>
>                 Key: JBAS-1419
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1419
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1420) last resource gambit
 recovery logger
Message-ID: <22633934.1193307783264.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1420?page=all ]

Adrian Brock closed JBAS-1420.
------------------------------

    Resolution: Out of Date

> last resource gambit recovery logger
> ------------------------------------
>
>                 Key: JBAS-1420
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1420
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:25:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14520616.1193307903722.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Thomas Diesler reassigned JBAS-4901:
------------------------------------

    Assignee: Thomas Diesler

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:25:03 2007
From: jira-events at lists.jboss.org (Ovidiu Nichifor (JIRA))
Date: Thu, 25 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19623618.1193307903979.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=comments#action_12384291 ] 
            
Ovidiu Nichifor commented on JBPORTAL-1773:
-------------------------------------------

Since instance customizations are not persisted until some preferences are stored i found it very useful to create a portlet that stores/displays preferences. The attached war file contains sources and this portlet.

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:28:01 2007
From: jira-events at lists.jboss.org (Ovidiu Nichifor (JIRA))
Date: Thu, 25 Oct 2007 06:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28694259.1193308081601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=all ]

Ovidiu Nichifor updated JBPORTAL-1773:
--------------------------------------

    Attachment: sample-portlet.war

A sample portlet that stores/displays its attached preferences.

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>         Attachments: sample-portlet.war
>
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1120) Data channel
 from
 MultiplexerChannelFactory prevents state transfers from other users of the
 shared channel
In-Reply-To: <2574382.1193240941938.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25232466.1193309641673.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1120?page=all ]

Tim Fox updated JBMESSAGING-1120:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1120
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Distributed Support
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang.
> Problem is JBM's MultiplexerChannelFactory creates the data channel as follows:
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE);
> }
> The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service.  JBM never calls getState(), so it *must not* pass Boolean.TRUE.  Valid usages are:
> public Channel createDataChannel() throws Exception
> {
>       String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"};
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature);
> }
> or 
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE);
> }
> The former invokes a convenience method that delegates to the latter.
> Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState().  If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.)
> When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState().
> I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1118) Sucker
 connection created back to itself doesn't need to be created
In-Reply-To: <1544433.1193076306087.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31969692.1193309642535.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1118?page=all ]

Tim Fox updated JBMESSAGING-1118:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> Sucker connection created back to itself doesn't need to be created
> -------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1118
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment.  So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker.
> while (iter.hasNext())
> 		{
> 			Map.Entry entry = (Map.Entry)iter.next();
> 			
> 			Integer nid = (Integer)entry.getKey();
> 			
> 			ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue();
> 			
> 			if (connections.get(nid) == null)
> 			{
> 				try
> 				{
>    				ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword);
>    				
>    				log.trace(this + " created connection info " + info);
>    				
>    				connections.put(nid, info);
>    				
>    				info.start();
>    						         							         			
> 				}
> 				catch (Exception e)
> 				{
> 					log.error("Failed to start connection info ", e);
> 				}
> 			}

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20244057.1193309642792.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=all ]

Tim Fox updated JBMESSAGING-1115:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1117) Request for
 feature to
 close connections on server side by ip address and by connection id
In-Reply-To: <5418814.1193073363722.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2164762.1193309643543.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1117?page=all ]

Tim Fox updated JBMESSAGING-1117:
---------------------------------

    Fix Version/s: Unscheduled

> Request for feature to close connections on server side by ip address and by connection id
> ------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1117
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1117
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> Several customers have asked for a management method to drop client connections from the server by ip address and by client id.
> So there would be two cases.
> By ipaddress - this would stop the pinger and also close all connections associated with that client ip address.  Only one pinger exists for an ip address, so this would require closging of the pinger connection also.
> By clientid - this would close the pinger thread only if there are no other connections present.
> In each of the cases, clients should get an asynchronous onException call.  
> The person writing the client will have to have this in mind.  If a client has 1000 connections and the connection logic on the client reconnects.  When the server drops the ip address, then that machine will try to reconnect all 1000 clients.  I really depends on how the connection pooling on the client works.  

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:26:06 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Thu, 25 Oct 2007 08:26:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4898) class-loading not
 found as a child of jboss-web
In-Reply-To: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15459809.1193315166235.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4898?page=comments#action_12384308 ] 
            
Alexey Loubyansky commented on JBAS-4898:
-----------------------------------------

Fixed in metadata trunk. The test is

package org.jboss.test.metadata.web;
public class JBossWebApp24UnitTestCase extends AbstractJavaEEEverythingTest


> class-loading not found as a child of jboss-web
> -----------------------------------------------
>
>                 Key: JBAS-4898
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
>   <class-loading>
>     <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
>   </class-loading>
> </jboss-web>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:40:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:40:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1120) Data channel
 from
 MultiplexerChannelFactory prevents state transfers from other users of the
 shared channel
In-Reply-To: <2574382.1193240941938.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <888727.1193316012366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1120?page=all ]

Tim Fox closed JBMESSAGING-1120.
--------------------------------

    Resolution: Done

> Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1120
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Distributed Support
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang.
> Problem is JBM's MultiplexerChannelFactory creates the data channel as follows:
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE);
> }
> The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service.  JBM never calls getState(), so it *must not* pass Boolean.TRUE.  Valid usages are:
> public Channel createDataChannel() throws Exception
> {
>       String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"};
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature);
> }
> or 
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE);
> }
> The former invokes a convenience method that delegates to the latter.
> Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState().  If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.)
> When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState().
> I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:40:12 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 08:40:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4911)
 MSSQLValidConnectionChecker
 throws exception with MS SQL Server 2005 JDBC driver
In-Reply-To: <20099656.1193305621823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1175032.1193316012709.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4911?page=all ]

Luc Texier updated JBAS-4911:
-----------------------------

    Description: 
After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource

<datasources>
  <local-tx-datasource>
    <jndi-name>DefaultDS</jndi-name>
    <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
    <user-name>sa</user-name>
    <password>jboss</password>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>

    <metadata>
       <type-mapping>MS SQLSERVER2000</type-mapping>
    </metadata>
  </local-tx-datasource>
</datasources>


during start-up, the following exception is throwed 


2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)


IMPORTANT NOTE: I've been testing against MSSQL Server 2000. This issue might very well not exist at all with MS SQL Server 2005...



  was:
After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource

<datasources>
  <local-tx-datasource>
    <jndi-name>DefaultDS</jndi-name>
    <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
    <user-name>sa</user-name>
    <password>jboss</password>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>

    <metadata>
       <type-mapping>MS SQLSERVER2000</type-mapping>
    </metadata>
  </local-tx-datasource>
</datasources>


during start-up, the following exception is throwed 


2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)


> MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4911
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4911
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Luc Texier
>         Assigned To: Weston Price
>
> After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource
> <datasources>
>   <local-tx-datasource>
>     <jndi-name>DefaultDS</jndi-name>
>     <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
>     <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
>     <user-name>sa</user-name>
>     <password>jboss</password>
>    <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>
>     <metadata>
>        <type-mapping>MS SQLSERVER2000</type-mapping>
>     </metadata>
>   </local-tx-datasource>
> </datasources>
> during start-up, the following exception is throwed 
> 2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
> com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
> 	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
> 	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
> 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
> 	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
> 	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
> 	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
> IMPORTANT NOTE: I've been testing against MSSQL Server 2000. This issue might very well not exist at all with MS SQL Server 2005...

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:42:01 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 08:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4911)
 MSSQLValidConnectionChecker
 throws exception with MS SQL Server 2005 JDBC driver
In-Reply-To: <20099656.1193305621823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32597148.1193316121573.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4911?page=comments#action_12384313 ] 
            
Luc Texier commented on JBAS-4911:
----------------------------------

FYI, the workaround for now is to use the parameter check-valid-connection-sql instead as follows:

<check-valid-connection-sql>SELECT 1 FROM sysobjects</check-valid-connection-sql>


> MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4911
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4911
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Luc Texier
>         Assigned To: Weston Price
>
> After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource
> <datasources>
>   <local-tx-datasource>
>     <jndi-name>DefaultDS</jndi-name>
>     <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
>     <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
>     <user-name>sa</user-name>
>     <password>jboss</password>
>    <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>
>     <metadata>
>        <type-mapping>MS SQLSERVER2000</type-mapping>
>     </metadata>
>   </local-tx-datasource>
> </datasources>
> during start-up, the following exception is throwed 
> 2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
> com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
> 	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
> 	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
> 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
> 	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
> 	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
> 	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
> IMPORTANT NOTE: I've been testing against MSSQL Server 2000. This issue might very well not exist at all with MS SQL Server 2005...

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:42:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:42:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1118) Sucker
 connection created back to itself doesn't need to be created
In-Reply-To: <1544433.1193076306087.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14320530.1193316122230.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1118?page=all ]

Tim Fox closed JBMESSAGING-1118.
--------------------------------

    Resolution: Rejected

After investigating this doesn't appear to be a bug.

When starting a postoffice in clustered mode it will obtain connections to all nodes in the cluster including itself for message suckers.

If you start the post office in non clustered mode you will find no such connections get created.

> Sucker connection created back to itself doesn't need to be created
> -------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1118
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment.  So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker.
> while (iter.hasNext())
> 		{
> 			Map.Entry entry = (Map.Entry)iter.next();
> 			
> 			Integer nid = (Integer)entry.getKey();
> 			
> 			ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue();
> 			
> 			if (connections.get(nid) == null)
> 			{
> 				try
> 				{
>    				ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword);
>    				
>    				log.trace(this + " created connection info " + info);
>    				
>    				connections.put(nid, info);
>    				
>    				info.start();
>    						         							         			
> 				}
> 				catch (Exception e)
> 				{
> 					log.error("Failed to start connection info ", e);
> 				}
> 			}

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:49:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16067251.1193316542316.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox closed JBMESSAGING-1119.
--------------------------------

    Resolution: Done
      Assignee: Tim Fox  (was: Clebert Suconic)

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:53:02 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 25 Oct 2007 08:53:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-27) Container
 Task:JBoss 4.2.x related Tasks for Security 2.0
In-Reply-To: <17497988.1172167236604.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27651666.1193316782129.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-27?page=all ]

Anil Saldhana updated SECURITY-27:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Container Task:JBoss 4.2.x related Tasks for Security 2.0
> ---------------------------------------------------------
>
>                 Key: SECURITY-27
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-27
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Container task for all 4.2.x related tasks that need to be performed for the 5.x releases of JBAS.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:57:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <27188498.1193317021862.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12384316 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

We need to support automatic failover for the case where no shared file systems is present.

In which case we need to replicate state to a buddy.

This should be configurable on a per queue level.

We can supply different levels of reliability:

1) Once and only once - with this mode we would need two streams one for replication messages and one for replication acks
We would also need to store last sequence received in the storage to avoid having to use XA

2) At most once - replication sent async. Chance of message loss.

3) No replication

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:59:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:59:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <15451995.1193317145729.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12384317 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

Very large messages should be stored outside the store on the file system and referenced via pointers.

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:01:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 09:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <19332013.1193317261978.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12384319 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

Should also support active passive failover

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:14:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 09:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1116) Consuming
 client grinds to
 a halt if a node different from the "active" one fails
In-Reply-To: <10435351.1193029683486.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6214220.1193318041840.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1116?page=all ]

Tim Fox closed JBMESSAGING-1116.
--------------------------------

    Resolution: Done

> Consuming client grinds to a halt if a node different from the "active" one fails
> ---------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1116
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> This is how to replicate it:
> - Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A
> - Start consuming concurrently using 50 parallel consumers over a connection to node A
> - Kill node B
> The consumption rate drop to 0 and never recovers.
> Trying to close the connection on the client-side never completes.
> Trying to shut down node A fails, need to eventually kill it.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:16:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 25 Oct 2007 09:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging
 levels don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2376485.1193318161482.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384324 ] 
            
David Lloyd commented on JBCOMMON-39:
-------------------------------------

The problem is that if you use the JDK14LoggerPlugin, and you log a message at, say, TRACE, it shows up as FINER in the log.  And the DOMConfigurator for the JDK plugin has to map the "old" log4j names to the (roughly) equivalent JUL name.  I propose that we just create a subclass of java.util.logging.Level, and an instance for each of the log levels that WE use, e.g. TRACE, DEBUG, etc.  Then not only will the old, familiar levels be printed in the log, but then JUL will parse the log level names for us, so we don't need to map them.

No forum thread because honestly I don't know what forum is relevant for this project.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:22:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 25 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18042231.1193318521583.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

David Lloyd updated JBCOMMON-39:
--------------------------------

    Attachment: JBCOMMON-39.patch

Updated patch.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBCOMMON-39.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:22:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 25 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26495472.1193318521743.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

David Lloyd updated JBCOMMON-39:
--------------------------------

    Attachment:     (was: JBAS-4907.patch)

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBCOMMON-39.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:46:16 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 09:46:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6581118.1193319976815.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Luc Texier updated JBAS-4830:
-----------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt

Here is revision 3.1

basically I've rewritten 80% of it. Now this chapter includes a section for MS SQL Server and the Oracle one has been simplified and updated. They are all refering to the latest jdbc drivers available from these vendors.

FYI while testing with MS SQL I found the following bug: JBAS-4911

Thanks to Colin for fixing the english typos

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:52:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 09:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
Message-ID: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>

Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
----------------------------------------------------------------------------------------------------------------------

                 Key: JBMICROCONT-212
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
             Project: JBoss MicroContainer
          Issue Type: Bug
    Affects Versions: JBossMC-2.0.0.Beta4
            Reporter: Adrian Brock
         Assigned To: Adrian Brock
             Fix For: JBossMC-2.0.0.Beta5


The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
when the deployment failed during deploy().

The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:52:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 09:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33069480.1193320321821.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=all ]

Adrian Brock updated JBMICROCONT-212:
-------------------------------------

    Component/s: Deployment

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:52:02 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 09:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33264365.1193320322024.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4830?page=comments#action_12384332 ] 
            
Luc Texier commented on JBAS-4830:
----------------------------------

BTW the table of content has to be double-checked and setup properly

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:54:07 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 09:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7644514.1193320447309.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Luc Texier resolved JBAS-4830.
------------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:59:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 09:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-212) Deployment
 Contexts are
 not removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12451712.1193320741923.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=comments#action_12384335 ] 
            
Adrian Brock commented on JBMICROCONT-212:
------------------------------------------

This has been fixed, but I'm not closing this until I know what release it is going in.

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 10:01:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 10:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28577466.1193320861623.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Adrian Brock updated JBAS-4900:
-------------------------------

    Component/s: Deployment services

This has been fixed in the trunk of the deployers-impl project.
It's need a microcontainer release to fix the problem in the appserver.

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:15:06 2007
From: jira-events at lists.jboss.org (Aslak (JIRA))
Date: Thu, 25 Oct 2007 11:15:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1122)
 *MessageCountersAsHTML LastAdd uses wrong value
Message-ID: <15674199.1193325306988.JavaMail.jira@cloud.prod.atl2.jboss.com>

*MessageCountersAsHTML LastAdd uses wrong value
-----------------------------------------------

                 Key: JBMESSAGING-1122
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
            Reporter: Aslak
         Assigned To: Tim Fox


ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:21:01 2007
From: jira-events at lists.jboss.org (Aslak (JIRA))
Date: Thu, 25 Oct 2007 11:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1122)
 *MessageCountersAsHTML LastAdd uses wrong value
In-Reply-To: <15674199.1193325306988.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23309610.1193325661741.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1122?page=all ]

Aslak updated JBMESSAGING-1122:
-------------------------------

    Attachment: JBMESSAGING-1122.patch

A patch that adds a MessageCounter.getLastAdd. It is not 100% since it only updates itself each time 
the onTime method is called, but close enough..

Also did a little clean up, using the MessageCounter 'directly' insted of hassling with the StringTokenizer/getCounterAsString/Integer.parseInt stuff..

> *MessageCountersAsHTML LastAdd uses wrong value
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1122
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>            Reporter: Aslak
>         Assigned To: Tim Fox
>         Attachments: JBMESSAGING-1122.patch
>
>
> ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:34:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Thu, 25 Oct 2007 11:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3556165.1193326441421.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-570?page=comments#action_12384367 ] 
            
Vladimir Blagojevic commented on JGRP-570:
------------------------------------------

Bela, what do you think? It would be very nice to have ThreadFactory and create threads from factory. Did you talk about exposing this API so users can hook their own factory? Maybe 2.6 afterall? 

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:54:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 11:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2561807.1193327641564.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler reopened JBAS-4895:
----------------------------------

             
PortComponentRef should be unbounded

   /** The port-component-ref */
   private PortComponentRef portComponentRef;

     <xsd:element name="port-component-ref"
		   type="javaee:port-component-refType"
		   minOccurs="0" maxOccurs="unbounded">
	<xsd:annotation>
	  <xsd:documentation>

	    The port-component-ref element declares a client dependency
	    on the container for resolving a Service Endpoint Interface
	    to a WSDL port. It optionally associates the Service Endpoint
	    Interface with a particular port-component. This is only used
	    by the container for a Service.getPort(Class) method call.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:20:12 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Thu, 25 Oct 2007 12:20:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-2) process monitoring
 and statistics capabilities (BAM)
Message-ID: <21821145.1193329212670.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12384380 ] 
            
Ronald van Kuijk commented on JBPM-2:
-------------------------------------

This is NEW functionality.. so it is not dangerous at all (real admins look further than just a red flag ;-) ) It is not closed either since jbpm does not have this functionality (yet).

I do think however that an issue can hardly be blocking if no version is assigned to it.

> process monitoring and statistics capabilities (BAM)
> ----------------------------------------------------
>
>                 Key: JBPM-2
>                 URL: http://jira.jboss.com/jira/browse/JBPM-2
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>         Environment: N/A
>            Reporter: Ronald van Kuijk
>            Priority: Blocker
>
> JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=49900689
> 1.  jBPM should store the duration and start date of a state/process in the logs
> 2.  Write some detailed info on wiki
> 3.  Show processinstance and data
> 4.  day/week/month overviews
> 5.  near realtime data per process
> 6.  produce graphs of day/week/month overviews
> Some more ideas i got from a requirements document...
> -  Number of cases processed in through a particular process definition
> -  Number of cases flowing through a particular activity
> -  Longest work item delay by activity
> -  Workitems awaiting a particular task
> -  Workitems in a specific worklist claimed and/or completed by a particular user
> -  Longest end-to-end delay
> -  Mean time to approve by activity by participant
> -  Mean end-to-end completion time.
> as background info, here's what the competition says about BAM:
> http://appian.com/AppianEnt/Analytics/analytics.html
> http://www.webmethods.com/meta/default/folder/0000005936
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduction/htm/ebiz_intro_story_piew.asp
> http://www.tibco.com/software/business_optimization/activity_monitoring.jsp?m=c1
> http://www.vitria.com/products/platform/bam.html
> http://looselycoupled.com/glossary/BAM

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:20:12 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:20:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13785177.1193329212832.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384381 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

soapHeader should be of type List<QName>

   private List<String> soapHeader;

      <xsd:element name="soap-header"
		   type="javaee:xsdQNameType"
		   minOccurs="0" maxOccurs="unbounded">
	<xsd:annotation>
	  <xsd:documentation>

	    Defines the QName of a SOAP header that will be processed
	    by the handler.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:39:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23313246.1193330343994.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384388 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

serviceNamePattern should be of type QName

   private String serviceNamePattern;

  <xsd:simpleType name="service-ref_qname-pattern">
     <xsd:annotation>
        <xsd:documentation>
	     This is used to specify the QName pattern in the
	     attribute service-name-pattern and port-name-pattern in
	     the handler-chain element

	     For example, the various forms acceptable here for
	     service-name-pattern attribute in handler-chain element
	     are :

	     Exact Name: service-name-pattern="ns1:EchoService"

		 In this case, handlers specified in this
		 handler-chain element will apply to all ports with
		 this exact service name. The namespace prefix must
		 have been declared in a namespace declaration
		 attribute in either the start-tag of the element
		 where the prefix is used or in an an ancestor
		 element (i.e. an element in whose content the
		 prefixed markup occurs)

	     Pattern : service-name-pattern="ns1:EchoService*"

		 In this case, handlers specified in this
		 handler-chain element will apply to all ports whose
		 Service names are like EchoService1, EchoServiceFoo
		 etc. The namespace prefix must have been declared in
		 a namespace declaration attribute in either the
		 start-tag of the element where the prefix is used or
		 in an an ancestor element (i.e. an element in whose
		 content the prefixed markup occurs)

	     Wild Card : service-name-pattern="*"

		In this case, handlers specified in this handler-chain
		element will apply to ports of all service names.

	    The same can be applied to port-name attribute in
	    handler-chain element.

        </xsd:documentation>
     </xsd:annotation>

     <xsd:restriction base="xsd:token">
        <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
     </xsd:restriction>

  </xsd:simpleType>


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:41:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25190627.1193330461461.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384389 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

Both should be of type QName

   private String serviceNamePattern;
   
   private String portNamePattern;


         <xsd:element name="service-name-pattern"
		      type="javaee:service-ref_qname-pattern" />
         <xsd:element name="port-name-pattern"
	              type="javaee:service-ref_qname-pattern" />


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:43:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2036372.1193330581828.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384391 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

protocolBindings should be of type String

   // TODO protocol-bindings


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:51:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 12:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27718444.1193331061733.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384396 ] 
            
Scott M Stark commented on JBAS-4895:
-------------------------------------

Attach standard and jboss xml fragments that can be incorporated into the metadata unit tests for these please.


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:57:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 25 Oct 2007 12:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24758336.1193331421645.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Galder Zamarreno updated JBAS-4841:
-----------------------------------

    Attachment: updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt

Attached can be found an updated version of the document.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Galder Zamarreno
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:01:05 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 25 Oct 2007 13:01:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31865614.1193331665487.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4841?page=comments#action_12384401 ] 
            
Galder Zamarreno commented on JBAS-4841:
----------------------------------------

Due to lack of time, the following sections have not been incorporated:

- Explain common down_thread and up_thread attributes from http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsProtocolCommonProperties
- Cluster does not join / troubleshooting section from http://www.jgroups.org/javagroupsnew/docs/manual/html/ch02.html#ItDoesntWork
- Best practices explained in http://wiki.jboss.org/wiki/Wiki.jsp?page=TwoClustersSameNetwork 
- Effect of -b AS parameter in JGroups.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Galder Zamarreno
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:34:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <637905.1193333643828.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384408 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

jaxrpc <service-ref>

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/jaxrpc/serviceref/

jaxws <service-ref>

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/jaxws/webserviceref/


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:37:11 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Thu, 25 Oct 2007 13:37:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1123) When working
 with a
 snapshot release, JBM should report at boot  "r<svn-revision-number"
 instead of the next point release
Message-ID: <8939922.1193333831608.JavaMail.jira@cloud.prod.atl2.jboss.com>

When working with a snapshot release, JBM should report at boot  "r<svn-revision-number" instead of the next point release
--------------------------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1123
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1123
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Ovidiu Feodorov
            Priority: Minor




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:42:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 13:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8999279.1193334121506.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384409 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

jaxws <service-ref> 

https://svn.jboss.org/repos/jbossws/framework/branches/jbossws-framework-2.0.2/src/test/resources/jaxws/samples/webserviceref/

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:51:01 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 13:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10474064.1193334661498.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-480?page=comments#action_12384411 ] 
            
Jason T. Greene commented on JBAOP-480:
---------------------------------------

There are 2 unit tests in in the pojo cache project that hit it frequently, (about 1 in 4 runs triggers it on my system)

svn co https://svn.jboss.org/repos/jbosscache/pojo/trunk pojocache-trunk
cd pojocache-trunk
mvn -Dtest=LocalConcurrentTest test

The failure logs for whichever test failes are in target/surefire-reports/

Is this sufficient?





> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:03:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 14:03:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25257674.1193335382118.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384412 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

The name of the property probably becomes a discussion whose scope extends across the AS, since if there's a requirement to provide an id to each server, we might as well use that value elsewhere.  See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122241 .

Also, there should be a cmd line switch to set this.  Gone are the days of telling people in trainings, etc "fire up 2 AS instances with run - c all and you'll have a cluster."  Saying "run -i 0 - c all" and "run -i 1 -c all" is fairly palatable.  Saying "run -Dserver.peer.id=0 -c all" and "run -Dserver.peer.id=1 - c all" .... well, yuck.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:20:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Thu, 25 Oct 2007 14:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10048564.1193336401570.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Vladimir Blagojevic reopened JGRP-608:
--------------------------------------

             
Lock scope is too big. There are tests failures with this "fix".

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:46:01 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 14:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7473239.1193337961609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Stefan Guilhen resolved JBAS-4804.
----------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
       Resolution: Rejected

The ssoid and session cookie name can now be injected by the httpHeaderForSSOAuth and sessionCookieForSSOAuth attributes of GenericHeaderAuthenticator. A web application can now perform the whole generic header auth configuration on it's own WEB-INF/context.xml file. No changes to the container config files are needed. 

This is how the WEB-INF/context.xml should look like now when using the GenericHeaderAuthenticator:

<Context>
  <Valve className="org.jboss.web.tomcat.security.GenericHeaderAuthenticator" httpHeaderForSSOAuth="sm_ssoid,ct-remote-user,HTTP_OBLIX_UID"
         sessionCookieForSSOAuth="SMSESSION,CTSESSION,ObSSOCookie"/>
</Context>

A test case named GenericHeaderAuthUnitTestCase has been developed to test this behaviour. The wiki has also been updated.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:01 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 14:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32989127.1193338321934.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Stefan Guilhen reopened JBAS-4804:
----------------------------------

             
Re-opening issue to assign to correct resolution.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For: JBossAS-4.2.3.GA,  JBossAS-5.0.0.Beta3
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:02 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 14:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5429916.1193338322096.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Stefan Guilhen resolved JBAS-4804.
----------------------------------

    Resolution: Done

Issue's resolution set to Done instead of Rejected.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:02 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 25 Oct 2007 14:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5096906.1193338322260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Anil Saldhana reopened JBAS-4804:
---------------------------------

             
Reopen to remove the rejected tag from resolution field.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For: JBossAS-4.2.3.GA,  JBossAS-5.0.0.Beta3
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:02 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 25 Oct 2007 14:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21107393.1193338322450.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Anil Saldhana closed JBAS-4804.
-------------------------------

    Resolution: Done

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:54:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 14:54:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24078940.1193338451727.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384424 ] 
            
Tim Fox commented on JBMESSAGING-1121:
--------------------------------------

We may be able to do away with the necessity of the user configuring a unique id by doing something like the following:

When a server starts look in it's config files for the server id, if it does not exist request one from a sequence managed by the co-ordinator. Once it obtains an id, write it into its config files

When the server starts the next time it will already have the generated id so it will know which queues in the database "belong" to it.

Server ids need to be persistent since each node owns it's own set of queues.

Alternatively we could generate the ids as GUIDs then we avoid a global sequence, but then lookups in the DB based on a GUID string will be slower than an int, potentially hitting JBM performance.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:56:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 14:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7760196.1193338561661.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384426 ] 
            
Tim Fox commented on JBMESSAGING-1121:
--------------------------------------

Actually I think GUIDs are the only option, since different bridged servers also need unique ids and they won't be in the same JGroups group so a shared sequence won't work.

For JBM 2.0 using a GUID becomes a non issue since each node will have its own store.

I can do an experiment and see if there is much impact in making node_id a (potentially long) string...

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:05:11 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 15:05:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13487616.1193339111806.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Jason T. Greene updated JBAOP-480:
----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098971

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:07:01 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 15:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5687725.1193339221608.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-480?page=comments#action_12384428 ] 
            
Jason T. Greene commented on JBAOP-480:
---------------------------------------

BTW, I noticed a couple of thread safety problems in GeneratedClassAdvisor, which are likely the cause, and started a forum thread here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098971


> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:11:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 15:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15989998.1193339461582.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384430 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

That would be useful information. But, TBH, the integer approach you have now could be fine, if you regard trusting the user to pass in the correct value at startup to be adequate persistence (seems OK to me.) I used to dislike your use of integer, but now it's growing on me; i.e. it makes a perfectly good jvmRoute for the web tier.  A GUID would be a pretty long to append to web session ids.

Suggest we try and use the http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122241 thread to have a general discussion of where node ids might be needed and what format is required for each use case.  That thread's got Scott's attention. If we can come up with a single approach that meets all needs, that would be ideal.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:26:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 15:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19707246.1193340361565.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384433 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

LOL. This all seemed so familiar.  Then I found http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108609  .

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:11:16 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 16:11:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6778138.1193343076481.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384439 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

I have temporarily commented out ConnectionConsumerTest::testStopWhileProcessing since it hangs the test suite until this task is complete.

Be sure to uncommented it before closing this task

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:25:01 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-409) Make a version of
 ScopedJbossClassPool that works with AS 5
In-Reply-To: <32250594.1181062448417.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5575078.1193343901554.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-409?page=all ]

Kabir Khan closed JBAOP-409.
----------------------------

    Resolution: Done

> Make a version of ScopedJbossClassPool that works with AS 5
> -----------------------------------------------------------
>
>                 Key: JBAOP-409
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-409
>             Project: JBoss AOP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.beta2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20945904.1193344082290.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Kabir Khan updated JBAOP-480:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.CR2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-388) Allow specification
 of the exception for after-throwing and finally bindings
In-Reply-To: <12227475.1176743158464.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1599406.1193344082652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-388?page=all ]

Kabir Khan updated JBAOP-388:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Allow specification of the exception for after-throwing and finally bindings
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-388
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-388
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> We need to provide an optional attribute to the throwing/finally tags (and to the corrersponding annotation, if it has already been implemented JBAOP-386), so the user can specify an exception type.
> This task includes updating:
> - advice validation algorithm
> - overloaded advice selection algorithm
> - documentation (tutorial, reference manual, etc)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-107) The different types
 of classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <5899603.1193344082932.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan updated JBAOP-107:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-253) Before release,
 submit the jar to the Messaging team for testing
Message-ID: <29545429.1193344083188.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ]

Kabir Khan updated JBAOP-253:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Before release, submit the jar to the Messaging team for testing
> ----------------------------------------------------------------
>
>                 Key: JBAOP-253
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-253
>             Project: JBoss AOP
>          Issue Type: Task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-209) Change any usage of
 java.rmi.MarshalledObject with JBoss Serialization's equivalent.
Message-ID: <30091269.1193344083397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-209?page=all ]

Kabir Khan updated JBAOP-209:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.
> ------------------------------------------------------------------------------------
>
>                 Key: JBAOP-209
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-209
>             Project: JBoss AOP
>          Issue Type: Feature Request
>    Affects Versions: 1.3.5
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-416) Exclude tests
 testing new functionality from precompiled-compatibility-tests
In-Reply-To: <15845906.1181767768177.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23452125.1193344083536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-416?page=all ]

Kabir Khan updated JBAOP-416:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Exclude tests testing new functionality from precompiled-compatibility-tests
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-416
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-416
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>            Priority: Optional
>             Fix For: 2.0.0.CR2
>
>
> Once that is done, can you do me a favour?
> Kabir says:
> build.sh -f build-test-jdk50.xml clean-tests compile-test-classes precompiled-compatibility-tests
> Kabir says:
> It weaves with aop 1.5.5.GA and runs with AOP 2.0
> Kabir says:
> some tests will fail, but most should pass
> Fl?via says:
> Sure
> Kabir says:
> The tests that fail will hopefully be tests where we added some functionality in AOP 2.0 that does not exist in AOP 1.5.5.GA
> Kabir says:
> Ideally we need some way to exclude tests that are newer functionality than exists in the old version
> Kabir says:
> I'll add a JIRA for that
> Kabir says:
> since it would be good to get these automated
> Kabir says:
> I only remembered this since I spoke to Jason Green earlier about backward compatibility
> Fl?via says:
> Yes. After all, we don't have a way of making new functionality work in JBAOP1.5
> Kabir says:
> Thanks

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-433) Caller Interceptor
 Chains Are Not Rebuilt
In-Reply-To: <1733027.1183437963987.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28366582.1193344083739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-433?page=all ]

Kabir Khan updated JBAOP-433:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Caller Interceptor Chains Are Not Rebuilt
> -----------------------------------------
>
>                 Key: JBAOP-433
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-433
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha5
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> The rebuild process of interceptor chains for caller pointcuts is not taking place correctly: no pointcut rematching is being performed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-380) JBoss AOP sets info
 field to null before rebuilding a chain
In-Reply-To: <18445535.1176731518531.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29657920.1193344083916.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-380?page=all ]

Kabir Khan updated JBAOP-380:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> JBoss AOP sets info field to null before rebuilding a chain
> -----------------------------------------------------------
>
>                 Key: JBAOP-380
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-380
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha4
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> Advisor sets the joinpoint info field as null before rebuilding the interceptor chain. So, for a short period of time, that joinpoint will not be intercepted.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-380) JBoss AOP sets info
 field to null before rebuilding a chain
In-Reply-To: <18445535.1176731518531.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4984019.1193344203829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-380?page=all ]

Kabir Khan updated JBAOP-380:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> JBoss AOP sets info field to null before rebuilding a chain
> -----------------------------------------------------------
>
>                 Key: JBAOP-380
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-380
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha4
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> Advisor sets the joinpoint info field as null before rebuilding the interceptor chain. So, for a short period of time, that joinpoint will not be intercepted.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30692669.1193344204036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Kabir Khan updated JBAOP-480:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.CR1
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-253) Before release,
 submit the jar to the Messaging team for testing
Message-ID: <3885674.1193344204302.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ]

Kabir Khan updated JBAOP-253:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Before release, submit the jar to the Messaging team for testing
> ----------------------------------------------------------------
>
>                 Key: JBAOP-253
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-253
>             Project: JBoss AOP
>          Issue Type: Task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Kabir Khan
>            Priority: Minor
>             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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-209) Change any usage of
 java.rmi.MarshalledObject with JBoss Serialization's equivalent.
Message-ID: <9168969.1193344204443.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-209?page=all ]

Kabir Khan updated JBAOP-209:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.
> ------------------------------------------------------------------------------------
>
>                 Key: JBAOP-209
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-209
>             Project: JBoss AOP
>          Issue Type: Feature Request
>    Affects Versions: 1.3.5
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>            Priority: Minor
>             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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-416) Exclude tests
 testing new functionality from precompiled-compatibility-tests
In-Reply-To: <15845906.1181767768177.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19266197.1193344204586.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-416?page=all ]

Kabir Khan updated JBAOP-416:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Exclude tests testing new functionality from precompiled-compatibility-tests
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-416
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-416
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>            Priority: Optional
>             Fix For: 2.0.0.CR1
>
>
> Once that is done, can you do me a favour?
> Kabir says:
> build.sh -f build-test-jdk50.xml clean-tests compile-test-classes precompiled-compatibility-tests
> Kabir says:
> It weaves with aop 1.5.5.GA and runs with AOP 2.0
> Kabir says:
> some tests will fail, but most should pass
> Fl?via says:
> Sure
> Kabir says:
> The tests that fail will hopefully be tests where we added some functionality in AOP 2.0 that does not exist in AOP 1.5.5.GA
> Kabir says:
> Ideally we need some way to exclude tests that are newer functionality than exists in the old version
> Kabir says:
> I'll add a JIRA for that
> Kabir says:
> since it would be good to get these automated
> Kabir says:
> I only remembered this since I spoke to Jason Green earlier about backward compatibility
> Fl?via says:
> Yes. After all, we don't have a way of making new functionality work in JBAOP1.5
> Kabir says:
> Thanks

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-433) Caller Interceptor
 Chains Are Not Rebuilt
In-Reply-To: <1733027.1183437963987.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6901723.1193344204765.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-433?page=all ]

Kabir Khan updated JBAOP-433:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Caller Interceptor Chains Are Not Rebuilt
> -----------------------------------------
>
>                 Key: JBAOP-433
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-433
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha5
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> The rebuild process of interceptor chains for caller pointcuts is not taking place correctly: no pointcut rematching is being performed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:05 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-107) The different types
 of classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <7040881.1193344205037.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan updated JBAOP-107:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:05 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-388) Allow specification
 of the exception for after-throwing and finally bindings
In-Reply-To: <12227475.1176743158464.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31595471.1193344205211.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-388?page=all ]

Kabir Khan updated JBAOP-388:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Allow specification of the exception for after-throwing and finally bindings
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-388
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-388
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> We need to provide an optional attribute to the throwing/finally tags (and to the corrersponding annotation, if it has already been implemented JBAOP-386), so the user can specify an exception type.
> This task includes updating:
> - advice validation algorithm
> - overloaded advice selection algorithm
> - documentation (tutorial, reference manual, etc)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:32:01 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-107) The different
 types of
 classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <3649005.1193344321523.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-107?page=comments#action_12384444 ] 
            
Kabir Khan commented on JBAOP-107:
----------------------------------

asintegration/org.jboss.aop.asintegration.jboss5 should be moved into the AS 5 source tree, once that has the MC upgraded to 2.0.0.Beta5

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:59:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 16:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11055981.1193345941491.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis reassigned JBCOMMON-36:
------------------------------------------

    Assignee: Dimitris Andreadis  (was: Vicky Kak)

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:03:04 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 17:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1292) SFSB session
	replication
Message-ID: <31825584.1193346184761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1292?page=all ]

Jason T. Greene closed JBAS-1292.
---------------------------------

    Resolution: Out of Date

> SFSB session replication
> ------------------------
>
>                 Key: JBAS-1292
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1292
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Bela Ban
>         Assigned To: Jason T. Greene
>   Original Estimate: 10 weeks
>  Remaining Estimate: 10 weeks
>
> - Issues: who instrument the user-specified object? Can it be done transparently?
>   - SFSB has states defined already and user declared it as "clusterable", can we
>     declare the fields object as "advisable" at runtime. Meaning, deployer will know
>     this bean is clusterable and it will "delegate" it to JBossAop to declare all
>     the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor
>     at run time. Check with Bill on this feature.
>   - Check modified field and do fine-grained replication only

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:16:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2106347.1193346961698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

              Summary: Add a Classes.getAllUniqueInterfaces utility method.  (was: ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.)
           Issue Type: Feature Request  (was: Bug)
    Affects Version/s:     (was: 1.0.0.GA)
          Description: 
Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.


  was:
In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
>>java.lang.IllegalArgumentException: repeated interface: 


> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:16:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9772801.1193346961850.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis closed JBCOMMON-36.
--------------------------------------

    Resolution: Done

Added the new utility method.

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.2.3.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:18:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21083444.1193347081672.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Comment: was deleted

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:18:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13359204.1193347081834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Comment: was deleted

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:18:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:18:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21562425.1193347082044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Comment: was deleted

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:40:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4753) ExternalContext
 needs pass proxy
 interface set to the Proxy.newProxyInstance(loader, interfaces, handler);
 in createProxyContext method.
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32615750.1193348401510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4753?page=all ]

Dimitris Andreadis reassigned JBAS-4753:
----------------------------------------

    Assignee: Dimitris Andreadis  (was: Vicky Kak)

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.5.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can  populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler);  it results in the exception 
> >>java.lang.IllegalArgumentException: repeated interface:

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:42:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4753) ExternalContext can
 pass
 duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5595344.1193348521540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4753?page=all ]

Dimitris Andreadis updated JBAS-4753:
-------------------------------------

              Summary: ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)  (was: ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.)
        Fix Version/s: JBossAS-4.2.3.GA
    Affects Version/s: JBossAS-4.2.2.GA
                       JBossAS-4.2.1.GA
                       JBossAS-4.2.0.GA
                       JBossAS-5.0.0.Beta2
                           (was: JBossAS-4.0.5.GA)
          Description: 
The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).





  was:
In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can  populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler);  it results in the exception 
>>java.lang.IllegalArgumentException: repeated interface:







> ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:49:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4753) ExternalContext
 can pass
 duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15858262.1193348941707.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4753?page=comments#action_12384448 ] 
            
Dimitris Andreadis commented on JBAS-4753:
------------------------------------------

I didn't change the existing Classes.getAllInterfaces(..) for compatibility reasons.

I added a new utility method in JBCOMMON-36 that can be used to construct the array of implemented interfaces, in presence of duplicates.

To avoid generating yet another jboss-common release just for this fix, I copied the body of the utility method inside server/src/main/org/jboss/naming/ExternalContext.java.

After we update Branch_4_2 to jboss common 1.2.2 and HEAD to jboss common-core 2.2.3, this can be properly replaced with a call to the Classes.getAllUniqueInterfaces(..) utility.

> ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 18:00:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 18:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4753) ExternalContext can
 pass duplicate
 interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31826824.1193349601746.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4753?page=all ]

Dimitris Andreadis closed JBAS-4753.
------------------------------------

    Resolution: Done

Done.

> ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 18:33:01 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 18:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4701) JaasSecurityDomain
 doesn't handle encrypted truststore passwords properly
In-Reply-To: <19151046.1189539013902.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <497067.1193351581861.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4701?page=all ]

Stefan Guilhen closed JBAS-4701.
--------------------------------


The fix code has been added to Brach_4_0, Branch_4_2 and Trunk.

> JaasSecurityDomain doesn't handle encrypted truststore passwords properly
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4701
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4701
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.5.GA
>            Reporter: Stefan Guilhen
>         Assigned To: Stefan Guilhen
>             Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.2.GA
>
>
> In a recent support case, the user reported that he could not set an encrypted password for the truststore in the same way he does for the keystore. The application server fails to start when the encrypted truststore password is used, displaying the following exception:
> java.io.IOException: Keystore was tampered with, or password was incorrect.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 18:56:11 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Thu, 25 Oct 2007 18:56:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1300) BRMS -
 misspelling in label in "create new category" dialog
Message-ID: <7924962.1193352971576.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS - misspelling in label in "create new category" dialog
-----------------------------------------------------------

                 Key: JBRULES-1300
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1300
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
            Priority: Trivial


In BRMS, go to Admin > Manage Categories > Create new category. The dialog box has a misspelling in the first label "Cateogory name" should say "Category name"

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 20:13:12 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 25 Oct 2007 20:13:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-851) Provide RuleFlow
 editing capabilities within JBRMS
In-Reply-To: <10955939.1179153237844.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17473218.1193357592189.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-851?page=comments#action_12384464 ] 
            
Michael Neale commented on JBRULES-851:
---------------------------------------

Oh man that would be nice. No sorry to let everyone down but my chops aren't that great ! Maybe after ruleflow has matured some more, we could have this. I think there are still a few iterations to go in adding features to rule flow, after that point we could look at how to do it on the web. I have seen demos on how to do it, it can be done but the moment its not really that easy. (and time wise am always pressed). 

Always happy to be pressured and bribed to make this happen. 

No, I know next to nothing about ajax (I never though ajax was hard, just a clever use of old tech).

> Provide RuleFlow editing capabilities within JBRMS
> --------------------------------------------------
>
>                 Key: JBRULES-851
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-851
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Anstis
>         Assigned To: Fernando Meyer
>
> Ruleflow should be available in the JBRMS (apologies is this JIRA should have been raised against JBRMS).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 20:19:01 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 25 Oct 2007 20:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1150) Drools 4.0 BRMS
 not working with geronimo-jetty6-jee5-2.0.1
In-Reply-To: <25850901.1188508878448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29773365.1193357941535.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1150?page=comments#action_12384466 ] 
            
Michael Neale commented on JBRULES-1150:
----------------------------------------

ah yes - there could be java 6 issues - I haven't had a chance to check at this stage, but will shortly. With trunk we are moving to java 5 and up, so that will make it easier to get rid of the legacy that would be holding back for java 6 support. I believe most containers have some issues with java 6 at this stage (but they should be getting resolved rapidly). 

> Drools 4.0 BRMS not working with geronimo-jetty6-jee5-2.0.1
> -----------------------------------------------------------
>
>                 Key: JBRULES-1150
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1150
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>         Environment: geronimo-jetty6-jee5-2.0.1
> drools-4.0.1.SNAPSHOT-brms
>            Reporter: Bhagwath Vadyala
>         Assigned To: Fernando Meyer
>         Attachments: drools-error-screenshot.doc, jetty_2007_09_04.log, screenshot-1.jpg
>
>
> I am trying to test and see whether Drools 4.0 BRMS works with Geronimo-jetty6-jee5-2.0.1 or not.
> Drools BRMS version which I am using is drools-4.0.1.SNAPSHOT-brms.
> It deploys fine in Geronimo but when I open the BRMS error message I am getting is HTTP ERROR:404.
> Please let me know whether we can make Drools 4.0 work with Geronimo-jetty 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

        


From jira-events at lists.jboss.org  Thu Oct 25 21:55:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 21:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18209321.1193363701548.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Scott M Stark resolved JBAS-4895.
---------------------------------

    Resolution: Done

These changes are in the latest metadata snapshot (rev 1678).


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 21:57:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 21:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4898) class-loading not
 found as a child of jboss-web
In-Reply-To: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17451757.1193363821468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4898?page=all ]

Scott M Stark resolved JBAS-4898.
---------------------------------

    Resolution: Done

This is included in the current metadata snapshot (rev 1678).

> class-loading not found as a child of jboss-web
> -----------------------------------------------
>
>                 Key: JBAS-4898
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
>   <class-loading>
>     <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
>   </class-loading>
> </jboss-web>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 21:59:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 21:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4910) NPE in
	AbstractMappedMetaData
In-Reply-To: <32126662.1193303701492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11028878.1193363941449.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4910?page=all ]

Scott M Stark resolved JBAS-4910.
---------------------------------

    Resolution: Done

These changes are in the latest metadata snapshot (rev 1678).

> NPE in AbstractMappedMetaData
> -----------------------------
>
>                 Key: JBAS-4910
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4910
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefClientTestCase one-test
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.javaee.support.AbstractMappedMetaData.addAll(AbstractMappedMetaData.java:188)
>         at org.jboss.metadata.javaee.spec.MessageDestinationsMetaData.merge(MessageDestinationsMetaData.java:66)
>         at org.jboss.metadata.client.jboss.JBossClientMetaData.merge(JBossClientMetaData.java:316)
>         at org.jboss.ejb3.deployers.JBossClientParsingDeployer.createMetaData(JBossClientParsingDeployer.java:63)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> To reproduce this, you need to enable the test in src/resources/test-excludes-jboss500.txt

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 22:01:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 22:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27460093.1193364061441.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Scott M Stark updated JBAS-4901:
--------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was:  JBossAS-5.0.0.Beta3)

This also is not a metadata issue.

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-5.0.0.CR1
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 00:45:07 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Fri, 26 Oct 2007 00:45:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8080334.1193373907028.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-480?page=comments#action_12384472 ] 
            
Flavia Rainone commented on JBAOP-480:
--------------------------------------

Yes, those examples are excelent to reproduce the error. Thanks Jason!

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.CR1
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:03:01 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Fri, 26 Oct 2007 01:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-459) Memory leaks
In-Reply-To: <18921234.1189678031248.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20406458.1193374981507.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-459?page=all ]

Flavia Rainone updated JBAOP-459:
---------------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.beta2)

> Memory leaks 
> -------------
>
>                 Key: JBAOP-459
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-459
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 1.3.6
>            Reporter: Kabir Khan
>         Assigned To: Flavia Rainone
>             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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:20:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 01:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBXB-112) Failed to create a
	new SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19698025.1193376001636.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Thomas Diesler reopened JBXB-112:
---------------------------------

             
 There are more occurances of this. I actually found 4, only one of them is fixed.

Caused by: java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
        at javax.xml.parsers.SAXParser.isXIncludeAware(SAXParser.java:511)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:204)
        ... 24 more


> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:39:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Fri, 26 Oct 2007 01:39:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14322369.1193377141532.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

cheng dan updated JBAS-4825:
----------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-1.odt

made some small changes.

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:42:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Fri, 26 Oct 2007 01:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4825) TECH REVIEW:
 Getting Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13086937.1193377321545.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

cheng dan resolved JBAS-4825.
-----------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 02:17:02 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 02:17:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13339060.1193379422252.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384483 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

To elaborate on the changes, they involve adding 

1. method event() to CoyoteInvoker
2. method getSSLSupport(SSLSession session) to RemotingSSLImplementation, and
3. constructor RemotingSSLSupport(SSLSession session) to RemotingSSLSupport(SSLSession.

The important thing to note is that, while these changes are necessary to achieve source compatibility with JBossWeb, they are not necessary for binary compatibility.  The CoyoteInvoker.event() method would only be called when the coyote system is in "comet" mode, and the RemotingSSLImplementation.getSSLSupport(SSLSession session)  would only be called by the Http11NioProtocol coyote class.  Neither of these is relevant to the current use of the coyote system by Remotig.

So current Remoting releases running in, for example, JBossAS 4.2.0.GA, will work with jbossweb.jar that ships with JBossAS.

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 03:45:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 03:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-610) Problems with large
 return value and FC
Message-ID: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>

Problems with large return value and FC
---------------------------------------

                 Key: JGRP-610
                 URL: http://jira.jboss.com/jira/browse/JGRP-610
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.6


When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:25:01 2007
From: jira-events at lists.jboss.org (joshmoore (JIRA))
Date: Fri, 26 Oct 2007 04:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3012) MemoryLeak in
 JaasSecurityManager::DomainInfo
Message-ID: <22847974.1193387101704.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3012?page=comments#action_12384499 ] 
            
joshmoore commented on JBAS-3012:
---------------------------------

Scott, could you clarify what you think the cause is here? We are running into this as well. A long running server had over 100K login modules plus 400K SimplePrincipals and 100K SecurityAssociationHandlers, SimpleGroups, etc. which eventually brought it to its knees. I've posted a screen shot from jprofiler at https://trac.openmicroscopy.org.uk/omero/ticket/818 , and confirmed that calling DynamicLoginConfig's flushAuthenticationCaches does free almost everything up. Not, however, the SecurityAssociation$SubjectContext instances. I'm still looking into that.

My planned work-around is to periodically call flushAuthenticationCaches. Any thoughts?

Many thanks,
Josh Moore
Glencoe Software, Inc.
The Open Microscopy Environment


From: jboss-service.xml

   <mbean code="org.jboss.security.auth.login.DynamicLoginConfig"
      name="omero:service=LoginConfig">
      <attribute name="AuthConfig">META-INF/jboss-login.xml</attribute>
      <depends optional-attribute-name="LoginConfigService">
         jboss.security:service=XMLLoginConfig
      </depends>
      <depends optional-attribute-name="SecurityManagerService">
         jboss.security:service=JaasSecurityManager
      </depends>
   </mbean>

From: jboss-login.xml

 <policy>
   <application-policy name="OmeroSecurity">
      <authentication>
          <login-module code = "ome.security.JBossLoginModule" flag = "required">
            <module-option name = "unauthenticatedIdentity">guest</module-option>
            <module-option name = "dsJndiName">java:/omeroDS</module-option>
            <module-option name = "hashAlgorithm">MD5</module-option>


> MemoryLeak in JaasSecurityManager::DomainInfo
> ---------------------------------------------
>
>                 Key: JBAS-3012
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3012
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Security
>            Reporter: Adrian Brock
>         Assigned To: Scott M Stark
>             Fix For: No Release
>
>
> There is a memory leak caused by the JaasSecurityManager::DomainInfo
> holding a reference to the LoginContext.
> Internally, this holds a reference to the context classloader.
> If this information is cached and then the classloader undeployed,
> the classloader and all associated classes/proxies/static data
> don't get garbage collected until this information is flushed.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:27:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 26 Oct 2007 04:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13857706.1193387221662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=all ]

Thomas Heute updated JBPORTAL-1773:
-----------------------------------

    Fix Version/s: 2.6.3 Final
         Assignee: Thomas Heute  (was: Julien Viet)

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>         Attachments: sample-portlet.war
>
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:38:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 04:38:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16761738.1193387881624.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12384500 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

Might be a UNICAST retransmission issue in connection with FRAG(2). If FRAG2 mangles the (unicast) headers, then we have an issue in unicast.

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:40:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 04:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24639860.1193388001407.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12384501 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

Not possible: FRAG2 is on top of UNICAST ! But possibly UNICAST's retransmission mangles the fragmentation IDs (FragHeader) ?

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 05:02:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 05:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
Message-ID: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>

Unwrap MetaValue in MetaValueFactory
------------------------------------

                 Key: JBMICROCONT-213
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: General
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta5


Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.

   /**
    * Unwrap meta value.
    * Supports simple and generic meta value.
    *
    * @param metaValue meta value
    * @return meta value's value
    */
   public abstract Object unwrap(MetaValue metaValue);

   /**
    * Unwrap meta value.
    * Supports simple and generic meta value.
    *
    * @param metaValue meta value
    * @param type the type
    * @return meta value's value
    */
   public abstract Object unwrap(MetaValue metaValue, Type type);

   /**
    * Unwrap meta value.
    * Supports simple and generic meta value.
    *
    * @param metaValue meta value
    * @param type the type
    * @return meta value's value
    */
   public abstract Object unwrap(MetaValue metaValue, TypeInfo type);




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 05:04:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 05:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27166065.1193389441395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=all ]

Ales Justin resolved JBMICROCONT-213.
-------------------------------------

    Resolution: Done

Implemented in DefaultMetaValueFactory.
We currently support all types of MetaValue except TableValue.

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 05:47:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 05:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-611) MergeTask GMS
 ConcurrentModificationException
Message-ID: <32335654.1193392021705.JavaMail.jira@cloud.prod.atl2.jboss.com>

MergeTask GMS ConcurrentModificationException
---------------------------------------------

                 Key: JGRP-611
                 URL: http://jira.jboss.com/jira/browse/JGRP-611
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.5.2, 2.6


[Vivek Sar]

I'm using JGroups 2.5 GA and have 3 members in the group using udp
gossip router (stack below). Occasionally, we have seen the following
exception if a node goes down and comes up again. This happens over
and over, only way to recover would then be to stop all the members
and start them again.


 2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - exception while merging
java.util.ConcurrentModificationException
	at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
	at java.util.AbstractList$Itr.next(Unknown Source)
	at org.jgroups.protocols.pbcast.CoordGmsImpl.removeRejectedMergeRequests(CoordGmsImpl.java:749)
	at org.jgroups.protocols.pbcast.CoordGmsImpl.access$500(CoordGmsImpl.java:26)
	at org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask.run(CoordGmsImpl.java:817)
	at java.lang.Thread.run(Unknown Source)
2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:27,237 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
...
...

Protocol Stack,

<config>
    <UDP
		 ip_mcast="false"
		 mcast_addr="228.10.10.10"
		 mcast_port="3092"
		 bind_addr="${jgroups.bindaddress.ip:jgroupshost}"
		 bind_port="${jgroups.bindaddress.port:3092}"		 		
         tos="16"
         ucast_recv_buf_size="200000"
         ucast_send_buf_size="640000"
         mcast_recv_buf_size="250000"
         mcast_send_buf_size="640000"
         loopback="true"
         discard_incompatible_packets="true"
         max_bundle_size="64000"
         max_bundle_timeout="30"
         use_incoming_packet_handler="true"
         use_outgoing_packet_handler="false"
         ip_ttl="32"
         enable_bundling="true"
		 use_concurrent_stack="true"
		 thread_pool.enabled="true"
		 thread_pool.min_threads="1"
		 thread_pool.max_threads="100"
		 thread_pool.keep_alive_time="20000"
		 thread_pool.queue_enabled="false"
		 thread_pool.queue_max_size="10"
		 thread_pool.rejection_policy="Run"
		 oob_thread_pool.enabled="true"
		 oob_thread_pool.min_threads="1"
		 oob_thread_pool.max_threads="4"
		 oob_thread_pool.keep_alive_time="30000"
		 oob_thread_pool.queue_enabled="true"
		 oob_thread_pool.queue_max_size="10"
		 oob_thread_pool.rejection_policy="Run"/>

    <PING gossip_host="${jgroups.gossiprouter.ip:jgroupshost}"
gossip_port="${jgroups.gossiprouter.port:3091}"
		    gossip_refresh="15000"
		    timeout="3000"
            num_initial_members="3"/>
	
	<MERGE2 min_interval="5000" max_interval="10000"
		down_thread="false" up_thread="false"/>
	
	<FD_SOCK up_thread="false" down_thread="false"/>
	
    <FD timeout="10000" max_tries="5" shun="true"/>

    <VERIFY_SUSPECT timeout="1500"/>
	
    <pbcast.NAKACK max_xmit_size="60000"
                   use_mcast_xmit="false" gc_lag="0"
                   retransmit_timeout="100,200,300,600,1200,2400,4800"
                   discard_delivered_msgs="true"/>
	
    <UNICAST timeout="300,600,1200,2400,3600"/>
	
    <ENCRYPT key_store_name="keystore" store_password="xxx"
key_password="xxx" alias="xxx"/>
	
    <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
                   max_bytes="400000"/>
	
    <VIEW_SYNC avg_send_interval="60000"/>

	
	
	<AUTH auth_class="org.jgroups.auth.MD5Token"
        auth_value="xxx"
        token_hash="MD5"/>
		
    <pbcast.GMS print_local_addr="true" join_timeout="5000"
                join_retry_timeout="2000" shun="true"/>
	
     <FC max_credits="2000000"
         min_threshold="0.10"/>
	
	<FRAG2 frag_size="60000"/>
	
    <pbcast.STATE_TRANSFER  />
</config>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 06:03:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Fri, 26 Oct 2007 06:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13337769.1193392981490.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Colin Mondesir resolved JBAS-4828.
----------------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:38:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 07:38:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4913) wsdl-override not
 found as a child of service-ref
Message-ID: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>

wsdl-override not found as a child of service-ref
-------------------------------------------------

                 Key: JBAS-4913
                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 07:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15721110.1193398801607.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4913?page=all ]

Thomas Diesler updated JBAS-4913:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

         Assignee: Alexey Loubyansky

> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:40:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 07:40:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9281629.1193398802065.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4913?page=comments#action_12384533 ] 
            
Thomas Diesler commented on JBAS-4913:
--------------------------------------

<!DOCTYPE jboss-client PUBLIC "-//JBoss//DTD Application Client 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-client_4_0.dtd">

<jboss-client>
  <jndi-name>benchmark-client</jndi-name>

  <service-ref>
    <service-ref-name>service/BenchmarkJSE</service-ref-name>
    <wsdl-override>http://@jboss.bind.address@:8080/jaxrpc-benchmark-doc/jse?wsdl</wsdl-override>
  </service-ref>
  <service-ref>
    <service-ref-name>service/BenchmarkEJB</service-ref-name>
    <wsdl-override>http://@jboss.bind.address@:8080/jaxrpc-benchmark-doc-ejb?wsdl</wsdl-override>
  </service-ref>

</jboss-client>


> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:48:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 26 Oct 2007 07:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20070716.1193399281737.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=all ]

Adrian Brock updated JBMICROCONT-212:
-------------------------------------

    Fix Version/s: JBossMC-2.0.0.Beta6
                       (was: JBossMC-2.0.0.Beta5)

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta6
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:50:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 26 Oct 2007 07:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23568949.1193399401476.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=all ]

Adrian Brock closed JBMICROCONT-212.
------------------------------------

    Resolution: Done

Resolved in beta6

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta6
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:11:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 26 Oct 2007 08:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1124) Cannot find
 replicant to
 remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
Message-ID: <21857133.1193400661417.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
-----------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1124
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1124
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Tim Fox
         Assigned To: Tim Fox
            Priority: Minor
             Fix For: EAP 4.3 Integration


Get the following exception in logs when shutting down JBoss 4.2.1.GA server with JBM by pressing CTRL-C

Seems benign but annoying.

13:00:12,932 WARN  [ConnectionFactory] Stopping failed jboss.messaging.connectionfactory:service=ConnectionFactory
java.lang.IllegalStateException: Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
        at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.unregisterConnectionFactory(ConnectionFactoryJNDIMapper.java:274)
        at org.jboss.jms.server.connectionfactory.ConnectionFactory.stopService(ConnectionFactory.java:239)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
        at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:206)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
        at $Proxy0.stop(Unknown Source)
        at org.jboss.system.ServiceController.stop(ServiceController.java:508)
        at org.jboss.system.ServiceController.stop(ServiceController.java:499)
        at org.jboss.system.ServiceController.stop(ServiceController.java:499)
        at org.jboss.system.ServiceController.stop(ServiceController.java:499)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.stop(Unknown Source)
        at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:336)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy51.stop(Unknown Source)
        at org.jboss.deployment.XSLSubDeployer.stop(XSLSubDeployer.java:202)
        at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
        at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
        at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:516)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:1058)
        at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:1033)
        at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:996)
13:00:12,968 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at c971d55 undeployed
13:00:13,063 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 7451b0af undeployed


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:37:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 26 Oct 2007 08:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27090207.1193402221523.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=comments#action_12384547 ] 
            
Dimitris Andreadis commented on JBMICROCONT-213:
------------------------------------------------

You can't have both Affects the Fixed version the same! If Beta5 was released on the 20th, the fixed version should be Beta6.

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:45:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21724839.1193402701605.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=all ]

Ales Justin updated JBMICROCONT-213:
------------------------------------

    Affects Version/s: JBossMC-2.0.0.Beta4
                           (was: JBossMC-2.0.0.Beta5)

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:47:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8309743.1193402821815.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=all ]

Ales Justin updated JBMICROCONT-213:
------------------------------------

    Comment: was deleted

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:54:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-210) Change
 KernelBus implementation
In-Reply-To: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3341158.1193403241482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-210?page=all ]

Ales Justin updated JBMICROCONT-210:
------------------------------------

    Affects Version/s: JBossMC-2.0.0.Beta4
                           (was: JBossMC-2.0.0.Beta5)

> Change KernelBus implementation
> -------------------------------
>
>                 Key: JBMICROCONT-210
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
> Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:54:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-209) Trim string
	value
In-Reply-To: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30825176.1193403241616.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-209?page=all ]

Ales Justin updated JBMICROCONT-209:
------------------------------------

    Affects Version/s: JBossMC-2.0.0.Beta4
                           (was: JBossMC-2.0.0.Beta5)

> Trim string value
> -----------------
>
>                 Key: JBMICROCONT-209
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: MetaData
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:58:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMICROCONT-205) Accessing
 content of vfsfile url fails
In-Reply-To: <22654520.1188863898204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18654671.1193403481842.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-205?page=all ]

Ales Justin reassigned JBMICROCONT-205:
---------------------------------------

    Assignee: Ales Justin

> Accessing content of vfsfile url fails
> --------------------------------------
>
>                 Key: JBMICROCONT-205
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-205
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>            Reporter: Scott M Stark
>         Assigned To: Ales Justin
>             Fix For: JBossMC-2.0.0.CR1
>
>
> When trying to create a ManagedProperty for a URL type with a vfsfile: url value, the content fails to be obtained:
> Caused by: java.net.UnknownServiceException: no content-type
>         at java.net.URLConnection.getContentHandler(URLConnection.java:1167)
>         at java.net.URLConnection.getContent(URLConnection.java:683)
>         at java.net.URL.getContent(URL.java:1021)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
>         at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
>         at org.jboss.beans.info.plugins.AbstractPropertyInfo.get(AbstractPropertyInfo.java:172)
>         at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:238)
>         at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:371)
>         ... 23 more
> VirtualFileURLConnection should be overriding the getContent method to return the VirtualFile I suppose.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:00:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-210) Change KernelBus
 implementation
In-Reply-To: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5491781.1193403601431.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-210?page=all ]

Ales Justin closed JBMICROCONT-210.
-----------------------------------


> Change KernelBus implementation
> -------------------------------
>
>                 Key: JBMICROCONT-210
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
> Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:02:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMICROCONT-211) Support ..
 notion in vfs paths
In-Reply-To: <9963001.1193307301447.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30252399.1193403721548.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-211?page=all ]

Ales Justin reassigned JBMICROCONT-211:
---------------------------------------

    Assignee: Ales Justin

> Support .. notion in vfs paths
> ------------------------------
>
>                 Key: JBMICROCONT-211
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-211
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: VFS
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>
> If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
> in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
> currently the PathTokenizer will report an error if the path contains a . or ..
> It should still through an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:02:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-211) Support ..
 notion in vfs paths
In-Reply-To: <9963001.1193307301447.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1232033.1193403721754.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-211?page=all ]

Ales Justin updated JBMICROCONT-211:
------------------------------------

    Description: 
If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
currently the PathTokenizer will report an error if the path contains a . or ..

It should still throw an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

  was:
If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
currently the PathTokenizer will report an error if the path contains a . or ..

It should still through an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.


> Support .. notion in vfs paths
> ------------------------------
>
>                 Key: JBMICROCONT-211
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-211
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: VFS
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>
> If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
> in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
> currently the PathTokenizer will report an error if the path contains a . or ..
> It should still throw an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:06:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 09:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4914) NPE in JBossWebRealm
Message-ID: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in JBossWebRealm
--------------------

                 Key: JBAS-4914
                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:06:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-209) Trim string
	value
In-Reply-To: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16314963.1193403961742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-209?page=all ]

Ales Justin closed JBMICROCONT-209.
-----------------------------------


> Trim string value
> -----------------
>
>                 Key: JBMICROCONT-209
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: MetaData
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:06:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 09:06:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14430629.1193403962044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Thomas Diesler updated JBAS-4914:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED

java.lang.NullPointerException
        at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
        at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
        at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
        at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
        at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

         Assignee: Anil Saldhana

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:17:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 09:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26588129.1193404621677.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Anil Saldhana reassigned JBAS-4914:
-----------------------------------

    Assignee: Scott M Stark  (was: Anil Saldhana)

Assigned to Scott temporarily to resolve the metadata.

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:19:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 09:19:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9108579.1193404744622.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12384557 ] 
            
Anil Saldhana commented on JBAS-4914:
-------------------------------------

============
  ServletMetaData servletMD = metaData.getServlets().get(servletName);
  SecurityRoleRefsMetaData roleRefs = servletMD.getSecurityRoleRefs();
==================

servletMD is null.

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:01:02 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:01:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29537681.1193407262006.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

Shelly McGowan updated JBAS-4843:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt

Updates.

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:03:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Fri, 26 Oct 2007 10:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <986864.1193407381569.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

Right, all are fixed now in trunk.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:09:12 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:09:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4843) TECH REVIEW: Server
 Configuration Guide - AppendixB - Use Alternative
 Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16270629.1193407752500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

Shelly McGowan resolved JBAS-4843.
----------------------------------

    Resolution: Done

updates are in attachment #2 - pls be sure to get the latest updates

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:13:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Fri, 26 Oct 2007 10:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31792115.1193407981521.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4913?page=comments#action_12384571 ] 
            
Alexey Loubyansky commented on JBAS-4913:
-----------------------------------------

Is it org.jboss.metadata.javaee.spec.ServiceReferenceMetaData that is bound to service-ref? Could you tell which property in that class is supposed to be bound to wsdl-override element?

> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:22:01 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22893885.1193408521709.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

Shelly McGowan updated JBAS-4885:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt

minor edit attached

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt, JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:22:02 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:22:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19178241.1193408522027.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

Shelly McGowan resolved JBAS-4885.
----------------------------------

    Resolution: Done

marking resolved to indicate a full chapter review was done

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt, JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:36:01 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16644743.1193409361582.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

Shelly McGowan resolved JBAS-4844.
----------------------------------

    Resolution: Done

no changes

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt, JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:59:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 10:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-85) Release Security
	V2.0.1.GA
In-Reply-To: <25608054.1192819263974.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5418268.1193410741800.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-85?page=all ]

Anil Saldhana updated SECURITY-85:
----------------------------------

    Summary: Release Security V2.0.1.GA  (was: Release Security V2.0.1-GA)

> Release Security V2.0.1.GA
> --------------------------
>
>                 Key: SECURITY-85
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-85
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:01:01 2007
From: jira-events at lists.jboss.org (Prakash Chellappa (JIRA))
Date: Fri, 26 Oct 2007 11:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1302) Drools
	ConsequenceException
Message-ID: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>

Drools ConsequenceException
---------------------------

                 Key: JBRULES-1302
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
         Environment: Unix 
            Reporter: Prakash Chellappa
             Fix For: 4.0.1


Hi 

We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.

org.drools.spi.ConsequenceException: java.lang.NullPointerException
    at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
    at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
    at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
    at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
    at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
    at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
    at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
    at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
    at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
    at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
    at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
    at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
    at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
    at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
    at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
    at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
    at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
    at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
    at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
    at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
    at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
    at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
    at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
    at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
    at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
    at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
    at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
    at org.drools.reteoo.Rete.retractObject(Rete.java:214)
    at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
    at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
    at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
    at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
    at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
    at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
    at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)

We get the error message when we retract the object.The piece of code is given below

                if( c instanceof TransactionBulkBean ) {
                        retract(c);
                        }

                if( t instanceof TransactionBulkBean )  {
                        retract(t);
                        }


                // Retract Old Events
                for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
                         ev.setMessage(null) ; retract (ev);
                }

We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.

We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.

Thanks
Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:19:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 11:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-85) Release Security
	V2.0.1.GA
In-Reply-To: <25608054.1192819263974.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25683851.1193411941665.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-85?page=all ]

Anil Saldhana closed SECURITY-85.
---------------------------------

    Resolution: Done

Tagged and released. The docs trunk needs to be tagged and released by SECURITY-84

> Release Security V2.0.1.GA
> --------------------------
>
>                 Key: SECURITY-85
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-85
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:41:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 11:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17704985.1193413261504.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4913?page=comments#action_12384595 ] 
            
Thomas Diesler commented on JBAS-4913:
--------------------------------------

Its actually JBossServiceReferenceMetaData, because <wsdl-override> is a proprietary extension to the <service-ref> element in jboss-client.xml, jboss.xml, jboss-web.xml

Please see the service-ref dtd include in the respective jboss dtds

> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:58:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 11:58:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-84) Update
 documentation for 2.0.1.GA Release
In-Reply-To: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <224507.1193414286666.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-84?page=all ]

Anil Saldhana updated SECURITY-84:
----------------------------------

    Summary: Update documentation for 2.0.1.GA Release  (was: Update documentation for 2.0.1-GA Release)

> Update documentation for 2.0.1.GA Release
> -----------------------------------------
>
>                 Key: SECURITY-84
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>
> Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 12:00:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Fri, 26 Oct 2007 12:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15606117.1193414403294.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Stelios Koussouris updated JBAS-4829:
-------------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-5.odt

changes so far

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 12:00:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Fri, 26 Oct 2007 12:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4829) TECH REVIEW:
 Getting Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13860687.1193414403576.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4829?page=comments#action_12384605 ] 
            
Stelios Koussouris commented on JBAS-4829:
------------------------------------------

Almost complete. Problem in deploying SEAM example. Investigating

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 13:51:01 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Fri, 26 Oct 2007 13:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
Message-ID: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
---------------------------------------------------------------------------------------

                 Key: EJBTHREE-1081
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
             Project: EJB 3.0
          Issue Type: Feature Request
         Environment: JBoss 4.2.2.GA
            Reporter: Michael McKibben
            Priority: Minor


I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:09:01 2007
From: jira-events at lists.jboss.org (Emmanuel Bernard (JIRA))
Date: Fri, 26 Oct 2007 14:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
In-Reply-To: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17071543.1193422141729.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1081?page=comments#action_12384635 ] 
            
Emmanuel Bernard commented on EJBTHREE-1081:
--------------------------------------------

I'm not user it's a good idea. The annotation processor can look at the super class without having to use @Inherited. Plus @Inherited does not propagates to interfaces.

> Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1081
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
>             Project: EJB 3.0
>          Issue Type: Feature Request
>         Environment: JBoss 4.2.2.GA
>            Reporter: Michael McKibben
>            Priority: Minor
>
> I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:09:02 2007
From: jira-events at lists.jboss.org (Emmanuel Bernard (JIRA))
Date: Fri, 26 Oct 2007 14:09:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
In-Reply-To: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3473221.1193422142066.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1081?page=comments#action_12384636 ] 
            
Emmanuel Bernard commented on EJBTHREE-1081:
--------------------------------------------

user => sure

> Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1081
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
>             Project: EJB 3.0
>          Issue Type: Feature Request
>         Environment: JBoss 4.2.2.GA
>            Reporter: Michael McKibben
>            Priority: Minor
>
> I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:19:01 2007
From: jira-events at lists.jboss.org (vivek v (JIRA))
Date: Fri, 26 Oct 2007 14:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26975466.1193422741433.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12384639 ] 
            
vivek v commented on JGRP-610:
------------------------------

Could this be related to - JGRP-590?

We have also seen this problem on our system, when a large return value (when using RpcDispatcher) never gets to the caller and the caller always times out (with TimeoutException).  (http://sourceforge.net/mailarchive/message.php?msg_id=a206fb7e0710042312g71c60d7ar4ef5b43ec8b48db5%40mail.gmail.com)

We use Gossip Router with UDP. 

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:32:28 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Fri, 26 Oct 2007 14:32:28 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
In-Reply-To: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26546516.1193423548085.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1081?page=comments#action_12384643 ] 
            
Michael McKibben commented on EJBTHREE-1081:
--------------------------------------------

hmm, perhaps this is a bug with the annotation processor then, because I can only get JBoss to recognize my @AspectDomain and @RemoteBindings annotation if I have them on the actual ejb type, and not on a base type.

> Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1081
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
>             Project: EJB 3.0
>          Issue Type: Feature Request
>         Environment: JBoss 4.2.2.GA
>            Reporter: Michael McKibben
>            Priority: Minor
>
> I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:44:11 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 14:44:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
Message-ID: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>

ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
----------------------------------------------------------------

                 Key: JBPM-1076
                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
             Project: JBoss jBPM
          Issue Type: Feature Request
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
            Reporter: Flavio Crispim
         Assigned To: Tom Baeyens


I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:37:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-86) Adapt Resource
 Interface for ACL
Message-ID: <877125.1193427421449.JavaMail.jira@cloud.prod.atl2.jboss.com>

Adapt Resource Interface for ACL
--------------------------------

                 Key: SECURITY-86
                 URL: http://jira.jboss.com/jira/browse/SECURITY-86
             Project: JBoss Security and Identity Management
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Security SPI
    Affects Versions: 2.0.1.GA
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.2-BETA


The Authorization framework interface "Resource" needs to be adapted for the ACL implementation.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:37:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-87)
 AuthorizationManager interface needs ACL semantics
Message-ID: <19665680.1193427421571.JavaMail.jira@cloud.prod.atl2.jboss.com>

AuthorizationManager interface needs ACL semantics
--------------------------------------------------

                 Key: SECURITY-87
                 URL: http://jira.jboss.com/jira/browse/SECURITY-87
             Project: JBoss Security and Identity Management
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Security SPI
    Affects Versions: 2.0.1.GA
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.2-BETA


The AuthorizationManager interface needs to be upgraded to handle the fast ACL implementation needs.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:39:16 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:39:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-88) Refactor
 JaasSecurityManager into JBossAuthenticationManager
Message-ID: <11984892.1193427556659.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor JaasSecurityManager into JBossAuthenticationManager
------------------------------------------------------------

                 Key: SECURITY-88
                 URL: http://jira.jboss.com/jira/browse/SECURITY-88
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.1.GA
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.2.GA


The code that exists in JaasSecurityManager needs to be pulled into a generic delegate in JBossSX such that the JaasSecurityManager in the AS security integration as well as the default AuthenticationManager can reuse.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:50:17 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:50:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-89) Fast ACL
	Implementation
Message-ID: <18943842.1193428217352.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fast ACL Implementation
-----------------------

                 Key: SECURITY-89
                 URL: http://jira.jboss.com/jira/browse/SECURITY-89
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: ACL
            Reporter: Anil Saldhana
         Assigned To: Stefan Guilhen
             Fix For: 2.0.2.GA


We need to implement a FAST ACL implementation to be used by the non JBAS projects such as JBoss Rules, Portal etc.

The key here is performance.

We basically have a tuple (key, CRUD) where key is an object instance.  We need to devise some mechanism by which the projects can plug in their key (similar to hibernate primary key mapping).

The ACL implementation should not assume any strategies, which need to be pluggable. The strategies can be Hibernate, Cache or ldap depending on user needs.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 16:09:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 16:09:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (SECURITY-74) Policy Management
 Console using JBoss SEAM
In-Reply-To: <14814510.1186178449283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8422719.1193429344076.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-74?page=all ]

Anil Saldhana reassigned SECURITY-74:
-------------------------------------

    Assignee: Marcus Moyses  (was: Anil Saldhana)

Marcus has shown a lot of initiative in learning more on the JBoss Admin Console.  He is driving the Policy Plugin.

> Policy Management Console using JBoss SEAM
> ------------------------------------------
>
>                 Key: SECURITY-74
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-74
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossXACML-Console
>            Reporter: Anil Saldhana
>         Assigned To: Marcus Moyses
>             Fix For: NO_VERSION
>
>
> Need for a progressive Policy Management console using JBoss SEAM.  The JAXB2 object model provided with JBoss XACML can be used to construct the policies.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 16:27:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 16:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-74) Policy Management
 Console using JBoss Admin Console/JBoss SEAM
In-Reply-To: <14814510.1186178449283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24243632.1193430421618.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-74?page=all ]

Anil Saldhana updated SECURITY-74:
----------------------------------

    Summary: Policy Management Console using JBoss Admin Console/JBoss SEAM  (was: Policy Management Console using JBoss SEAM)

> Policy Management Console using JBoss Admin Console/JBoss SEAM
> --------------------------------------------------------------
>
>                 Key: SECURITY-74
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-74
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossXACML-Console
>            Reporter: Anil Saldhana
>         Assigned To: Marcus Moyses
>             Fix For: NO_VERSION
>
>
> Need for a progressive Policy Management console using JBoss SEAM.  The JAXB2 object model provided with JBoss XACML can be used to construct the policies.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 16:33:02 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 16:33:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1300) BRMS -
 misspelling in label in "create new category" dialog
In-Reply-To: <7924962.1193352971576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31591863.1193430782012.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1300?page=all ]

Fernando Meyer reassigned JBRULES-1300:
---------------------------------------

    Assignee: Fernando Meyer

> BRMS - misspelling in label in "create new category" dialog
> -----------------------------------------------------------
>
>                 Key: JBRULES-1300
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1300
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>            Priority: Trivial
>
> In BRMS, go to Admin > Manage Categories > Create new category. The dialog box has a misspelling in the first label "Cateogory name" should say "Category name"

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:18:15 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 17:18:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10854987.1193433495637.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

Brian Stansberry updated JBAS-4836:
-----------------------------------

    Attachment: updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section1+-+Clustered-JNDI-Services.odt

My edits to the HA-JNDI section are attached.

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section1+-+Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:20:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 17:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16266506.1193433602137.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

Brian Stansberry reassigned JBAS-4836:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

Note that there are a couple places where I added things along the lines of 'see the "XYZ" section..' where hyperlinks should be added.

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section1+-+Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:51:14 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 17:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
In-Reply-To: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25454885.1193435474513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1297?page=all ]

Fernando Meyer reassigned JBRULES-1297:
---------------------------------------

    Assignee: Fernando Meyer

> DroolsCompilerAntTask.java should reset threadContextLoader to original value
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-1297
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Bali
>         Assigned To: Fernando Meyer
>         Attachments: droolsAntClasspathFixPatch.txt
>
>
> DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:53:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 17:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
In-Reply-To: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30951061.1193435581489.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1297?page=all ]

Fernando Meyer closed JBRULES-1297.
-----------------------------------

    Fix Version/s: 4.1.0
       Resolution: Done

patch applied Thanks

> DroolsCompilerAntTask.java should reset threadContextLoader to original value
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-1297
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Bali
>         Assigned To: Fernando Meyer
>             Fix For: 4.1.0
>
>         Attachments: droolsAntClasspathFixPatch.txt
>
>
> DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:58:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 17:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8212368.1193435881739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=all ]

Fernando Meyer reassigned JBRULES-1302:
---------------------------------------

    Assignee: Mark Proctor

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Mark Proctor
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:00:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 18:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29174468.1193436001642.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=all ]

Fernando Meyer reassigned JBRULES-1302:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:07:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25149924.1193436421563.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384674 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

It's important to note that jbossweb.jar is built with jdk 1.5, so the http transport can work with jbossweb only if Remoting is also built with jdk 1.5.  

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:09:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 18:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-84) Update
 documentation for 2.0.1.GA Release
In-Reply-To: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15583802.1193436541434.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-84?page=all ]

Anil Saldhana closed SECURITY-84.
---------------------------------

    Resolution: Done

> Update documentation for 2.0.1.GA Release
> -----------------------------------------
>
>                 Key: SECURITY-84
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>
> Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:11:05 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 18:11:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1300) BRMS -
 misspelling in label in "create new category" dialog
In-Reply-To: <7924962.1193352971576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25415289.1193436665580.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1300?page=all ]

Fernando Meyer resolved JBRULES-1300.
-------------------------------------

    Fix Version/s: 4.1.0
       Resolution: Done

> BRMS - misspelling in label in "create new category" dialog
> -----------------------------------------------------------
>
>                 Key: JBRULES-1300
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1300
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>            Priority: Trivial
>             Fix For: 4.1.0
>
>
> In BRMS, go to Admin > Manage Categories > Create new category. The dialog box has a misspelling in the first label "Cateogory name" should say "Category name"

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:15:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 18:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (SECURITY-84) Update
 documentation for 2.0.1.GA Release
In-Reply-To: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28507239.1193436901438.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/SECURITY-84?page=comments#action_12384675 ] 
            
Anil Saldhana commented on SECURITY-84:
---------------------------------------

http://labs.jboss.com/file-access/default/members/jbosssecurity/freezone/releases/guide/2.0.1.GA/jbosssecurity.html

> Update documentation for 2.0.1.GA Release
> -----------------------------------------
>
>                 Key: SECURITY-84
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>
> Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:26:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-825) Verify that
 CoyoteInvoker works with Apache Portable Runtime
In-Reply-To: <16554394.1193188321512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26360995.1193437561536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-825?page=all ]

Ron Sigal updated JBREM-825:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)

> Verify that CoyoteInvoker works with Apache Portable Runtime
> ------------------------------------------------------------
>
>                 Key: JBREM-825
>                 URL: http://jira.jboss.com/jira/browse/JBREM-825
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars.  When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:
> 21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
> 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
> 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
> 	at org.jboss.remoting.Client.invoke(Client.java:1632)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> 	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
> 	... 31 more

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:26:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-823)
 ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value
 is IPv6
In-Reply-To: <9184117.1192689903468.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31501383.1193437561804.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-823?page=all ]

Ron Sigal updated JBREM-823:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP2
                       2.2.2.GA_CP01
                       2.4.0.Beta1 (Pinto)
                           (was: 3.0.0.Alpha1 (Otter))

> ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6
> -----------------------------------------------------------------------------------
>
>                 Key: JBREM-823
>                 URL: http://jira.jboss.com/jira/browse/JBREM-823
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>            Reporter: Takayoshi Kimura
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: JBREM-823.patch
>
>
> IPv6 address contains ":" character, so it cannot be used in ObjectName.
> 2007-10-18 15:37:40,476 WARN  [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer.
> javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
> 	at javax.management.ObjectName.construct(ObjectName.java:529)
> 	at javax.management.ObjectName.<init>(ObjectName.java:1304)
> 	at org.jboss.remoting.transport.Connector.init(Connector.java:402)
> 	at org.jboss.remoting.transport.Connector.create(Connector.java:760)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:349)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy4.create(Unknown Source)
> 	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy5.deploy(Unknown Source)
> 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
> 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
> 	at org.jboss.Main.boot(Main.java:200)
> 	at org.jboss.Main$1.run(Main.java:508)
> 	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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:30:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the
 legacy configuration that embeds xml parsing
Message-ID: <9204450.1193437801785.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12384677 ] 
            
Ron Sigal commented on JBREM-63:
--------------------------------

Need to update Remoting Guide.

> Get rid of the legacy configuration that embeds xml parsing
> -----------------------------------------------------------
>
>                 Key: JBREM-63
>                 URL: http://jira.jboss.com/jira/browse/JBREM-63
>             Project: JBoss Remoting
>          Issue Type: Task
>    Affects Versions: 1.0.1 beta
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:30:02 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:30:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the
 legacy configuration that embeds xml parsing
Message-ID: <31706621.1193437802119.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12384678 ] 
            
Ron Sigal commented on JBREM-63:
--------------------------------

Unit test passed on cruisecontrol.

> Get rid of the legacy configuration that embeds xml parsing
> -----------------------------------------------------------
>
>                 Key: JBREM-63
>                 URL: http://jira.jboss.com/jira/browse/JBREM-63
>             Project: JBoss Remoting
>          Issue Type: Task
>    Affects Versions: 1.0.1 beta
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:30:02 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 26 Oct 2007 18:30:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15551455.1193437802447.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=comments#action_12384679 ] 
            
Edson Tirelli commented on JBRULES-1302:
----------------------------------------

Prakash,

Please, can you update to the 4.0.3 version of drools, since we fixed a number of bugs. If the problem still persists, we will need a self contained test case from you showing the problem, so that we can fix it.

Thanks,
Edson

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:37:01 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 26 Oct 2007 18:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9033746.1193438221742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=all ]

Edson Tirelli reassigned JBRULES-1302:
--------------------------------------

    Assignee: Edson Tirelli  (was: Fernando Meyer)

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:54:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17327326.1193439241744.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]

Ron Sigal reassigned JBREM-675:
-------------------------------

    Assignee: Ron Sigal  (was: Tom  Elrod)

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:04:01 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11972326.1193439841593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Flavio Crispim updated JBPM-1076:
---------------------------------

    Attachment: hibernate.queries.hbm.xml.patch

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:04:01 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33115959.1193439841775.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Flavio Crispim updated JBPM-1076:
---------------------------------

    Attachment: JbpmContext.java.patch

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:04:01 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24367979.1193439841943.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Flavio Crispim updated JBPM-1076:
---------------------------------

    Attachment: TaskMgmtSession.java.patch

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:23:01 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Fri, 26 Oct 2007 19:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6669554.1193440981503.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=comments#action_12384684 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1115:
----------------------------------------------

Happened again with r3237. I am analyzing the log, I will follow up with more details.

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 22:51:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 22:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1293) Backport for
	Eclipse 3.3
In-Reply-To: <12660311.1193073123217.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21330690.1193453461960.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1293?page=all ]

Fernando Meyer closed JBRULES-1293.
-----------------------------------

    Resolution: Done

> Backport for Eclipse 3.3
> ------------------------
>
>                 Key: JBRULES-1293
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1293
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> We now how two parallel eclipse projects for 4.0.x.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 22:51:02 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 22:51:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1294) Upgrade to MVEL
	1.2.10
In-Reply-To: <16163147.1193073243211.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22297299.1193453462890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1294?page=all ]

Fernando Meyer closed JBRULES-1294.
-----------------------------------

    Resolution: Done

> Upgrade to MVEL 1.2.10
> ----------------------
>
>                 Key: JBRULES-1294
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1294
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: All
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 23:27:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 23:27:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15484039.1193455622394.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Brian Stansberry updated JBAS-4840:
-----------------------------------

    Attachment: updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section5+-+Clustered_JMS_Services.odt

My edits attached.

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section5+-+Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 23:27:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 23:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8725513.1193455623069.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Brian Stansberry reassigned JBAS-4840:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section5+-+Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 23:52:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Fri, 26 Oct 2007 23:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-114) Reusing a model group
Message-ID: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>

Reusing a model group
---------------------

                 Key: JBXB-114
                 URL: http://jira.jboss.com/jira/browse/JBXB-114
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Feature Request
            Reporter: Scott M Stark
             Fix For: JBossXB-2.0.0.CR5


We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:

<!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
 exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
 security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
 resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
 cluster-config?, method-attributes?, depends*,
 ior-security-config?, port-component*,  ejb-timeout-identity?)>

See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:

org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
...
Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
	... 41 more


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 00:27:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Sat, 27 Oct 2007 00:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBXB-114) Reusing a model group
In-Reply-To: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21015085.1193459221432.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-114?page=all ]

Scott M Stark updated JBXB-114:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099525

> Reusing a model group
> ---------------------
>
>                 Key: JBXB-114
>                 URL: http://jira.jboss.com/jira/browse/JBXB-114
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>            Reporter: Scott M Stark
>             Fix For: JBossXB-2.0.0.CR5
>
>
> We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:
> <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
>  exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
>  security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
>  resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
>  cluster-config?, method-attributes?, depends*,
>  ior-security-config?, port-component*,  ejb-timeout-identity?)>
> See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:
> org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
> 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
> ...
> Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
> 	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
> 	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
> 	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
> 	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
> 	... 41 more

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 02:55:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Sat, 27 Oct 2007 02:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27667189.1193468101518.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

Brian Stansberry updated JBAS-4837:
-----------------------------------

    Attachment: updated-27-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section2+-+Clustered_Session_EJBs.odt

My edits attached.

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt, updated-27-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section2+-+Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 02:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Sat, 27 Oct 2007 02:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27306519.1193468221659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

Brian Stansberry reassigned JBAS-4837:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt, updated-27-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section2+-+Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 04:46:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 04:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5681558.1193474761717.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=comments#action_12384702 ] 
            
Tim Fox commented on JBMESSAGING-1115:
--------------------------------------

Can you explain what you were doing when you saw this, then I can replicate?

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 04:56:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Sat, 27 Oct 2007 04:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18932921.1193475361488.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4913?page=all ]

Scott M Stark resolved JBAS-4913.
---------------------------------

    Resolution: Done

The jboss extensions are resolved with metadata snapshot update rev 1693.


> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 06:59:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 06:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1125) Allow
 replication to be turned off for transacted sessions
Message-ID: <32410117.1193482741436.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow replication to be turned off for transacted sessions
----------------------------------------------------------

                 Key: JBMESSAGING-1125
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1125
             Project: JBoss Messaging
          Issue Type: Feature Request
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 2.0.0 Beta


We should allow the ability to turn off session replication for transacted sessions.

Replicating transacted sessions is only needed to cope with the possibility that another session grabs unacked messages from the queue before the original session.

If the user never has more than one session on the queue at any one time this becomes unnecessary.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:12:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8889768.1193483521666.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384711 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

ClusteredClientCrashTest also fails because of this

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:12:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22141827.1193483521893.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: AS 5.0 Integration)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:49:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19145867.1193485741832.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox reopened JBMESSAGING-1119:
----------------------------------

             

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:49:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21725489.1193485742173.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox updated JBMESSAGING-1119:
---------------------------------

    Priority: Minor  (was: Major)

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:49:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23832701.1193485742408.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox closed JBMESSAGING-1119.
--------------------------------

    Resolution: Done

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:51:19 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:51:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19497536.1193485879967.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox reopened JBMESSAGING-1096:
----------------------------------

             

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:51:20 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:51:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32474023.1193485880108.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox updated JBMESSAGING-1096:
---------------------------------

    Priority: Minor  (was: Major)

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:51:20 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:51:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19034578.1193485880297.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox closed JBMESSAGING-1096.
--------------------------------

    Resolution: Done

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 08:07:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 08:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1122)
 *MessageCountersAsHTML LastAdd uses wrong value
In-Reply-To: <15674199.1193325306988.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2109328.1193486821683.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1122?page=all ]

Tim Fox updated JBMESSAGING-1122:
---------------------------------

    Fix Version/s: Unscheduled
         Priority: Minor  (was: Major)

> *MessageCountersAsHTML LastAdd uses wrong value
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1122
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>            Reporter: Aslak
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>         Attachments: JBMESSAGING-1122.patch
>
>
> ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:09:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5248440.1193490541707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                   EAP 4.3 Integration

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:09:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20864318.1193490541970.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384712 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

I have commented out ClusteredClientCrashTest until this task is fixed

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:09:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:09:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15332602.1193490542228.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Priority: Blocker  (was: Critical)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:11:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1126)
 ClusterViewUpdateTest::testGarbageCollectionOnClusteredCF fails on Hudson
Message-ID: <7233444.1193490661446.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClusterViewUpdateTest::testGarbageCollectionOnClusteredCF fails on Hudson
-------------------------------------------------------------------------

                 Key: JBMESSAGING-1126
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1126
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Tim Fox
         Assigned To: Clebert Suconic
             Fix For: AS 5.0 Integration, EAP 4.3 Integration


This test fails on Hudson.

The test makes assumptions about when Garbage collection is going to occur so IMHO is not a valid test.

We cannot ever be sure GC is going to occur - this is up the JVM implementation to decide.

The test has been commented out until this is resolved.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 10:21:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Sat, 27 Oct 2007 10:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11250703.1193494861502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Ronald van Kuijk updated JBPM-1076:
-----------------------------------


workaround exists: apply the patches attached to to this issue

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 12:46:01 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Sat, 27 Oct 2007 12:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1765) Adapt the admin
 portlet to let the user set a default window state
In-Reply-To: <32743739.1192742134373.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8263031.1193503561799.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1765?page=all ]

Wesley Hales resolved JBPORTAL-1765.
------------------------------------

    Resolution: Done

> Adapt the admin portlet to let the user set a default window state
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1765
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1765
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Thomas Heute
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> We'll need to be able to define which window (if any) of a page should be maximized when a window opens, we'll also need to define if a window must first be displayed as minimized.
> The back end is not done 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

        


From jira-events at lists.jboss.org  Sat Oct 27 14:55:02 2007
From: jira-events at lists.jboss.org (Fang Tianying (JIRA))
Date: Sat, 27 Oct 2007 14:55:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1082) Exception
 wrapping and delivering
Message-ID: <8075056.1193511302237.JavaMail.jira@cloud.prod.atl2.jboss.com>

Exception wrapping and delivering
---------------------------------

                 Key: EJBTHREE-1082
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1082
             Project: EJB 3.0
          Issue Type: Bug
          Components: EJB3 Extensions
    Affects Versions: AS 4.2.1.GA
         Environment: SUN jdk1.5  ,  windows XP ,  JBoss4.2.1GA
            Reporter: Fang Tianying


hi, 

This problem is easy to recur.
When SLSB A(transaction att:requried) calls SLSB B(transaction att: not supported ) though B's local interface, and B throws a RuntimeException, then A will recieve just this very RuntimeException rather than an EJBException. 
I mean the EJB Container should wrap the rt. ex thrown by SLSB B to an EJBException, and then deliver the EJBException to it's caller - SLSB A. 

If it is a bug, I'm appriciated to any responses.  fangtianying at yahoo.cn

best regards,
FangTianying

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:30:15 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:30:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
Message-ID: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve testsuite issues introduced by metadata refactoring
-----------------------------------------------------------

                 Key: EJBTHREE-1083
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:34:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1084) Resolve Failure:
 org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
Message-ID: <8059247.1193517241440.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
-------------------------------------------------------------------------------------

                 Key: EJBTHREE-1084
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1084
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase

JAR does not deploy due to error:

Caused by: org.xml.sax.SAXException: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

@IgnoreDependency is not used in this test, but is defined in jboss.xml

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:43:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1085) Resolve Failure:
Message-ID: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: 
-----------------

                 Key: EJBTHREE-1085
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger


Error on JAR deployment:


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:43:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1085) Resolve Failure:
 org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
In-Reply-To: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23492057.1193517781668.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1085?page=all ]

Andrew Rubinger updated EJBTHREE-1085:
--------------------------------------

          Summary: Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase  (was: Resolve Failure: )
    Fix Version/s: HEAD
      Description: 
Error on JAR deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

  was:
Error on JAR deployment:


         Assignee: Andrew Rubinger

> Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1085
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Error on JAR deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:45:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1085) Resolve Failure:
 org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
In-Reply-To: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24231875.1193517901662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1085?page=all ]

Andrew Rubinger updated EJBTHREE-1085:
--------------------------------------

    Description: 
shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase

Error on JAR deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

  was:
Error on JAR deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[


> Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1085
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> Error on JAR deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:47:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1086) Resolve Failure:
 org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
Message-ID: <12693205.1193518021659.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
-----------------------------------------------------------------------

                 Key: EJBTHREE-1086
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1086
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase

Error on JAR Deployment:

Caused by: java.lang.RuntimeException: org.jboss.xb.binding.JBossXBException: Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:47:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32721822.1193518021817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=all ]

Andrew Rubinger updated EJBTHREE-1083:
--------------------------------------

    Priority: Critical  (was: Major)

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:50:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1087) Resolve Failure:
 org.jboss.ejb3.test.container.unit.ContainerTestCase
Message-ID: <27563923.1193518201480.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.container.unit.ContainerTestCase
---------------------------------------------------------------------

                 Key: EJBTHREE-1087
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1087
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.container.unit.ContainerTestCase

Error on JAR Deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:52:21 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:52:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21281168.1193518341873.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=comments#action_12384728 ] 
            
Andrew Rubinger commented on EJBTHREE-1083:
-------------------------------------------

Many issues failing due to the same underlying error:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

This is discussed in the linked JBoss Forum Reference.

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:54:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13336615.1193518441956.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=all ]

Andrew Rubinger updated EJBTHREE-1083:
--------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119764

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:56:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1088) Resolve Failure:
 org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
Message-ID: <27878026.1193518561424.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
----------------------------------------------------------------

                 Key: EJBTHREE-1088
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1088
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell>  ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase

Error on Deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 17:01:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 17:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1089) Resolve Failure:
 org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
Message-ID: <3816689.1193518861438.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
---------------------------------------------------------------------------

                 Key: EJBTHREE-1089
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1089
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase

Error on JAR Deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:44:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1303) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <7852123.1193582641743.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1303
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1303
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
         Environment: MacBook running Leopard, Eclipse Europa, Java 1.5 (Mac OSX), Drools 4.0.3
            Reporter: John Dunning


The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:48:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1304) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <15904136.1193582881635.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1304
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1304
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: John Dunning




-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:54:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1305) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <13001809.1193583241581.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1305
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1305
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
            Reporter: John Dunning


The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:58:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1306
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
            Reporter: John Dunning


The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 11:03:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 11:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21084981.1193583781644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1306?page=all ]

John Dunning updated JBRULES-1306:
----------------------------------

    Attachment: Archive.zip

3 Separate Eclipse Projects 

Lib - contains common library code
RuleRunner - invokes the drools engine
SpeedTest - how to invoke the tests and re-create the bug.

Run

et.tplusplus.test.drools.speedtest.SpeedTest1

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1306
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>         Attachments: Archive.zip
>
>
> The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.
> The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.
> The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).
> The rules are described below:
> package net.tplusplus.drools.speedtest.rules.test1;
> import net.tplusplus.drools.speedtest.facts.*;
> import net.tplusplus.drools.speedtest.bank.*;
> rule "Test 01 - Credit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Credit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Debit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Debit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Print Balance"
> 	salience 90
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		UpdatingAccount( $accountNo : accountNo, $account : account)
> 		not AccountingPeriod( start < $start)
> 	then
> 		//System.out.print("Period End: "+$end);
> 		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
> end
> rule "Test 01 - Retract Period"
> 	salience 80
> 	when
> 		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
> 		not AccountingPeriod( start < $start)
> 	then
> 		retract($accountingPeriod);
> end
> rule "Test 01 - Retract Remaining AccountingPeriods"
> 	salience 1
> 	when
> 		$fact : AccountingPeriod( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining Cashflows"
> 	salience 1
> 	when
> 		$fact : Cashflow( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining UpdatingAccounts"
> 	salience 1
> 	when
> 		$fact : UpdatingAccount( )
> 	then
> 		retract($fact);
> end
> The code is as follows:
> package net.tplusplus.drools.speedtest.bank;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> /**
>  * This class provides a simple Bank Account.
>  * 
>  * @author DunningJ
>  *
>  */
> public class Account
> {
> 	private long accountNo;
> 	private double balance=0;
> 	
> 	public Account(){};
> 	
> 	public Account(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public double getBalance()
> 	{
> 		return balance;
> 	}
> 	public void setBalance(double balance)
> 	{
> 		this.balance = balance;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Account objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Account account = (Account) obj;
> 		
> 		return (getAccountNo()==account.getAccountNo());
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Account[" 
> 				+"accountNo="+accountNo
> 				+",balance="+balance
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.rules.runner.rao.Fact;
> /**
>  * Each bank transaction must fall within an AccountingPeriod - which
>  * is normally a quarter.  A separate AccountingPeriod fact is passed to the
>  * Drools engine for each accounting period for which we are processing 
>  * calculations.
>  * 
>  * @author DunningJ
>  *
>  */
> public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
> {
> 	private Date start;
> 	private long startl;
> 	private Long startL;
> 	private Date end;
> 	private long endl;
> 	private Long endL;
> 	
> 	public AccountingPeriod(){}
> 	
> 	public AccountingPeriod(Date start, Date end)
> 	{
> 		this.start = start;
> 		this.startl = start.getTime();
> 		this.startL = start.getTime();
> 		this.end = end;
> 		this.endl = end.getTime();
> 		this.endL = end.getTime();
> 	}
> 	public Date getStart()
> 	{
> 		return start;
> 	}
> 	
> 	public long getStartl()
> 	{
> 		return startl;
> 	}
> 	
> 	public long getStartL()
> 	{
> 		return startL;
> 	}
> 	public void setStart(Date start)
> 	{
> 		this.start = start;
> 	}
> 	public Date getEnd()
> 	{
> 		return end;
> 	}
> 	public long getEndl()
> 	{
> 		return endl;
> 	}
> 	
> 	public Long getEndL()
> 	{
> 		return endL;
> 	}
> 	public void setEnd(Date end)
> 	{
> 		this.end = end;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  AccountingPeriod by period start date.
> 	 */
> 	public int compareTo(AccountingPeriod accountingPeriod)
> 	{
> 		if(this.start.after(accountingPeriod.getStart()))
> 		{
> 			return 1;
> 		}
> 		if(this.start.before(accountingPeriod.getStart()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}	
> 	
> 	/**
> 	 *  This method enables the comparison of AccountingPeriod objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof AccountingPeriod))
> 		{
> 			return false;
> 		}
> 		
> 		AccountingPeriod ap = (AccountingPeriod) obj;
> 		
> 		return getStart().equals(ap.getStart());
> 	}
> 	public String toString()
> 	{
> 		return "AccountingPeriod[" 
> 				+"start="+start
> 				+",end="+end
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class Cashflow implements Fact, Comparable<Cashflow>
> {	
> 	public static final int CREDIT = 0;
> 	public static final int DEBIT = 1;
> 	
> 	private Date date;
> 	private long datel;
> 	private Long dateL;
> 	private double amount;
> 	private int type;
> 	private Account account;
> 	
> 	public Cashflow()
> 	{
> 	}
> 	
> 	public Cashflow(Date date, double amount, int type, Account account)
> 	{
> 		this();
> 		
> 		this.date = date;
> 		this.datel= date.getTime();
> 		this.dateL = date.getTime();
> 		this.amount = amount;
> 		this.type = type;
> 		this.account = account;
> 	}
> 	public Date getDate()
> 	{
> 		return date;
> 	}
> 	
> 	public void setDate(Date date)
> 	{
> 		this.date = date;
> 	}
> 	
> 	public double getAmount()
> 	{
> 		return amount;
> 	}
> 	
> 	public void setAmount(double amount)
> 	{
> 		this.amount = amount;
> 	}
> 	
> 	public int getType()
> 	{
> 		return type;
> 	}
> 	public void setType(int type)
> 	{
> 		this.type = type;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	public long getDatel()
> 	{
> 		return datel;
> 	}
> 	
> 	public long getDateL()
> 	{
> 		return dateL;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  Cashflow by cashflow date.
> 	 */	
> 	public int compareTo(Cashflow cashflow)
> 	{
> 		if(getDate().after(cashflow.getDate()))
> 		{
> 			return 1;
> 		}
> 		if(getDate().before(cashflow.getDate()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Cashflow objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Cashflow cashflow = (Cashflow) obj;
> 		
> 		if(!getAccount().equals(cashflow.getAccount())) return false;
> 		if(getAmount()!=cashflow.getAmount()) return false;
> 		if(!getDate().equals(cashflow.getDate())) return false;
> 		if(getType()!=cashflow.getType()) return false;
> 		
> 		return true;
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Cashflow["
> 				//+"account="+account
> 				+"date="+date
> 				+",amount="+amount
> 				+",type="+(type==CREDIT?"Credit":"Debit")
> 				+"]";
> 	}
> 	
> 	
> }
> package net.tplusplus.drools.speedtest.facts;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
> {
> 	private long accountNo;
> 	private Account account;
> 	
> 	public UpdatingAccount(long accountNo, Account account)
> 	{
> 		this.accountNo = accountNo;
> 		this.account = account;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  UpdatingAccount by account no.
> 	 */	
> 	public int compareTo(UpdatingAccount updatingAccount)
> 	{
> 		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
> 		
> 		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of UpdatingAccount objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof UpdatingAccount))
> 		{
> 			return false;
> 		}
> 		
> 		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
> 		
> 		return (getAccountNo()==updatingAccount.getAccountNo());	
> 	}		
> }
> package net.tplusplus.test.drools.speedtest.data;
> import java.util.ArrayList;
> import java.util.Date;
> import java.util.List;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.utils.SimpleDate;
> public class TestData
> {
> 	private static Date startDate;
> 	private static Date endDate;
> 	
> 	private static List<Account> accounts;
> 	private static List<UpdatingAccount> updatingAccounts;
> 	private static List<Cashflow> cashflows;
> 	private static List<AccountingPeriod> accountingPeriods;
> 	
> 	static
> 	{
> 		try
> 		{
> 			startDate = new SimpleDate("01/01/2007");
> 			endDate = new SimpleDate("31/12/2007");
> 		}
> 		catch(Exception e){}
> 	}
> 	
> 	private static List<Account> getAllAccounts()
> 	{
> 		if(accounts==null)
> 		{
> 			accounts = new ArrayList<Account>();
> 		
> 			accounts.add(new Account(1));
> 		}
> 		
> 		return accounts;
> 	}
> 	
> 	public static List<UpdatingAccount> getAllUpdatingAccounts()
> 	{
> 		if(updatingAccounts==null)
> 		{
> 			updatingAccounts = new ArrayList<UpdatingAccount>();
> 			
> 			for(Account account : getAllAccounts())
> 			{
> 				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
> 			}
> 		}
> 		
> 		return updatingAccounts;
> 	}
> 	
> 	public static List<Cashflow> getAllCashflows()
> 	throws Exception
> 	{
> 		if(cashflows==null)
> 		{
> 			cashflows = new ArrayList<Cashflow>();		
> 				
> 			for(Date date = startDate; !date.after(endDate);)
> 			{
> 				int adj = 0;
> 				
> 				for(Account acct : getAllAccounts())
> 				{
> 					adj++;
> 					
> 					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
> 					int[] debits = new int[]{ 200, 50, 50, 30};
> 					
> 					for(int credit : credits)
> 					{
> 						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
> 						cashflows.add(c);
> 					}
> 					
> 					for(int debit : debits)
> 					{
> 						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
> 						cashflows.add(c);
> 					}	
> 				}
> 				
> 				long newDate = date.getTime() + 24l*60l*60l*1000l;
> 				date = new Date(newDate);
> 			}
> 		}
> 		
> 		return cashflows;
> 	}
> 	
> 	public static List<AccountingPeriod> getAccountingPeriods()
> 	throws Exception
> 	{
> 		if(accountingPeriods==null)
> 		{
> 			accountingPeriods = new ArrayList<AccountingPeriod>();
> 			
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
> 		}
> 		
> 		return accountingPeriods;
> 	}
> 	
> 	public static List<Fact> getAllFacts()
> 	throws Exception
> 	{
> 		List<Fact> facts = new ArrayList<Fact>();
> 		
> 		facts.addAll(getAccountingPeriods());
> 		facts.addAll(getAllCashflows());
> 		facts.addAll(getAllUpdatingAccounts());
> 		
> 		return facts;		
> 	}
> 	
> 	public static void resetAccounts()
> 	{
> 		for(Account account : getAllAccounts())
> 		{
> 			account.setBalance(0);
> 		}
> 	}
> }
> package net.tplusplus.test.drools.speedtest;
> import java.util.List;
> import org.drools.RuleBase;
> import org.drools.WorkingMemory;
> import net.tplusplus.rules.runner.RuleRunner;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.test.drools.speedtest.data.TestData;
> import net.tplusplus.utils.TimedResults;
> public class SpeedTest1
> {
> 	public static void main(String[] args)
> 	throws Exception
> 	{
> 		int iterations = 1000;
> 		
> 		//runTest1(iterations);
> 		runTest2(iterations);
> 		runTest3(iterations);
> 		runTest4(iterations);
> 		runTest5(iterations);
> 		runTest6(iterations);
> 	}
> 	
> 	public static void runTest1(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 1 - NO CACHING");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			runner.createRuleBase();
> 			runner.createWorkingMemory();
> 			runner.runRules();
> 			
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest2(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		RuleBase cachedRuleBase = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			System.out.println(i);
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedRuleBase==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setRuleBase(cachedRuleBase);
> 				runner.createWorkingMemory();
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest3(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest4(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest5(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest6(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> }
> package net.tplusplus.rules.runner;
> import java.io.File;
> import java.io.FileReader;
> import java.net.URL;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.List;
> import java.util.Iterator;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.rules.runner.rao.Global;
> import org.drools.FactHandle;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.spi.ActivationGroup;
> import org.drools.spi.AgendaGroup;
> public class RuleRunner
> {
> 	private RuleBase ruleBase;
> 	private WorkingMemory workingMemory;
> 	
> 	private List<String> rules;
> 	private List<Global> globals;
> 	private List<Fact> facts;
> 	
> 	public RuleRunner()
> 	{
> 		rules = new ArrayList<String>();
> 		globals = new ArrayList<Global>();
> 		facts = new ArrayList<Fact>();	
> 	}
> 	
> 	public void addRules(String... rules)
> 	{
> 		this.rules.addAll(Arrays.asList(rules));
> 	}
> 	
> 	public void addGlobals(Global... globals)
> 	{
> 		this.globals.addAll(Arrays.asList(globals));
> 	}
> 	
> 	public void addFacts(Fact... facts)
> 	{
> 		this.facts.addAll(Arrays.asList(facts));
> 	}
> 	
> 	public void addFacts(List<? extends Fact> facts)
> 	{
> 		this.facts.addAll(facts);
> 	}	
> 	
> 	public List<Fact> getFacts()
> 	{
> 		return this.facts;
> 	}
> 	
> 	public void clearFacts()
> 	{
> 		this.facts = new ArrayList<Fact>();
> 	}
> 	
> 	public RuleBase createRuleBase()
> 	throws Exception
> 	{
> 		if(rules==null)
> 		{
> 			throw new Exception("No rules provided for Engine");
> 		}
> 		
> 		ruleBase = RuleBaseFactory.newRuleBase();
> 		PackageBuilder builder = new PackageBuilder();		
> 		
> 		for(String ruleFile : rules)
> 		{
> 			URL resource = this.getClass().getResource(ruleFile);
> 			
> 			if(resource==null)
> 			{
> 				System.err.println("Could not find resource: "+ruleFile);
> 				continue;
> 			}
> 			File file = new File(this.getClass().getResource(ruleFile).getPath());
> 			if(!file.exists())
> 			{
> 				System.err.println("Could not find rule file: "+file.getPath());
> 				continue;
> 			}
> 			
> 			builder.addPackageFromDrl(new FileReader(file.getPath()));
> 		}
> 		
> 		org.drools.rule.Package pkg = builder.getPackage();		
> 		ruleBase.addPackage(pkg);	
> 		
> 		return ruleBase;
> 	}
> 	
> 	public void setRuleBase(RuleBase ruleBase)
> 	{
> 		this.ruleBase = ruleBase;
> 	}
> 	
> 	public RuleBase getRuleBase()
> 	{
> 		return ruleBase;
> 	}
> 	
> 	public WorkingMemory createWorkingMemory()
> 	throws Exception
> 	{
> 		if(ruleBase==null)
> 		{
> 			createRuleBase();
> 		}
> 		
> 		workingMemory = null;
> 		
> 		workingMemory = ruleBase.newStatefulSession();
> 		
> 		return workingMemory;
> 	}
> 	
> 	public void setWorkingMemory(WorkingMemory workingMemory)
> 	{
> 		this.workingMemory = workingMemory;
> 	}
> 	
> 	public WorkingMemory getWorkingMemory()
> 	{
> 		return workingMemory;
> 	}
> 	
> 	public void runRules()
> 	throws Exception
> 	{		
> 		if(workingMemory==null)
> 		{
> 			throw new Exception("No workingMemory created for Engine");
> 		}
> 		
> 		System.gc();
> 		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
> 		
> 		
> 		if(globals!=null)
> 		{
> 			for(Global global : globals)
> 			{
> 				workingMemory.setGlobal(global.getName(), global.getValue());
> 			}
> 		}
> 		if(facts!=null)
> 		{
> 			for(Fact fact : facts)
> 			{
> 				workingMemory.insert(fact);
> 			}
> 		}
> 		workingMemory.fireAllRules();
> 	}
> }
> package net.tplusplus.rules.runner.rao;
> public interface Fact
> {
> }
> package net.tplusplus.rules.runner.rao;
> public class Global
> {
> 	private String name;
> 	private Object value;
> 	
> 	public Global(String name, Object value)
> 	{
> 		this.name = name;
> 		this.value = value;
> 	}
> 	public String getName()
> 	{
> 		return name;
> 	}
> 	public void setName(String name)
> 	{
> 		this.name = name;
> 	}
> 	public Object getValue()
> 	{
> 		return value;
> 	}
> 	public void setValue(Object value)
> 	{
> 		this.value = value;
> 	}
> 	
> 	public String toString()
> 	{
> 		return "Global["
> 				+"name="+name
> 				+"value="+value
> 				+"]";
> 	}
> }
> package net.tplusplus.utils;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> public class SimpleDate extends Date
> {
> 	public static final long serialVersionUID = 1;
> 	
> 	public SimpleDate(String datestr)
> 	throws Exception
> 	{
> 		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
> 		this.setTime(format.parse(datestr).getTime());
> 	}
> }
> package net.tplusplus.utils;
> import java.util.HashMap;
> import java.util.Map;
> public class TimedResults
> {
> 	private long fastest = -1;
> 	private long slowest = -1;
> 	
> 	private Map<Long,Long> results = new HashMap<Long,Long>();
> 	
> 	public TimedResults()
> 	{
> 	}
> 	
> 	public void addTime(long time)
> 	throws Exception
> 	{
> 		if(time < 0)
> 		{
> 			throw new Exception("Invalid Time");
> 		}
> 		
> 		Long key = System.currentTimeMillis();
> 		results.put(key,time);
> 		
> 		if(fastest==-1 || fastest>time) fastest=time;
> 		if(slowest==-1 || slowest<time) slowest=time;
> 	}
> 	
> 	public Map<Long,Long> getResults()
> 	{
> 		return results;
> 	}
> 	
> 	public long getFastest()
> 	{
> 		return fastest;
> 	}
> 	
> 	public long getSlowest()
> 	{
> 		return slowest;
> 	}
> 	
> 	public long getAverage()
> 	{
> 		long time = 0;
> 		
> 		for(Long timetaken : results.values())
> 		{
> 			time += timetaken;
> 		}
> 		
> 		return time / results.size();
> 	}
> }

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 11:07:50 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 11:07:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <940479.1193584070550.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1306?page=all ]

John Dunning updated JBRULES-1306:
----------------------------------

    Description: 
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.


The rules and code are listed below and attached as eclipse projects.

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



  was:
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}




> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1306
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>         Attachments: Archive.zip
>
>
> The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.
> The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.
> The rules and code are listed below and attached as eclipse projects.
> package net.tplusplus.drools.speedtest.rules.test1;
> import net.tplusplus.drools.speedtest.facts.*;
> import net.tplusplus.drools.speedtest.bank.*;
> rule "Test 01 - Credit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Credit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Debit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Debit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Print Balance"
> 	salience 90
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		UpdatingAccount( $accountNo : accountNo, $account : account)
> 		not AccountingPeriod( start < $start)
> 	then
> 		//System.out.print("Period End: "+$end);
> 		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
> end
> rule "Test 01 - Retract Period"
> 	salience 80
> 	when
> 		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
> 		not AccountingPeriod( start < $start)
> 	then
> 		retract($accountingPeriod);
> end
> rule "Test 01 - Retract Remaining AccountingPeriods"
> 	salience 1
> 	when
> 		$fact : AccountingPeriod( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining Cashflows"
> 	salience 1
> 	when
> 		$fact : Cashflow( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining UpdatingAccounts"
> 	salience 1
> 	when
> 		$fact : UpdatingAccount( )
> 	then
> 		retract($fact);
> end
> The code is as follows:
> package net.tplusplus.drools.speedtest.bank;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> /**
>  * This class provides a simple Bank Account.
>  * 
>  * @author DunningJ
>  *
>  */
> public class Account
> {
> 	private long accountNo;
> 	private double balance=0;
> 	
> 	public Account(){};
> 	
> 	public Account(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public double getBalance()
> 	{
> 		return balance;
> 	}
> 	public void setBalance(double balance)
> 	{
> 		this.balance = balance;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Account objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Account account = (Account) obj;
> 		
> 		return (getAccountNo()==account.getAccountNo());
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Account[" 
> 				+"accountNo="+accountNo
> 				+",balance="+balance
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.rules.runner.rao.Fact;
> /**
>  * Each bank transaction must fall within an AccountingPeriod - which
>  * is normally a quarter.  A separate AccountingPeriod fact is passed to the
>  * Drools engine for each accounting period for which we are processing 
>  * calculations.
>  * 
>  * @author DunningJ
>  *
>  */
> public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
> {
> 	private Date start;
> 	private long startl;
> 	private Long startL;
> 	private Date end;
> 	private long endl;
> 	private Long endL;
> 	
> 	public AccountingPeriod(){}
> 	
> 	public AccountingPeriod(Date start, Date end)
> 	{
> 		this.start = start;
> 		this.startl = start.getTime();
> 		this.startL = start.getTime();
> 		this.end = end;
> 		this.endl = end.getTime();
> 		this.endL = end.getTime();
> 	}
> 	public Date getStart()
> 	{
> 		return start;
> 	}
> 	
> 	public long getStartl()
> 	{
> 		return startl;
> 	}
> 	
> 	public long getStartL()
> 	{
> 		return startL;
> 	}
> 	public void setStart(Date start)
> 	{
> 		this.start = start;
> 	}
> 	public Date getEnd()
> 	{
> 		return end;
> 	}
> 	public long getEndl()
> 	{
> 		return endl;
> 	}
> 	
> 	public Long getEndL()
> 	{
> 		return endL;
> 	}
> 	public void setEnd(Date end)
> 	{
> 		this.end = end;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  AccountingPeriod by period start date.
> 	 */
> 	public int compareTo(AccountingPeriod accountingPeriod)
> 	{
> 		if(this.start.after(accountingPeriod.getStart()))
> 		{
> 			return 1;
> 		}
> 		if(this.start.before(accountingPeriod.getStart()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}	
> 	
> 	/**
> 	 *  This method enables the comparison of AccountingPeriod objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof AccountingPeriod))
> 		{
> 			return false;
> 		}
> 		
> 		AccountingPeriod ap = (AccountingPeriod) obj;
> 		
> 		return getStart().equals(ap.getStart());
> 	}
> 	public String toString()
> 	{
> 		return "AccountingPeriod[" 
> 				+"start="+start
> 				+",end="+end
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class Cashflow implements Fact, Comparable<Cashflow>
> {	
> 	public static final int CREDIT = 0;
> 	public static final int DEBIT = 1;
> 	
> 	private Date date;
> 	private long datel;
> 	private Long dateL;
> 	private double amount;
> 	private int type;
> 	private Account account;
> 	
> 	public Cashflow()
> 	{
> 	}
> 	
> 	public Cashflow(Date date, double amount, int type, Account account)
> 	{
> 		this();
> 		
> 		this.date = date;
> 		this.datel= date.getTime();
> 		this.dateL = date.getTime();
> 		this.amount = amount;
> 		this.type = type;
> 		this.account = account;
> 	}
> 	public Date getDate()
> 	{
> 		return date;
> 	}
> 	
> 	public void setDate(Date date)
> 	{
> 		this.date = date;
> 	}
> 	
> 	public double getAmount()
> 	{
> 		return amount;
> 	}
> 	
> 	public void setAmount(double amount)
> 	{
> 		this.amount = amount;
> 	}
> 	
> 	public int getType()
> 	{
> 		return type;
> 	}
> 	public void setType(int type)
> 	{
> 		this.type = type;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	public long getDatel()
> 	{
> 		return datel;
> 	}
> 	
> 	public long getDateL()
> 	{
> 		return dateL;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  Cashflow by cashflow date.
> 	 */	
> 	public int compareTo(Cashflow cashflow)
> 	{
> 		if(getDate().after(cashflow.getDate()))
> 		{
> 			return 1;
> 		}
> 		if(getDate().before(cashflow.getDate()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Cashflow objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Cashflow cashflow = (Cashflow) obj;
> 		
> 		if(!getAccount().equals(cashflow.getAccount())) return false;
> 		if(getAmount()!=cashflow.getAmount()) return false;
> 		if(!getDate().equals(cashflow.getDate())) return false;
> 		if(getType()!=cashflow.getType()) return false;
> 		
> 		return true;
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Cashflow["
> 				//+"account="+account
> 				+"date="+date
> 				+",amount="+amount
> 				+",type="+(type==CREDIT?"Credit":"Debit")
> 				+"]";
> 	}
> 	
> 	
> }
> package net.tplusplus.drools.speedtest.facts;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
> {
> 	private long accountNo;
> 	private Account account;
> 	
> 	public UpdatingAccount(long accountNo, Account account)
> 	{
> 		this.accountNo = accountNo;
> 		this.account = account;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  UpdatingAccount by account no.
> 	 */	
> 	public int compareTo(UpdatingAccount updatingAccount)
> 	{
> 		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
> 		
> 		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of UpdatingAccount objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof UpdatingAccount))
> 		{
> 			return false;
> 		}
> 		
> 		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
> 		
> 		return (getAccountNo()==updatingAccount.getAccountNo());	
> 	}		
> }
> package net.tplusplus.test.drools.speedtest.data;
> import java.util.ArrayList;
> import java.util.Date;
> import java.util.List;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.utils.SimpleDate;
> public class TestData
> {
> 	private static Date startDate;
> 	private static Date endDate;
> 	
> 	private static List<Account> accounts;
> 	private static List<UpdatingAccount> updatingAccounts;
> 	private static List<Cashflow> cashflows;
> 	private static List<AccountingPeriod> accountingPeriods;
> 	
> 	static
> 	{
> 		try
> 		{
> 			startDate = new SimpleDate("01/01/2007");
> 			endDate = new SimpleDate("31/12/2007");
> 		}
> 		catch(Exception e){}
> 	}
> 	
> 	private static List<Account> getAllAccounts()
> 	{
> 		if(accounts==null)
> 		{
> 			accounts = new ArrayList<Account>();
> 		
> 			accounts.add(new Account(1));
> 		}
> 		
> 		return accounts;
> 	}
> 	
> 	public static List<UpdatingAccount> getAllUpdatingAccounts()
> 	{
> 		if(updatingAccounts==null)
> 		{
> 			updatingAccounts = new ArrayList<UpdatingAccount>();
> 			
> 			for(Account account : getAllAccounts())
> 			{
> 				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
> 			}
> 		}
> 		
> 		return updatingAccounts;
> 	}
> 	
> 	public static List<Cashflow> getAllCashflows()
> 	throws Exception
> 	{
> 		if(cashflows==null)
> 		{
> 			cashflows = new ArrayList<Cashflow>();		
> 				
> 			for(Date date = startDate; !date.after(endDate);)
> 			{
> 				int adj = 0;
> 				
> 				for(Account acct : getAllAccounts())
> 				{
> 					adj++;
> 					
> 					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
> 					int[] debits = new int[]{ 200, 50, 50, 30};
> 					
> 					for(int credit : credits)
> 					{
> 						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
> 						cashflows.add(c);
> 					}
> 					
> 					for(int debit : debits)
> 					{
> 						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
> 						cashflows.add(c);
> 					}	
> 				}
> 				
> 				long newDate = date.getTime() + 24l*60l*60l*1000l;
> 				date = new Date(newDate);
> 			}
> 		}
> 		
> 		return cashflows;
> 	}
> 	
> 	public static List<AccountingPeriod> getAccountingPeriods()
> 	throws Exception
> 	{
> 		if(accountingPeriods==null)
> 		{
> 			accountingPeriods = new ArrayList<AccountingPeriod>();
> 			
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
> 		}
> 		
> 		return accountingPeriods;
> 	}
> 	
> 	public static List<Fact> getAllFacts()
> 	throws Exception
> 	{
> 		List<Fact> facts = new ArrayList<Fact>();
> 		
> 		facts.addAll(getAccountingPeriods());
> 		facts.addAll(getAllCashflows());
> 		facts.addAll(getAllUpdatingAccounts());
> 		
> 		return facts;		
> 	}
> 	
> 	public static void resetAccounts()
> 	{
> 		for(Account account : getAllAccounts())
> 		{
> 			account.setBalance(0);
> 		}
> 	}
> }
> package net.tplusplus.test.drools.speedtest;
> import java.util.List;
> import org.drools.RuleBase;
> import org.drools.WorkingMemory;
> import net.tplusplus.rules.runner.RuleRunner;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.test.drools.speedtest.data.TestData;
> import net.tplusplus.utils.TimedResults;
> public class SpeedTest1
> {
> 	public static void main(String[] args)
> 	throws Exception
> 	{
> 		int iterations = 1000;
> 		
> 		//runTest1(iterations);
> 		runTest2(iterations);
> 		runTest3(iterations);
> 		runTest4(iterations);
> 		runTest5(iterations);
> 		runTest6(iterations);
> 	}
> 	
> 	public static void runTest1(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 1 - NO CACHING");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			runner.createRuleBase();
> 			runner.createWorkingMemory();
> 			runner.runRules();
> 			
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest2(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		RuleBase cachedRuleBase = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			System.out.println(i);
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedRuleBase==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setRuleBase(cachedRuleBase);
> 				runner.createWorkingMemory();
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest3(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest4(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest5(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest6(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> }
> package net.tplusplus.rules.runner;
> import java.io.File;
> import java.io.FileReader;
> import java.net.URL;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.List;
> import java.util.Iterator;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.rules.runner.rao.Global;
> import org.drools.FactHandle;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.spi.ActivationGroup;
> import org.drools.spi.AgendaGroup;
> public class RuleRunner
> {
> 	private RuleBase ruleBase;
> 	private WorkingMemory workingMemory;
> 	
> 	private List<String> rules;
> 	private List<Global> globals;
> 	private List<Fact> facts;
> 	
> 	public RuleRunner()
> 	{
> 		rules = new ArrayList<String>();
> 		globals = new ArrayList<Global>();
> 		facts = new ArrayList<Fact>();	
> 	}
> 	
> 	public void addRules(String... rules)
> 	{
> 		this.rules.addAll(Arrays.asList(rules));
> 	}
> 	
> 	public void addGlobals(Global... globals)
> 	{
> 		this.globals.addAll(Arrays.asList(globals));
> 	}
> 	
> 	public void addFacts(Fact... facts)
> 	{
> 		this.facts.addAll(Arrays.asList(facts));
> 	}
> 	
> 	public void addFacts(List<? extends Fact> facts)
> 	{
> 		this.facts.addAll(facts);
> 	}	
> 	
> 	public List<Fact> getFacts()
> 	{
> 		return this.facts;
> 	}
> 	
> 	public void clearFacts()
> 	{
> 		this.facts = new ArrayList<Fact>();
> 	}
> 	
> 	public RuleBase createRuleBase()
> 	throws Exception
> 	{
> 		if(rules==null)
> 		{
> 			throw new Exception("No rules provided for Engine");
> 		}
> 		
> 		ruleBase = RuleBaseFactory.newRuleBase();
> 		PackageBuilder builder = new PackageBuilder();		
> 		
> 		for(String ruleFile : rules)
> 		{
> 			URL resource = this.getClass().getResource(ruleFile);
> 			
> 			if(resource==null)
> 			{
> 				System.err.println("Could not find resource: "+ruleFile);
> 				continue;
> 			}
> 			File file = new File(this.getClass().getResource(ruleFile).getPath());
> 			if(!file.exists())
> 			{
> 				System.err.println("Could not find rule file: "+file.getPath());
> 				continue;
> 			}
> 			
> 			builder.addPackageFromDrl(new FileReader(file.getPath()));
> 		}
> 		
> 		org.drools.rule.Package pkg = builder.getPackage();		
> 		ruleBase.addPackage(pkg);	
> 		
> 		return ruleBase;
> 	}
> 	
> 	public void setRuleBase(RuleBase ruleBase)
> 	{
> 		this.ruleBase = ruleBase;
> 	}
> 	
> 	public RuleBase getRuleBase()
> 	{
> 		return ruleBase;
> 	}
> 	
> 	public WorkingMemory createWorkingMemory()
> 	throws Exception
> 	{
> 		if(ruleBase==null)
> 		{
> 			createRuleBase();
> 		}
> 		
> 		workingMemory = null;
> 		
> 		workingMemory = ruleBase.newStatefulSession();
> 		
> 		return workingMemory;
> 	}
> 	
> 	public void setWorkingMemory(WorkingMemory workingMemory)
> 	{
> 		this.workingMemory = workingMemory;
> 	}
> 	
> 	public WorkingMemory getWorkingMemory()
> 	{
> 		return workingMemory;
> 	}
> 	
> 	public void runRules()
> 	throws Exception
> 	{		
> 		if(workingMemory==null)
> 		{
> 			throw new Exception("No workingMemory created for Engine");
> 		}
> 		
> 		System.gc();
> 		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
> 		
> 		
> 		if(globals!=null)
> 		{
> 			for(Global global : globals)
> 			{
> 				workingMemory.setGlobal(global.getName(), global.getValue());
> 			}
> 		}
> 		if(facts!=null)
> 		{
> 			for(Fact fact : facts)
> 			{
> 				workingMemory.insert(fact);
> 			}
> 		}
> 		workingMemory.fireAllRules();
> 	}
> }
> package net.tplusplus.rules.runner.rao;
> public interface Fact
> {
> }
> package net.tplusplus.rules.runner.rao;
> public class Global
> {
> 	private String name;
> 	private Object value;
> 	
> 	public Global(String name, Object value)
> 	{
> 		this.name = name;
> 		this.value = value;
> 	}
> 	public String getName()
> 	{
> 		return name;
> 	}
> 	public void setName(String name)
> 	{
> 		this.name = name;
> 	}
> 	public Object getValue()
> 	{
> 		return value;
> 	}
> 	public void setValue(Object value)
> 	{
> 		this.value = value;
> 	}
> 	
> 	public String toString()
> 	{
> 		return "Global["
> 				+"name="+name
> 				+"value="+value
> 				+"]";
> 	}
> }
> package net.tplusplus.utils;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> public class SimpleDate extends Date
> {
> 	public static final long serialVersionUID = 1;
> 	
> 	public SimpleDate(String datestr)
> 	throws Exception
> 	{
> 		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
> 		this.setTime(format.parse(datestr).getTime());
> 	}
> }
> package net.tplusplus.utils;
> import java.util.HashMap;
> import java.util.Map;
> public class TimedResults
> {
> 	private long fastest = -1;
> 	private long slowest = -1;
> 	
> 	private Map<Long,Long> results = new HashMap<Long,Long>();
> 	
> 	public TimedResults()
> 	{
> 	}
> 	
> 	public void addTime(long time)
> 	throws Exception
> 	{
> 		if(time < 0)
> 		{
> 			throw new Exception("Invalid Time");
> 		}
> 		
> 		Long key = System.currentTimeMillis();
> 		results.put(key,time);
> 		
> 		if(fastest==-1 || fastest>time) fastest=time;
> 		if(slowest==-1 || slowest<time) slowest=time;
> 	}
> 	
> 	public Map<Long,Long> getResults()
> 	{
> 		return results;
> 	}
> 	
> 	public long getFastest()
> 	{
> 		return fastest;
> 	}
> 	
> 	public long getSlowest()
> 	{
> 		return slowest;
> 	}
> 	
> 	public long getAverage()
> 	{
> 		long time = 0;
> 		
> 		for(Long timetaken : results.values())
> 		{
> 			time += timetaken;
> 		}
> 		
> 		return time / results.size();
> 	}
> }

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 11:15:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 11:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1305) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <13001809.1193583241581.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23654956.1193584501635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1305?page=all ]

John Dunning updated JBRULES-1305:
----------------------------------

    Description: 
THIS BUG IS RAISED IN 

Key: JBRULES-1306
URL: http://jira.jboss.com/jira/browse/JBRULES-1306

browser problems when submitting :(

  was:
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}




> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1305
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1305
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306
> browser problems when submitting :(

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 14:50:02 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 14:50:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6933239.1193597402181.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Andrew Lee Rubinger updated EJBTHREE-1057:
------------------------------------------

    Fix Version/s: HEAD

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 16:09:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 16:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21192254.1193602141704.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1075.
-------------------------------------------

    Resolution: Done

Verified OK in Automated QA

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 16:11:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 16:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1071) Business
 Interface must not extend EJBObject or EJBLocalObject
In-Reply-To: <18467162.1192494129846.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3821063.1193602261677.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1071?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1071.
-------------------------------------------

    Resolution: Done

Satisfied as a result of resolving linked issue EJBTHREE-1075

> Business Interface must not extend EJBObject or EJBLocalObject
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-1071
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1071
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> EJB3 Spec 4.6.6 Bullet 1:
> "The following are the requirements for the session bean's business interface:
>      * The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface."
> ...thus the following construct:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean 
> ...should fail with a deployment exception referencing the specification.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 16:47:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 16:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24766630.1193604421601.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=comments#action_12384739 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1057:
-----------------------------------------------

Fix for Branch_4_2 introduces regression into:

org.jboss.ejb3.test.mdb.unit.ConcurrentMDBUnitTestCase.testQueue
org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 17:03:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 17:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11038069.1193605381607.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=comments#action_12384742 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1057:
-----------------------------------------------

Both:

org.jboss.ejb3.test.mdb.unit.ConcurrentMDBUnitTestCase.testQueue
org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA

...use temporal-based waiting to ensure that the tests pass.  On manual single runs, verified OK; these tests should not be affected by code changes to resolve this issue.


> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 17:05:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 17:05:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4145280.1193605501512.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1057.
-------------------------------------------

    Resolution: Done

Completed

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 04:23:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 04:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11776518.1193646181440.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=comments#action_12384762 ] 
            
Carlo de Wolf commented on EJBTHREE-1083:
-----------------------------------------

Rename the workspace in all tests to the new one.

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 05:40:02 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 05:40:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1082) Exception
 wrapping and delivering
In-Reply-To: <8075056.1193511302237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31747697.1193650802395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1082?page=all ]

Carlo de Wolf updated EJBTHREE-1082:
------------------------------------

    Component/s:     (was: EJB3 Extensions)
        Affects:   (was: [Interactive Demo/Tutorial, Compatibility/Configuration])
       Assignee: Andrew Lee Rubinger
     Complexity:   (was: Low)

> Exception wrapping and delivering
> ---------------------------------
>
>                 Key: EJBTHREE-1082
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1082
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>         Environment: SUN jdk1.5  ,  windows XP ,  JBoss4.2.1GA
>            Reporter: Fang Tianying
>         Assigned To: Andrew Lee Rubinger
>
> hi, 
> This problem is easy to recur.
> When SLSB A(transaction att:requried) calls SLSB B(transaction att: not supported ) though B's local interface, and B throws a RuntimeException, then A will recieve just this very RuntimeException rather than an EJBException. 
> I mean the EJB Container should wrap the rt. ex thrown by SLSB B to an EJBException, and then deliver the EJBException to it's caller - SLSB A. 
> If it is a bug, I'm appriciated to any responses.  fangtianying at yahoo.cn
> best regards,
> FangTianying

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 06:19:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Mon, 29 Oct 2007 06:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1304) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <15904136.1193582881635.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32390495.1193653141757.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1304?page=all ]

John Dunning updated JBRULES-1304:
----------------------------------

    Description: 
THIS BUG IS RAISED IN 

Key: JBRULES-1306 
URL: http://jira.jboss.com/jira/browse/JBRULES-1306 

browser problems when submitting :( 


> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1304
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1304
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 06:21:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Mon, 29 Oct 2007 06:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1303) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <7852123.1193582641743.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19180210.1193653261794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1303?page=all ]

John Dunning updated JBRULES-1303:
----------------------------------

    Description: 
THIS BUG IS RAISED IN 

Key: JBRULES-1306 
URL: http://jira.jboss.com/jira/browse/JBRULES-1306 

browser problems when submitting :( 


  was:
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}




> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1303
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1303
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook running Leopard, Eclipse Europa, Java 1.5 (Mac OSX), Drools 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:02:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9926094.1193655721557.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis updated JBAS-4845:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt)

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:02:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8744550.1193655721752.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis reassigned JBAS-4845:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:13:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 29 Oct 2007 07:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4829) TECH REVIEW:
 Getting Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22833540.1193656381593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Stelios Koussouris resolved JBAS-4829.
--------------------------------------

    Resolution: Done

Completed

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:20:01 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Mon, 29 Oct 2007 07:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-107) The different types
 of classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <20442553.1193656801550.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan updated JBAOP-107:
-----------------------------

    Priority: Major  (was: Minor)

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:33:14 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 29 Oct 2007 07:33:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBXB-114) Reusing a model
	group
In-Reply-To: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22124747.1193657594080.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBXB-114?page=comments#action_12384780 ] 
            
Alexey Loubyansky commented on JBXB-114:
----------------------------------------

There seems to be a missing if statement

   @XmlElement(type=JBossEnvironmentRefsGroupMetaData.class)
   public void setJndiEnvironmentRefsGroup(Environment env)
   {
      if (env == null)
         throw new IllegalArgumentException("Null jndiEnvironmentRefsGroup");   // line 265


> Reusing a model group
> ---------------------
>
>                 Key: JBXB-114
>                 URL: http://jira.jboss.com/jira/browse/JBXB-114
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>            Reporter: Scott M Stark
>             Fix For: JBossXB-2.0.0.CR5
>
>
> We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:
> <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
>  exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
>  security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
>  resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
>  cluster-config?, method-attributes?, depends*,
>  ior-security-config?, port-component*,  ejb-timeout-identity?)>
> See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:
> org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
> 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
> ...
> Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
> 	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
> 	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
> 	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
> 	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
> 	... 41 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:33:14 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:33:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4915) service-ref merge
	looses data
Message-ID: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>

service-ref merge looses data
-----------------------------

                 Key: JBAS-4915
                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:36:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26989598.1193657761434.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4915?page=all ]

Thomas Diesler updated JBAS-4915:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
In the following scenario only jboss-client.xml contains <service-ref> elements

<application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
  
  <display-name>TestEndpointService</display-name>
  
</application-client>

<jboss-client>
  <jndi-name>jbossws-client</jndi-name>
  
  <!-- 
  @WebServiceRef(name = "Service1")
  -->
  <service-ref>
    <service-ref-name>Service1</service-ref-name>
    <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
    <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Service2")
  -->
  <service-ref>
    <service-ref-name>Service2</service-ref-name>
    <config-name>Custom Client</config-name>
    <config-file>META-INF/jbossws-client-config.xml</config-file>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Service3")
  -->
  <service-ref>
    <service-ref-name>Service3</service-ref-name>
    <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
    <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Service4")
  -->
  <service-ref>
    <service-ref-name>Service4</service-ref-name>
    <port-component-ref>
      <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
      <config-name>Custom Client</config-name>
      <config-file>META-INF/jbossws-client-config.xml</config-file>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Port1", type = TestEndpoint.class)
  -->
  <service-ref>
    <service-ref-name>Port1</service-ref-name>
    <port-component-ref>
      <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
      <config-name>Custom Client</config-name>
      <config-file>META-INF/jbossws-client-config.xml</config-file>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Port2")
  -->
  <service-ref>
    <service-ref-name>Port2</service-ref-name>
    <port-component-ref>
      <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
      <config-name>Custom Client</config-name>
      <config-file>META-INF/jbossws-client-config.xml</config-file>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Port3")
  -->
  <service-ref>
    <service-ref-name>Port3</service-ref-name>
    <port-component-ref>
      <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
      <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
      <stub-property>
        <prop-name>javax.xml.ws.security.auth.username</prop-name>
        <prop-value>kermit</prop-value>
      </stub-property>
      <stub-property>
        <prop-name>javax.xml.ws.security.auth.password</prop-name>
        <prop-value>thefrog</prop-value>
      </stub-property>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
</jboss-client>

These are lost by

   public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
         ServiceReferencesMetaData overriden,
         String overridenFile, String overrideFile)
   {
      if (override == null && overriden == null)
         return null;

      JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
      JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
      return merged;
   }

because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22507513.1193658001420.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4915?page=comments#action_12384782 ] 
            
Thomas Diesler commented on JBAS-4915:
--------------------------------------

[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase one-test

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
    [junit] javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.ws.WSException: Cannot create service]
    [junit]     at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1337)
    [junit]     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:765)
    [junit]     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
    [junit]     at org.jboss.ejb3.JndiUtil.lookup(JndiUtil.java:44)
    [junit]     at org.jboss.injection.JndiFieldInjector.lookup(JndiFieldInjector.java:82)
    [junit]     at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:101)
    [junit]     at org.jboss.ejb3.client.ClientContainer.<init>(ClientContainer.java:120)
    [junit]     at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:76)
    [junit]     at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:179)
    [junit]     at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at junit.framework.TestCase.runTest(TestCase.java:154)
    [junit]     at junit.framework.TestCase.runBare(TestCase.java:127)
    [junit]     at junit.framework.TestResult$1.protect(TestResult.java:106)
    [junit]     at junit.framework.TestResult.runProtected(TestResult.java:124)
    [junit]     at junit.framework.TestResult.run(TestResult.java:109)
    [junit]     at junit.framework.TestCase.run(TestCase.java:118)
    [junit]     at junit.framework.TestSuite.runTest(TestSuite.java:208)
    [junit]     at junit.framework.TestSuite.run(TestSuite.java:203)
    [junit]     at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    [junit]     at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    [junit]     at junit.framework.TestResult.runProtected(TestResult.java:124)
    [junit]     at junit.extensions.TestSetup.run(TestSetup.java:23)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567)
    [junit] Caused by: org.jboss.ws.WSException: Cannot create service
    [junit]     at org.jboss.ws.WSException.rethrow(WSException.java:60)
    [junit]     at org.jboss.ws.core.jaxws.client.ServiceObjectFactoryJAXWS.getObjectInstance(ServiceObjectFactoryJAXWS.java:201)
    [junit]     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    [junit]     at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1312)
    [junit]     at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1329)
    [junit]     ... 28 more
    [junit] Caused by: java.lang.IllegalArgumentException: Cannot create generic javax.xml.ws.Service without wsdlLocation: org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointClientOne/port4
    [junit]     at org.jboss.ws.core.jaxws.client.ServiceObjectFactoryJAXWS.getObjectInstance(ServiceObjectFactoryJAXWS.java:139)
    [junit]     ... 31 more
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 1,399.484 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED


> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:42:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <330287.1193658123007.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4915?page=all ]

Thomas Diesler reassigned JBAS-4915:
------------------------------------

    Assignee: Scott M Stark

> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:49:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 07:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7651061.1193658541418.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=all ]

Carlo de Wolf reopened EJBTHREE-1075:
-------------------------------------

             
Code does not work with assertions enabled.

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:57:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 29 Oct 2007 07:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBXB-114) Reusing a model
	group
In-Reply-To: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6779958.1193659021460.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBXB-114?page=comments#action_12384788 ] 
            
Alexey Loubyansky commented on JBXB-114:
----------------------------------------

It's because of this change

 - - - @XmlElement(type=JBossEnvironmentRefsGroupMetaData.class)
-- - - public- void- setJndiEnvironmentRefsGroup(Environment- jndiEnvironmentRefsGroup)
+- - - public- void- setJndiEnvironmentRefsGroup(Environment- env)
- - - {
-- - - - - - if(this.jndiEnvironmentRefsGroup- !=- null)
-- - - - - - - - - throw- new- IllegalArgumentException("jndiEnvironmentRefsGroup- already- set");
-- - - - - - this.jndiEnvironmentRefsGroup- =- (JBossEnvironmentRefsGroupMetaData)- jndiEnvironmentRefsGroup;
+- - - - - - if- (env- ==- null)
+- - - - - - - - - throw- new- IllegalArgumentException("Null- jndiEnvironmentRefsGroup");
+- - - - - - JBossEnvironmentRefsGroupMetaData- jenv- =- (JBossEnvironmentRefsGroupMetaData)- env;
+- - - - - - if(jndiEnvironmentRefsGroup- !=- null)
+- - - - - - - - - jndiEnvironmentRefsGroup.merge(jenv,- null,- null,- "jboss.xml",- "ejb-jar.xml",- false);
+- - - - - - else
+- - - - - - - - - jndiEnvironmentRefsGroup- =- jenv;
- - - } 

> Reusing a model group
> ---------------------
>
>                 Key: JBXB-114
>                 URL: http://jira.jboss.com/jira/browse/JBXB-114
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>            Reporter: Scott M Stark
>             Fix For: JBossXB-2.0.0.CR5
>
>
> We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:
> <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
>  exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
>  security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
>  resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
>  cluster-config?, method-attributes?, depends*,
>  ior-security-config?, port-component*,  ejb-timeout-identity?)>
> See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:
> org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
> 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
> ...
> Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
> 	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
> 	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
> 	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
> 	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
> 	... 41 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 08:22:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 08:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29262820.1193660521874.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Carlo de Wolf updated EJBTHREE-1057:
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                       (was: HEAD)

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:03:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2451904.1193662981687.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis updated JBAS-4845:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt

Attach reviewed file.

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:05:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:05:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30718435.1193663101503.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis resolved JBAS-4845.
--------------------------------------

    Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:11:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
In-Reply-To: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32672979.1193663462117.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4881?page=all ]

Dimitris Andreadis updated JBAS-4881:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4881
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:11:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
In-Reply-To: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26845746.1193663462313.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4881?page=all ]

Dimitris Andreadis resolved JBAS-4881.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done
         Assignee: Dimitris Andreadis

Reviewed with tiny changes.

> TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4881
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:13:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7595114.1193663581468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

Dimitris Andreadis reassigned JBAS-4883:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:15:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 09:15:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
Message-ID: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>

Invalid content was found starting with element 'env-entry'
-----------------------------------------------------------

                 Key: JBAS-4916
                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:15:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 09:15:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9590157.1193663702846.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4916?page=all ]

Thomas Diesler updated JBAS-4916:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test

<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
  version="2.4">

  <servlet>
    <servlet-name>TestService</servlet-name>
    <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
  </servlet>

  <servlet-mapping>
    <servlet-name>TestService</servlet-name>
    <url-pattern>/*</url-pattern>
  </servlet-mapping>

  <env-entry>
   <env-entry-name>jsr109/entry1</env-entry-name>
   <env-entry-type>java.lang.String</env-entry-type>
   <env-entry-value>web</env-entry-value>
  </env-entry>
  
  <env-entry>
   <env-entry-name>jsr109/entry2</env-entry-name>
   <env-entry-type>java.lang.Integer</env-entry-type>
   <env-entry-value>8</env-entry-value>
  </env-entry>

</web-app>

Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
        at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

         Assignee: Alexey Loubyansky

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:17:02 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 09:17:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-761)
 SessionContext.getCallerPrincipal() throws NullPointerException in embedded
 container
In-Reply-To: <10842764.1161790961554.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1472943.1193663822577.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-761?page=all ]

Carlo de Wolf reassigned EJBTHREE-761:
--------------------------------------

    Assignee: Carlo de Wolf

> SessionContext.getCallerPrincipal() throws NullPointerException in embedded container
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-761
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-761
>             Project: EJB 3.0
>          Issue Type: Patch
>          Components: Security
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: John Gilbert
>         Assigned To: Carlo de Wolf
>
> The exception happens in org.jboss.security.plugins.JaasSecurityManager.getPrincipal(Principal principal) when it is synchronized on domainCache. domainCache is null because org.jboss.ejb3.embedded.JaasSecurityManagerService does not initialize it.
> There are two possible fixes:
> 1 - org.jboss.security.plugins.JaasSecurityManager should check for null first like it does in most of the methods.
> 2 - have org.jboss.ejb3.embedded.JaasSecurityManagerService initialize the cache with a mock cache policy. This is what I did to fix mine.
> 	private static JaasSecurityManager getSecurityManager(String name) {
>                        ...
> 			manager = new JaasSecurityManager(name,
> 					new SecurityAssociationHandler());
> 			manager.setCachePolicy(new MockCachePolicy());               //MockCachePolicy is just a noop impl
>                         ...
> 	}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:17:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 09:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-761)
 SessionContext.getCallerPrincipal() throws NullPointerException in embedded
 container
In-Reply-To: <10842764.1161790961554.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4268660.1193663823024.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-761?page=all ]

Carlo de Wolf resolved EJBTHREE-761.
------------------------------------

    Resolution: Duplicate Issue

> SessionContext.getCallerPrincipal() throws NullPointerException in embedded container
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-761
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-761
>             Project: EJB 3.0
>          Issue Type: Patch
>          Components: Security
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: John Gilbert
>         Assigned To: Carlo de Wolf
>
> The exception happens in org.jboss.security.plugins.JaasSecurityManager.getPrincipal(Principal principal) when it is synchronized on domainCache. domainCache is null because org.jboss.ejb3.embedded.JaasSecurityManagerService does not initialize it.
> There are two possible fixes:
> 1 - org.jboss.security.plugins.JaasSecurityManager should check for null first like it does in most of the methods.
> 2 - have org.jboss.ejb3.embedded.JaasSecurityManagerService initialize the cache with a mock cache policy. This is what I did to fix mine.
> 	private static JaasSecurityManager getSecurityManager(String name) {
>                        ...
> 			manager = new JaasSecurityManager(name,
> 					new SecurityAssociationHandler());
> 			manager.setCachePolicy(new MockCachePolicy());               //MockCachePolicy is just a noop impl
>                         ...
> 	}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:22:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16398900.1193664121563.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

Dimitris Andreadis updated JBAS-4883:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:22:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3142064.1193664121713.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

Dimitris Andreadis resolved JBAS-4883.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

Done.

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:33:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4882) TECH REVIEW: Server
 Configuration Guide - Chapter9 - Web Services
In-Reply-To: <11998244.1192791183470.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2785602.1193664781917.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4882?page=all ]

Dimitris Andreadis reassigned JBAS-4882:
----------------------------------------

    Assignee: Thomas Diesler

Thomas, can you or someone from the ws team review this document? It probably needs updating to reflect the switch to jbossws-2.0.x.

> TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services
> -----------------------------------------------------------------
>
>                 Key: JBAS-4882
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4882
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Thomas Diesler
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:41:02 2007
From: jira-events at lists.jboss.org (Brendan Sibre (JIRA))
Date: Mon, 29 Oct 2007 09:41:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1127) Use SSL
 certificate for client authentication
Message-ID: <15518406.1193665262950.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use SSL certificate for client authentication
---------------------------------------------

                 Key: JBMESSAGING-1127
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1127
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: JMS Remoting, JMS Security
    Affects Versions: 1.4.0.GA
         Environment: JBAS 4.2.1 on Solaris 9 and 10, Sun JVM 1.5.0
            Reporter: Brendan Sibre
         Assigned To: Tim Fox


Clients connect to JBM using the sslbisocket connector.  They should be able to use a client certificate to authenticate them via my custom loginmodule (which has been tested and works with EJBs, Tomcat, etc).

Use the principal created by the SSL connection for the getConnection() so that I do not need to pass a username and password.  It seems that the callback handler used by the JBoss Messaging and the remoting SSLBisocket connector needs to be able to handle an X509Callback.  This probably means that
it will need to be a HandshakeCompletedListener on the remoting connector.

Ideally, this method of authentication would be configured with the connector and then JBoss Messaging would use a CallerIdentityLoginModule to
accept the Subject that already exists so that JBoss Messaging will continue to work with EJBs (JmsXA) etc.

Forum posts include links to other potentially related JIRA issues.  Hopefully JBoss Messaging can address this issue as it fits in the junction between
JBM and remoting.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:46:02 2007
From: jira-events at lists.jboss.org (Martin Putz (JIRA))
Date: Mon, 29 Oct 2007 09:46:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1774) CMS metadata is
 lost on export
Message-ID: <33128493.1193665562021.JavaMail.jira@cloud.prod.atl2.jboss.com>

CMS metadata is lost on export
------------------------------

                 Key: JBPORTAL-1774
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1774
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final, 2.4.1 SP1
            Reporter: Martin Putz
         Assigned To: Sohil Shah


CMS metadata, such as title or description, is not being exported. If you do an export/import cycle of CMS data, you will therefore lose information.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:06:01 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 29 Oct 2007 10:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9651084.1193666761840.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1306?page=all ]

Edson Tirelli resolved JBRULES-1306.
------------------------------------

    Fix Version/s: 4.0.3
       Resolution: Rejected
         Assignee: Edson Tirelli

John,

I checked your test case and apparently the only problem is that you are not calling dispose() on the stateful session after using it (http://downloads.jboss.com/drools/docs/4.0.3.15993.GA/html/index.html section 2.5.5). Remember that all stateful sessions must be disposed after use:

public class RuleRunner
{
        ...
	private StatefulSession workingMemory;

       ...
    public void dispose() {
        workingMemory.dispose();
    }
      ...	
}

	public static void runTest2(int iterations)
	throws Exception
	{		
         ...			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
            
            runner.dispose();
            ...
	}
	
After adding the dispose() call, I get stable and consistent results (snippet bellow):

...
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
409
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
410
Heap/Used/Free Memory: 82Mb / 9Mb / 73Mb
411
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
412
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
413
...

Can you double check and reopen the issue in case you find any other problem? thanks.

Edson

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1306
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3
>
>         Attachments: Archive.zip
>
>
> The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.
> The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.
> The rules and code are listed below and attached as eclipse projects.
> package net.tplusplus.drools.speedtest.rules.test1;
> import net.tplusplus.drools.speedtest.facts.*;
> import net.tplusplus.drools.speedtest.bank.*;
> rule "Test 01 - Credit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Credit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Debit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Debit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Print Balance"
> 	salience 90
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		UpdatingAccount( $accountNo : accountNo, $account : account)
> 		not AccountingPeriod( start < $start)
> 	then
> 		//System.out.print("Period End: "+$end);
> 		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
> end
> rule "Test 01 - Retract Period"
> 	salience 80
> 	when
> 		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
> 		not AccountingPeriod( start < $start)
> 	then
> 		retract($accountingPeriod);
> end
> rule "Test 01 - Retract Remaining AccountingPeriods"
> 	salience 1
> 	when
> 		$fact : AccountingPeriod( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining Cashflows"
> 	salience 1
> 	when
> 		$fact : Cashflow( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining UpdatingAccounts"
> 	salience 1
> 	when
> 		$fact : UpdatingAccount( )
> 	then
> 		retract($fact);
> end
> The code is as follows:
> package net.tplusplus.drools.speedtest.bank;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> /**
>  * This class provides a simple Bank Account.
>  * 
>  * @author DunningJ
>  *
>  */
> public class Account
> {
> 	private long accountNo;
> 	private double balance=0;
> 	
> 	public Account(){};
> 	
> 	public Account(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public double getBalance()
> 	{
> 		return balance;
> 	}
> 	public void setBalance(double balance)
> 	{
> 		this.balance = balance;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Account objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Account account = (Account) obj;
> 		
> 		return (getAccountNo()==account.getAccountNo());
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Account[" 
> 				+"accountNo="+accountNo
> 				+",balance="+balance
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.rules.runner.rao.Fact;
> /**
>  * Each bank transaction must fall within an AccountingPeriod - which
>  * is normally a quarter.  A separate AccountingPeriod fact is passed to the
>  * Drools engine for each accounting period for which we are processing 
>  * calculations.
>  * 
>  * @author DunningJ
>  *
>  */
> public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
> {
> 	private Date start;
> 	private long startl;
> 	private Long startL;
> 	private Date end;
> 	private long endl;
> 	private Long endL;
> 	
> 	public AccountingPeriod(){}
> 	
> 	public AccountingPeriod(Date start, Date end)
> 	{
> 		this.start = start;
> 		this.startl = start.getTime();
> 		this.startL = start.getTime();
> 		this.end = end;
> 		this.endl = end.getTime();
> 		this.endL = end.getTime();
> 	}
> 	public Date getStart()
> 	{
> 		return start;
> 	}
> 	
> 	public long getStartl()
> 	{
> 		return startl;
> 	}
> 	
> 	public long getStartL()
> 	{
> 		return startL;
> 	}
> 	public void setStart(Date start)
> 	{
> 		this.start = start;
> 	}
> 	public Date getEnd()
> 	{
> 		return end;
> 	}
> 	public long getEndl()
> 	{
> 		return endl;
> 	}
> 	
> 	public Long getEndL()
> 	{
> 		return endL;
> 	}
> 	public void setEnd(Date end)
> 	{
> 		this.end = end;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  AccountingPeriod by period start date.
> 	 */
> 	public int compareTo(AccountingPeriod accountingPeriod)
> 	{
> 		if(this.start.after(accountingPeriod.getStart()))
> 		{
> 			return 1;
> 		}
> 		if(this.start.before(accountingPeriod.getStart()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}	
> 	
> 	/**
> 	 *  This method enables the comparison of AccountingPeriod objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof AccountingPeriod))
> 		{
> 			return false;
> 		}
> 		
> 		AccountingPeriod ap = (AccountingPeriod) obj;
> 		
> 		return getStart().equals(ap.getStart());
> 	}
> 	public String toString()
> 	{
> 		return "AccountingPeriod[" 
> 				+"start="+start
> 				+",end="+end
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class Cashflow implements Fact, Comparable<Cashflow>
> {	
> 	public static final int CREDIT = 0;
> 	public static final int DEBIT = 1;
> 	
> 	private Date date;
> 	private long datel;
> 	private Long dateL;
> 	private double amount;
> 	private int type;
> 	private Account account;
> 	
> 	public Cashflow()
> 	{
> 	}
> 	
> 	public Cashflow(Date date, double amount, int type, Account account)
> 	{
> 		this();
> 		
> 		this.date = date;
> 		this.datel= date.getTime();
> 		this.dateL = date.getTime();
> 		this.amount = amount;
> 		this.type = type;
> 		this.account = account;
> 	}
> 	public Date getDate()
> 	{
> 		return date;
> 	}
> 	
> 	public void setDate(Date date)
> 	{
> 		this.date = date;
> 	}
> 	
> 	public double getAmount()
> 	{
> 		return amount;
> 	}
> 	
> 	public void setAmount(double amount)
> 	{
> 		this.amount = amount;
> 	}
> 	
> 	public int getType()
> 	{
> 		return type;
> 	}
> 	public void setType(int type)
> 	{
> 		this.type = type;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	public long getDatel()
> 	{
> 		return datel;
> 	}
> 	
> 	public long getDateL()
> 	{
> 		return dateL;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  Cashflow by cashflow date.
> 	 */	
> 	public int compareTo(Cashflow cashflow)
> 	{
> 		if(getDate().after(cashflow.getDate()))
> 		{
> 			return 1;
> 		}
> 		if(getDate().before(cashflow.getDate()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Cashflow objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Cashflow cashflow = (Cashflow) obj;
> 		
> 		if(!getAccount().equals(cashflow.getAccount())) return false;
> 		if(getAmount()!=cashflow.getAmount()) return false;
> 		if(!getDate().equals(cashflow.getDate())) return false;
> 		if(getType()!=cashflow.getType()) return false;
> 		
> 		return true;
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Cashflow["
> 				//+"account="+account
> 				+"date="+date
> 				+",amount="+amount
> 				+",type="+(type==CREDIT?"Credit":"Debit")
> 				+"]";
> 	}
> 	
> 	
> }
> package net.tplusplus.drools.speedtest.facts;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
> {
> 	private long accountNo;
> 	private Account account;
> 	
> 	public UpdatingAccount(long accountNo, Account account)
> 	{
> 		this.accountNo = accountNo;
> 		this.account = account;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  UpdatingAccount by account no.
> 	 */	
> 	public int compareTo(UpdatingAccount updatingAccount)
> 	{
> 		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
> 		
> 		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of UpdatingAccount objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof UpdatingAccount))
> 		{
> 			return false;
> 		}
> 		
> 		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
> 		
> 		return (getAccountNo()==updatingAccount.getAccountNo());	
> 	}		
> }
> package net.tplusplus.test.drools.speedtest.data;
> import java.util.ArrayList;
> import java.util.Date;
> import java.util.List;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.utils.SimpleDate;
> public class TestData
> {
> 	private static Date startDate;
> 	private static Date endDate;
> 	
> 	private static List<Account> accounts;
> 	private static List<UpdatingAccount> updatingAccounts;
> 	private static List<Cashflow> cashflows;
> 	private static List<AccountingPeriod> accountingPeriods;
> 	
> 	static
> 	{
> 		try
> 		{
> 			startDate = new SimpleDate("01/01/2007");
> 			endDate = new SimpleDate("31/12/2007");
> 		}
> 		catch(Exception e){}
> 	}
> 	
> 	private static List<Account> getAllAccounts()
> 	{
> 		if(accounts==null)
> 		{
> 			accounts = new ArrayList<Account>();
> 		
> 			accounts.add(new Account(1));
> 		}
> 		
> 		return accounts;
> 	}
> 	
> 	public static List<UpdatingAccount> getAllUpdatingAccounts()
> 	{
> 		if(updatingAccounts==null)
> 		{
> 			updatingAccounts = new ArrayList<UpdatingAccount>();
> 			
> 			for(Account account : getAllAccounts())
> 			{
> 				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
> 			}
> 		}
> 		
> 		return updatingAccounts;
> 	}
> 	
> 	public static List<Cashflow> getAllCashflows()
> 	throws Exception
> 	{
> 		if(cashflows==null)
> 		{
> 			cashflows = new ArrayList<Cashflow>();		
> 				
> 			for(Date date = startDate; !date.after(endDate);)
> 			{
> 				int adj = 0;
> 				
> 				for(Account acct : getAllAccounts())
> 				{
> 					adj++;
> 					
> 					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
> 					int[] debits = new int[]{ 200, 50, 50, 30};
> 					
> 					for(int credit : credits)
> 					{
> 						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
> 						cashflows.add(c);
> 					}
> 					
> 					for(int debit : debits)
> 					{
> 						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
> 						cashflows.add(c);
> 					}	
> 				}
> 				
> 				long newDate = date.getTime() + 24l*60l*60l*1000l;
> 				date = new Date(newDate);
> 			}
> 		}
> 		
> 		return cashflows;
> 	}
> 	
> 	public static List<AccountingPeriod> getAccountingPeriods()
> 	throws Exception
> 	{
> 		if(accountingPeriods==null)
> 		{
> 			accountingPeriods = new ArrayList<AccountingPeriod>();
> 			
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
> 		}
> 		
> 		return accountingPeriods;
> 	}
> 	
> 	public static List<Fact> getAllFacts()
> 	throws Exception
> 	{
> 		List<Fact> facts = new ArrayList<Fact>();
> 		
> 		facts.addAll(getAccountingPeriods());
> 		facts.addAll(getAllCashflows());
> 		facts.addAll(getAllUpdatingAccounts());
> 		
> 		return facts;		
> 	}
> 	
> 	public static void resetAccounts()
> 	{
> 		for(Account account : getAllAccounts())
> 		{
> 			account.setBalance(0);
> 		}
> 	}
> }
> package net.tplusplus.test.drools.speedtest;
> import java.util.List;
> import org.drools.RuleBase;
> import org.drools.WorkingMemory;
> import net.tplusplus.rules.runner.RuleRunner;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.test.drools.speedtest.data.TestData;
> import net.tplusplus.utils.TimedResults;
> public class SpeedTest1
> {
> 	public static void main(String[] args)
> 	throws Exception
> 	{
> 		int iterations = 1000;
> 		
> 		//runTest1(iterations);
> 		runTest2(iterations);
> 		runTest3(iterations);
> 		runTest4(iterations);
> 		runTest5(iterations);
> 		runTest6(iterations);
> 	}
> 	
> 	public static void runTest1(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 1 - NO CACHING");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			runner.createRuleBase();
> 			runner.createWorkingMemory();
> 			runner.runRules();
> 			
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest2(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		RuleBase cachedRuleBase = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			System.out.println(i);
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedRuleBase==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setRuleBase(cachedRuleBase);
> 				runner.createWorkingMemory();
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest3(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest4(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest5(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest6(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> }
> package net.tplusplus.rules.runner;
> import java.io.File;
> import java.io.FileReader;
> import java.net.URL;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.List;
> import java.util.Iterator;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.rules.runner.rao.Global;
> import org.drools.FactHandle;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.spi.ActivationGroup;
> import org.drools.spi.AgendaGroup;
> public class RuleRunner
> {
> 	private RuleBase ruleBase;
> 	private WorkingMemory workingMemory;
> 	
> 	private List<String> rules;
> 	private List<Global> globals;
> 	private List<Fact> facts;
> 	
> 	public RuleRunner()
> 	{
> 		rules = new ArrayList<String>();
> 		globals = new ArrayList<Global>();
> 		facts = new ArrayList<Fact>();	
> 	}
> 	
> 	public void addRules(String... rules)
> 	{
> 		this.rules.addAll(Arrays.asList(rules));
> 	}
> 	
> 	public void addGlobals(Global... globals)
> 	{
> 		this.globals.addAll(Arrays.asList(globals));
> 	}
> 	
> 	public void addFacts(Fact... facts)
> 	{
> 		this.facts.addAll(Arrays.asList(facts));
> 	}
> 	
> 	public void addFacts(List<? extends Fact> facts)
> 	{
> 		this.facts.addAll(facts);
> 	}	
> 	
> 	public List<Fact> getFacts()
> 	{
> 		return this.facts;
> 	}
> 	
> 	public void clearFacts()
> 	{
> 		this.facts = new ArrayList<Fact>();
> 	}
> 	
> 	public RuleBase createRuleBase()
> 	throws Exception
> 	{
> 		if(rules==null)
> 		{
> 			throw new Exception("No rules provided for Engine");
> 		}
> 		
> 		ruleBase = RuleBaseFactory.newRuleBase();
> 		PackageBuilder builder = new PackageBuilder();		
> 		
> 		for(String ruleFile : rules)
> 		{
> 			URL resource = this.getClass().getResource(ruleFile);
> 			
> 			if(resource==null)
> 			{
> 				System.err.println("Could not find resource: "+ruleFile);
> 				continue;
> 			}
> 			File file = new File(this.getClass().getResource(ruleFile).getPath());
> 			if(!file.exists())
> 			{
> 				System.err.println("Could not find rule file: "+file.getPath());
> 				continue;
> 			}
> 			
> 			builder.addPackageFromDrl(new FileReader(file.getPath()));
> 		}
> 		
> 		org.drools.rule.Package pkg = builder.getPackage();		
> 		ruleBase.addPackage(pkg);	
> 		
> 		return ruleBase;
> 	}
> 	
> 	public void setRuleBase(RuleBase ruleBase)
> 	{
> 		this.ruleBase = ruleBase;
> 	}
> 	
> 	public RuleBase getRuleBase()
> 	{
> 		return ruleBase;
> 	}
> 	
> 	public WorkingMemory createWorkingMemory()
> 	throws Exception
> 	{
> 		if(ruleBase==null)
> 		{
> 			createRuleBase();
> 		}
> 		
> 		workingMemory = null;
> 		
> 		workingMemory = ruleBase.newStatefulSession();
> 		
> 		return workingMemory;
> 	}
> 	
> 	public void setWorkingMemory(WorkingMemory workingMemory)
> 	{
> 		this.workingMemory = workingMemory;
> 	}
> 	
> 	public WorkingMemory getWorkingMemory()
> 	{
> 		return workingMemory;
> 	}
> 	
> 	public void runRules()
> 	throws Exception
> 	{		
> 		if(workingMemory==null)
> 		{
> 			throw new Exception("No workingMemory created for Engine");
> 		}
> 		
> 		System.gc();
> 		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
> 		
> 		
> 		if(globals!=null)
> 		{
> 			for(Global global : globals)
> 			{
> 				workingMemory.setGlobal(global.getName(), global.getValue());
> 			}
> 		}
> 		if(facts!=null)
> 		{
> 			for(Fact fact : facts)
> 			{
> 				workingMemory.insert(fact);
> 			}
> 		}
> 		workingMemory.fireAllRules();
> 	}
> }
> package net.tplusplus.rules.runner.rao;
> public interface Fact
> {
> }
> package net.tplusplus.rules.runner.rao;
> public class Global
> {
> 	private String name;
> 	private Object value;
> 	
> 	public Global(String name, Object value)
> 	{
> 		this.name = name;
> 		this.value = value;
> 	}
> 	public String getName()
> 	{
> 		return name;
> 	}
> 	public void setName(String name)
> 	{
> 		this.name = name;
> 	}
> 	public Object getValue()
> 	{
> 		return value;
> 	}
> 	public void setValue(Object value)
> 	{
> 		this.value = value;
> 	}
> 	
> 	public String toString()
> 	{
> 		return "Global["
> 				+"name="+name
> 				+"value="+value
> 				+"]";
> 	}
> }
> package net.tplusplus.utils;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> public class SimpleDate extends Date
> {
> 	public static final long serialVersionUID = 1;
> 	
> 	public SimpleDate(String datestr)
> 	throws Exception
> 	{
> 		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
> 		this.setTime(format.parse(datestr).getTime());
> 	}
> }
> package net.tplusplus.utils;
> import java.util.HashMap;
> import java.util.Map;
> public class TimedResults
> {
> 	private long fastest = -1;
> 	private long slowest = -1;
> 	
> 	private Map<Long,Long> results = new HashMap<Long,Long>();
> 	
> 	public TimedResults()
> 	{
> 	}
> 	
> 	public void addTime(long time)
> 	throws Exception
> 	{
> 		if(time < 0)
> 		{
> 			throw new Exception("Invalid Time");
> 		}
> 		
> 		Long key = System.currentTimeMillis();
> 		results.put(key,time);
> 		
> 		if(fastest==-1 || fastest>time) fastest=time;
> 		if(slowest==-1 || slowest<time) slowest=time;
> 	}
> 	
> 	public Map<Long,Long> getResults()
> 	{
> 		return results;
> 	}
> 	
> 	public long getFastest()
> 	{
> 		return fastest;
> 	}
> 	
> 	public long getSlowest()
> 	{
> 		return slowest;
> 	}
> 	
> 	public long getAverage()
> 	{
> 		long time = 0;
> 		
> 		for(Long timetaken : results.values())
> 		{
> 			time += timetaken;
> 		}
> 		
> 		return time / results.size();
> 	}
> }

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:14:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 29 Oct 2007 10:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4916) Invalid content
 was found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33133957.1193667241667.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4916?page=comments#action_12384834 ] 
            
Alexey Loubyansky commented on JBAS-4916:
-----------------------------------------

This is thrown by Xerces. It's validation against the XSD. I tried a small validation test but it passed

   public void testMain() throws Exception
   {
      String xml = "<web-app xmlns='http://java.sun.com/xml/ns/j2ee' " +
         "xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' " +
         "xsi:schemaLocation='http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd' " +
         "version='2.4'>" +
         "<servlet>" +
         "  <servlet-name>TestService</servlet-name>" +
         "  <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>" +
         "</servlet>" +
         "<servlet-mapping>" +
         "  <servlet-name>TestService</servlet-name>" +
         "  <url-pattern>/*</url-pattern>" +
         "</servlet-mapping>" +
         "<env-entry>" +
         "  <env-entry-name>jsr109/entry1</env-entry-name>" +
         "  <env-entry-type>java.lang.String</env-entry-type>" +
         "  <env-entry-value>web</env-entry-value>" +
         "</env-entry>" +
         "<env-entry>" +
         "  <env-entry-name>jsr109/entry2</env-entry-name>" +
         "  <env-entry-type>java.lang.Integer</env-entry-type>" +
         "  <env-entry-value>8</env-entry-value>" +
         "</env-entry>" +
         "</web-app>";

      Validator.assertValidXml(xml, new EntityResolver()
      {
         public InputSource resolveEntity(String publicId, String systemId) throws SAXException, IOException
         {            
            String path = "file:///e:/cvsroot/projects/metadata/trunk/src/main/resources/schema/";
            if(systemId != null && systemId.startsWith(path))
            {
               path = systemId;
            }
            else if("http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd".equals(systemId))
            {
               path += "web-app_2_4.xsd";
            }
            else if("http://www.w3.org/2001/xml.xsd".equals(systemId))
            {
               path += "xml.xsd";
            }
            else if("http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd".endsWith(systemId))
            {
               path += "j2ee_web_services_client_1_1.xsd";
            }
            else
            {
               System.out.println("resolveEntity: '" + publicId + "' '" + systemId + "'");
               return null;
            }
            
            return new InputSource(path);
         }}
      );
   }

Could you try to come up with a test like this that fails? I tried creating a test in the metadata project but that would also pass. I can commit it if you want.

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:31:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:31:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
In-Reply-To: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4154067.1193668264587.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4884?page=all ]

Dimitris Andreadis updated JBAS-4884:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
> -------------------------------------------------------------------
>
>                 Key: JBAS-4884
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:31:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:31:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
In-Reply-To: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19150643.1193668265586.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4884?page=all ]

Dimitris Andreadis resolved JBAS-4884.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done
         Assignee: Dimitris Andreadis

Reviewed.

> TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
> -------------------------------------------------------------------
>
>                 Key: JBAS-4884
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:33:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33457023.1193668381561.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis updated JBAS-4851:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt)

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:41:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:41:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4301364.1193668862973.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4916?page=all ]

Thomas Diesler reassigned JBAS-4916:
------------------------------------

    Assignee: Thomas Diesler  (was: Alexey Loubyansky)

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:43:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28077719.1193668981582.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis updated JBAS-4851:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt

Attach reviewed file.

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:43:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30446857.1193668981701.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4916?page=all ]

Thomas Diesler resolved JBAS-4916.
----------------------------------

    Resolution: Done

The application-client.xml was invalid

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:43:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4851) TECH REVIEW: Server
 Configuration Guide - Chapter1 - Enterprise
 Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1454511.1193668981949.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis reassigned JBAS-4851:
----------------------------------------

    Assignee: Carlo de Wolf

Carlo, can you or someone from EJB3 review this document? I made a first pass with some minor changes.

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Carlo de Wolf
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:45:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13013619.1193669101798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis updated JBAS-4851:
-------------------------------------

    Fix Version/s: No Release

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Carlo de Wolf
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:49:02 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-923) Acquired node lock
 never released after transaction timeout
In-Reply-To: <9534770.1167949167059.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33224877.1193669342344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-923?page=all ]

Manik Surtani updated JBCACHE-923:
----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> Acquired node lock never released after transaction timeout
> -----------------------------------------------------------
>
>                 Key: JBCACHE-923
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-923
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP4
>         Environment: Windows XP, Weblogic 9.1
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: AsyncRollbackTxTest.zip
>
>
> Under weblogic 9.1 (and probably earlier version too, not tested) in some situations locks aquired on nodes are never released. Only way to release locks is stop and start again treecache.
> On WebLogic the rollback after a tx timeout is handled in a separate thread (and all registered transaction synchronization handlers are invoked in separated thread! In treecache information about InvocationContext (GlobalTransaction, Transaction etc) is stored in ThreadLocal. In this situation SynchronizationHandler is scrubbing NOT correct invocationContext with information about currend rolled-back transaction, but new created empty invocationContext !!!! Informations from TransactionTable are correctly removed, because mapping of transactions is not stored in ThreadLocal variable.
> This caused unexpected effects:
> Information about GlobalTransaction is not cleared and when in main thread TransactionTimedOutException is catched and put/get operations without explicity created transaction are invoked, TreeCache is trying aquire RL/WL on node and caller is set to non-exist and cleared GlobalTransaction. Lock is aquired but not added to LockTable! (and not released).
> From now every access to locked node failed, because RL/WL can't be aquired in 10 secs. Only way to get system working is stop and start again TreeCache.
> 2007-01-04 10:13:42,092 DEBUG  - calling aftercompletion for GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - Running rollback phase
> 2007-01-04 10:13:42,092 DEBUG  -  running rollback for GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - PessimisticLockInterceptor invoked for method rollback(GlobalTransaction:<192.168.141.1:2100>:1)
> 2007-01-04 10:13:42,092 DEBUG  - called to rollback cache with GlobalTransaction=GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - _remove(GlobalTransaction:<192.168.141.1:2100>:1, "/NODEA/NODEB", systemProperty)
> 2007-01-04 10:13:42,092 DEBUG  - _remove(GlobalTransaction:<192.168.141.1:2100>:1, "/NODEA/NODEB")
> 2007-01-04 10:13:42,092 DEBUG  - removed child NODEB
> 2007-01-04 10:13:42,092 DEBUG  - releasing lock for /NODEA/NODEB (<unlocked>)
> 2007-01-04 10:13:42,092 DEBUG  - releasing lock for /NODEA (read owners=[GlobalTransaction:<192.168.141.1:2100>:1])
> 2007-01-04 10:13:42,092 DEBUG  - removing local transaction Name=FooManager.foo,Xid=BEA1-00068143BD8A02E8BAA1(4771853),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 20 seconds 
> BEA1-00068143BD8A02E8BAA1],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds left=20,activeThread=Thread[Timer-5,5,Pooled Threads],XAServerResourceInfo[dataSource]=(ServerResourceInfo[dataSource]=(state=rolledback,assigned=AdminServer),xar=dataSource,re-Registered = false),SCInfo[sample_domain+AdminServer]=(state=rolledback),properties=({weblogic.transaction.name=FooManager.foo}),local properties=({weblogic.jdbc.jta.dataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+10.1.1.218:9002+sample_domain+admin+, XAResources={dataSource, WLStore_sample_domain__WLS_AdminServer},NonXAResources={})],CoordinatorURL=AdminServer+10.1.1.218:9002+sample_domain+admin+) and global transaction GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - bypassed locking as method rollback() doesn't require locking
> 2007-01-04 10:13:42,092 DEBUG  - Suppressing invocation of method rollback(GlobalTransaction:<192.168.141.1:2100>:1) on cache.
> 2007-01-04 10:13:42,092 DEBUG  - Attempting to release locks on current thread.  Lock table is {}
> 2007-01-04 10:13:42,092 DEBUG  - Finished local commit/rollback method for GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - Finished rollback phase
> (...)
> 2007-01-04 10:14:12,302 DEBUG  - Non-tx and non crud meth
> 2007-01-04 10:14:37,310 DEBUG  - (192.168.141.1:2100) call on method [_get(/NODEC, NODE_VALUE, true)]
> 2007-01-04 10:14:37,310 DEBUG  - PessimisticLockInterceptor invoked for method _get(/NODEC, NODE_VALUE, true)
> 2007-01-04 10:14:37,310 DEBUG  - Attempting to lock node /NODEC for owner GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:14:37,310 DEBUG  - acquiring RL: fqn=/NODEC, caller=GlobalTransaction:<192.168.141.1:2100>:1, lock=<unlocked>
> 2007-01-04 10:14:37,310 DEBUG  - acquired RL: fqn=/NODEC, caller=GlobalTransaction:<192.168.141.1:2100>:1, lock=read owners=[GlobalTransaction:<192.168.141.1:2100>:1]
> 2007-01-04 10:14:37,310 ERROR  - transaction entry not found for (gtx=GlobalTransaction:<192.168.141.1:2100>:1)
> 2007-01-04 10:14:37,310 DEBUG  - Invoking method _get(/NODEC, NODE_VALUE, true) on cache.
> 2007-01-04 10:14:37,310 DEBUG  - _get("/NODEC", NODE_VALUE, "true")
> 2007-01-04 10:14:37,310 DEBUG  - Attempting to release locks on current thread.  Lock table is {} 
> 	

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1164)
 NodeNotExistException with concurrent put/remove operations
In-Reply-To: <18249492.1187299741540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27824345.1193669474712.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1164?page=all ]

Manik Surtani updated JBCACHE-1164:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> NodeNotExistException with concurrent put/remove operations
> -----------------------------------------------------------
>
>                 Key: JBCACHE-1164
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1164
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: Windows XP, Sun jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: ConcurentOperationsTest.java
>
>
> When 2 Threads are putting/removing data from this same node, put operation fails with exception
> org.jboss.cache.NodeNotExistsException: node /a/b/c/d not found (gtx=GlobalTransaction::2, caller=Thread[Thread-0,5,main]) 
> at org.jboss.cache.TreeCache._put(TreeCache.java:4618) 
> at org.jboss.cache.TreeCache._put(TreeCache.java:4579) 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
> at java.lang.reflect.Method.invoke(Unknown Source) 
> at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330) 
> at org.jboss.cache.interceptors.CallInterceptor.invoke(CallInterceptor.java:52) 
> at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) 
> at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:89) 
> at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) 
> at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32) 
> at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) 
> (...) 
> Thread 1 is calling: 
> 	cache.remove("/a/b/c/d");
> 	cache.remove("/a");
>  Thread 2 is calling: 
> 	cache.putObject("/a/b/c/d", "text" + x);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock
 could be not released after async transaction rollback
In-Reply-To: <19139966.1189557851483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20587157.1193669474834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]

Manik Surtani updated JBCACHE-1183:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                   2.1.0.GA
                       (was: 1.4.1.SP6)

> Acquired WL lock could be not released after async transaction rollback
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-1183
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: WindowsXP, jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: AsyncRollbackTxLockTest.java
>
>
> In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1166) UpgradeException
 on concurrent put/remove operation
In-Reply-To: <33448482.1187338441457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19069834.1193669474959.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1166?page=all ]

Manik Surtani updated JBCACHE-1166:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> UpgradeException on concurrent put/remove operation
> ---------------------------------------------------
>
>                 Key: JBCACHE-1166
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1166
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: Windows XP, Sun jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: ConcurentOperationTest.java, ConcurentOperationTestCore.java
>
>
> When 2 Threads simultanous are attaching/detaching object from this same region sometimes TreeCache fails with Exception:
> upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock
> Full StackTrace:
> org.jboss.cache.pojo.PojoCacheException: detach /a/b/c/d failed
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:158)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:136)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:101)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
> 	at org.jboss.cache.aop.ConcurentOperationTest$WorkThread.run(ConcurentOperationTest.java:80)
> Caused by: org.jboss.cache.lock.UpgradeException: failure upgrading lock: fqn=/__JBossInternal__/a/b/c/d/_ID_/a1170-d7nvs9-f5gejrti-1-f5gejrti-2, caller=GlobalTransaction:<10.1.1.252:4508>:19, lock=read owners=[GlobalTransaction:<10.1.1.252:4508>:18, GlobalTransaction:<10.1.1.252:4508>:19] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=1, waitingUpgrader=1)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:508)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:579)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:393)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:329)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:187)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:298)
> 	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
> 	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3939)
> 	at org.jboss.cache.CacheImpl.put(CacheImpl.java:1598)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.removeObject(PojoCacheDelegate.java:273)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.removeObject(PojoCacheImpl.java:170)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:153)
> 	... 5 more
> Caused by: org.jboss.cache.lock.UpgradeException: acquireWriteLock(): lock upgrade failed for /__JBossInternal__/a/b/c/d/_ID_/a1170-d7nvs9-f5gejrti-1-f5gejrti-2 (caller=GlobalTransaction:<10.1.1.252:4508>:19, lock info: read owners=[GlobalTransaction:<10.1.1.252:4508>:18, GlobalTransaction:<10.1.1.252:4508>:19] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=1, waitingUpgrader=1))
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:209)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
> 	... 25 more
> Caused by: org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock
> 	at org.jboss.cache.lock.ReadWriteLockWithUpgrade.upgradeLockAttempt(ReadWriteLockWithUpgrade.java:107)
> 	at org.jboss.cache.lock.LockStrategyRepeatableRead.upgradeLockAttempt(LockStrategyRepeatableRead.java:43)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:203)
> 	... 27 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1168) Sometimes
 acquired locks are not released
In-Reply-To: <30832886.1187878698592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28550792.1193669475429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1168?page=all ]

Manik Surtani updated JBCACHE-1168:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                   2.1.0.GA
                       (was: 1.4.1.SP6)

> Sometimes acquired locks are not released
> -----------------------------------------
>
>                 Key: JBCACHE-1168
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4
>         Environment: Windows XP, jrockit90_150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: jbosscache.log, output.txt, TransactionStormTest.java
>
>
> Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache.
> Main loop:
> 		while (true) {
> 			for (int x = 0; x < 2; x++) {
> 				WorkThread t = new WorkThread(x == 1);
> 				threads.add(t);
> 				t.start();
> 			}
> 			for (WorkThread separateThread : threads) {
> 				separateThread.join();
> 				if (separateThread.getException() != null) {
> 					//separateThread.getException().getMessage();
> 				}
> 			}
> 			int locksNum = getNumberOfLocksHeld();
> //			System.out.println("Locks="+locksNum);
> 			// checkpoint
> 			if (cache.getNumberOfLocksHeld()>0){
> 				System.out.println("ERROR, locks="+locksNum);
> 				doDomethingOnCache(1);
> 			}
> 			assertEquals(0, locksNum);
> 		}
> Exception - after //checkpoint line numberOfLocks is grater than 0!
> JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in
 PessimisticLockInterceptor
In-Reply-To: <14669904.1187336057521.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7700087.1193669475593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]

Manik Surtani updated JBCACHE-1165:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> Endless loop in PessimisticLockInterceptor
> ------------------------------------------
>
>                 Key: JBCACHE-1165
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1165
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: Windows XP, Sun jdk150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
>
>
> When 2 Threads are simulatanous putting/removing values from this same node TreeCache hang's up and goes into endless loop.
> Main loop looks like:
> 				for (int x = 0; x < 1000; x++) {
> 					tm.begin();
> 					System.out.println("R" + Thread.currentThread().getName());
> 					//inside transaction
> 					cache.remove("/a");
> 					System.out.println("AR" + Thread.currentThread().getName());
> 					tm.commit();
> 					//outside transaction
> 					System.out.println("P" + Thread.currentThread().getName());
> 					cache.put("/a/b/c/d", "text"+x,"b");
> 					System.out.println("AP" + Thread.currentThread().getName());
> 				}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock
 could be not released after async transaction rollback
In-Reply-To: <19139966.1189557851483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14383441.1193669475736.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]

Manik Surtani updated JBCACHE-1183:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

> Acquired WL lock could be not released after async transaction rollback
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-1183
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: WindowsXP, jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: AsyncRollbackTxLockTest.java
>
>
> In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1168) Sometimes
 acquired locks are not released
In-Reply-To: <30832886.1187878698592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32847394.1193669475904.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1168?page=all ]

Manik Surtani updated JBCACHE-1168:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

> Sometimes acquired locks are not released
> -----------------------------------------
>
>                 Key: JBCACHE-1168
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4
>         Environment: Windows XP, jrockit90_150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: jbosscache.log, output.txt, TransactionStormTest.java
>
>
> Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache.
> Main loop:
> 		while (true) {
> 			for (int x = 0; x < 2; x++) {
> 				WorkThread t = new WorkThread(x == 1);
> 				threads.add(t);
> 				t.start();
> 			}
> 			for (WorkThread separateThread : threads) {
> 				separateThread.join();
> 				if (separateThread.getException() != null) {
> 					//separateThread.getException().getMessage();
> 				}
> 			}
> 			int locksNum = getNumberOfLocksHeld();
> //			System.out.println("Locks="+locksNum);
> 			// checkpoint
> 			if (cache.getNumberOfLocksHeld()>0){
> 				System.out.println("ERROR, locks="+locksNum);
> 				doDomethingOnCache(1);
> 			}
> 			assertEquals(0, locksNum);
> 		}
> Exception - after //checkpoint line numberOfLocks is grater than 0!
> JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:53:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6083220.1193669581676.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12384851 ] 
            
Thomas Diesler commented on JBAS-4902:
--------------------------------------

Same is true for nested wars

[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws128 test

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxrpc.jbws128.JBWS128TestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.724 sec
    [junit] Test org.jboss.test.ws.jaxrpc.jbws128.JBWS128TestCase FAILED


> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:53:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20767518.1193669581888.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4902?page=all ]

Thomas Diesler updated JBAS-4902:
---------------------------------

    Priority: Critical  (was: Major)

Raising this to 'critical' because most CTS tests deploy eras

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:15:01 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?Fran=EF=BF=A7ois_Karman_=28JIRA=29?=)
Date: Mon, 29 Oct 2007 11:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4917) remote call to
 LoaderRepository.getPackageClassLoaders throws a NotSerializableException
Message-ID: <30267597.1193670901823.JavaMail.jira@cloud.prod.atl2.jboss.com>

remote call to LoaderRepository.getPackageClassLoaders throws a NotSerializableException
----------------------------------------------------------------------------------------

                 Key: JBAS-4917
                 URL: http://jira.jboss.com/jira/browse/JBAS-4917
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JMX
         Environment: I have tested this problems on Windows Platform only.
            Reporter: Fran?ois Karman
         Assigned To: Dimitris Andreadis


A call to the getPackageClassLoaders operation of the MBean : JMImplementation:name=Default,service=LoaderRepository throws an exception.

The simpliest way to view the bug : 
twiddle invoke "JMImplementation:name=Default,service=LoaderRepository" getPackageClassLoaders javax.ejb.EntityBean

Start of the trace :
java.io.NotSerializableException: org.jboss.mx.loading.ClassLoaderUtils$RepositoryClassLoaderComparator
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
	at java.util.TreeSet.writeObject(TreeSet.java:458)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)

The comparator used by the result TreeSet is not serializable and could not be send to the remote client. (twiddle or a J2EE Client application)

http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jmx/src/main/org/jboss/mx/loading/ClassLoaderUtils.java?view=markup


-- 
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

       



From jira-events at lists.jboss.org  Mon Oct 29 11:29:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 29 Oct 2007 11:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-214) Extend the
 demand/supply dependency
Message-ID: <1166215.1193671741496.JavaMail.jira@cloud.prod.atl2.jboss.com>

Extend the demand/supply dependency
-----------------------------------

                 Key: JBMICROCONT-214
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-214
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: Kernel
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta6


Add a way to do a demand 'matching' on supplied items.
See forum thread for more details.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:29:01 2007
From: jira-events at lists.jboss.org (John Scott (JIRA))
Date: Mon, 29 Oct 2007 11:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1307) Update and expand
 documentation for decision tables to show actual uses
 for all keywords
Message-ID: <18860217.1193671741757.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update and expand documentation for decision tables to show actual uses for all keywords
----------------------------------------------------------------------------------------

                 Key: JBRULES-1307
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1307
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
         Environment: Drools 4.0.3, Rational Application Developer 7.0.0, XP SP2,
            Reporter: John Scott
            Priority: Minor


I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL, but reading the documentation for the UNLOOP keyword, this is the only description:

"Indicates that if there cell values in this column, the no-loop attribute should be set"

In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?

Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.

Thanks

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:41:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 29 Oct 2007 11:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-214) Extend the
 demand/supply dependency
In-Reply-To: <1166215.1193671741496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24969461.1193672461600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-214?page=all ]

Ales Justin closed JBMICROCONT-214.
-----------------------------------

    Resolution: Done

> Extend the demand/supply dependency
> -----------------------------------
>
>                 Key: JBMICROCONT-214
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-214
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta6
>
>
> Add a way to do a demand 'matching' on supplied items.
> See forum thread for more details.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:49:01 2007
From: jira-events at lists.jboss.org (John Scott (JIRA))
Date: Mon, 29 Oct 2007 11:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1307) Update and expand
 documentation for decision tables to show actual uses
 for all keywords
In-Reply-To: <18860217.1193671741757.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22053191.1193672941419.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1307?page=all ]

John Scott updated JBRULES-1307:
--------------------------------

    Description: 
I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL and using "no-loop" solved the problem, but reading the documentation for the UNLOOP keyword to turn on no-loop, this is the only description:

"Indicates that if there cell values in this column, the no-loop attribute should be set"

In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?

Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.

Thanks

  was:
I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL, but reading the documentation for the UNLOOP keyword, this is the only description:

"Indicates that if there cell values in this column, the no-loop attribute should be set"

In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?

Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.

Thanks


> Update and expand documentation for decision tables to show actual uses for all keywords
> ----------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1307
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1307
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Drools 4.0.3, Rational Application Developer 7.0.0, XP SP2,
>            Reporter: John Scott
>            Priority: Minor
>
> I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL and using "no-loop" solved the problem, but reading the documentation for the UNLOOP keyword to turn on no-loop, this is the only description:
> "Indicates that if there cell values in this column, the no-loop attribute should be set"
> In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?
> Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.
> Thanks

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:53:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 29 Oct 2007 11:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22563080.1193673181700.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

David Lloyd closed JBCOMMON-39.
-------------------------------

    Resolution: Done

Committed in rev. 2661 of trunk.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBCOMMON-39.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 12:01:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 12:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1205) Data shipped with
 NodeModified events different on different ccache instances in the cluster
In-Reply-To: <24023938.1193238901431.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14396829.1193673661960.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1205?page=all ]

Manik Surtani resolved JBCACHE-1205.
------------------------------------

    Fix Version/s:     (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)
       Resolution: Cannot Reproduce Bug

> Data shipped with NodeModified events different on different ccache instances in the cluster
> --------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1205
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1205
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 12:09:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 29 Oct 2007 12:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-612) ChannelFactory should
 have only channel create methods
Message-ID: <1245470.1193674141792.JavaMail.jira@cloud.prod.atl2.jboss.com>

ChannelFactory should have only channel create methods
------------------------------------------------------

                 Key: JGRP-612
                 URL: http://jira.jboss.com/jira/browse/JGRP-612
             Project: JGroups
          Issue Type: Task
    Affects Versions: 2.5, 2.6, 2.7, 2.x
            Reporter: Vladimir Blagojevic
         Assigned To: Bela Ban
             Fix For: 3.0


ChannelFactory should not have setMultiplexerConfig methods but rather only create channel methods. Multiplexer configuration can be initialized through implementors constructor. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 12:15:01 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Mon, 29 Oct 2007 12:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-704) Externalise the TM
 used in the test suite so the TM can be injected when running tests.
In-Reply-To: <32285530.1153238351263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26001158.1193674501761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-704?page=all ]

Jason T. Greene closed JBCACHE-704.
-----------------------------------

    Fix Version/s: 2.0.0.BETA1
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)
       Resolution: Done

> Externalise the TM used in the test suite so the TM can be injected when running tests.
> ---------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-704
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-704
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.0.0.BETA1
>
>
> Allows for QA to certify JBC on other TMs like JBossTS and JBossTM.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:01:01 2007
From: jira-events at lists.jboss.org (Matthew Sandoz (JIRA))
Date: Mon, 29 Oct 2007 13:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-183) Cut/Copy/Paste of
 transitions and nodes in the process designer
Message-ID: <26128738.1193677261486.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cut/Copy/Paste of transitions and nodes in the process designer
---------------------------------------------------------------

                 Key: GPD-183
                 URL: http://jira.jboss.com/jira/browse/GPD-183
             Project: JBoss jBPM GPD
          Issue Type: Feature Request
          Components: jpdl
            Reporter: Matthew Sandoz
         Assigned To: Koen Aers


It would be very useful to support cut/copy/paste in the process designer. These operations would have the challenge of creating new element names where there were conflicts and determining which transitions to carry along - only connected transitions - that is those whose source and target nodes are also in the selection.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:08:01 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 29 Oct 2007 13:08:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1090) NPE when
 combining AOP and EJB3 interceptors
Message-ID: <21367962.1193677681731.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE when combining AOP and EJB3 interceptors
--------------------------------------------

                 Key: EJBTHREE-1090
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1090
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA
            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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:10:02 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 29 Oct 2007 13:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20018066.1193677802330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

    Description: 
When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.

HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

  was:Need to investigate


> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.
> HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:21:01 2007
From: jira-events at lists.jboss.org (Seth Wilcox (JIRA))
Date: Mon, 29 Oct 2007 13:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3275) Can't chain ldap
 login modules together using useFirstPass=password-stacking
Message-ID: <24519741.1193678461452.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3275?page=all ]

Seth Wilcox updated JBAS-3275:
------------------------------

    Attachment: LDAPAuth.patch

Patch to fix password stacking in LDAPExtLoginModule on version 4.0.5 GA

> Can't chain ldap login modules together using useFirstPass=password-stacking
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-3275
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3275
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>         Attachments: LDAPAuth.patch
>
>
> The way roles are pulled in from the authentication phase validatePassword callback precludes chaining of ldap login modules. If one server does authentication and another authorization this cannot be configured to work currently.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:32:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Mon, 29 Oct 2007 13:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11136557.1193679121478.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12384887 ] 
            
Scott M Stark commented on JBAS-4902:
-------------------------------------

Attach the jaxrpc/jbws128 test  ear or describe how to build it. The java module is an issue with java application client container not being started that being worked on. 

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:44:04 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 29 Oct 2007 13:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-613) Access to
 NAKACK#rebroadcast_digest field needs a lock
Message-ID: <8602308.1193679844347.JavaMail.jira@cloud.prod.atl2.jboss.com>

Access to NAKACK#rebroadcast_digest field needs a lock
------------------------------------------------------

                 Key: JGRP-613
                 URL: http://jira.jboss.com/jira/browse/JGRP-613
             Project: JGroups
          Issue Type: Bug
    Affects Versions: 2.6
            Reporter: Vladimir Blagojevic
         Assigned To: Bela Ban
            Priority: Minor
             Fix For: 2.6


It seems that rebroadcast_digest field of NAKACK  is accessed by multiple threads which step over each other leading to a consequences below.
This is very hard to reproduce and I have seen it only a few times so far.



-------------------------------------------------------
GMS: address is 127.0.0.1:2528
-------------------------------------------------------
11141 [INFO][main] ConcurrentStateTransferTest: - Thread for channel 127.0.0.1:2528[A] started
15250 [INFO][A] ConcurrentStateTransferTest: - channel.getState at A127.0.0.1:2518 returned false
15297 [INFO][Multiplexer,udp,127.0.0.1:2520] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2520)]: received 127.0.0.1:2518
15297 [INFO][Multiplexer,udp,127.0.0.1:2524] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2524)]: received 127.0.0.1:2518
15297 [INFO][Multiplexer,udp,127.0.0.1:2518] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2518)]: received 127.0.0.1:2518
15297 [INFO][Multiplexer,udp,127.0.0.1:2528] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2528)]: received 127.0.0.1:2518
15328 [ERROR][OOB,udp,127.0.0.1:2520] UDP: - failed handling incoming message
java.lang.NullPointerException
	at org.jgroups.protocols.pbcast.NAKACK.rebroadcastMessages(NAKACK.java:1036)
	at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:620)
	at org.jgroups.protocols.UNICAST.down(UNICAST.java:434)
	at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317)
	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:813)
	at org.jgroups.protocols.FC.down(FC.java:370)
	at org.jgroups.protocols.FRAG2.down(FRAG2.java:175)
	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:318)
	at org.jgroups.protocols.pbcast.FLUSH.handleFlushReconcile(FLUSH.java:455)
	at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:337)
	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:258)
	at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
	at org.jgroups.protocols.FC.up(FC.java:408)
	at org.jgroups.protocols.pbcast.GMS.up(GMS.java:742)
	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
	at org.jgroups.protocols.UNICAST.up(UNICAST.java:264)
	at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:798)
	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:662)
	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
	at org.jgroups.protocols.FD.up(FD.java:322)
	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308)
	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1461)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	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

        


From jira-events at lists.jboss.org  Mon Oct 29 14:17:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 14:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8338154.1193681821851.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

Brian Stansberry updated JBAS-4838:
-----------------------------------

    Attachment: updated-29-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section3+-+Clustered_Entity_EJBs.odt

My edits attached.

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt, updated-29-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section3+-+Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 14:17:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 14:17:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1322352.1193681822065.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

Brian Stansberry reassigned JBAS-4838:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt, updated-29-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section3+-+Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 14:19:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 14:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24742704.1193681941900.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry reassigned JBAS-4841:
--------------------------------------

    Assignee: Brian Stansberry  (was: Galder Zamarreno)

Assigning to myself, as Galder is on vacation.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 15:41:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 15:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3075) ClassLoading code
	out of sync.
Message-ID: <29991406.1193686861617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3075?page=all ]

Dimitris Andreadis updated JBAS-3075:
-------------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was:  JBossAS-5.0.0.Beta3)

> ClassLoading code out of sync.
> ------------------------------
>
>                 Key: JBAS-3075
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3075
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>            Reporter: Adrian Brock
>             Fix For: JBossAS-5.0.0.CR1
>
>
> The classloading code is out-of-sync between jboss-4.0.x and jboss-head.
> Looks like all the changes/fixes have not been applied in head.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:01:02 2007
From: jira-events at lists.jboss.org (Adam Lewandowski (JIRA))
Date: Mon, 29 Oct 2007 16:01:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1308) getFactHandle with
 equality-based assert behavior
Message-ID: <3690771.1193688062726.JavaMail.jira@cloud.prod.atl2.jboss.com>

getFactHandle with equality-based assert behavior
-------------------------------------------------

                 Key: JBRULES-1308
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1308
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
            Reporter: Adam Lewandowski


If I set my rule base to use equality-based assert behavior, I'm expecting to be able to use the getFactHandle(object) method to retrieve a previously asserted fact by providing an equivalent (by equals() and hashCode()) object as an argument. This appears to not be the case, as AbstractWorkingMemory uses it's identityMap and associated IdentityAssertMapComparator to do the getFactHandle lookup instead of the assertMap and EqualityAssertMapComparator. This causes the lookup to be done with the system hashCode() method and not the overridden version supplied in my fact class. The lookup thus fails and returns null. 

See attached unit test.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:03:01 2007
From: jira-events at lists.jboss.org (Adam Lewandowski (JIRA))
Date: Mon, 29 Oct 2007 16:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1308) getFactHandle with
 equality-based assert behavior
In-Reply-To: <3690771.1193688062726.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4829321.1193688181452.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1308?page=all ]

Adam Lewandowski updated JBRULES-1308:
--------------------------------------

    Attachment: GetFactHandleWithEqualityTest.java

Unit test demonstrating expected behavior

> getFactHandle with equality-based assert behavior
> -------------------------------------------------
>
>                 Key: JBRULES-1308
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1308
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>            Reporter: Adam Lewandowski
>         Attachments: GetFactHandleWithEqualityTest.java
>
>
> If I set my rule base to use equality-based assert behavior, I'm expecting to be able to use the getFactHandle(object) method to retrieve a previously asserted fact by providing an equivalent (by equals() and hashCode()) object as an argument. This appears to not be the case, as AbstractWorkingMemory uses it's identityMap and associated IdentityAssertMapComparator to do the getFactHandle lookup instead of the assertMap and EqualityAssertMapComparator. This causes the lookup to be done with the system hashCode() method and not the overridden version supplied in my fact class. The lookup thus fails and returns null. 
> See attached unit test.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:27:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8431331.1193689621820.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=comments#action_12384936 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1083:
-----------------------------------------------

EJB Tests Before Fixes:

Tests,Failures,Errors,Success rate
375,16,198,42.93%

After:

Tests,Failures,Errors,Success rate
375,31,98,65.60%

No parsing errors remain in EJB3 testsuite - 

* Start Server
shell> ./run.sh -c all > /tmp/jboss_xml_schema.txt

* Run EJB tests
shell> ./build.sh -f build-test.xml main no-start-jboss-ejb-tests

* Ensure no parse errors:
shell> grep 'but the target namespace of the schema' /tmp/jboss_xml_schema.txt


> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:37:02 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:37:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5174663.1193690222138.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1083.
-------------------------------------------

    Resolution: Done

This issue addresses only parse errors related to new jboss.xml namespace

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:37:03 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1084) Resolve Failure:
 org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
In-Reply-To: <8059247.1193517241440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9565169.1193690223999.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1084?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1084.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1084
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1084
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
> JAR does not deploy due to error:
> Caused by: org.xml.sax.SAXException: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]
> @IgnoreDependency is not used in this test, but is defined in jboss.xml

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:37:04 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:37:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1085) Resolve Failure:
 org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
In-Reply-To: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15409021.1193690224257.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1085?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1085.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1085
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> Error on JAR deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1086) Resolve Failure:
 org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
In-Reply-To: <12693205.1193518021659.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8814352.1193690341821.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1086?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1086.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
> -----------------------------------------------------------------------
>
>                 Key: EJBTHREE-1086
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1086
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
> Error on JAR Deployment:
> Caused by: java.lang.RuntimeException: org.jboss.xb.binding.JBossXBException: Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1087) Resolve Failure:
 org.jboss.ejb3.test.container.unit.ContainerTestCase
In-Reply-To: <27563923.1193518201480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32058624.1193690341966.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1087?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1087.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.container.unit.ContainerTestCase
> ---------------------------------------------------------------------
>
>                 Key: EJBTHREE-1087
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1087
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.container.unit.ContainerTestCase
> Error on JAR Deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:02 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1088) Resolve Failure:
 org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
In-Reply-To: <27878026.1193518561424.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27914710.1193690342119.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1088?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1088.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
> ----------------------------------------------------------------
>
>                 Key: EJBTHREE-1088
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1088
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell>  ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
> Error on Deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:03 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1089) Resolve Failure:
 org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
In-Reply-To: <3816689.1193518861438.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9043514.1193690343101.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1089?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1089.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
> ---------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1089
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1089
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
> Error on JAR Deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:50:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 16:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12670497.1193691001628.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Brian Stansberry updated JBAS-4839:
-----------------------------------

    Attachment: updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part1.odt
                updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part2.odt

My edits attached.  OpenOffice kept crashing, so I tried to minimize this by breaking the document in half. Didn't help, but that's why there are two documents attached.

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part1.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part2.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:50:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 16:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28646052.1193691002043.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Brian Stansberry reassigned JBAS-4839:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part1.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part2.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:54:35 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:54:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1091) Ensure all
 metadata files are included in the Schema test case
Message-ID: <18825902.1193691275979.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure all metadata files are included in the Schema test case
--------------------------------------------------------------

                 Key: EJBTHREE-1091
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1091
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Lee Rubinger
         Assigned To: Andrew Lee Rubinger
             Fix For: HEAD


Be sure that all ejb-jar.xml, jboss.xml files in the EJB3 module are included in the tests of org.jboss.ejb3.test.schema.unit.SchemaTestCase

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 18:43:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 29 Oct 2007 18:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1712) Make producer
 tests go through the WS stack
In-Reply-To: <22960492.1190516351026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1760375.1193697781534.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=comments#action_12384961 ] 
            
Thomas Heute commented on JBPORTAL-1712:
----------------------------------------

Can we set that with a higher priority ? At the moment in the 2.6 testsuite, the 2 tests which are failing are related to this issue.
For that reason, we are getting used to ignore Hudson error reports which is not good.

> Make producer tests go through the WS stack
> -------------------------------------------
>
>                 Key: JBPORTAL-1712
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1712
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal WSRP
>    Affects Versions: 2.8 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>             Fix For: 2.8 Final, 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 18:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 18:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5998500.1193698741616.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry updated JBAS-4841:
-----------------------------------

    Attachment: updated-29.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt

My edits attached.  The items Galder mentioned in his last comment are done.

Note that the file attached to this JIRA did not include the JBoss Cache section.  I looked at it on-line and it looked pretty reasonable.  My only suggestion is that it include a reference or link to the main JBoss Cache 1.4.1.SP5 documentation, which of course is far more complete.  Same things goes for JGroups.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt, updated-29.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 18:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 18:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26863618.1193698741885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry reassigned JBAS-4841:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt, updated-29.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 19:53:01 2007
From: jira-events at lists.jboss.org (Jon Stevens (JIRA))
Date: Mon, 29 Oct 2007 19:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4918) for logging,
 server.xml references another variable than jboss-log4j.xml does
Message-ID: <20868859.1193701981886.JavaMail.jira@cloud.prod.atl2.jboss.com>

for logging, server.xml references another variable than jboss-log4j.xml does
-----------------------------------------------------------------------------

                 Key: JBAS-4918
                 URL: http://jira.jboss.com/jira/browse/JBAS-4918
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: JBossAS-4.2.0.GA
         Environment: all
            Reporter: Jon Stevens
         Assigned To: Scott M Stark


jboss-log4j.xml has this as default:

      <param name="File" value="${jboss.server.log.dir}/server.log"/>

jboss-web.deployer has this:

            <!-- Access logger -->
            <Valve className="org.apache.catalina.valves.AccessLogValve"
                prefix="localhost_access_log." suffix=".log"
                pattern="common" directory="${jboss.server.home.dir}/log" 
                resolveHosts="false" />

Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because

#1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir}
#2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value.

My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything.

jon

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 21:10:02 2007
From: jira-events at lists.jboss.org (John Gilbert (JIRA))
Date: Mon, 29 Oct 2007 21:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-615) NPE in Embedded
 Jboss when getCallerPrincipal method on SessionContext
Message-ID: <11451022.1193706602722.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-615?page=comments#action_12384972 ] 
            
John Gilbert commented on EJBTHREE-615:
---------------------------------------

What does "EJB 3 embedded is no longer supported." mean? 
Is something replacing it?

> NPE in Embedded Jboss when getCallerPrincipal method on SessionContext
> ----------------------------------------------------------------------
>
>                 Key: EJBTHREE-615
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-615
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Nicolai ?dum
>         Assigned To: Carlo de Wolf
>         Attachments: BugReportInterceptor.java
>
>
> The bug is pretty easy to create.
> Modify the CalculaterBean in the security example that is distributed with JBoss embedded like this
> import javax.annotation.Resource;
> import java.security.Principal;
> import javax.ejb.SessionContext;
> ..
> public class CalculatorBean implements Calculator
> {
> @Resource SessionContext ctx;	
> @RolesAllowed({"student"})
> public int subtract(int x, int y)
> {
> Principal caller = ctx.getCallerPrincipal(); //Nullpointer
> return x - y;
> }
> The exception
> full stacktrace: 
> javax.ejb.EJBException: java.lang.NullPointerException 
> at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) 
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) 
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:167) 
> at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:100) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:181) 
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79) 
> at $Proxy15.getSubscriberDetails(Unknown Source) 
> Another user has reported that is is possible to get the principal from org.jboss.security.SecurityAssociation.getPrincipal(), but not from the Session Context.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 21:13:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 29 Oct 2007 21:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1309) Gui refactoring
	and redesign
Message-ID: <2055807.1193706781420.JavaMail.jira@cloud.prod.atl2.jboss.com>

Gui refactoring and redesign 
-----------------------------

                 Key: JBRULES-1309
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1309
             Project: JBoss Drools
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 23:11:21 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Mon, 29 Oct 2007 23:11:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (BPEL-282) Engine runs process
 instances in serie instead of in parallel
In-Reply-To: <7870750.1193112683491.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8980951.1193713881357.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/BPEL-282?page=comments#action_12384976 ] 
            
Alejandro Guizar commented on BPEL-282:
---------------------------------------

Currently, all start message listeners run on a single JMS session. Since JMS delivers messages one at a time per session, this feature may cause the perceived serial execution. I have made slight modifications which allow each start listener to run in a separate JMS session. This should enable parallel execution as far as the JMS connection and, ultimately, the available CPU cycles permit it.

Once I complete the QA procedure I will upload a new version of the jBPM BPEL binaries to the repository and mark the issue as resolved.

> Engine runs process instances in serie instead of in parallel
> -------------------------------------------------------------
>
>                 Key: BPEL-282
>                 URL: http://jira.jboss.com/jira/browse/BPEL-282
>             Project: JBoss jBPM BPEL
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>         Environment: RHEL
>            Reporter: Santiago Erquicia
>         Assigned To: Alejandro Guizar
>
> We are stress testing a BPEL process and we found out that the engine runs all the requests it receives in serie. That means that if there are two or more concurrent users of the system, one has to wait till the first process instance stops at some point (wait state) so the other request can be processed.
> On our test environment, we are calling a web service which is also calling another web service. The are connection problems with the second one, so from time to time the web service just times out. This means that a concurrent user has to wait for that time out, and whatever is left of that process instance, in order to be processed.
> On our JMeter test, the throughput keeps stable even if there number of request is bigger than the throughput of the BPEL engine. The result is that the time for response of each process request increases indefinitely if the usage is bigger than the throughput. This obviously doesn't scale at all for the processing requirement we are considering.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 23:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 23:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4919)
 HASingletonElectionPolicySimple
 does not handle heterogeneous topologies
Message-ID: <10465338.1193716621629.JavaMail.jira@cloud.prod.atl2.jboss.com>

HASingletonElectionPolicySimple does not handle heterogeneous topologies
------------------------------------------------------------------------

                 Key: JBAS-4919
                 URL: http://jira.jboss.com/jira/browse/JBAS-4919
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


HASingletonElectionPolicySimple is just getting the current view from HAPartition and making a decision based on that, ignoring the fact that the service it's managing may not be running on all members of the cluster.

The HASingletonElectionPolicy API should be changed.  The isMasterReplica method should take (List<ClusterNode> newReplicants, int newViewID) rather than HAPartition.  The partition is provided via dependency injection at startup, no need to pass it in the method call. HASingletonElectionPolicySimple uses the provided replicants to make its decision, not the HAPartition view.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 23:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 23:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
In-Reply-To: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24674937.1193716621931.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4834?page=all ]

Brian Stansberry updated JBAS-4834:
-----------------------------------

    Attachment: JBAS-422+-+Clustering+-++Chapter1+-+Section4.5+-+HASingleton.odt

Attached is a new section that needs to be added. It should go just before the Clustered JMS section.

> TECH REVIEW: Clustering Guide - TRACKER
> ---------------------------------------
>
>                 Key: JBAS-4834
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422+-+Clustering+-++Chapter1+-+Section4.5+-+HASingleton.odt
>
>
> Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 00:01:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 00:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4920) Add section on
	HASingleton
Message-ID: <29549172.1193716861536.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add section on HASingleton
--------------------------

                 Key: JBAS-4920
                 URL: http://jira.jboss.com/jira/browse/JBAS-4920
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Brian Stansberry
         Assigned To: samson kittoli


I've added a new section for a significant area that was missing, HASingleton; document is attached to the parent issue.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 00:27:01 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 30 Oct 2007 00:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18051090.1193718421511.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------

    Resolution: Done

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>
> When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.
> HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 00:31:01 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 30 Oct 2007 00:31:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22187280.1193718661750.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384985 ] 
            
Clebert Suconic commented on JBMESSAGING-1099:
----------------------------------------------

The failure on ClusteredClientCrashTest is another case

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.
> HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 01:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 01:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9405442.1193723941696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Brian Stansberry updated JBAS-4835:
-----------------------------------

    Attachment: updated-30-10-2007-JBAS-422+-+Clustering+-++Chapter1+-+Introduction.odt

My edits attached.

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt, updated-30-10-2007-JBAS-422+-+Clustering+-++Chapter1+-+Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 01:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 01:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12128236.1193723941902.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Brian Stansberry reassigned JBAS-4835:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assign back to samson.

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt, updated-30-10-2007-JBAS-422+-+Clustering+-++Chapter1+-+Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 01:59:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 01:59:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
In-Reply-To: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14054570.1193723942106.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4834?page=all ]

Brian Stansberry reassigned JBAS-4834:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Done. :) Assigning back to samson.

> TECH REVIEW: Clustering Guide - TRACKER
> ---------------------------------------
>
>                 Key: JBAS-4834
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422+-+Clustering+-++Chapter1+-+Section4.5+-+HASingleton.odt
>
>
> Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:20:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:20:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-826) JBoss Remoting logs
 at ERROR and WARN in many places
Message-ID: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Remoting logs at ERROR and WARN in many places
----------------------------------------------------

                 Key: JBREM-826
                 URL: http://jira.jboss.com/jira/browse/JBREM-826
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Tim Fox
             Fix For: 2.4.0.Beta1 (Pinto)


In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

@main 08:01:30,648 INFO  [ServerManagement] Waiting for server to die
@main 08:01:30,953 INFO  [ServerManagement] server 1 killed and dead
@Timer-3 08:01:31,253 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,277 WARN  [ClientClusteredConnectionFactoryDelegate] org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:93)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 9 more
@Thread-9 08:01:31,299 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
SERVER 0 STDOUT: @Timer-4 08:01:31,301 ERROR [SocketClientInvoker] Got marshalling exception, exiting
SERVER 0 STDOUT: java.net.SocketException: end of file
SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
@Thread-9 08:01:31,320 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed sending disconnect for client lease for client with session ID 3j001-bj8ucn-f8e4sbxc-1-f8e4sbxd-2
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,345 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?cli

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:24:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:24:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-826) JBoss Remoting logs
 at ERROR and WARN in many places
In-Reply-To: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28680681.1193732642566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-826?page=all ]

Tim Fox updated JBREM-826:
--------------------------

    Description: 
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

  was:
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

@main 08:01:30,648 INFO  [ServerManagement] Waiting for server to die
@main 08:01:30,953 INFO  [ServerManagement] server 1 killed and dead
@Timer-3 08:01:31,253 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,277 WARN  [ClientClusteredConnectionFactoryDelegate] org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:93)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 9 more
@Thread-9 08:01:31,299 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
SERVER 0 STDOUT: @Timer-4 08:01:31,301 ERROR [SocketClientInvoker] Got marshalling exception, exiting
SERVER 0 STDOUT: java.net.SocketException: end of file
SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
@Thread-9 08:01:31,320 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed sending disconnect for client lease for client with session ID 3j001-bj8ucn-f8e4sbxc-1-f8e4sbxd-2
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,345 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?cli

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.


> JBoss Remoting logs at ERROR and WARN in many places
> ----------------------------------------------------
>
>                 Key: JBREM-826
>                 URL: http://jira.jboss.com/jira/browse/JBREM-826
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tim Fox
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.
> JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.
> There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd
> Failover in JBoss Messaging is a good example.
> In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.
> However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:
> This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.
> If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.
> In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:36:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-826) JBoss Remoting logs
 at ERROR and WARN in many places
In-Reply-To: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32512115.1193733361749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-826?page=all ]

Tim Fox updated JBREM-826:
--------------------------

    Description: 
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. 

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projects. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exception occurs.

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,571 INFO  [RMITestServer] kill() invoked - first deregistering from the rmi registry
SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,572 INFO  [RMITestServer] unregistered messaging_rmi_server_1 from registry
SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] unregistered naming_rmi_server_1 from registry
SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] Killing VM!!!!
@main 08:27:29,940 INFO  [ServerManagement] Waiting for server to die
SERVER 0 STDOUT: @Timer-4 08:27:30,084 ERROR [SocketClientInvoker] Got marshalling exception, exiting
SERVER 0 STDOUT: java.net.SocketException: end of file
SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
@main 08:27:30,241 INFO  [ServerManagement] server 1 killed and dead
@Timer-3 08:27:30,275 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:27:30,318 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-9 08:27:30,338 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pqua-2
@Thread-9 08:27:30,360 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-10 08:27:30,532 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-10 08:27:30,551 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pss1-9
@Thread-10 08:27:30,570 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-9 08:27:30,600 ERROR [BisocketServerInvoker] unable to get secondary locator
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
        at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
        at org.jboss.remoting.Client.addListener(Client.java:921)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 14 more
@Thread-9 08:27:30,620 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-9 08:27:30,639 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5puat-k
@Thread-10 08:27:30,760 ERROR [BisocketServerInvoker] unable to get secondary locator
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
        at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
        at org.jboss.remoting.Client.addListener(Client.java:921)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 14 more
@Thread-10 08:27:30,780 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-10 08:27:30,807 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pugn-p
@Thread-13 08:27:31,491 INFO  [FailoverCommandCenter] JBoss Messaging server failure detected - waiting for failover to complete...
@Thread-13 08:27:31,793 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
        at java.io.FilterInputStream.read(FilterInputStream.java:66)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
        at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
        at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:358)
        at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
        at org.jboss.remoting.Client.connect(Client.java:1525)
        at org.jboss.remoting.Client.connect(Client.java:462)
        at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:295)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:291)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
        at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
        at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
        at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:134)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
        at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
        at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
        at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
@Thread-13 08:27:31,801 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[682406, bisocket://localhost:2854](3j001-c12qds-f8e5pqu9-1-f8e5puj4-v)] failed to ping to server: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is:
        java.net.SocketException: Connection reset
@Thread-2 08:27:31,820 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
        at java.io.FilterInputStream.read(FilterInputStream.java:66)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.finalize(ClientClusteredConnectionFactoryDelegate.java:158)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:418)
@Thread-2 08:27:31,839 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2854/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=fals

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

The customer says "Why was JBoss reporting errors when everything was ok?"

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

  was:
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.


> JBoss Remoting logs at ERROR and WARN in many places
> ----------------------------------------------------
>
>                 Key: JBREM-826
>                 URL: http://jira.jboss.com/jira/browse/JBREM-826
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tim Fox
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.
> JBR is a toolkit and should not log errors it does not handle. 
> There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projects. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exception occurs.
> Failover in JBoss Messaging is a good example.
> In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.
> However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,571 INFO  [RMITestServer] kill() invoked - first deregistering from the rmi registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,572 INFO  [RMITestServer] unregistered messaging_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] unregistered naming_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] Killing VM!!!!
> @main 08:27:29,940 INFO  [ServerManagement] Waiting for server to die
> SERVER 0 STDOUT: @Timer-4 08:27:30,084 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> SERVER 0 STDOUT: java.net.SocketException: end of file
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
> SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
> SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
> SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
> @main 08:27:30,241 INFO  [ServerManagement] server 1 killed and dead
> @Timer-3 08:27:30,275 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: end of file
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
>         at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> @Thread-9 08:27:30,318 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,338 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pqua-2
> @Thread-9 08:27:30,360 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,532 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,551 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pss1-9
> @Thread-10 08:27:30,570 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,600 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-9 08:27:30,620 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,639 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5puat-k
> @Thread-10 08:27:30,760 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-10 08:27:30,780 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,807 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pugn-p
> @Thread-13 08:27:31,491 INFO  [FailoverCommandCenter] JBoss Messaging server failure detected - waiting for failover to complete...
> @Thread-13 08:27:31,793 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
>         at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:358)
>         at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
>         at org.jboss.remoting.Client.connect(Client.java:1525)
>         at org.jboss.remoting.Client.connect(Client.java:462)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:295)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:291)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
>         at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:134)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
>         at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
>         at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> @Thread-13 08:27:31,801 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[682406, bisocket://localhost:2854](3j001-c12qds-f8e5pqu9-1-f8e5puj4-v)] failed to ping to server: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is:
>         java.net.SocketException: Connection reset
> @Thread-2 08:27:31,820 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.finalize(ClientClusteredConnectionFactoryDelegate.java:158)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:418)
> @Thread-2 08:27:31,839 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2854/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=fals
> This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.
> The customer says "Why was JBoss reporting errors when everything was ok?"
> If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.
> In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:54:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-826) JBoss Remoting
 logs at ERROR and WARN in many places
In-Reply-To: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17971820.1193734441899.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-826?page=comments#action_12385011 ] 
            
Tim Fox commented on JBREM-826:
-------------------------------

I can supress the error messages using the following log4j snippet:


   <category name="org.jboss.remoting.transport.socket.SocketClientInvoker">
      <priority value="FATAL"/>
   </category>

   <category name="org.jboss.remoting.transport.bisocket.BisocketServerInvoker">
      <priority value="FATAL"/>
   </category>

   <category name="org.jboss.remoting.Client">
      <priority value="FATAL"/>
   </category>

   <category name="org.jboss.remoting.LeasePinger">
      <priority value="FATAL"/>
   </category>

This works nicely - but it might hide valid error conditions

> JBoss Remoting logs at ERROR and WARN in many places
> ----------------------------------------------------
>
>                 Key: JBREM-826
>                 URL: http://jira.jboss.com/jira/browse/JBREM-826
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tim Fox
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.
> JBR is a toolkit and should not log errors it does not handle. 
> There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projects. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exception occurs.
> Failover in JBoss Messaging is a good example.
> In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.
> However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,571 INFO  [RMITestServer] kill() invoked - first deregistering from the rmi registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,572 INFO  [RMITestServer] unregistered messaging_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] unregistered naming_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] Killing VM!!!!
> @main 08:27:29,940 INFO  [ServerManagement] Waiting for server to die
> SERVER 0 STDOUT: @Timer-4 08:27:30,084 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> SERVER 0 STDOUT: java.net.SocketException: end of file
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
> SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
> SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
> SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
> @main 08:27:30,241 INFO  [ServerManagement] server 1 killed and dead
> @Timer-3 08:27:30,275 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: end of file
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
>         at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> @Thread-9 08:27:30,318 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,338 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pqua-2
> @Thread-9 08:27:30,360 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,532 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,551 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pss1-9
> @Thread-10 08:27:30,570 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,600 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-9 08:27:30,620 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,639 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5puat-k
> @Thread-10 08:27:30,760 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-10 08:27:30,780 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,807 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pugn-p
> @Thread-13 08:27:31,491 INFO  [FailoverCommandCenter] JBoss Messaging server failure detected - waiting for failover to complete...
> @Thread-13 08:27:31,793 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
>         at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:358)
>         at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
>         at org.jboss.remoting.Client.connect(Client.java:1525)
>         at org.jboss.remoting.Client.connect(Client.java:462)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:295)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:291)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
>         at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:134)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
>         at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
>         at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> @Thread-13 08:27:31,801 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[682406, bisocket://localhost:2854](3j001-c12qds-f8e5pqu9-1-f8e5puj4-v)] failed to ping to server: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is:
>         java.net.SocketException: Connection reset
> @Thread-2 08:27:31,820 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.finalize(ClientClusteredConnectionFactoryDelegate.java:158)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:418)
> @Thread-2 08:27:31,839 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2854/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=fals
> This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.
> The customer says "Why was JBoss reporting errors when everything was ok?"
> If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.
> In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 05:02:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 30 Oct 2007 05:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1707) New
 UserModule/RoleModule finders
In-Reply-To: <6276632.1190228243214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9649873.1193734921906.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1707?page=all ]

Thomas Heute updated JBPORTAL-1707:
-----------------------------------

    Fix Version/s: 2.8 Final

> New UserModule/RoleModule finders
> ---------------------------------
>
>                 Key: JBPORTAL-1707
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1707
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final
>            Reporter: Andrew Oliver
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.8 Final
>
>
> While working with clients using the portal API some efficiency issues with regards to finders have become apparent:
> It is presently possible to find users having a role by calling MembershipModule.getUsers(role).  However it is not possible to get a list of users with a set of roles, a list of users who do NOT have a role or set of roles.  (there are ways in both HQL and LDAP to construct each type of query).  I suggest something similar to hibernate conditions.
> MembershipModule.getUsers().addCondition(
>    Condition.and(
>         Condition.not(roleSet), Condition.with(roleSet)
>    )
> )
> this would result in roughly:
> from Users where roles in (:roleSet) and roles not in (:roleSet2)
> and something like 
> (& (|(role=roleName)(role=roleName)  )
>      (&(!role=roleName)(!role=roleName) )
> )
> in LDAP
> the attribute name can be based on the type.  As it stands you have to do something like:
> 		try {			
> 			Role roleApproved = rolemodule.findRoleByName("approved");
> 			Role roleUsers = rolemodule.findRoleByName("User");
> 			//todo create transient wrapper set.
> 		    Set users = membership.getUsers(roleUsers);
> 		    dirtyStinkyHackToGetAroundPortalAPIBugACO(users);
> 		    System.err.println("Total number of users with User Role  : " + users.size() );
> 		    Set temp = new HashSet();
> 		    temp = dirtyStinkyHackToGetAroundPortalAPIBugACO(users); //because the hibernate set doesn't have removeall
> 		    users = temp;
> 			Set usersApproved = membership.getUsers(roleApproved);
> 			System.err.println("number of users with approved role: "+usersApproved.size());
> 			users.removeAll(usersApproved);
> 			System.err.println("Total number of users with User Role and NO approved role : " + users.size() );
> 			Map profiles = profiles(users);
> 			response.setRenderParameter("op", "new");
> 			request.getPortletSession().setAttribute("users", users);
> 			request.getPortletSession().setAttribute("profiles", profiles);
> 		} catch (IdentityException e) {
> 			//todo type this and catch it up higher to make a 
> 			//smarter error message
> 			throw new RuntimeException(e);
> 		}
> 	private Map profiles(Set users) throws IdentityException {
> 		Iterator i = users.iterator();
> 		Map retval = new HashMap();
> 		while(i.hasNext()) {
> 			User user = (User) i.next();
> 			retval.put(user, profileModule.getProperties(user));
> 		}
> 		return retval;
> 	}
> 	
> 	private Set dirtyStinkyHackToGetAroundPortalAPIBugACO(Set users) {
> 		Iterator i = users.iterator();
> 		Set retval = new HashSet();
> 		while(i.hasNext()) {
> 			User u = (User)i.next();
> 			u.getUserName();
> 			retval.add(u);
> 		}
> 		return retval;
> 	}
> Just to get the list of users who DONT have the "approved" role.  For our immediate needs:
> UserModule.getUsersWithout(role) would work...until next time.
> -Andy

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 05:02:02 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 30 Oct 2007 05:02:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24203208.1193734922086.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=all ]

Thomas Heute updated JBPORTAL-1713:
-----------------------------------

        Fix Version/s: 2.6.3 Final
    Affects Version/s: 2.6.2 Final
                           (was: 2.6.3 Final)

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.2 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 05:24:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 05:24:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4918) for logging,
 server.xml references another variable than jboss-log4j.xml does
In-Reply-To: <20868859.1193701981886.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14039219.1193736241899.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4918?page=all ]

Dimitris Andreadis updated JBAS-4918:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
         Assignee: Dimitris Andreadis  (was: Scott M Stark)

> for logging, server.xml references another variable than jboss-log4j.xml does
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4918
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4918
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: all
>            Reporter: Jon Stevens
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.3.GA
>
>
> jboss-log4j.xml has this as default:
>       <param name="File" value="${jboss.server.log.dir}/server.log"/>
> jboss-web.deployer has this:
>             <!-- Access logger -->
>             <Valve className="org.apache.catalina.valves.AccessLogValve"
>                 prefix="localhost_access_log." suffix=".log"
>                 pattern="common" directory="${jboss.server.home.dir}/log" 
>                 resolveHosts="false" />
> Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because
> #1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir}
> #2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value.
> My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything.
> jon

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:24:01 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 30 Oct 2007 06:24:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4921) Web service
 deployment: web.xml modified to web.xml.org - Subsequent runs fail
Message-ID: <12195707.1193739841403.JavaMail.jira@cloud.prod.atl2.jboss.com>

Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
------------------------------------------------------------------------------

                 Key: JBAS-4921
                 URL: http://jira.jboss.com/jira/browse/JBAS-4921
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Web Services
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Heiko Braun
         Assigned To: Heiko Braun


See associated JBossWS issue

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:26:01 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 30 Oct 2007 06:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4921) Web service
 deployment: web.xml modified to web.xml.org - Subsequent runs fail
In-Reply-To: <12195707.1193739841403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13918070.1193739961526.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4921?page=all ]

Heiko Braun updated JBAS-4921:
------------------------------

    Fix Version/s: JBossAS-4.2.3.GA

> Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4921
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4921
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Heiko Braun
>         Assigned To: Heiko Braun
>             Fix For: JBossAS-4.2.3.GA
>
>
> See associated JBossWS issue

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:26:01 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 30 Oct 2007 06:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4921) Web service
 deployment: web.xml modified to web.xml.org - Subsequent runs fail
In-Reply-To: <12195707.1193739841403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20702312.1193739961673.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4921?page=all ]

Heiko Braun resolved JBAS-4921.
-------------------------------

    Resolution: Done

> Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4921
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4921
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Heiko Braun
>         Assigned To: Heiko Braun
>             Fix For: JBossAS-4.2.3.GA
>
>
> See associated JBossWS issue

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:53:10 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 06:53:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4922) NPE in
	AssemblyDescriptorMetaData
Message-ID: <21462601.1193741590212.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in AssemblyDescriptorMetaData
---------------------------------

                 Key: JBAS-4922
                 URL: http://jira.jboss.com/jira/browse/JBAS-4922
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:55:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 06:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4922) NPE in
	AssemblyDescriptorMetaData
In-Reply-To: <21462601.1193741590212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10882342.1193741701499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4922?page=all ]

Thomas Diesler updated JBAS-4922:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test

11:47:39,226 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=ejb/ConfidentialSLSB,service=EJB state=Configured mode=Manual requiredState=Create
java.lang.NullPointerException
        at org.jboss.metadata.AssemblyDescriptorMetaData.getPrincipalVersusRolesMap(AssemblyDescriptorMetaData.java:126)
        at org.jboss.ejb.plugins.SecurityInterceptor.setContainer(SecurityInterceptor.java:132)
        at org.jboss.ejb.SessionContainer.createInterceptors(SessionContainer.java:374)
        at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:182)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:267)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
        at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)

         Assignee: Scott M Stark

> NPE in AssemblyDescriptorMetaData
> ---------------------------------
>
>                 Key: JBAS-4922
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4922
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> 11:47:39,226 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=ejb/ConfidentialSLSB,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at org.jboss.metadata.AssemblyDescriptorMetaData.getPrincipalVersusRolesMap(AssemblyDescriptorMetaData.java:126)
>         at org.jboss.ejb.plugins.SecurityInterceptor.setContainer(SecurityInterceptor.java:132)
>         at org.jboss.ejb.SessionContainer.createInterceptors(SessionContainer.java:374)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:182)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:267)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
>         at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:02:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4856) Web Services
 regression after update to new metadata model
In-Reply-To: <28485098.1192452063304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15999708.1193742121464.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4856?page=all ]

Thomas Diesler updated JBAS-4856:
---------------------------------

    Summary: Web Services regression after update to new metadata model  (was: Issues related to the new metadata model)

> Web Services regression after update to new metadata model
> ----------------------------------------------------------
>
>                 Key: JBAS-4856
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4856
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:02:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4923) No valid security
 context for the caller identity
Message-ID: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>

No valid security context for the caller identity
-------------------------------------------------

                 Key: JBAS-4923
                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:04:12 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:04:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9843317.1193742252481.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4923?page=all ]

Thomas Diesler updated JBAS-4923:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test

Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
        at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
        at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
        at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
        at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)


> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:04:12 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:04:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6588545.1193742252684.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4923?page=all ]

Thomas Diesler reassigned JBAS-4923:
------------------------------------

    Assignee: Anil Saldhana

> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:19:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4924) NPE caused by
 SessionContainer.createService
Message-ID: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE caused by SessionContainer.createService
--------------------------------------------

                 Key: JBAS-4924
                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:21:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28581936.1193743261405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler updated JBAS-4924:
---------------------------------

    Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test

12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
java.lang.NullPointerException
        at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
        at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
        at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
        at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
        at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.jboss.ejb.Container.createService(Container.java:854)
        at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)


> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:23:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18912757.1193743381680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler updated JBAS-4924:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:23:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12077261.1193743381813.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler reassigned JBAS-4924:
------------------------------------

    Assignee: Thomas Diesler

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:27:19 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 07:27:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-613) Access to
 NAKACK#rebroadcast_digest field needs a lock
In-Reply-To: <8602308.1193679844347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26290239.1193743639837.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-613?page=comments#action_12385024 ] 
            
Bela Ban commented on JGRP-613:
-------------------------------

This is caused by FLUSH handling the FLUSH_RECONCILE message. I thought that is sent out by the FLUSH coordinator, so it should not get invoked concurrently ?

I'll fix the NPE, but why is this code invoked by multiple threads ?

> Access to NAKACK#rebroadcast_digest field needs a lock
> ------------------------------------------------------
>
>                 Key: JGRP-613
>                 URL: http://jira.jboss.com/jira/browse/JGRP-613
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Vladimir Blagojevic
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.6
>
>
> It seems that rebroadcast_digest field of NAKACK  is accessed by multiple threads which step over each other leading to a consequences below.
> This is very hard to reproduce and I have seen it only a few times so far.
> -------------------------------------------------------
> GMS: address is 127.0.0.1:2528
> -------------------------------------------------------
> 11141 [INFO][main] ConcurrentStateTransferTest: - Thread for channel 127.0.0.1:2528[A] started
> 15250 [INFO][A] ConcurrentStateTransferTest: - channel.getState at A127.0.0.1:2518 returned false
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2520] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2520)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2524] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2524)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2518] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2518)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2528] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2528)]: received 127.0.0.1:2518
> 15328 [ERROR][OOB,udp,127.0.0.1:2520] UDP: - failed handling incoming message
> java.lang.NullPointerException
> 	at org.jgroups.protocols.pbcast.NAKACK.rebroadcastMessages(NAKACK.java:1036)
> 	at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:620)
> 	at org.jgroups.protocols.UNICAST.down(UNICAST.java:434)
> 	at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317)
> 	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:813)
> 	at org.jgroups.protocols.FC.down(FC.java:370)
> 	at org.jgroups.protocols.FRAG2.down(FRAG2.java:175)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:318)
> 	at org.jgroups.protocols.pbcast.FLUSH.handleFlushReconcile(FLUSH.java:455)
> 	at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:337)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:258)
> 	at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
> 	at org.jgroups.protocols.FC.up(FC.java:408)
> 	at org.jgroups.protocols.pbcast.GMS.up(GMS.java:742)
> 	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:264)
> 	at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:798)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:662)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1461)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:42:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 07:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-613) Access to
 NAKACK#rebroadcast_digest field needs a lock
In-Reply-To: <8602308.1193679844347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7789445.1193744521693.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-613?page=all ]

Bela Ban resolved JGRP-613.
---------------------------

    Resolution: Done

> Access to NAKACK#rebroadcast_digest field needs a lock
> ------------------------------------------------------
>
>                 Key: JGRP-613
>                 URL: http://jira.jboss.com/jira/browse/JGRP-613
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Vladimir Blagojevic
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.6
>
>
> It seems that rebroadcast_digest field of NAKACK  is accessed by multiple threads which step over each other leading to a consequences below.
> This is very hard to reproduce and I have seen it only a few times so far.
> -------------------------------------------------------
> GMS: address is 127.0.0.1:2528
> -------------------------------------------------------
> 11141 [INFO][main] ConcurrentStateTransferTest: - Thread for channel 127.0.0.1:2528[A] started
> 15250 [INFO][A] ConcurrentStateTransferTest: - channel.getState at A127.0.0.1:2518 returned false
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2520] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2520)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2524] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2524)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2518] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2518)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2528] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2528)]: received 127.0.0.1:2518
> 15328 [ERROR][OOB,udp,127.0.0.1:2520] UDP: - failed handling incoming message
> java.lang.NullPointerException
> 	at org.jgroups.protocols.pbcast.NAKACK.rebroadcastMessages(NAKACK.java:1036)
> 	at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:620)
> 	at org.jgroups.protocols.UNICAST.down(UNICAST.java:434)
> 	at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317)
> 	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:813)
> 	at org.jgroups.protocols.FC.down(FC.java:370)
> 	at org.jgroups.protocols.FRAG2.down(FRAG2.java:175)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:318)
> 	at org.jgroups.protocols.pbcast.FLUSH.handleFlushReconcile(FLUSH.java:455)
> 	at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:337)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:258)
> 	at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
> 	at org.jgroups.protocols.FC.up(FC.java:408)
> 	at org.jgroups.protocols.pbcast.GMS.up(GMS.java:742)
> 	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:264)
> 	at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:798)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:662)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1461)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:42:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31026780.1193744521867.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12385028 ] 
            
Thomas Diesler commented on JBAS-4902:
--------------------------------------

To run any of the tests you do:

svn co https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2
cd jbossws-native-2.0.2
cp ant.properties.example ant.properties
vi ant.properties
ant deploy-jboss500
ant tests-main

ant -Dtest=jaxrpc/jbws128 test 

This is also described here

http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source


> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 08:43:13 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 08:43:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-611) MergeTask GMS
 ConcurrentModificationException
In-Reply-To: <32335654.1193392021705.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33531090.1193748193011.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-611?page=all ]

Bela Ban resolved JGRP-611.
---------------------------

    Resolution: Done

fixed in 2.6 (CVS head) and 2.5 branch

> MergeTask GMS ConcurrentModificationException
> ---------------------------------------------
>
>                 Key: JGRP-611
>                 URL: http://jira.jboss.com/jira/browse/JGRP-611
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.5.2, 2.6
>
>
> [Vivek Sar]
> I'm using JGroups 2.5 GA and have 3 members in the group using udp
> gossip router (stack below). Occasionally, we have seen the following
> exception if a node goes down and comes up again. This happens over
> and over, only way to recover would then be to stop all the members
> and start them again.
>  2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - exception while merging
> java.util.ConcurrentModificationException
> 	at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> 	at java.util.AbstractList$Itr.next(Unknown Source)
> 	at org.jgroups.protocols.pbcast.CoordGmsImpl.removeRejectedMergeRequests(CoordGmsImpl.java:749)
> 	at org.jgroups.protocols.pbcast.CoordGmsImpl.access$500(CoordGmsImpl.java:26)
> 	at org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask.run(CoordGmsImpl.java:817)
> 	at java.lang.Thread.run(Unknown Source)
> 2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:27,237 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
> ...
> ...
> Protocol Stack,
> <config>
>     <UDP
> 		 ip_mcast="false"
> 		 mcast_addr="228.10.10.10"
> 		 mcast_port="3092"
> 		 bind_addr="${jgroups.bindaddress.ip:jgroupshost}"
> 		 bind_port="${jgroups.bindaddress.port:3092}"		 		
>          tos="16"
>          ucast_recv_buf_size="200000"
>          ucast_send_buf_size="640000"
>          mcast_recv_buf_size="250000"
>          mcast_send_buf_size="640000"
>          loopback="true"
>          discard_incompatible_packets="true"
>          max_bundle_size="64000"
>          max_bundle_timeout="30"
>          use_incoming_packet_handler="true"
>          use_outgoing_packet_handler="false"
>          ip_ttl="32"
>          enable_bundling="true"
> 		 use_concurrent_stack="true"
> 		 thread_pool.enabled="true"
> 		 thread_pool.min_threads="1"
> 		 thread_pool.max_threads="100"
> 		 thread_pool.keep_alive_time="20000"
> 		 thread_pool.queue_enabled="false"
> 		 thread_pool.queue_max_size="10"
> 		 thread_pool.rejection_policy="Run"
> 		 oob_thread_pool.enabled="true"
> 		 oob_thread_pool.min_threads="1"
> 		 oob_thread_pool.max_threads="4"
> 		 oob_thread_pool.keep_alive_time="30000"
> 		 oob_thread_pool.queue_enabled="true"
> 		 oob_thread_pool.queue_max_size="10"
> 		 oob_thread_pool.rejection_policy="Run"/>
>     <PING gossip_host="${jgroups.gossiprouter.ip:jgroupshost}"
> gossip_port="${jgroups.gossiprouter.port:3091}"
> 		    gossip_refresh="15000"
> 		    timeout="3000"
>             num_initial_members="3"/>
> 	
> 	<MERGE2 min_interval="5000" max_interval="10000"
> 		down_thread="false" up_thread="false"/>
> 	
> 	<FD_SOCK up_thread="false" down_thread="false"/>
> 	
>     <FD timeout="10000" max_tries="5" shun="true"/>
>     <VERIFY_SUSPECT timeout="1500"/>
> 	
>     <pbcast.NAKACK max_xmit_size="60000"
>                    use_mcast_xmit="false" gc_lag="0"
>                    retransmit_timeout="100,200,300,600,1200,2400,4800"
>                    discard_delivered_msgs="true"/>
> 	
>     <UNICAST timeout="300,600,1200,2400,3600"/>
> 	
>     <ENCRYPT key_store_name="keystore" store_password="xxx"
> key_password="xxx" alias="xxx"/>
> 	
>     <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
>                    max_bytes="400000"/>
> 	
>     <VIEW_SYNC avg_send_interval="60000"/>
> 	
> 	
> 	<AUTH auth_class="org.jgroups.auth.MD5Token"
>         auth_value="xxx"
>         token_hash="MD5"/>
> 		
>     <pbcast.GMS print_local_addr="true" join_timeout="5000"
>                 join_retry_timeout="2000" shun="true"/>
> 	
>      <FC max_credits="2000000"
>          min_threshold="0.10"/>
> 	
> 	<FRAG2 frag_size="60000"/>
> 	
>     <pbcast.STATE_TRANSFER  />
> </config>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:36:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 30 Oct 2007 09:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6328052.1193751361682.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Vladimir Blagojevic resolved JGRP-608.
--------------------------------------

    Resolution: Done

Smaller lock scope. Commit set:
protocols/pbcast/FLUSH.java 1.77

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:42:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 09:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28564576.1193751721462.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12385051 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

The problem is that, when a synchronous call is received via UNICAST, the thread acquires a caller-based lock in UNICAST and then dispatches the request up the stack.

When the same thread is used to send a large return value, FRAG2 splits the response message into many smaller messages, which then get sent to the sender (self in RpcDispatcher.testLargeReturnValue()), thus blocking FC.

The thread pool for regular threads is blocked and all other messages (even OOB ones !) are sitting in the IP buffers and don't even make it to the transport. This means, credits (sent via OOB messages) are not received and we just block.

Solution (pick one or more):

- In the regular thread pool:
    - Use a queue
    - Increase the max thread
    - Set rejection policy to "discard" rather than "run"
- Increase FC.max_credits to a value greater than the largest return value. Dangerous, as this increases time without blocks


I'll keep looking for a better solution

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:47:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 09:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4874) Track JBoss and
 thirdparty dependencies for JBossAS 4.2.3
In-Reply-To: <29949338.1192721463216.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14806801.1193752021721.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4874?page=all ]

Dimitris Andreadis updated JBAS-4874:
-------------------------------------

    Assignee: Dimitris Andreadis
    Priority: Critical  (was: Major)

> Track JBoss and thirdparty dependencies for JBossAS 4.2.3
> ---------------------------------------------------------
>
>                 Key: JBAS-4874
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4874
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>            Priority: Critical
>             Fix For: JBossAS-4.2.3.GA
>
>
> Use subtasks to track component updates in AS 4.2.3.GA

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:51:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 09:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4925) Upgrade jboss cache
 to 1.4.1.SP6 (from 1.4.1.SP5)
Message-ID: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
-------------------------------------------------

                 Key: JBAS-4925
                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: JBoss Cache
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Dimitris Andreadis
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:53:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 09:53:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4925) Upgrade jboss
 cache to 1.4.1.SP6 (from 1.4.1.SP5)
In-Reply-To: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27215690.1193752382562.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4925?page=comments#action_12385056 ] 
            
Dimitris Andreadis commented on JBAS-4925:
------------------------------------------

Flipped the build to SP6; leave this open until we verify it's ok.

> Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
> -------------------------------------------------
>
>                 Key: JBAS-4925
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.3.GA
>
>
> Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:13:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 10:13:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
Message-ID: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>

IncompleteDeploymentException prevents further deployments
----------------------------------------------------------

                 Key: JBAS-4926
                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:15:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 10:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13123589.1193753701492.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4926?page=all ]

Thomas Diesler updated JBAS-4926:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
It seems that an incomplete deployment prevents any further deployment

    [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
    [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
    [junit]     ... 45 more
    [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

    [junit] *** CONTEXTS IN ERROR: Name -> Error

    [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started


    [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
    [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
    [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

         Assignee: Scott M Stark

> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:55:14 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 10:55:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7176652.1193756114311.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Lee Rubinger reopened EJBTHREE-1062:
-------------------------------------------

             
Reopened to merge w/ Branch_4_2

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:55:14 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 10:55:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29076030.1193756114634.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Lee Rubinger updated EJBTHREE-1062:
------------------------------------------

    Fix Version/s: Branch_4_2

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:28:13 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 11:28:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4925) Upgrade jboss
 cache to 1.4.1.SP6 (from 1.4.1.SP5)
In-Reply-To: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16546479.1193758093602.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4925?page=comments#action_12385086 ] 
            
Brian Stansberry commented on JBAS-4925:
----------------------------------------

Guys, 1.4.1.SP6 isn't even released yet. Until it is, and the brew build is redone from the QE approved src, the current integration is equivalent to a snapshot.

> Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
> -------------------------------------------------
>
>                 Key: JBAS-4925
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.3.GA
>
>
> Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:32:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 11:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4925) Upgrade jboss
 cache to 1.4.1.SP6 (from 1.4.1.SP5)
In-Reply-To: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32963594.1193758321784.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4925?page=comments#action_12385090 ] 
            
Dimitris Andreadis commented on JBAS-4925:
------------------------------------------

That's cool, we are on the bleeding edge :-)

> Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
> -------------------------------------------------
>
>                 Key: JBAS-4925
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.3.GA
>
>
> Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:48:01 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Tue, 30 Oct 2007 11:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1712) Make producer
 tests go through the WS stack
In-Reply-To: <22960492.1190516351026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4131704.1193759281405.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=comments#action_12385100 ] 
            
Chris Laprun commented on JBPORTAL-1712:
----------------------------------------

Gonna see what I can do... It's tricky because I would like to switch to the new test framework as well as I would like to touching the test infrastructure too many times.

> Make producer tests go through the WS stack
> -------------------------------------------
>
>                 Key: JBPORTAL-1712
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1712
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal WSRP
>    Affects Versions: 2.8 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>             Fix For: 2.8 Final, 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:50:06 2007
From: jira-events at lists.jboss.org (Greg Bridges (JIRA))
Date: Tue, 30 Oct 2007 11:50:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4927) Code added in 4.2.1
 breaks web app that works in 4.2.0
Message-ID: <22925434.1193759406449.JavaMail.jira@cloud.prod.atl2.jboss.com>

Code added in 4.2.1 breaks web app that works in 4.2.0
------------------------------------------------------

                 Key: JBAS-4927
                 URL: http://jira.jboss.com/jira/browse/JBAS-4927
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
         Environment: linux, java5
            Reporter: Greg Bridges
         Assigned To: Remy Maucherat


Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.

I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.

At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.

If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:05:01 2007
From: jira-events at lists.jboss.org (Remy Maucherat (JIRA))
Date: Tue, 30 Oct 2007 12:05:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4927) Code added in
 4.2.1 breaks web app that works in 4.2.0
In-Reply-To: <22925434.1193759406449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5785654.1193760301634.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4927?page=comments#action_12385109 ] 
            
Remy Maucherat commented on JBAS-4927:
--------------------------------------

Caused by fixing JBCTS-609.

> Code added in 4.2.1 breaks web app that works in 4.2.0
> ------------------------------------------------------
>
>                 Key: JBAS-4927
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4927
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
>         Environment: linux, java5
>            Reporter: Greg Bridges
>         Assigned To: Remy Maucherat
>
> Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.
> I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.
> At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.
> If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:11:02 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Tue, 30 Oct 2007 12:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-255) Arrows in admin
 page are displayed wrongly
Message-ID: <22269073.1193760662165.JavaMail.jira@cloud.prod.atl2.jboss.com>

Arrows in admin page are displayed wrongly
------------------------------------------

                 Key: JBFORUMS-255
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-255
             Project: JBoss Forums
          Issue Type: Bug
          Components: Forum View Layer
            Reporter: Ryszard Kozmik
            Priority: Minor
             Fix For: 1.0.1 RC, 1.1.0 Alpha


Arrows for changing order of forums and categories are messed up after admin panel view refactoring.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:13:11 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 12:13:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4927) Code added in 4.2.1
 breaks web app that works in 4.2.0
In-Reply-To: <22925434.1193759406449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22969989.1193760791809.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4927?page=all ]

Dimitris Andreadis updated JBAS-4927:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA

Schedule for 4.2.3.GA. Maybe we should look at it in trunk, too.

> Code added in 4.2.1 breaks web app that works in 4.2.0
> ------------------------------------------------------
>
>                 Key: JBAS-4927
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4927
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
>         Environment: linux, java5
>            Reporter: Greg Bridges
>         Assigned To: Remy Maucherat
>             Fix For: JBossAS-4.2.3.GA
>
>
> Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.
> I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.
> At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.
> If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:13:12 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 30 Oct 2007 12:13:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9205571.1193760792698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

Koen Aers closed GPD-169.
-------------------------

    Resolution: Done

The issue was fixed on HEAD. It would be nice if someone could verify if the problem is gone.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:15:01 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Tue, 30 Oct 2007 12:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-256) Update build
	script
Message-ID: <14140527.1193760901691.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update build script
-------------------

                 Key: JBFORUMS-256
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-256
             Project: JBoss Forums
          Issue Type: Task
          Components: Portlet Productization
            Reporter: Ryszard Kozmik
         Assigned To: Przemyslaw Dej
            Priority: Critical
             Fix For: 1.0.1 RC, 1.1.0 Alpha, 1.0.0 GA


A package for JBoss Portal 2.6.1 was made and is available in project's downloads but build script was not updated to build such a package. Mostly the change is bundling more jars and an xml with defined scoped classloader repo.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:40:02 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Tue, 30 Oct 2007 12:40:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-257) Not efficient
	admin view
Message-ID: <13466011.1193762402854.JavaMail.jira@cloud.prod.atl2.jboss.com>

Not efficient admin view
------------------------

                 Key: JBFORUMS-257
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-257
             Project: JBoss Forums
          Issue Type: Bug
          Components: Forum Model Layer, Forum View Layer
            Reporter: Ryszard Kozmik
             Fix For: 1.0.1 RC, 1.1.0 Alpha


When having lots of forums/categories in database, admin view breaks due to model layer problems. Probably something was messed up while doing view refactoring.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:37:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 13:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1091) Ensure all
 metadata files are included in the Schema test case
In-Reply-To: <18825902.1193691275979.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22800996.1193765821542.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1091?page=comments#action_12385145 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1091:
-----------------------------------------------

Included all ejb-jar.xml and jboss*.xml files (excluding jboss-service.xml, jboss-app.xml, etc)

> Ensure all metadata files are included in the Schema test case
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-1091
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1091
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> Be sure that all ejb-jar.xml, jboss.xml files in the EJB3 module are included in the tests of org.jboss.ejb3.test.schema.unit.SchemaTestCase

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:37:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 13:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1091) Ensure all
 metadata files are included in the Schema test case
In-Reply-To: <18825902.1193691275979.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12532390.1193765821854.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1091?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1091.
-------------------------------------------

    Resolution: Done

> Ensure all metadata files are included in the Schema test case
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-1091
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1091
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> Be sure that all ejb-jar.xml, jboss.xml files in the EJB3 module are included in the tests of org.jboss.ejb3.test.schema.unit.SchemaTestCase

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:44:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 13:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBXB-112) Failed to create a
	new SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6535534.1193766241623.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Thomas Diesler reopened JBXB-112:
---------------------------------

             
Could you please update the repository snapshot?

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:48:01 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 30 Oct 2007 13:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1092)
 <load-balance-policy> does not override annotation
Message-ID: <17076593.1193766481412.JavaMail.jira@cloud.prod.atl2.jboss.com>

<load-balance-policy> does not override annotation
--------------------------------------------------

                 Key: EJBTHREE-1092
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1092
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            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

        


From jira-events at lists.jboss.org  Tue Oct 30 14:24:06 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 30 Oct 2007 14:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12136184.1193768646538.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-570?page=all ]

Vladimir Blagojevic resolved JGRP-570.
--------------------------------------

    Resolution: Done

Resolved by introducing ThreadFactory as a field of ProtocolStack. Thus we removed all proliferated ThreadNamingPattern references as well as resolved the problem of thread renaming for short lived threads (ViewHandler, MergeTask and so on).

Commit set:

Revision  Path
1.1             JGroups/src/org/jgroups/ThreadFactory.java
1.54          JGroups/src/org/jgroups/stack/ProtocolStack.java

All other changes are trivial string replacement.

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:11:39 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 15:11:39 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4928) Compare AS library
 names between 4.2.x & 5.0.x
Message-ID: <17641383.1193771499144.JavaMail.jira@cloud.prod.atl2.jboss.com>

Compare AS library names between 4.2.x & 5.0.x 
-----------------------------------------------

                 Key: JBAS-4928
                 URL: http://jira.jboss.com/jira/browse/JBAS-4928
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Build System
            Reporter: Dimitris Andreadis
         Assigned To: Rajesh Rajasekaran
             Fix For: JBossAS-5.0.0.CR1


Check how similar libraries are deployed under different names in server/xxx/lib between 4.2.x & 5.0.x

The names shouldn't change, unless there is a good reason for that.

E.g.
lib/servlet-api.jar in 4.2.x
lib/javax.servlet.jar in 5.0.x

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:19:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:19:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6103051.1193771984729.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385160 ] 
            
Thomas Diesler commented on JBAS-4926:
--------------------------------------

I reverted the change that caused this

[tdiesler at tdvaio trunk]$ svn diff -rPREV system-jmx/src/main/org/jboss/deployment/MainDeployer.java
Index: system-jmx/src/main/org/jboss/deployment/MainDeployer.java
===================================================================
--- system-jmx/src/main/org/jboss/deployment/MainDeployer.java  (revision 66567)
+++ system-jmx/src/main/org/jboss/deployment/MainDeployer.java  (working copy)
@@ -811,7 +811,7 @@
             deploymentName = deployment.getName();
             delegate.process();
             // TODO: JBAS-4292
-            delegate.checkComplete();
+            delegate.checkComplete(deployment);
             contextMap.put(url, deploymentName);
          }
          catch(Exception e)


> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:27:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:27:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26857238.1193772464806.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4926?page=all ]

Thomas Diesler resolved JBAS-4926.
----------------------------------

    Resolution: Done

> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:29:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:29:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5219507.1193772585155.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Thomas Diesler reassigned JBAS-4901:
------------------------------------

    Assignee: Ales Justin  (was: Thomas Diesler)

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Ales Justin
>             Fix For: JBossAS-5.0.0.CR1
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:33:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4929) mapped-name is
 required for jdbc/juddiDB of deployment juddi.war
Message-ID: <548500.1193772824675.JavaMail.jira@cloud.prod.atl2.jboss.com>

mapped-name is required for jdbc/juddiDB of deployment juddi.war
----------------------------------------------------------------

                 Key: JBAS-4929
                 URL: http://jira.jboss.com/jira/browse/JBAS-4929
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:37:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:37:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4929) mapped-name is
 required for jdbc/juddiDB of deployment juddi.war
In-Reply-To: <548500.1193772824675.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24618239.1193773064754.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4929?page=all ]

Thomas Diesler updated JBAS-4929:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
When you deploy

http://repository.jboss.com/jboss/jaxr/1.2.0.GA/lib/juddi-service.sar

you get

20:22:46,758 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
20:22:46,779 ERROR [BaseModelMBean] Exception invoking method addChild
java.lang.RuntimeException: mapped-name is required for jdbc/juddiDB of deployment juddi.war
        at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:130)
        at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:212)
        at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:343)

         Assignee: Carlo de Wolf

> mapped-name is required for jdbc/juddiDB of deployment juddi.war
> ----------------------------------------------------------------
>
>                 Key: JBAS-4929
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4929
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> When you deploy
> http://repository.jboss.com/jboss/jaxr/1.2.0.GA/lib/juddi-service.sar
> you get
> 20:22:46,758 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
> 20:22:46,779 ERROR [BaseModelMBean] Exception invoking method addChild
> java.lang.RuntimeException: mapped-name is required for jdbc/juddiDB of deployment juddi.war
>         at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:130)
>         at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:212)
>         at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:343)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:36:09 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 15:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28905516.1193772969221.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4926?page=all ]

Scott M Stark reopened JBAS-4926:
---------------------------------

             
This fails to identify deployments that should fail as failing. What is the real issue with this exception? Why shouldn't the ear deployment be failing?


> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:46:09 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:46:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <597914.1193773569491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385164 ] 
            
Thomas Diesler commented on JBAS-4926:
--------------------------------------

If I do not have the juddi-service.sar deployed i.e. there is no failed deployment because of [JBAS-4929]
then the ear deployment does not fail either.

Also, the junit output contains a list of all failed deployments for every test. This prevents junit-reports because of the xml volume to process.
Is it not enough to list the deployment as failed when it actually is deployed for the first time?





> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:55:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 15:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25464925.1193774144718.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385166 ] 
            
Scott M Stark commented on JBAS-4926:
-------------------------------------

Ok, then the real problem for this issue is that the checkIncomplete(Deployment) call is not working.


> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 16:16:45 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 30 Oct 2007 16:16:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1092)
 <load-balance-policy> does not override annotation
In-Reply-To: <17076593.1193766481412.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23067018.1193775405296.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1092?page=all ]

William DeCoste closed EJBTHREE-1092.
-------------------------------------

    Resolution: Rejected

Works fine - user's jboss.xml was invalid and did not reference the schema.

> <load-balance-policy> does not override annotation
> --------------------------------------------------
>
>                 Key: EJBTHREE-1092
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1092
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            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

        


From jira-events at lists.jboss.org  Tue Oct 30 16:20:44 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 30 Oct 2007 16:20:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1093) create tutorial
 for validating jboss.xml
Message-ID: <29220382.1193775644586.JavaMail.jira@cloud.prod.atl2.jboss.com>

create tutorial for validating jboss.xml
----------------------------------------

                 Key: EJBTHREE-1093
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1093
             Project: EJB 3.0
          Issue Type: Task
          Components: Documentation
            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

        


From jira-events at lists.jboss.org  Tue Oct 30 17:06:45 2007
From: jira-events at lists.jboss.org (Mike Clark (JIRA))
Date: Tue, 30 Oct 2007 17:06:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1128) Message not
 routed from one node to node with only consumer.
Message-ID: <15994322.1193778405017.JavaMail.jira@cloud.prod.atl2.jboss.com>

Message not routed from one node to node with only consumer.
------------------------------------------------------------

                 Key: JBMESSAGING-1128
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
            Reporter: Mike Clark
         Assigned To: Tim Fox


In trying to reproduce behavior described in case 18885, I can reproduce the following:

Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.

Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)

Both instances were created from a clean "all" instance.


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 18:44:44 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 18:44:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22150810.1193784284685.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1062.
-------------------------------------------

    Resolution: Done

Merged tests and fix w/ Branch_4_2

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 19:04:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 30 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10951676.1193785441337.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12385176 ] 
            
Ronald van Kuijk commented on GPD-169:
--------------------------------------

is the head used in the nightly builds of jbosstools? 

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 19:28:44 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 30 Oct 2007 19:28:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14699049.1193786924767.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12385178 ] 
            
Koen Aers commented on GPD-169:
-------------------------------

i am not sure, i will ping marshall about it

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 19:39:44 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Tue, 30 Oct 2007 19:39:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMICROCONT-187) Complete the
 single deployment api
In-Reply-To: <3044720.1183400757621.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9612966.1193787584681.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-187?page=all ]

Ales Justin reassigned JBMICROCONT-187:
---------------------------------------

    Assignee: Ales Justin  (was: Adrian Brock)

> Complete the single deployment api
> ----------------------------------
>
>                 Key: JBMICROCONT-187
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-187
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Deployment
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>             Fix For: JBossMC-2.0.0.GA
>
>
> The single deployment api needs finishing.
> 1) deploy()/undeploy() on the DeployerClient/MainDeployer need making threadsafe such
> that they only do work on the deployment passed a parameter
> 2) The incomplete checking for a single deployment needs to "know" look at only those microcontainer
> contexts that it created (+ those contexts/deployments referenced as dependencies).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 22:25:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 22:25:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4929) mapped-name is
 required for jdbc/juddiDB of deployment juddi.war
In-Reply-To: <548500.1193772824675.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19082183.1193797544630.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4929?page=all ]

Scott M Stark resolved JBAS-4929.
---------------------------------

    Resolution: Done

> mapped-name is required for jdbc/juddiDB of deployment juddi.war
> ----------------------------------------------------------------
>
>                 Key: JBAS-4929
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4929
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> When you deploy
> http://repository.jboss.com/jboss/jaxr/1.2.0.GA/lib/juddi-service.sar
> you get
> 20:22:46,758 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
> 20:22:46,779 ERROR [BaseModelMBean] Exception invoking method addChild
> java.lang.RuntimeException: mapped-name is required for jdbc/juddiDB of deployment juddi.war
>         at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:130)
>         at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:212)
>         at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:343)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 22:50:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 22:50:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4922) NPE in
 AssemblyDescriptorMetaData
In-Reply-To: <21462601.1193741590212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15004566.1193799044658.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4922?page=all ]

Scott M Stark resolved JBAS-4922.
---------------------------------

    Resolution: Done

Fixed in jboss-metadata.jar snapshot rev 1721

> NPE in AssemblyDescriptorMetaData
> ---------------------------------
>
>                 Key: JBAS-4922
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4922
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> 11:47:39,226 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=ejb/ConfidentialSLSB,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at org.jboss.metadata.AssemblyDescriptorMetaData.getPrincipalVersusRolesMap(AssemblyDescriptorMetaData.java:126)
>         at org.jboss.ejb.plugins.SecurityInterceptor.setContainer(SecurityInterceptor.java:132)
>         at org.jboss.ejb.SessionContainer.createInterceptors(SessionContainer.java:374)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:182)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:267)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
>         at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 23:43:45 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 23:43:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28915121.1193802225374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4915?page=all ]

Scott M Stark resolved JBAS-4915.
---------------------------------

    Resolution: Done

Resolved by jboss-metadata.jar snapshot rev 1722

> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 23:49:48 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 23:49:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12150656.1193802588046.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385194 ] 
            
Scott M Stark commented on JBAS-4914:
-------------------------------------

When I run the test, it does not try to deploy anything or run any test:

[starksm at succubus jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase

...

bs/jaxrpc-samples-jsr109ejb-rpc-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109ejb-doc.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109ejb-doc-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-rpc.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-rpc-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-doc.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-doc-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-message.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-message-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-mtom.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-mtom-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-oneway.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-oneway-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-rpcstyle.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-rpcstyle-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-secureejb.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-secureejb-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-swa.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-swa-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-store-pass-encrypt.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-store-pass-encrypt-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wsbpel-hello.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wsbpel-hello-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-sign.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-sign-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-encrypt.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-encrypt-client.jar

build-jars-jaxws:
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-benchmark-doclit.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/ri-benchmark-doclit.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-complex.war
    [unjar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.jar into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.jar
    [unwar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.war into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.war
    [unwar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.war into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.sar/jaxws-jbws1762-exploded.war
    [unwar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.war into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.ear/jaxws-jbws1762-exploded.war
    [unjar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.jar into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.ear/jaxws-jbws1762-exploded.jar

build-interop-jars:
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop-BaseDataTypesDocLitB.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop-BaseDataTypesDocLitW.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop-BaseDataTypesRpcLit.war
      [ear] Building ear: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop.ear

build-samples-jaxws:
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-secure-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-override-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecurity-encrypt.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecurity-sign.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecurityAnnotatedpolicy-encrypt.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecuritypolicy-encrypt.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-secure-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-override-client.jar

build-jars-jaxws:

tests-main:

most:

main:

BUILD SUCCESSFUL
Total time: 23 seconds
[starksm at succubus jbossws-native-2.0.2]$



> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 01:13:44 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 31 Oct 2007 01:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11053624.1193807624765.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385200 ] 
            
Anil Saldhana commented on JBAS-4914:
-------------------------------------

Scott, I have seen this.  You need to add "one-test" at the end.

This has worked last time I did:
a)  ant deploy-jboss500
b) Start JBoss
c) ant -Dtest=fqn one-test


> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 02:57:06 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 02:57:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17084263.1193813826663.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385205 ] 
            
Scott M Stark commented on JBAS-4914:
-------------------------------------

Ok, I get further, but something is still not built correctly as the reports output shows the test class is not found. This is after I have run ant and ant tests-compile.

Testsuite: org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec

   Caused an ERROR
org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.samples.context.WebSer
viceContextJSETestCase
   at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
   at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:164)


> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 03:19:54 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 03:19:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19158649.1193815194791.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12385207 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

CoyoteInvoker.event() is defined:

   public boolean event(Request arg0, Response arg1, SocketStatus arg2) throws Exception;

but org.apache.tomcat.util.net.SocketStatus is an enum that does not exist in tomcat.  To get around the problem, I've created an interface org.apache.tomcat.util.net.SocketStatus, put it in tomcat-addenda.jar, and put tomcat-addenda.jar in .../lib/apache-tomcat.  This way, a SocketStatus will be available if apache-tomcat/*.jar's are on the classpath.

Also, I've changed the definition of the classpaths in build.xml so that the tomcat jars are included if jdk is 1.4, and jbossweb.jar is included if jdk is 1.5.

Note:  test in build.xml should be jdk 1.5 or greater.

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 03:41:54 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 03:41:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1094) Update wiki page
 "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
Message-ID: <816416.1193816514805.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
---------------------------------------------------------------------

                 Key: EJBTHREE-1094
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1094
             Project: EJB 3.0
          Issue Type: Task
          Components: Documentation
            Reporter: Ron Sigal


1. As of Remoting 2.2.x, the Object Name of the org.jboss.remoting.transport.servlet.ServerServletInvoker is hard coded as "jboss.remoting:service=invoker,transport=servlet", which means that only a single instance of ServerServletInvoker can be created.  That would be a problem if, say, EJB3 and JBossMessaging both wanted to use the servlet transport.

As of Remoting 2.4.0, the Object Name will be generated by org.jboss.remoting.ServerInvoker.getMBeanObjectName(), which adds values for "host", "port", and any other parameters on the InvokerLocator.  For example, the Object Name for the ServerServletInvoker in the example is now

   jboss.remoting:service=invoker,transport=servlet,host=127.0.0.1,port=8080

2. While the https example works for org.apache.coyote.http11.Http11Protocol (the non-native version), it doesn't seem to work with org.apache.coyote.http11.Http11AprProtocol.  It seems that jbossweb wants keystores in openssl PEM format.  I must be missing something, though, because I couldn't get it to work with APR.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 03:58:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 03:58:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29584948.1193817524668.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385210 ] 
            
Ron Sigal commented on JBREM-675:
---------------------------------

There seem to be three changes in the attached ServletServerInvoker:

1. The MBean Object Name is no longer hard coded.
2. Leasing information is added to responses.
3. Response code 200 is used instead of 204 to avoid a null response.

ServletServerInvoker has been updated as follows:

1. The ServletServerInvoker.getMBeanObjectName() method is deleted, so that org.jboss.remoting.ServerInvoker.getMBeanObjectName() is called instead.  The latter adds values for "port", "host", and all parameters that appear in the InvokerLocator. 

2. Leasing is handled by ServerInvoker and doesn't need to be handled by ServletServerInvoker.

3. The response code issue has been fixed along the lines of the treatment in org.jboss.remoting.transport.coyote.CoyoteInvoker.  That is, if the request did not come from org.jboss.remoting.transport.http.HTTPClientInvoker or the request method was PUT, then 204 is used for a null response.  Otherwise, 200 is used.

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:08:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 04:08:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1052) When running
 stress tests wrong log4j.xml is picked up
In-Reply-To: <10580807.1187882838240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19049657.1193818124743.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1052?page=all ]

Tim Fox reopened JBMESSAGING-1052:
----------------------------------

             
It's still picking up the wrong one from tests/etc

> When running stress tests wrong log4j.xml is picked up
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-1052
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used.
> This means stress tests are being run on trace logging, which is incorrect (makes them take ages)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:08:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 04:08:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1052) When running
 stress tests wrong log4j.xml is picked up
In-Reply-To: <10580807.1187882838240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31407497.1193818124920.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1052?page=all ]

Tim Fox reassigned JBMESSAGING-1052:
------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> When running stress tests wrong log4j.xml is picked up
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-1052
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: EAP 4.3 Integration
>
>
> When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used.
> This means stress tests are being run on trace logging, which is incorrect (makes them take ages)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:08:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 04:08:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1052) When running
 stress tests wrong log4j.xml is picked up
In-Reply-To: <10580807.1187882838240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8595723.1193818125106.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1052?page=all ]

Tim Fox updated JBMESSAGING-1052:
---------------------------------

    Fix Version/s: EAP 4.3 Integration
                       (was: 1.4.0.CR2)
         Priority: Minor  (was: Major)

> When running stress tests wrong log4j.xml is picked up
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-1052
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: EAP 4.3 Integration
>
>
> When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used.
> This means stress tests are being run on trace logging, which is incorrect (makes them take ages)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:26:49 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 04:26:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27762249.1193819209668.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385215 ] 
            
Thomas Diesler commented on JBAS-4914:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers

You will need to comment this

# [JBAS-4890] EJBAccessException: Caller unauthorized
org/jboss/test/ws/jaxws/samples/context/**


> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:28:44 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 04:28:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7984447.1193819324604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

Updated the snapshot.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:33:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 04:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27553144.1193819624736.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385217 ] 
            
Thomas Diesler commented on JBAS-4914:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers

You will need to comment this

# [JBAS-4890] EJBAccessException: Caller unauthorized
org/jboss/test/ws/jaxws/samples/context/**

before you run tests-main

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:33:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 04:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18247574.1193819624920.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Thomas Diesler updated JBAS-4914:
---------------------------------

    Comment: was deleted

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:06:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 05:06:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22866124.1193821604724.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=all ]

Thomas Heute updated JBPORTAL-1773:
-----------------------------------

    Assignee: Julien Viet  (was: Thomas Heute)

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: sample-portlet.war
>
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:13:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4930) Cannot lookup ejb3
	remote proxy
Message-ID: <16096432.1193822024649.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot lookup ejb3 remote proxy
-------------------------------

                 Key: JBAS-4930
                 URL: http://jira.jboss.com/jira/browse/JBAS-4930
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:15:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:15:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4930) Cannot lookup ejb3
	remote proxy
In-Reply-To: <16096432.1193822024649.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5192444.1193822144652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4930?page=all ]

Thomas Diesler updated JBAS-4930:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test

one-test:
    [mkdir] Created dir: /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/reports
    [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 3.901 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED

Testcase: testEJBClient took 0.023 sec
        Caused an ERROR
ejb not bound
javax.naming.NameNotFoundException: ejb not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
        at sun.rmi.transport.Transport$1.run(Transport.java:153)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
        at java.lang.Thread.run(Thread.java:595)
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
        at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
        at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
        at $Proxy0.lookup(Unknown Source)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.testEJBClient(ServiceRefEJBTestCase.java:86)


@Remote(EJBRemote.class)
@RemoteBinding(jndiBinding = "/ejb/EJBClient")
@Stateless

public class EJBClient 
{
   ...
}

   public void testEJBClient() throws Exception
   {      
      // JAXWS <service-ref> is only supported in EE5 
      if (isTargetJBoss50())
      {
         InitialContext iniCtx = getInitialContext();
         EJBRemote ejbRemote = (EJBRemote)iniCtx.lookup("/ejb/EJBClient");

         String helloWorld = "Hello World!";
         Object retObj = ejbRemote.echo(helloWorld);
         assertEquals(helloWorld, retObj);
      }
   }


         Assignee: Carlo de Wolf

> Cannot lookup ejb3 remote proxy
> -------------------------------
>
>                 Key: JBAS-4930
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4930
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
> one-test:
>     [mkdir] Created dir: /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/reports
>     [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 3.901 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
> Testcase: testEJBClient took 0.023 sec
>         Caused an ERROR
> ejb not bound
> javax.naming.NameNotFoundException: ejb not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
>         at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
>         at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
>         at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
>         at $Proxy0.lookup(Unknown Source)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.testEJBClient(ServiceRefEJBTestCase.java:86)
> @Remote(EJBRemote.class)
> @RemoteBinding(jndiBinding = "/ejb/EJBClient")
> @Stateless
> public class EJBClient 
> {
>    ...
> }
>    public void testEJBClient() throws Exception
>    {      
>       // JAXWS <service-ref> is only supported in EE5 
>       if (isTargetJBoss50())
>       {
>          InitialContext iniCtx = getInitialContext();
>          EJBRemote ejbRemote = (EJBRemote)iniCtx.lookup("/ejb/EJBClient");
>          String helloWorld = "Hello World!";
>          Object retObj = ejbRemote.echo(helloWorld);
>          assertEquals(helloWorld, retObj);
>       }
>    }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:29:44 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Wed, 31 Oct 2007 05:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18058595.1193822984596.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4823?page=comments#action_12385220 ] 
            
Luc Texier commented on JBAS-4823:
----------------------------------

The JBoss Frontline Team has now completed the review of this manual



> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:32:42 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Wed, 31 Oct 2007 05:32:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25985015.1193823162744.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12385221 ] 
            
Luc Texier commented on JBAS-4819:
----------------------------------

The JBoss Frontline Team has now completed the review of this manual

> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:38:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:38:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBXB-112) Failed to create a
	new SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13375090.1193823524658.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Thomas Diesler reopened JBXB-112:
---------------------------------

             
Did you update repository.jboss.org/jboss/jbossxb/snapshot as well?

[tdiesler at tddell snapshot]$ svn info
Path: .
URL: https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossxb/snapshot
Repository Root: https://svn.jboss.org/repos/repository.jboss.org
Repository UUID: 51ec34b3-9f2d-0410-9c14-dfb4b5b5928d
Revision: 1724
Node Kind: directory
Schedule: normal
Last Changed Author: scott.stark at jboss.org
Last Changed Rev: 1654
Last Changed Date: 2007-10-25 07:06:07 +0200 (Thu, 25 Oct 2007)


> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:46:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:46:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4931) Fix ejb3
	ClientLaucher
Message-ID: <32592692.1193824004672.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix ejb3 ClientLaucher
----------------------

                 Key: JBAS-4931
                 URL: http://jira.jboss.com/jira/browse/JBAS-4931
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:48:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:48:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4931) Fix ejb3
	ClientLaucher
In-Reply-To: <32592692.1193824004672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7321225.1193824124814.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4931?page=all ]

Thomas Diesler updated JBAS-4931:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase 

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.82 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED

java.lang.RuntimeException: NYI
        at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:116)
        at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:99)
        at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:186)
        at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)

         Assignee: Carlo de Wolf

> Fix ejb3 ClientLaucher
> ----------------------
>
>                 Key: JBAS-4931
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4931
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.82 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED
> java.lang.RuntimeException: NYI
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:116)
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:99)
>         at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:186)
>         at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:54:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:54:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6150444.1193824485163.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler updated JBAS-4924:
---------------------------------

    Assignee: Carlo de Wolf  (was: Thomas Diesler)

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29316220.1193824605489.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4900?page=comments#action_12385229 ] 
            
Thomas Diesler commented on JBAS-4900:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2759577.1193824605846.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4901?page=comments#action_12385230 ] 
            
Thomas Diesler commented on JBAS-4901:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Ales Justin
>             Fix For: JBossAS-5.0.0.CR1
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1180764.1193824606020.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12385231 ] 
            
Thomas Diesler commented on JBAS-4902:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4903) EJB 2.1 view
	cannot be realized
In-Reply-To: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3163056.1193824606199.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4903?page=comments#action_12385232 ] 
            
Thomas Diesler commented on JBAS-4903:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> EJB 2.1 view cannot be realized
> -------------------------------
>
>                 Key: JBAS-4903
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Andrew Lee Rubinger
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test
> 19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
> 19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
> 19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
> 19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
> java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
>         at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
>         at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
>         at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)
> @WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
> @WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> @Remote(EJB3RemoteInterface.class)
> @RemoteHome(EJB3RemoteHome.class)
> @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
> @Stateless(name = "FooBean01")
> public class EJB3Bean01 implements EJB3RemoteInterface
> {
>    @WebMethod
>    public String echo(String input)
>    {
>       return input;
>    }
> }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14669290.1193824606353.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4923?page=comments#action_12385233 ] 
            
Thomas Diesler commented on JBAS-4923:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23805245.1193824606523.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4924?page=comments#action_12385234 ] 
            
Thomas Diesler commented on JBAS-4924:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:58:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:58:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15224889.1193824724789.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385235 ] 
            
Thomas Diesler commented on JBAS-4926:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:58:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4930) Cannot lookup ejb3
	remote proxy
In-Reply-To: <16096432.1193822024649.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13109645.1193824725202.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4930?page=comments#action_12385236 ] 
            
Thomas Diesler commented on JBAS-4930:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> Cannot lookup ejb3 remote proxy
> -------------------------------
>
>                 Key: JBAS-4930
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4930
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
> one-test:
>     [mkdir] Created dir: /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/reports
>     [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 3.901 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
> Testcase: testEJBClient took 0.023 sec
>         Caused an ERROR
> ejb not bound
> javax.naming.NameNotFoundException: ejb not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
>         at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
>         at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
>         at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
>         at $Proxy0.lookup(Unknown Source)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.testEJBClient(ServiceRefEJBTestCase.java:86)
> @Remote(EJBRemote.class)
> @RemoteBinding(jndiBinding = "/ejb/EJBClient")
> @Stateless
> public class EJBClient 
> {
>    ...
> }
>    public void testEJBClient() throws Exception
>    {      
>       // JAXWS <service-ref> is only supported in EE5 
>       if (isTargetJBoss50())
>       {
>          InitialContext iniCtx = getInitialContext();
>          EJBRemote ejbRemote = (EJBRemote)iniCtx.lookup("/ejb/EJBClient");
>          String helloWorld = "Hello World!";
>          Object retObj = ejbRemote.echo(helloWorld);
>          assertEquals(helloWorld, retObj);
>       }
>    }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:58:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4931) Fix ejb3
	ClientLaucher
In-Reply-To: <32592692.1193824004672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7809336.1193824725370.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4931?page=comments#action_12385237 ] 
            
Thomas Diesler commented on JBAS-4931:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> Fix ejb3 ClientLaucher
> ----------------------
>
>                 Key: JBAS-4931
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4931
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.82 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED
> java.lang.RuntimeException: NYI
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:116)
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:99)
>         at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:186)
>         at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:20:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:20:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4932) Failed
 testRoleSecuredServiceAccess
Message-ID: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failed testRoleSecuredServiceAccess
-----------------------------------

                 Key: JBAS-4932
                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:22:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:22:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4932) Failed
 testRoleSecuredServiceAccess
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21842646.1193826164662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler updated JBAS-4932:
---------------------------------

    Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
    [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
    [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
    [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED

11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
java.rmi.AccessException: SecurityException; nested exception is: 
        java.lang.SecurityException: Denied: caller with subject=Subject:
        Principal: anonymous
        Principal: Roles(members)
 and security context post-mapping roles=Roles(members)
        at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
        at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
        at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
        at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
        at org.jboss.ejb.Container.invoke(Container.java:1013)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
        at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)


> Failed testRoleSecuredServiceAccess
> -----------------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:22:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:22:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4932) Failed
 testRoleSecuredServiceAccess
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10748819.1193826164842.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler updated JBAS-4932:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
         Assignee: Scott M Stark

> Failed testRoleSecuredServiceAccess
> -----------------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:34:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:34:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4932) Invalid principal:
	anonymous
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33118710.1193826884820.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler updated JBAS-4932:
---------------------------------

    Summary: Invalid principal: anonymous  (was: Failed testRoleSecuredServiceAccess)

> Invalid principal: anonymous
> ----------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:38:45 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 06:38:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-486) Optimize
	activations
Message-ID: <26176923.1193827125055.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-486?page=all ]

Manik Surtani updated JBCACHE-486:
----------------------------------

    Fix Version/s:     (was: 2.1.0.CR1)

> Optimize activations
> --------------------
>
>                 Key: JBCACHE-486
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-486
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.3.0.GA
>            Reporter: Jerry Gauthier
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA
>
>
> JBCACHE-420 notes that activation processing is performed excessively.  The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue.
> The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor.  Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated.  This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination.  This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader).
> It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance.  One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__
> to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when
> activated.  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:41:44 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 06:41:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-474) Compatibility fwk
 for all classes passed on the wire
Message-ID: <15960100.1193827304970.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-474?page=all ]

Manik Surtani updated JBCACHE-474:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> Compatibility fwk for all classes passed on the wire
> ----------------------------------------------------
>
>                 Key: JBCACHE-474
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-474
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.4SP1
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> Classes that are serialized:
> Fqn
> MethodCall (JG?)
> *Exception
> GlobalTransaction
> State transfers
> 1) Lets use JGroups Streamable where possible (dependency?  Externalizable instead?)
> 2) Provide a header short containing version
> 3) Use a MarshallingFactory for each version so we can understand messages from older installations
> 4) Provide MarshallingFactories as plugins so old versions can talk to newer versions (fwd compat)
> Object unmarshal(short version, Class type, InputStream is)
> {
> 	// if plugin directory empty or unset || version == currentVersion, revert back to existing mechanism
> 	// else
> 	// Look up UnmarshallerPlugin in the compat table (populated at startup with the contents of the plugin dir)
> 	// Lookup based on version and class type.  Unmarshaller then extracts and regenerates the relevant object.
> }
> Unit test as well.
> Standalone fwk?  jboss-compat.jar + plugins.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:45:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:45:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4932) Invalid principal:
	anonymous
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18435992.1193827545039.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler reassigned JBAS-4932:
------------------------------------

    Assignee: Anil Saldhana  (was: Scott M Stark)

> Invalid principal: anonymous
> ----------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:52:44 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 06:52:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1207) Investigate
 failures in StateTransferUnderLoadTest
Message-ID: <31639318.1193827964640.JavaMail.jira@cloud.prod.atl2.jboss.com>

Investigate failures in StateTransferUnderLoadTest
--------------------------------------------------

                 Key: JBCACHE-1207
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1207
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Manik Surtani
         Assigned To: Vladimir Blagojevic
             Fix For: 2.1.0.GA


This involves attempting to transfer state while having several concurrent put operations that *seem* to result in:

1) A block being issued
2) The put operation holding locks on the state generator
3) The put not being able to complete because of the block
4) The state transfer not being able to generate state because of the put operation
5) Deadlock!


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 07:58:45 2007
From: jira-events at lists.jboss.org (Shiva Shankar Reddy (JIRA))
Date: Wed, 31 Oct 2007 07:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1310)
 java.lang.NullPointerException at
 org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
Message-ID: <14615917.1193831925460.JavaMail.jira@cloud.prod.atl2.jboss.com>

java.lang.NullPointerException at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
-----------------------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1310
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1310
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.3
         Environment: OS: Windows
hardware : Pentium Duo Core2,
Server: JBOSS4.X
Drools: 4.0.3
            Reporter: Shiva Shankar Reddy


when i am using  drools 3.x jars then rules are getting fired in a proper manner and working perfectly.
I have tried to migrate from 3.x to 4.0.3 then i am getting the following error.
I have tried changing jars and so on....  
2007-10-31 16:20:48,120 ERROR [STDERR] java.lang.NullPointerException
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.remote.rules.RulesEngineInvoker.readRule(RulesEngineInvoker.java :103)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.RuleService.doProcess(RuleService.java:318)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.invokeRuleService (FetchFSSData.java:140)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.triggerData(FetchFSSData.java:68)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData$1.run (FetchFSSData.java:84)
2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:00:44 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 08:00:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21454106.1193832044584.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

Now I did. Sorry, I didn't know you meant that one.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:27:58 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 31 Oct 2007 08:27:58 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-107) The different types
 of classloader
 integration for AOP belong in the related release not jboss-head
Message-ID: <20303922.1193833678405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan closed JBAOP-107.
----------------------------

    Resolution: Done

Done for JBoss 5, AS 4 will remain as-is

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:29:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 08:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1730)
 IdentityServiceControllerImpl : unregister existing MBean service before to
 re register them
In-Reply-To: <4337065.1191178121268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31028698.1193833784966.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=all ]

Thomas Heute resolved JBPORTAL-1730.
------------------------------------

    Resolution: Done

> IdentityServiceControllerImpl : unregister existing MBean service before to re register them
> --------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1730
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
> the Identity Beans are registered as JMX MBeans.
> When redeploying the service, an exception is thrown, as the services are yet deployed.
> javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
> Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
> // Unregister the former service is if it is yet there.
> // This to avoid the exception when redeploying this service
> if (getServer().isRegistered(
> 		new ObjectName(module.getServiceName()))) {
> 	getServer().unregisterMBean(
> 			new ObjectName(module.getServiceName()));
> }
> Thanks,

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:31:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 08:31:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1730)
 IdentityServiceControllerImpl : unregister existing MBean service before to
 re register them
In-Reply-To: <4337065.1191178121268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7636610.1193833904647.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=comments#action_12385252 ] 
            
Thomas Heute commented on JBPORTAL-1730:
----------------------------------------

Thanks

> IdentityServiceControllerImpl : unregister existing MBean service before to re register them
> --------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1730
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
> the Identity Beans are registered as JMX MBeans.
> When redeploying the service, an exception is thrown, as the services are yet deployed.
> javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
> Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
> // Unregister the former service is if it is yet there.
> // This to avoid the exception when redeploying this service
> if (getServer().isRegistered(
> 		new ObjectName(module.getServiceName()))) {
> 	getServer().unregisterMBean(
> 			new ObjectName(module.getServiceName()));
> }
> Thanks,

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:13:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 09:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1597) i18n display
 name for portlet instances
In-Reply-To: <18247414.1184788607107.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31188280.1193836424641.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1597?page=all ]

Thomas Heute resolved JBPORTAL-1597.
------------------------------------

    Resolution: Done

> i18n display name for portlet instances
> ---------------------------------------
>
>                 Key: JBPORTAL-1597
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1597
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:19:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 09:19:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1736) Site structure
	i18n
In-Reply-To: <11410482.1191924963437.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17337815.1193836784886.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1736?page=all ]

Thomas Heute updated JBPORTAL-1736:
-----------------------------------

    Assignee: Thomas Heute  (was: Julien Viet)

> Site structure i18n
> -------------------
>
>                 Key: JBPORTAL-1736
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1736
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Portals, pages and windows (portal objects) should be i18nable. (So far only pages are, and not in a good manner)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:52:48 2007
From: jira-events at lists.jboss.org (Martin Trummer (JIRA))
Date: Wed, 31 Oct 2007 09:52:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4426) ADF integration!
In-Reply-To: <26955948.1179389152212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2347994.1193838768491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4426?page=comments#action_12385281 ] 
            
Martin Trummer commented on JBAS-4426:
--------------------------------------

make sure that you do not have the same library twice.
I got the same error, because I had 2 different versions of the same library (jsf-impl.jar):
* one in my .war archive under WEB-INF/lib
* the other one in jboss-4.2.0.GA\server\default\deploy\jboss-web.deployer\jsf-libs

removing the library from my .war archive fixed it

> ADF integration!
> ----------------
>
>                 Key: JBAS-4426
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4426
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: ADF components from Oracle!
>            Reporter: Cristian Olaru
>
> When I deploy an application with ADF components inside I get this exception:
> 10:51:34,213 ERROR [[/aplicatie_test]] Exception thrown by attributes event listener
> java.lang.ClassCastException: com.sun.faces.application.ApplicationAssociate cannot be cast to com.sun.faces.application.ApplicationAssociate
>         at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:180)
>         at com.sun.faces.application.WebappLifecycleListener.getAssociate(WebappLifecycleListener.java:289)
>         at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:225)
>         at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:144)
>         at org.apache.catalina.connector.Request.setAttribute(Request.java:1435)
>         at org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:193)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:619)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:58:45 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 31 Oct 2007 09:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1303) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <7852123.1193582641743.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9329218.1193839125333.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1303?page=all ]

Fernando Meyer closed JBRULES-1303.
-----------------------------------

    Resolution: Duplicate Issue

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1303
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1303
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook running Leopard, Eclipse Europa, Java 1.5 (Mac OSX), Drools 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:58:45 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 31 Oct 2007 09:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1304) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <15904136.1193582881635.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27958853.1193839125470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1304?page=all ]

Fernando Meyer closed JBRULES-1304.
-----------------------------------

    Resolution: Duplicate Issue

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1304
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1304
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:58:45 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 31 Oct 2007 09:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1305) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <13001809.1193583241581.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16533027.1193839125600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1305?page=all ]

Fernando Meyer closed JBRULES-1305.
-----------------------------------

    Resolution: Duplicate Issue

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1305
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1305
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306
> browser problems when submitting :(

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:09:44 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 10:09:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1308) getFactHandle
 with equality-based assert behavior
In-Reply-To: <3690771.1193688062726.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18627585.1193839784820.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1308?page=all ]

Edson Tirelli reassigned JBRULES-1308:
--------------------------------------

    Assignee: Edson Tirelli

> getFactHandle with equality-based assert behavior
> -------------------------------------------------
>
>                 Key: JBRULES-1308
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1308
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>            Reporter: Adam Lewandowski
>         Assigned To: Edson Tirelli
>         Attachments: GetFactHandleWithEqualityTest.java
>
>
> If I set my rule base to use equality-based assert behavior, I'm expecting to be able to use the getFactHandle(object) method to retrieve a previously asserted fact by providing an equivalent (by equals() and hashCode()) object as an argument. This appears to not be the case, as AbstractWorkingMemory uses it's identityMap and associated IdentityAssertMapComparator to do the getFactHandle lookup instead of the assertMap and EqualityAssertMapComparator. This causes the lookup to be done with the system hashCode() method and not the overridden version supplied in my fact class. The lookup thus fails and returns null. 
> See attached unit test.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:09:45 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 10:09:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1310)
 java.lang.NullPointerException at
 org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
In-Reply-To: <14615917.1193831925460.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26786757.1193839785978.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1310?page=all ]

Edson Tirelli reassigned JBRULES-1310:
--------------------------------------

    Assignee: Edson Tirelli

> java.lang.NullPointerException at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1310
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1310
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.3
>         Environment: OS: Windows
> hardware : Pentium Duo Core2,
> Server: JBOSS4.X
> Drools: 4.0.3
>            Reporter: Shiva Shankar Reddy
>         Assigned To: Edson Tirelli
>
> when i am using  drools 3.x jars then rules are getting fired in a proper manner and working perfectly.
> I have tried to migrate from 3.x to 4.0.3 then i am getting the following error.
> I have tried changing jars and so on....  
> 2007-10-31 16:20:48,120 ERROR [STDERR] java.lang.NullPointerException
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.remote.rules.RulesEngineInvoker.readRule(RulesEngineInvoker.java :103)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.RuleService.doProcess(RuleService.java:318)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.invokeRuleService (FetchFSSData.java:140)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.triggerData(FetchFSSData.java:68)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData$1.run (FetchFSSData.java:84)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:09:46 2007
From: jira-events at lists.jboss.org (chris effenberger (JIRA))
Date: Wed, 31 Oct 2007 10:09:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (HIBERNATE-72) Use oracle to
 generate the id with the orcle seqence table
In-Reply-To: <13799401.1190037869830.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13603888.1193839786584.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/HIBERNATE-72?page=comments#action_12385285 ] 
            
chris effenberger commented on HIBERNATE-72:
--------------------------------------------

see the TopLink solution for the problem. there is a explanation int his blog:
http://www.it-eye.nl/weblog/2007/06/12/what-i-would-like-to-see-in-jpa-2/


> Use oracle to generate the id with the orcle seqence table
> ----------------------------------------------------------
>
>                 Key: HIBERNATE-72
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-72
>             Project: Hibernate
>          Issue Type: Bug
>         Environment: jboss-4.2.1
>            Reporter: chris effenberger
>         Assigned To: Steve Ebersole
>
> I want to use the ejb3 entity model.
> the PK should generated by the orcle sequence table not by hibernate.
> So I configure me bean with:
>     @GeneratedValue(generator="select")
>     @GenericGenerator(name="select", strategy="select",
>     		parameters = 
>     		{
>     		  @Parameter(name = "key", value = "idstoerung")
>             })
> The following error occurs:
> javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.HibernateException: Unable to resolve property: idstoerung
> 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
> 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> Caused by: javax.persistence.PersistenceException: org.hibernate.HibernateException: Unable to resolve property: idstoerung
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:629)
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:218)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:182)
> 	at de.dillinger.ww.stoerzeit.session.StoerzeitFacadeBean.aktiviereStoerungAn(StoerzeitFacadeBean.java:98)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
> 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
> 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
> 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy5.aktiviereStoerungAn(Unknown Source)
> 	at de.dillinger.ww.stoerzeit.test.TestClient.aktiviereStoerungAn(TestClient.java:90)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> 	at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> 	at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> 	at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71)
> 	at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
> 	at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy5.aktiviereStoerungAn(Unknown Source)
> 	at de.dillinger.ww.stoerzeit.test.TestClient.aktiviereStoerungAn(TestClient.java:90)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> 	at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> 	at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> 	at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71)
> 	at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
> 	at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: org.hibernate.HibernateException: Unable to resolve property: idstoerung
> 	at org.hibernate.tuple.entity.EntityMetamodel.getPropertyIndex(EntityMetamodel.java:439)
> 	at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValue(AbstractEntityTuplizer.java:286)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValue(AbstractEntityPersister.java:3586)
> 	at org.hibernate.id.SelectGenerator$SelectGeneratorDelegate.bindParameters(SelectGenerator.java:116)
> 	at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:54)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2158)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2638)
> 	at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:48)
> 	at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250)
> 	at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:298)
> 	at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181)
> 	at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:107)
> 	at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:131)
> 	at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:87)
> 	at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38)
> 	at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:618)
> 	at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:592)
> 	at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:596)
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:212)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:182)
> 	at de.mycompany.StoerzeitFacadeBean.aktiviereStoerungAn(StoerzeitFacadeBean.java:98)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
> 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
> 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
> 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> This happens when there is no property in the EntityMetamodel. 
> In ejb2.x we have our own class 
> @jboss.entity-command
>    class = "de.mycompany.OracleCreateCommand"
>    name = "oracle-sequence"
> so we become the generated id with the RETURNING
> Is such a configuration possible in EJB3?

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:36:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 10:36:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1737) Themes should
 be able to display text with the correct locale
In-Reply-To: <16743422.1191925098787.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24390644.1193841404690.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1737?page=all ]

Thomas Heute resolved JBPORTAL-1737.
------------------------------------

    Resolution: Won't Fix

> Themes should be able to display text with the correct locale
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1737
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1737
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core, Portal Theme
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Not sure what's the current state 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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:36:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 10:36:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1737) Themes should
 be able to display text with the correct locale
In-Reply-To: <16743422.1191925098787.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13714789.1193841404914.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1737?page=comments#action_12385297 ] 
            
Thomas Heute commented on JBPORTAL-1737:
----------------------------------------

It was actually already the case. The correct locale is passed in the HTTPRequest.

> Themes should be able to display text with the correct locale
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1737
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1737
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core, Portal Theme
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Not sure what's the current state 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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:42:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 10:42:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1129) Change
 default data stack to TCP
Message-ID: <15869414.1193841765690.JavaMail.jira@cloud.prod.atl2.jboss.com>

Change default data stack to TCP
--------------------------------

                 Key: JBMESSAGING-1129
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1129
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


Default data stack is now TCP for better performance in smaller clusters

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:42:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 10:42:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1129) Change default
 data stack to TCP
In-Reply-To: <15869414.1193841765690.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <815780.1193841765975.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1129?page=all ]

Tim Fox closed JBMESSAGING-1129.
--------------------------------

    Resolution: Done

> Change default data stack to TCP
> --------------------------------
>
>                 Key: JBMESSAGING-1129
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1129
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Default data stack is now TCP for better performance in smaller clusters

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:44:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 10:44:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17387060.1193841885301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=all ]

Tim Fox closed JBMESSAGING-1115.
--------------------------------

    Resolution: Won't Fix

Apparently this is because the user is using Spring JMS Template, which creates huge numbers of connections.


> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:06:45 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 31 Oct 2007 11:06:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1094) Update wiki page
 "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
In-Reply-To: <816416.1193816514805.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19528888.1193843205275.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1094?page=all ]

William DeCoste reassigned EJBTHREE-1094:
-----------------------------------------

    Assignee: William DeCoste

> Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
> ---------------------------------------------------------------------
>
>                 Key: EJBTHREE-1094
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1094
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Ron Sigal
>         Assigned To: William DeCoste
>
> 1. As of Remoting 2.2.x, the Object Name of the org.jboss.remoting.transport.servlet.ServerServletInvoker is hard coded as "jboss.remoting:service=invoker,transport=servlet", which means that only a single instance of ServerServletInvoker can be created.  That would be a problem if, say, EJB3 and JBossMessaging both wanted to use the servlet transport.
> As of Remoting 2.4.0, the Object Name will be generated by org.jboss.remoting.ServerInvoker.getMBeanObjectName(), which adds values for "host", "port", and any other parameters on the InvokerLocator.  For example, the Object Name for the ServerServletInvoker in the example is now
>    jboss.remoting:service=invoker,transport=servlet,host=127.0.0.1,port=8080
> 2. While the https example works for org.apache.coyote.http11.Http11Protocol (the non-native version), it doesn't seem to work with org.apache.coyote.http11.Http11AprProtocol.  It seems that jbossweb wants keystores in openssl PEM format.  I must be missing something, though, because I couldn't get it to work with APR.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:13:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 11:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1775) Let a user
 define multiple
 display-name for a portlet-instance in the admin portlet
Message-ID: <27848379.1193843624923.JavaMail.jira@cloud.prod.atl2.jboss.com>

Let a user define multiple display-name for a portlet-instance in the admin portlet
-----------------------------------------------------------------------------------

                 Key: JBPORTAL-1775
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1775
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
            Reporter: Thomas Heute
         Assigned To: Wesley Hales
             Fix For: 2.6.3 Final


When an administrator creates a new portlet-instance, he should be able to define (and edit) different display-names for a single instance.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:15:44 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Wed, 31 Oct 2007 11:15:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (BPEL-282) Engine runs process
 instances in serie instead of in parallel
In-Reply-To: <7870750.1193112683491.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12161805.1193843744898.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-282?page=all ]

Alejandro Guizar updated BPEL-282:
----------------------------------

       Issue Type: Feature Request  (was: Bug)
    Fix Version/s: jBPM BPEL 1.1 GA

> Engine runs process instances in serie instead of in parallel
> -------------------------------------------------------------
>
>                 Key: BPEL-282
>                 URL: http://jira.jboss.com/jira/browse/BPEL-282
>             Project: JBoss jBPM BPEL
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>         Environment: RHEL
>            Reporter: Santiago Erquicia
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> We are stress testing a BPEL process and we found out that the engine runs all the requests it receives in serie. That means that if there are two or more concurrent users of the system, one has to wait till the first process instance stops at some point (wait state) so the other request can be processed.
> On our test environment, we are calling a web service which is also calling another web service. The are connection problems with the second one, so from time to time the web service just times out. This means that a concurrent user has to wait for that time out, and whatever is left of that process instance, in order to be processed.
> On our JMeter test, the throughput keeps stable even if there number of request is bigger than the throughput of the BPEL engine. The result is that the time for response of each process request increases indefinitely if the usage is bigger than the throughput. This obviously doesn't scale at all for the processing requirement we are considering.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:23:58 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Wed, 31 Oct 2007 11:23:58 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1153) Introduce a
 concept of structural nodes
In-Reply-To: <6252571.1185539387065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8166264.1193844238855.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1153?page=all ]

Mircea Markus resolved JBCACHE-1153.
------------------------------------

    Resolution: Won't Fix

as per foru, discussion decided to allow the user to to mark nodes as 'structural' using the resident flag.

> Introduce a concept of structural nodes
> ---------------------------------------
>
>                 Key: JBCACHE-1153
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1153
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.2.0.GA
>
>
> Structural nodes should not be taken into consideration when processing regions for eviction.
> Typically are nodes that do not contain data (and are not intended to contain data), but are used to build tree structure.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:27:45 2007
From: jira-events at lists.jboss.org (Shane Preater (JIRA))
Date: Wed, 31 Oct 2007 11:27:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-933) NPE when
 deploying web service beans
In-Reply-To: <16564123.1175251646383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20738161.1193844465152.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-933?page=comments#action_12385317 ] 
            
Shane Preater commented on EJBTHREE-933:
----------------------------------------

I am getting this exact error when attempting to deploy a local ejb 2.x session bean which is being referenced by an Ejb 3 session bean.

I am using 4.2.1.GA and the stack is thus:

15:22:07,875 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=migrationTesting.jar,na
me=EJB3BusinessInterfaceImplementation,service=EJB3 is not registered
15:22:07,875 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=migrationTesting.jar,na
me=RemoteHomeTest,service=EJB3 is not registered
15:22:07,875 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=migrationTesting.jar,na
me=LocalHomeTest,service=EJB3 is not registered
15:22:08,296 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jbo
ss.ejb3.stateless.StatelessContainer
15:22:08,296 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=migra
tionTesting.jar,name=EJB3BusinessInterfaceImplementation,service=EJB3 with depen
dencies:
15:22:08,296 INFO  [JmxKernelAbstraction]       jboss.j2ee:jar=migrationTesting.
jar,name=LocalHomeTest,service=EJB3
15:22:08,312 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jbo
ss.ejb3.stateless.StatelessContainer
15:22:08,312 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=migra
tionTesting.jar,name=RemoteHomeTest,service=EJB3 with dependencies:
15:22:08,312 INFO  [JmxKernelAbstraction]       jboss.j2ee:jar=migrationTesting.
jar,name=LocalHomeTest,service=EJB3
15:22:08,312 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jbo
ss.ejb3.stateless.StatelessContainer
15:22:08,312 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=migra
tionTesting.jar,name=LocalHomeTest,service=EJB3 with dependencies:
15:22:08,343 INFO  [EJBContainer] STARTED EJB: com.aeroint.ejbtest.server.sessio
n.LocalHomeTestEJB ejbName: LocalHomeTest
15:22:08,343 INFO  [EJBContainer] STOPPED EJB: com.aeroint.ejbtest.server.sessio
n.LocalHomeTestEJB ejbName: LocalHomeTest
15:22:08,359 WARN  [ServiceController] Problem starting service jboss.j2ee:jar=m
igrationTesting.jar,name=LocalHomeTest,service=EJB3
java.lang.NullPointerException
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(St
atelessRemoteProxyFactory.java:75)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStateless
ProxyFactory.java:172)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRe
moteProxyFactory.java:100)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStateles
sProxyFactory.java:221)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessR
emoteProxyFactory.java:107)
        at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
        at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:128)
        at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.
java:94)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWra
pper.java:103)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy66.start(Unknown Source)
        at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java
:120)
        at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.jav
a:301)
        at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:362)
        at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy32.start(Unknown Source)
        at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
        at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
rServiceMBeanSupport.java:238)
        at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerIn
terceptor.java:93)
        at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
start(SubDeployerInterceptorSupport.java:188)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:95)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy33.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy9.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:610)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:274)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:225)
15:22:08,453 INFO  [EJB3Deployer] Deployed: file:/C:/sapphire_system/jboss-4.2.1
.GA/server/default/deploy/migrationTesting.jar
15:22:08,468 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

> NPE when deploying web service beans
> ------------------------------------
>
>                 Key: EJBTHREE-933
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-933
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Heiko Braun
>
> The exception:
> java.lang.NullPointerException
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:74)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:172)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:100)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:221)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107)
>         at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
>         at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94)
> The bean that get's deployed:
> package com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest;
> import javax.ejb.Stateless;
> import javax.jws.WebService;
> @WebService(
>     portName="Hello", 
>     serviceName="HelloService", 
>     targetNamespace="http://Hello.org",
>     wsdlLocation="META-INF/wsdl/HelloService.wsdl",
>     endpointInterface="com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest.Hello")
> @Stateless(name="WSEjbPortFieldInjectionTest")
> public class HelloBean {
>    public String hello(String str)
>    {
>       return "WebSvcTest-Hello " + str;
>    }
>    public String bye(String str)
>    {
>       return "WebSvcTest-Bye and take care " + str;
>    }
> }
> The spec:
> Session bean's business interface(s), if the session bean provides an EJB 3.0 local or remote
> client view.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:31:44 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Wed, 31 Oct 2007 11:31:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-933) NPE when
 deploying web service beans
In-Reply-To: <16564123.1175251646383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3125750.1193844704570.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-933?page=comments#action_12385319 ] 
            
Heiko Braun commented on EJBTHREE-933:
--------------------------------------

Shane, the error you see was fixed upstream. 4.2.1 probably uses an EJB3 version that doesn't contain the fix. However you could workaround by implementing a remote interface on that bean.

> NPE when deploying web service beans
> ------------------------------------
>
>                 Key: EJBTHREE-933
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-933
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Heiko Braun
>
> The exception:
> java.lang.NullPointerException
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:74)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:172)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:100)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:221)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107)
>         at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
>         at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94)
> The bean that get's deployed:
> package com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest;
> import javax.ejb.Stateless;
> import javax.jws.WebService;
> @WebService(
>     portName="Hello", 
>     serviceName="HelloService", 
>     targetNamespace="http://Hello.org",
>     wsdlLocation="META-INF/wsdl/HelloService.wsdl",
>     endpointInterface="com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest.Hello")
> @Stateless(name="WSEjbPortFieldInjectionTest")
> public class HelloBean {
>    public String hello(String str)
>    {
>       return "WebSvcTest-Hello " + str;
>    }
>    public String bye(String str)
>    {
>       return "WebSvcTest-Bye and take care " + str;
>    }
> }
> The spec:
> Session bean's business interface(s), if the session bean provides an EJB 3.0 local or remote
> client view.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:46:14 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 11:46:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28929124.1193845574382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Scott M Stark resolved JBAS-4914.
---------------------------------

    Resolution: Done

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSE
TestCase
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 17.609 sec

BUILD SUCCESSFUL
Total time: 19 seconds
[starksm at valkyrie jbossws-native-2.0.2]$

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:55:44 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 31 Oct 2007 11:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25464989.1193846144842.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12385326 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

Detailed explanation:
- A unicast is received. This acquires a (sender-based) lockin UNICAST on its way up
- When the message is received, the RpcDispatcher sends the large return value back *on the same thread* (the lock in UNICAST is not released)
- FRAG2 splits the return message into many smaller messages
- All messages are sent down, but when max_credits is exceeded, FC.down() blocks. This means the lock in UNICAST is *still* not released
- On the receiver side (sender == receiver), incoming calls cannot reach FC due to the lock in UNICAST (because FC is somewhere above 
  UNICAST), therefore FC will not send new credits (via OOB) to unblock the sender
- The only way credits will be received is for the sender to periodically (max_block_time ms) send an OOB credit request and unblock when it 
  receives the credit response
- However, even OOB messages will not get processed when the default thread pool in TP has the queue *disabled* and all threads are *busy* !

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:01:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:01:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1095)
 ConsumerContainer throws NoInitialContextException on stop
Message-ID: <3234104.1193846504671.JavaMail.jira@cloud.prod.atl2.jboss.com>

ConsumerContainer throws NoInitialContextException on stop
----------------------------------------------------------

                 Key: EJBTHREE-1095
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1095
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf
         Assigned To: Carlo de Wolf
            Priority: Critical
             Fix For: AS 4.2.3.GA


2007-10-31 16:22:11,905 WARN  [org.jboss.ejb3.ServiceDelegateWrapper] Stopping failed jboss.j2ee:jar=consumer-test.jar,name=QueueTestConsumer,service=EJB3
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
	at javax.naming.InitialContext.getNameParser(InitialContext.java:439)
	at org.jboss.util.naming.Util.unbind(Util.java:135)
	at org.jboss.ejb3.mdb.ProducerFactory.stop(ProducerFactory.java:150)
	at org.jboss.ejb3.mdb.RemoteProducerFactory.stop(RemoteProducerFactory.java:99)
	at org.jboss.ejb3.mdb.ConsumerContainer.unregisterProducers(ConsumerContainer.java:286)
	at org.jboss.ejb3.mdb.ConsumerContainer.stop(ConsumerContainer.java:304)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.stop(Unknown Source)
	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy69.stop(Unknown Source)
	at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
	at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
	at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
	at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.stop(Unknown Source)
	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy33.stop(Unknown Source)
	at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
	at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy34.stop(Unknown Source)
	at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
	at sun.rmi.transport.Transport$1.run(Transport.java:153)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
	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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:01:44 2007
From: jira-events at lists.jboss.org (Jason Long (JIRA))
Date: Wed, 31 Oct 2007 12:01:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
Message-ID: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>

Make SLSB and SFSB hot deployable for RAD
-----------------------------------------

                 Key: EJBTHREE-1096
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
             Project: EJB 3.0
          Issue Type: Feature Request
    Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA, AS 5.0.0.Beta3, AS 4.2.3.GA, Branch_4_2, Branch_4_4, HEAD
            Reporter: Jason Long
             Fix For: AS 4.2.3.GA


Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:03:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:03:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1095)
 ConsumerContainer throws NoInitialContextException on stop
In-Reply-To: <3234104.1193846504671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18712043.1193846624608.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1095?page=comments#action_12385333 ] 
            
Carlo de Wolf commented on EJBTHREE-1095:
-----------------------------------------

MessagingContainer.getJMSProviderAdapter closes the context associated with the EJBContainer.

> ConsumerContainer throws NoInitialContextException on stop
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1095
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1095
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.3.GA
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> 2007-10-31 16:22:11,905 WARN  [org.jboss.ejb3.ServiceDelegateWrapper] Stopping failed jboss.j2ee:jar=consumer-test.jar,name=QueueTestConsumer,service=EJB3
> javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> 	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
> 	at javax.naming.InitialContext.getNameParser(InitialContext.java:439)
> 	at org.jboss.util.naming.Util.unbind(Util.java:135)
> 	at org.jboss.ejb3.mdb.ProducerFactory.stop(ProducerFactory.java:150)
> 	at org.jboss.ejb3.mdb.RemoteProducerFactory.stop(RemoteProducerFactory.java:99)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.unregisterProducers(ConsumerContainer.java:286)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.stop(ConsumerContainer.java:304)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy69.stop(Unknown Source)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
> 	at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
> 	at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy33.stop(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy34.stop(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:05:45 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:05:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1097)
 InitialContextFactory doesn't always create a new InitialContext
Message-ID: <25475823.1193846745189.JavaMail.jira@cloud.prod.atl2.jboss.com>

InitialContextFactory doesn't always create a new InitialContext
----------------------------------------------------------------

                 Key: EJBTHREE-1097
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


InitialContextFactory is not really a factory, it doesn't always create a new InitialContext.
This can lead to interesting situations if someone closes an InitialContext which doesn't have any properties and then tries to reuse it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:11:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
In-Reply-To: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31106516.1193847104987.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=all ]

Carlo de Wolf updated EJBTHREE-1096:
------------------------------------

        Fix Version/s:     (was: AS 4.2.3.GA)
    Affects Version/s:     (was: AS 5.0.0.Beta3)
                           (was: AS 4.2.0 GA)
                           (was: AS 4.2.1.GA)
                           (was: Branch_4_2)
                           (was: Branch_4_4)
                           (was: HEAD)
                           (was: AS 4.2.3.GA)

> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
>                 Key: EJBTHREE-1096
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:29:48 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Wed, 31 Oct 2007 12:29:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-609) Javadoc
	JChannelFactory
In-Reply-To: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12962568.1193848188929.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-609?page=comments#action_12385341 ] 
            
Vladimir Blagojevic commented on JGRP-609:
------------------------------------------

Let me know of any further changes you may suggest.

Vladimir


    /**
     * Creates an implementation of the Channel using a given stack name and
     * registering it under a given identity.
     * <p>
     *
     * Channel has to be created with a unique application id per stack name.
     *
     * <p>
     * Provided stack name has to be one of the stacks defined in a property
     * file that was passed to setMultiplexerConfig (e.g conf/stacks.xml). If
     * clients attempt to create a Channel for an undefined stack name or
     * they attempt to register a duplicate Channel per stack an Exception will be
     * thrown.
     *
     *
     * <p>
     * Rather than having each multiplexed channel do a separate state transfer
     * clients can bundle state transfers for all channels created with the same
     * ChannelFactory. First of all, clients have to create Channels with
     * register_for_state_transfer set to true. After the last Channel that was
     * created with register_for_state_transfer set to true connects and
     * initiates state transfer the actual state transfer for all such channels
     * from this ChannelFactory is executed.
     *
     * <p>
     * Using bundled state transfers is especially useful with the FLUSH
     * protocol in a stack. Recall that each state transfer triggers a flush and
     * thus instead of doing a separate flush for each Channel created with this
     * ChannelFactory we execute only one flush for all state transfers.
     *
     * <p>
     * However, be aware of the implication of asynchronous nature of bundled
     * state transfer with the respect of channel connect. Recall that each
     * Channel after it returns from successful getState method can assume that
     * state is available. In case of bundled state transfer, state will be set
     * only <strong>after</strong> the last Channel registered for the bundled
     * state transfer connects and executes getState.
     *
     *
     *
     *
     * @param stack_name
     *            The name of the stack to be used. All stacks are defined in
     *            the configuration with which the factory is configured (see
     *            {@link #setMultiplexerConfig(Object)} for example.
     * @param id
     *            The identifier used for multiplexing and demultiplexing
     *            (dispatching requests to one of possibly multiple receivers).
     *            Note that id needs to be a string since it will be shipped
     *            with each message. Try to pick a short string, because this is
     *            shipped with every message (overhead).
     * @param register_for_state_transfer
     *            If set to true, after all registered listeners called
     *            connect() on the returned Channel, the state for all
     *            registered listeners will be fetched and set in all listeners
     * @param substate_id
     *            The ID of the substate to be retrieved. Set this to null if
     *            the entire state should be retrieved. If
     *            register_for_state_transfer is false, substate_id will be
     *            ignored
     *            
     *            
     * @return An implementation of Channel which keeps track of the id, so that
     *         it can be attached to each message and be properly dispatched at
     *         the receiver.
     *         
     * @see Multiplexer
     * @see MuxChannel
     *         
     * @throws ChannelException
     */

> Javadoc JChannelFactory
> -----------------------
>
>                 Key: JGRP-609
>                 URL: http://jira.jboss.com/jira/browse/JGRP-609
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5.1
>            Reporter: Brian Stansberry
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.5.2, 2.6
>
>
> org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:29:49 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 12:29:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-115) remove use of
 System.out from XsdBinder
Message-ID: <2329678.1193848189064.JavaMail.jira@cloud.prod.atl2.jboss.com>

remove use of System.out from XsdBinder
---------------------------------------

                 Key: JBXB-115
                 URL: http://jira.jboss.com/jira/browse/JBXB-115
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Task
    Affects Versions: JBossXB-1.0.0.SP1
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-1.0.0.SP2


$ svn diff
Index: main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java
===================================================================
--- main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (revision 2639)
+++ main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (working copy)
@@ -852,7 +852,7 @@
             ctx.simpleContentWithIdAsSimpleType &&
             particle == null && hasOnlyIdAttrs)
       {
-         binding.setStartElementCreatesObject(false);System.out.println("no object for " + binding.getQName());
+         binding.setStartElementCreatesObject(false);
       }
       else

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:33:44 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 12:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-115) remove use of
 System.out from XsdBinder
In-Reply-To: <2329678.1193848189064.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27831143.1193848424577.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-115?page=all ]

Alexey Loubyansky closed JBXB-115.
----------------------------------

    Resolution: Done

Fixed.

> remove use of System.out from XsdBinder
> ---------------------------------------
>
>                 Key: JBXB-115
>                 URL: http://jira.jboss.com/jira/browse/JBXB-115
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Task
>    Affects Versions: JBossXB-1.0.0.SP1
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-1.0.0.SP2
>
>
> $ svn diff
> Index: main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java
> ===================================================================
> --- main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (revision 2639)
> +++ main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (working copy)
> @@ -852,7 +852,7 @@
>              ctx.simpleContentWithIdAsSimpleType &&
>              particle == null && hasOnlyIdAttrs)
>        {
> -         binding.setStartElementCreatesObject(false);System.out.println("no object for " + binding.getQName());
> +         binding.setStartElementCreatesObject(false);
>        }
>        else

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:37:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 12:37:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1130) Remove unused
 column INST_TIME
Message-ID: <11935598.1193848664775.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove unused column INST_TIME
------------------------------

                 Key: JBMESSAGING-1130
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1130
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: EAP 4.3 Integration




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:48:49 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 12:48:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20674535.1193849329490.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3885?page=comments#action_12385358 ] 
            
Dimitris Andreadis commented on JBAS-3885:
------------------------------------------

Actually, the problem is that the RMI registry that is created to store the remote object reference for the JMXConnectorServer, binds to all interfaces by default. 

Then the same registry is seen by both servers, and the second registration fails, because the same name is used. 


> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:50:45 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 12:50:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1208) CacheFactory to
 allow creation from InputStreams
Message-ID: <6022219.1193849445024.JavaMail.jira@cloud.prod.atl2.jboss.com>

CacheFactory to allow creation from InputStreams 
-------------------------------------------------

                 Key: JBCACHE-1208
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1208
             Project: JBoss Cache
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:50:45 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 12:50:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1208) CacheFactory to
 allow creation from InputStreams
In-Reply-To: <6022219.1193849445024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23496907.1193849445318.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1208?page=all ]

Manik Surtani resolved JBCACHE-1208.
------------------------------------

    Resolution: Done

> CacheFactory to allow creation from InputStreams 
> -------------------------------------------------
>
>                 Key: JBCACHE-1208
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1208
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:55:44 2007
From: jira-events at lists.jboss.org (Emmanuel Bernard (JIRA))
Date: Wed, 31 Oct 2007 12:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
In-Reply-To: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4216294.1193849744708.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_12385363 ] 
            
Emmanuel Bernard commented on EJBTHREE-1096:
--------------------------------------------

+1

> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
>                 Key: EJBTHREE-1096
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:55:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 12:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1128) Message not
 routed from one node to node with only consumer.
In-Reply-To: <15994322.1193778405017.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23844085.1193849744953.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1128?page=all ]

Tim Fox updated JBMESSAGING-1128:
---------------------------------

    Fix Version/s: EAP 4.3 Integration

> Message not routed from one node to node with only consumer.
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1128
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
>            Reporter: Mike Clark
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> In trying to reproduce behavior described in case 18885, I can reproduce the following:
> Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.
> Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)
> Both instances were created from a clean "all" instance.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:01:44 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 13:01:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1311) NPE when
 compiling rule consequences
Message-ID: <32316553.1193850104902.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE when compiling rule consequences
------------------------------------

                 Key: JBRULES-1311
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1311
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, Rule Assemply/SPI
    Affects Versions: 4.0.3, 4.0.2, 4.0.1,  4.0.0.GA
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.1.0


I have the following code: (note String[] ruleFiles contains only one string)

 

public class Engine {

    private static RuleBase ruleBase;

 

    public void start(String[] ruleFiles) throws Exception {

        PackageBuilderConfiguration cfg = new PackageBuilderConfiguration();

        JavaDialectConfiguration javaConf = (JavaDialectConfiguration) cfg.getDialectConfiguration("java");

        javaConf.setCompiler(JavaDialectConfiguration.ECLIPSE);

        PackageBuilder builder = new PackageBuilder(cfg);

        for (String file : ruleFiles) {

            builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file)));

        }

        Package pkg = builder.getPackage();

 

        PackageBuilderErrors errors = builder.getErrors();

        if (errors.getErrors().length != 0) {

            // do something

        }

 

        RuleBaseConfiguration conf = new RuleBaseConfiguration();

        conf.setAssertBehaviour(RuleBaseConfiguration.AssertBehaviour.EQUALITY);

 

        ruleBase = RuleBaseFactory.newRuleBase();

        ruleBase.addPackage(pkg);

        ruleBase.newStatefulSession(false);

 

    }

}

 

At the builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file))); line I'm getting the following exception:

java.lang.NullPointerException

            at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)

            at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)

            at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)

            at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)

            at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:167)

            at myPackage.rivoli.service.rules.Engine.start(Engine.java:33)

            at myPackage.rivoli.rules.LeaderKingAndHeirTest.setUp(LeaderKingAndHeirTest.java:26)

            at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

            at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)

 

I am using Drools 4.0.3

I have the following jars in my class path:

antlr-runtime-3.0.jar

core-3.2.3.v_686_R32x.jar

drools-compiler-4.0.3.jar

drools-core-4.0.3.jar

mvel14-1.2.10.jar

 

Any ideas would be helpful. Thanks.

 
rule "leaders in same location"

salience 10

when

    $result : RuleResult(rulesPassed not contains "leaders in same location")

    $loc : LocationImpl()

    $leaderName : String()

    $leader1 : LeaderImpl(name == $leaderName, location == $loc)

    $leader2 : LeaderImpl(name != $leaderName, this != $leader1, location == $loc)

then

    $result.addPassedRule(leaders in same location);

    update($result);

end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:03:55 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:03:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4933) Upgrade to jbossxb
 1.0.0.SP2 (from 1.0.0.SP1)
Message-ID: <33091523.1193850235177.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade to jbossxb 1.0.0.SP2 (from 1.0.0.SP1)
---------------------------------------------

                 Key: JBAS-4933
                 URL: http://jira.jboss.com/jira/browse/JBAS-4933
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: XML services
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Dimitris Andreadis
         Assigned To: Dimitris Andreadis
             Fix For: JBossAS-4.2.3.GA


Needed for fixing JBXB-115 (and anything else that pops up).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:17:44 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 13:17:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1311) NPE when compiling
 rule consequences
In-Reply-To: <32316553.1193850104902.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32852680.1193851064866.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1311?page=all ]

Edson Tirelli closed JBRULES-1311.
----------------------------------

    Fix Version/s: 4.0.4
       Resolution: Done

Fixed.

> NPE when compiling rule consequences
> ------------------------------------
>
>                 Key: JBRULES-1311
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1311
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rule Assemply/SPI, Drl Parser/Builder
>    Affects Versions:  4.0.0.GA, 4.0.1, 4.0.2, 4.0.3
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.4, 4.1.0
>
>
> I have the following code: (note String[] ruleFiles contains only one string)
>  
> public class Engine {
>     private static RuleBase ruleBase;
>  
>     public void start(String[] ruleFiles) throws Exception {
>         PackageBuilderConfiguration cfg = new PackageBuilderConfiguration();
>         JavaDialectConfiguration javaConf = (JavaDialectConfiguration) cfg.getDialectConfiguration("java");
>         javaConf.setCompiler(JavaDialectConfiguration.ECLIPSE);
>         PackageBuilder builder = new PackageBuilder(cfg);
>         for (String file : ruleFiles) {
>             builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file)));
>         }
>         Package pkg = builder.getPackage();
>  
>         PackageBuilderErrors errors = builder.getErrors();
>         if (errors.getErrors().length != 0) {
>             // do something
>         }
>  
>         RuleBaseConfiguration conf = new RuleBaseConfiguration();
>         conf.setAssertBehaviour(RuleBaseConfiguration.AssertBehaviour.EQUALITY);
>  
>         ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         ruleBase.newStatefulSession(false);
>  
>     }
> }
>  
> At the builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file))); line I'm getting the following exception:
> java.lang.NullPointerException
>             at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
>             at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
>             at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)
>             at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)
>             at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:167)
>             at myPackage.rivoli.service.rules.Engine.start(Engine.java:33)
>             at myPackage.rivoli.rules.LeaderKingAndHeirTest.setUp(LeaderKingAndHeirTest.java:26)
>             at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
>             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>             at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
>  
> I am using Drools 4.0.3
> I have the following jars in my class path:
> antlr-runtime-3.0.jar
> core-3.2.3.v_686_R32x.jar
> drools-compiler-4.0.3.jar
> drools-core-4.0.3.jar
> mvel14-1.2.10.jar
>  
> Any ideas would be helpful. Thanks.
>  
> rule "leaders in same location"
> salience 10
> when
>     $result : RuleResult(rulesPassed not contains "leaders in same location")
>     $loc : LocationImpl()
>     $leaderName : String()
>     $leader1 : LeaderImpl(name == $leaderName, location == $loc)
>     $leader2 : LeaderImpl(name != $leaderName, this != $leader1, location == $loc)
> then
>     $result.addPassedRule(leaders in same location);
>     update($result);
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:49:44 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:49:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16126743.1193852984635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3885?page=all ]

Dimitris Andreadis closed JBAS-3885.
------------------------------------

    Resolution: Done

Fixed. I can now create 2 servers (e.g. copy the default configuration) and start them up on different ports (-b xx.xx.xx.xx) without them conflicting with each other.

The JMXServiceURL is also printed upon startup. You can point directly a jconsole to it, e.g.:

19:38:03,281 INFO  [JMXConnectorServerService] JMX Connector server:
service:jmx:rmi://192.168.0.22/jndi/rmi://192.168.0.22:1090/jmxconnector

The underlying problem was the the rmi registry was binding all local addresses by default. It required a custom ServerSocketFactory to overcome the limitation.

> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:53:44 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4486) Binding the
 JMXConnector on a multihomed machine
In-Reply-To: <3535628.1181902331660.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23913666.1193853224835.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4486?page=comments#action_12385377 ] 
            
Dimitris Andreadis commented on JBAS-4486:
------------------------------------------

The rmi registry was actually causing the problem. It's fixed at JBAS-3885.

> Binding the JMXConnector on a multihomed machine
> ------------------------------------------------
>
>                 Key: JBAS-4486
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4486
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I am having trouble with a multihome setup.
> Event though I am using dedicated bind addresses the JXMConnector fails
> to start on the second instance. It looks to like as if the bind address
> is just disregarded and instead binds to 0.0.0.0:
> (1) Instance A  (-b 192.168.0.101) started successfully
> (2) Instance B (-b 192.168.0.102) logs:
> 17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL
> [rmi://192.168.0.102:1090/jmxconnector]:
> javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
> java.rmi.AlreadyBoundException: jmxconnector]
>         at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at
> org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
> (3) [tdiesler at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
>                 
>         tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     
> The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:55:44 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4485) JMXConnector always
 binds to the loopback device, regardless of the actual bind address
In-Reply-To: <33166904.1181814258577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15681299.1193853344843.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4485?page=all ]

Dimitris Andreadis updated JBAS-4485:
-------------------------------------

    Component/s: JMX
       Assignee: Dimitris Andreadis

> JMXConnector always binds to the loopback device, regardless of the actual bind address
> ---------------------------------------------------------------------------------------
>
>                 Key: JBAS-4485
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4485
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: URL: https://svn.jboss.org/repos/jbossas/trunk
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 63502
> java version "1.5.0_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
> Linux jbws 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686 i686 i386 GNU/Linux
>            Reporter: Heiko Braun
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I am having trouble with a multihome setup.
> Event though I am using dedicated bind addresses the JXMConnector fails
> to start on the second instance. It looks to like as if the bind address
> is just disregarded and instead binds to to the loopback device
> (1) Instance A  (-b 192.168.0.101) started successfully
> (2) Instance B (-b 192.168.0.102) logs:
> 17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL
> [rmi://192.168.0.102:1090/jmxconnector]:
> javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
> java.rmi.AlreadyBoundException: jmxconnector]
>         at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at
> org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
> (3) [hbraun at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
>                 
>         tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     
> The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.
> As far as i can tell, it pulls the jdk 1.5 JMX implementation.  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:55:45 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4485) JMXConnector always
 binds to the loopback device, regardless of the actual bind address
In-Reply-To: <33166904.1181814258577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24840333.1193853345044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4485?page=all ]

Dimitris Andreadis closed JBAS-4485.
------------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
       Resolution: Done

Should be fixed.

> JMXConnector always binds to the loopback device, regardless of the actual bind address
> ---------------------------------------------------------------------------------------
>
>                 Key: JBAS-4485
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4485
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: URL: https://svn.jboss.org/repos/jbossas/trunk
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 63502
> java version "1.5.0_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
> Linux jbws 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686 i686 i386 GNU/Linux
>            Reporter: Heiko Braun
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I am having trouble with a multihome setup.
> Event though I am using dedicated bind addresses the JXMConnector fails
> to start on the second instance. It looks to like as if the bind address
> is just disregarded and instead binds to to the loopback device
> (1) Instance A  (-b 192.168.0.101) started successfully
> (2) Instance B (-b 192.168.0.102) logs:
> 17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL
> [rmi://192.168.0.102:1090/jmxconnector]:
> javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
> java.rmi.AlreadyBoundException: jmxconnector]
>         at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at
> org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
> (3) [hbraun at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
>                 
>         tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     
> The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.
> As far as i can tell, it pulls the jdk 1.5 JMX implementation.  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:59:44 2007
From: jira-events at lists.jboss.org (Mike Clark (JIRA))
Date: Wed, 31 Oct 2007 13:59:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1128) Message not
 routed from one node to node with only consumer.
In-Reply-To: <15994322.1193778405017.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12138935.1193853584726.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1128?page=all ]

Mike Clark closed JBMESSAGING-1128.
-----------------------------------

    Resolution: Done

No bug here:  jgroups configuration was the root cause of the behavior I was seeing.

> Message not routed from one node to node with only consumer.
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1128
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
>            Reporter: Mike Clark
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> In trying to reproduce behavior described in case 18885, I can reproduce the following:
> Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.
> Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)
> Both instances were created from a clean "all" instance.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 14:13:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 14:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1095)
 ConsumerContainer throws NoInitialContextException on stop
In-Reply-To: <3234104.1193846504671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6626244.1193854424607.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1095?page=all ]

Carlo de Wolf resolved EJBTHREE-1095.
-------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
       Resolution: Done

> ConsumerContainer throws NoInitialContextException on stop
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1095
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1095
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.3.GA
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> 2007-10-31 16:22:11,905 WARN  [org.jboss.ejb3.ServiceDelegateWrapper] Stopping failed jboss.j2ee:jar=consumer-test.jar,name=QueueTestConsumer,service=EJB3
> javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> 	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
> 	at javax.naming.InitialContext.getNameParser(InitialContext.java:439)
> 	at org.jboss.util.naming.Util.unbind(Util.java:135)
> 	at org.jboss.ejb3.mdb.ProducerFactory.stop(ProducerFactory.java:150)
> 	at org.jboss.ejb3.mdb.RemoteProducerFactory.stop(RemoteProducerFactory.java:99)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.unregisterProducers(ConsumerContainer.java:286)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.stop(ConsumerContainer.java:304)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy69.stop(Unknown Source)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
> 	at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
> 	at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy33.stop(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy34.stop(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	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

        


From jira-events at lists.jboss.org  Wed Oct 31 14:29:44 2007
From: jira-events at lists.jboss.org (Jon Whitmore (JIRA))
Date: Wed, 31 Oct 2007 14:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1776)
 User.updatePassword() fails silently
Message-ID: <28848557.1193855384823.JavaMail.jira@cloud.prod.atl2.jboss.com>

User.updatePassword() fails silently
------------------------------------

                 Key: JBPORTAL-1776
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1776
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Identity, Portal Security
    Affects Versions: 2.6.2 Final
         Environment: XP, portal 2.6.2, AS 4.2.2.GA, authenticating against LDAP with org.jboss.security.auth.spi.LdapExtLoginModule
            Reporter: Jon Whitmore


The method updatePassword() on org.jboss.portal.identity.User offers the user no information as to the success or failure of the operation.  The method can fail if the password offered is not strong enough for the authenticating authority behind the LoginModule.  

I'm requesting that the method at least return a boolean to indicate success or failure.  A more descriptive return code would be even better.

My work around to is call verifyPassword() after calling updatePassword() to see if in fact the password has been changed.  This trick works for me only because I am not caching passwords - installations caching passwords for only a couple seconds will not be able to use my work around.


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 14:34:44 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 31 Oct 2007 14:34:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2076859.1193855684739.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4923?page=comments#action_12385385 ] 
            
Anil Saldhana commented on JBAS-4923:
-------------------------------------

The issue is that the unauthenticatedPrincipal from the ApplicationMetaData is null.

====================================
org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal

// Check for an unauthenticated principal value
               else
               {
                  ApplicationMetaData appMetaData = con.getBeanMetaData().getApplicationMetaData();
                  String name = appMetaData.getUnauthenticatedPrincipal();
                  if (name != null)
                     caller = new SimplePrincipal(name);
               }
===================================

> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:18:45 2007
From: jira-events at lists.jboss.org (Jason Long (JIRA))
Date: Wed, 31 Oct 2007 15:18:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
In-Reply-To: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23716652.1193858325251.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_12385396 ] 
            
Jason Long commented on EJBTHREE-1096:
--------------------------------------

What changes to JBoss AS or the EJB3 spec are required  to achieve this?

Please also comment on the difficulty and likely time frame for these changes.

> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
>                 Key: EJBTHREE-1096
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:42:44 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 31 Oct 2007 15:42:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1098) create base ejb3
 and session domains in ejb3-interceptors-aop.xml
Message-ID: <16662887.1193859764851.JavaMail.jira@cloud.prod.atl2.jboss.com>

create base ejb3 and session domains in ejb3-interceptors-aop.xml
-----------------------------------------------------------------

                 Key: EJBTHREE-1098
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1098
             Project: EJB 3.0
          Issue Type: Feature Request
    Affects Versions: AS 4.2.2.GA
            Reporter: William DeCoste
         Assigned To: William DeCoste
            Priority: Minor


Extent applicable domains from base domains so easier to add defaults to all domains

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:46:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 15:46:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4934) JBossCacheWrapper
 should not re-use data gravitation option
Message-ID: <6732877.1193860004854.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBossCacheWrapper should not re-use data gravitation option
-----------------------------------------------------------

                 Key: JBAS-4934
                 URL: http://jira.jboss.com/jira/browse/JBAS-4934
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering, Web (Tomcat) service
    Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.GA
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


JBossCacheWrapper has a minor optimization where it creates an instance of Option, sets it to forceDataGravitation=true and then tries to re-use it across all invocations where we need to gravitate.  This is invalid usage; JBC does not promise an Option will be in its original state when an invocation returns.

Just need to create an Option for each call; no big deal.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:50:45 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Wed, 31 Oct 2007 15:50:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4424)
 WebAuthentication:Generate a SSOID
In-Reply-To: <20618100.1179337252975.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10892089.1193860245148.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4424?page=comments#action_12385404 ] 
            
Stefan Guilhen commented on JBAS-4424:
--------------------------------------

The SSO cookie is now generated by the WebAuthentication class as part of the login process when a SSO valve has been set in the jboss-web.deployer/server.xml. On Branch_4_2, the org.jboss.web.tomcat.security.ExtendedSingleSignOn valve has to be used instead of the standard SingleSignOn valve, because the ExtendedSSO valve exposes some of the SSO methods as public, allowing the WebAuthentication to delegate sso behaviour to the proper valve. As no upgrade of the jbossweb is planned for Branch_4_2, we had to come up with this workaround. The SSO behaviour of the WebAuthentication has been tested on Branch_4_2, and the code has already been commited.

This new valve is not necessary on Trunk, as Remy is setting the necessary methods to public on SingleSignOn valve. Version 2.1.0.CR7 of jbossweb already sets some of the methods to public but one of them (update) still needs to be changed. As soon as we have the changes we need, I'll test this implementation on Trunk using the standard SSO valve, commit, and resolve the issue.

> WebAuthentication:Generate a SSOID
> ----------------------------------
>
>                 Key: JBAS-4424
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4424
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Security
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication
> The feature needs to implement the sso stuff if it is desired by the user.  At the least, ssoid needs to be generated and set on the session.
> The ssoid generation logic exists in AuthenticatorBase.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 16:20:45 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 31 Oct 2007 16:20:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-366) Ability to attach a
 .aop deployment to a particular scoped classloader
In-Reply-To: <7683783.1172254777318.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2741448.1193862045388.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ]

Kabir Khan closed JBAOP-366.
----------------------------

    Resolution: Done

> Ability to attach a .aop deployment to a particular scoped classloader
> ----------------------------------------------------------------------
>
>                 Key: JBAOP-366
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-366
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.alpha3
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.CR1
>
>
> e.g. if an .ear file has been scoped with:
> <jboss-app>
>   <loader-repository>
>       dot.com:loader=ear1test
>   </loader-repository>
> </jboss-app>
> It should be possible to deploy at a later time a .aop file like:
> <aop>
>    <attach-scoped-loader>dot.com:loader=ear1test</attach-scoped-loader>
>     <!-- aspects, bindings etc. -->
> </aop>
> The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 16:35:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 16:35:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13498577.1193862944959.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=all ]

Brian Stansberry reopened JBCACHE-1192:
---------------------------------------

             
Reopening because fix has introduced regressions in AS test suite; will create subtask for that issue.

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction, Replication
>    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6, 2.1.0.GA, 2.1.0.CR1
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 16:48:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 16:48:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1209) Restore existing
 Option to InvocationContext in TreeCache._gravitateData
Message-ID: <10112660.1193863724684.JavaMail.jira@cloud.prod.atl2.jboss.com>

Restore existing Option to InvocationContext in TreeCache._gravitateData
------------------------------------------------------------------------

                 Key: JBCACHE-1209
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1209
             Project: JBoss Cache
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 1.4.1.SP6
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
             Fix For: 1.4.1.SP6


The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:

1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to *that* instance of Option.

2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread.  Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread.  But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.

I'll attach a possible patch in a minute.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:05:49 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:05:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
Message-ID: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add configuration for Remoting servlet transport
------------------------------------------------

                 Key: JBMESSAGING-1131
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Ron Sigal
         Assigned To: Tim Fox
             Fix For: 2.0.0 Alpha


In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:05:49 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:05:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7979492.1193864749502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]

Ron Sigal updated JBMESSAGING-1131:
-----------------------------------

    Description: In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works.   (was: In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. )

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:12:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:12:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <88778.1193865164657.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]

Ron Sigal updated JBMESSAGING-1131:
-----------------------------------

    Attachment: messaging-servlet-service.xml
                ServletExample.java
                build.xml

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>         Attachments: build.xml, messaging-servlet-service.xml, ServletExample.java
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:14:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:14:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23065025.1193865284853.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]

Ron Sigal updated JBMESSAGING-1131:
-----------------------------------

    Attachment: remoting-servlet-service.xml
                web.xml

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>         Attachments: build.xml, messaging-servlet-service.xml, remoting-servlet-service.xml, ServletExample.java, web.xml
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:18:46 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:18:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21245804.1193865526087.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=comments#action_12385414 ] 
            
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------

I've attached the various files relevant to this example.

1. build.xml, messaging-servlet-service.xml and ServletExample.java go in <root>/docs/examples/servlet 

2. remoting-servlet-service.xml goes in <root>/src/etc/remoting

3. web.xml goes in <root>/src/etc/remoting/remoting-servlet-invoker.war/WEB-INF

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>         Attachments: build.xml, messaging-servlet-service.xml, remoting-servlet-service.xml, ServletExample.java, web.xml
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:33:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1132) Use blocking
 mode for callbacks with Remoting http transport
Message-ID: <33520361.1193866424644.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use blocking mode for callbacks with Remoting http transport
------------------------------------------------------------

                 Key: JBMESSAGING-1132
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1132
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Ron Sigal
         Assigned To: Tim Fox
             Fix For: 2.0.0 Alpha


In response to JBREM-641 "re-implement the callback polling for http transport to reduce latency", an alternative way of handling callbacks was introduced in Remoting.  In particular, instead of the client periodically polling for callbacks, in "blocking" mode, the request to download callbacks blocks on the server until either (1) a callback is available, or (2) the timeout period has expired.  The advantage is reduced latency in retrieving callbacks.  In fact, some JBM http transport stress tests which fail in "nonblocking" mode now pass in "blocking" mode.

1. The default mode is "nonblocking", so it is necessary to explicitly configure "blocking" mode.  One way to do so is to add the appropriate parameter to the metadata map when installing the callback listener.  E.g., add the following line to org.jboss.jms.client.remoting.JMSRemotingConnection.createCallbackMetadata():

         if (reportPollingStatistics != null)
         {
            metadata.put(CallbackPoller.REPORT_STATISTICS, reportPollingStatistics);
         }

         metadata.put(ServerInvoker.BLOCKING_MODE, ServerInvoker.BLOCKING);  //  <<=== add this line
         metadata.put(ServerInvoker.BLOCKING_TIMEOUT, "7777");                              // optional: default is 5000 milliseconds

2. The line

   <attribute name="callbackPollPeriod" isParam="true">102</attribute>

may be removed from remoting-http-service.xml, since it's no longer relevant.


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:40:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:40:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-827) Define a management
 interface for JBoss Remoting
Message-ID: <21180814.1193866844566.JavaMail.jira@cloud.prod.atl2.jboss.com>

Define a management interface for JBoss Remoting
------------------------------------------------

                 Key: JBREM-827
                 URL: http://jira.jboss.com/jira/browse/JBREM-827
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M2




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:43:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:43:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-824) Allow server to shut
 down connections from specified clients
In-Reply-To: <17720506.1193108054695.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8722207.1193867024700.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-824?page=all ]

David Lloyd closed JBREM-824.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Done
         Assignee:     (was: Trustin Lee)

Won't fix in the 2.x series.  Remoting 3 has a management interface defined in the roadmap; see JBREM-827.

> Allow server to shut down connections from specified clients
> ------------------------------------------------------------
>
>                 Key: JBREM-824
>                 URL: http://jira.jboss.com/jira/browse/JBREM-824
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>
> From Jay Howell:  
> Several customers have asked for a management method to drop client connections from the server by ip address and by client id.
> So there would be two cases.
>    By ipaddress - this would stop the pinger and also close all connections associated with that client ip address. Only one pinger exists for an ip address, so this would require closing of the pinger connection also.
>    By clientid - this would close the pinger thread only if there are no other connections present.
> In each of the cases, clients should get an asynchronous onException call. 
> This facility would be necessary to support JBMESSAGING-1117.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:45:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:45:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-819) Consider removing
 dependency on jboss-commons
In-Reply-To: <26278208.1192488064482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8579564.1193867144761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-819?page=all ]

David Lloyd closed JBREM-819.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Won't Fix

Won't fix in the 2.x series.  Remoting 3 does not depend on JBoss commons though.

> Consider removing dependency on jboss-commons
> ---------------------------------------------
>
>                 Key: JBREM-819
>                 URL: http://jira.jboss.com/jira/browse/JBREM-819
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Trustin Lee
>
> From Greg Hinkle of the JBoss Operations Network group:  
> "... not only are the including tons of crap in the garbage pale called commons, but they dictate tons of library dependencies and serialization versions. For a group like ours that has to be able to simultaneously connect to every version of jboss released in the last 3 years it is not a good situation. We end up having to create a separate class loader per connection.
> "Now with remoting, we're actually using it as a core infrastructure piece. That means its in parent classloaders to these connection classloaders. As long as commons is in that required list we can't use remoting this way. We're going to have to do some serious classloader restructuring to be able to support our needs."

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:45:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:45:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-812) Specify an API to
 discover services
In-Reply-To: <11944998.1191360663233.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14788143.1193867144890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-812?page=all ]

David Lloyd updated JBREM-812:
------------------------------

    Fix Version/s: Remoting 3 M1
                       (was: 3.0.0.Alpha1 (Otter))

> Specify an API to discover services
> -----------------------------------
>
>                 Key: JBREM-812
>                 URL: http://jira.jboss.com/jira/browse/JBREM-812
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: r3 api
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>            Priority: Minor
>             Fix For: Remoting 3 M1
>
>
> The Remoting 3 API presently has a mechanism to discover endpoints and supply information about how to connect to discovered endpoints.
> A mechanism is also needed to allow a user to find any endpoint that provides a specific service.  This mechanism would preferably work in tandem with the existing discovery API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:49:48 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:49:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-759) Client
 username/password
 authentication mechanism to provide JAAS UserPrincipal
In-Reply-To: <22936251.1182273876546.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32215262.1193867388802.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-759?page=all ]

David Lloyd closed JBREM-759.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Out of Date

Remoting 3 already specifies an authentication API that should meet this need.

> Client username/password authentication mechanism to provide JAAS UserPrincipal
> -------------------------------------------------------------------------------
>
>                 Key: JBREM-759
>                 URL: http://jira.jboss.com/jira/browse/JBREM-759
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: security
>            Reporter: Clark Updike
>
> Per the forum thread, Remoting needs a username/password-style authentication mechanism similar to JNDI for situations that require secure authentication but cannot support the infrastructure required for client certificates.  The mechanism should populate a JAAS UserPrinciple that can be used to access the authenticated client identity on the remote side.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:53:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-718) Support for more
 message-based protocols
In-Reply-To: <13567351.1173182602514.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16671778.1193867624694.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-718?page=all ]

David Lloyd closed JBREM-718.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Deferred

Remoting 3 has the ability to plug in transports.  That said, the default transports provided will probably be limited to the default (JRPP), HTTP, and a couple of loopback transports.

> Support for more message-based protocols
> ----------------------------------------
>
>                 Key: JBREM-718
>                 URL: http://jira.jboss.com/jira/browse/JBREM-718
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Little
>
> It would be good if Remoting supported more message-oriented protocols, such as JMS, FTP, email etc. RPC semantics could be layered on those, or simply say that the one-way approach is all that is supported. One slight worry might be if a supported plugin implementation for JBoss Remoting itself used JBoss Remoting (e.g., plugging JBoss Messaging into JBoss Remoting). This may set up some interesting circularities.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:55:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBREM-103) Transport progress
 notification for client
Message-ID: <22337093.1193867745342.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd reopened JBREM-103:
-------------------------------

             
Reopening to update the fix version...

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:55:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-103) Transport progress
 notification for client
Message-ID: <23374398.1193867745511.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd closed JBREM-103.
-----------------------------

    Fix Version/s: Remoting 3 M1
       Resolution: Done

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:58:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:58:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-38) SSH transport
Message-ID: <4265622.1193867924715.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-38?page=all ]

David Lloyd closed JBREM-38.
----------------------------

    Resolution: Won't Fix
      Assignee:     (was: Tom  Elrod)

SSH transport is not currently on the roadmap, as the default transport already does encryption without key management.  However this can be reopened if there is a use case.

> SSH transport
> -------------
>
>                 Key: JBREM-38
>                 URL: http://jira.jboss.com/jira/browse/JBREM-38
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: transport
>    Affects Versions: 1.0.1 beta
>            Reporter: Tom  Elrod
>            Priority: Optional
>
> Check out http://www.jcraft.com/jsch/index.html and see if can be used for a SSH transport.  Also see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=58498 for more comments on this topic.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:00:50 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:00:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-433) point to multipoint
	invocation api
Message-ID: <286787.1193868050849.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-433?page=all ]

David Lloyd closed JBREM-433.
-----------------------------

    Resolution: Deferred

Closed until/unless a use case is identified.

> point to multipoint invocation api
> ----------------------------------
>
>                 Key: JBREM-433
>                 URL: http://jira.jboss.com/jira/browse/JBREM-433
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>
> Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time.  The responses for each target server would be aggregated into one response as return to the client call.  Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for 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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:00:51 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:00:51 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-305) Provide support for
	JMS transport
Message-ID: <544030.1193868051293.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-305?page=all ]

David Lloyd closed JBREM-305.
-----------------------------

    Resolution: Deferred

JBoss Remoting may have a JMS transport at some point in the future.  However IF it does, the format of the message will be a black box, and no interoperability guarantees will be made.

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:02:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:02:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-48) JGroups transport
Message-ID: <28092129.1193868164945.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-48?page=all ]

David Lloyd closed JBREM-48.
----------------------------

    Resolution: Deferred
      Assignee:     (was: Tom  Elrod)

Deferred until a use case is identified.

> JGroups transport
> -----------------
>
>                 Key: JBREM-48
>                 URL: http://jira.jboss.com/jira/browse/JBREM-48
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: transport
>    Affects Versions: 1.0.1 beta
>            Reporter: Tom  Elrod
>
> Would like to add JGroups as a transport. In particular, would like to be able to add concept of being able to invoker on multiple servers and consolidate the responses. One use case would be for making two phase commit calls on distributed cache, so can verify that all servers successfully prepare.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:02:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:02:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-237) There is No String
 and Guage monitors in jboss
Message-ID: <3925671.1193868165152.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-237?page=all ]

David Lloyd closed JBREM-237.
-----------------------------

    Resolution: Rejected

No updates, and no idea what this issue is about.

> There is No String and Guage monitors in jboss
> ----------------------------------------------
>
>                 Key: JBREM-237
>                 URL: http://jira.jboss.com/jira/browse/JBREM-237
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: jmx remoting
>            Reporter: sree roja
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:04:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:04:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-381) IIOP transport impl
	for remoting
Message-ID: <27428013.1193868284929.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-381?page=all ]

David Lloyd closed JBREM-381.
-----------------------------

    Resolution: Deferred
      Assignee: David Lloyd  (was: Ron Sigal)

At the moment there are no plans for an IIOP transport for Remoting 3.  Reopen if there are *specific* requirements.

> IIOP transport impl for remoting
> --------------------------------
>
>                 Key: JBREM-381
>                 URL: http://jira.jboss.com/jira/browse/JBREM-381
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1 final
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>            Priority: Minor
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:08:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:08:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-68) Add persistent store
 for oneway messages
Message-ID: <8550013.1193868524649.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-68?page=all ]

David Lloyd closed JBREM-68.
----------------------------

    Resolution: Rejected
      Assignee:     (was: Tom  Elrod)

Remoting 3 won't have this type of delivery guarantee, but a user could layer it on pretty easily.

> Add persistent store for oneway messages
> ----------------------------------------
>
>                 Key: JBREM-68
>                 URL: http://jira.jboss.com/jira/browse/JBREM-68
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: transport
>    Affects Versions: 1.0.1 final
>            Reporter: Tom  Elrod
>            Priority: Optional
>
> Need to add ability to persist invocation messages on server when using oneway on the server side.  This will ensure that if server crashes and one message has made it to server worker pool, it will be processed when the server is restarted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:12:54 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 18:12:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1209) Restore existing
 Option to InvocationContext in TreeCache._gravitateData
In-Reply-To: <10112660.1193863724684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12731553.1193868774939.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1209?page=all ]

Brian Stansberry updated JBCACHE-1209:
--------------------------------------

    Attachment: TreeCache.patch

Possible patch.  With this in place, the 150 AS testsuite failures I was seeing went away.

Running the full JBC testsuite w/ this now (w/ 1.4.1.SP6 tag).

The above patch may be a bit of a sledgehammer; perhaps just the stuff in the finally block would take care of the problem. But I figured restoring the Option after each get(Fqn) call was just safer.

> Restore existing Option to InvocationContext in TreeCache._gravitateData
> ------------------------------------------------------------------------
>
>                 Key: JBCACHE-1209
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1209
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP6
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: TreeCache.patch
>
>
> The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:
> 1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to *that* instance of Option.
> 2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread.  Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread.  But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.
> I'll attach a possible patch in a minute.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:12:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:12:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-315) allow chaining of
 marshaller/unmarshallers
Message-ID: <26091351.1193868775104.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-315?page=all ]

David Lloyd closed JBREM-315.
-----------------------------

    Resolution: Done
      Assignee:     (was: Tom  Elrod)

The idea is sound - but implementation-wise, the interceptor stack should be negotiated between the two participants rather than relying on a static configuration.  This will be designed in to Remoting 3.

> allow chaining of marshaller/unmarshallers
> ------------------------------------------
>
>                 Key: JBREM-315
>                 URL: http://jira.jboss.com/jira/browse/JBREM-315
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 1.4.0 final
>            Reporter: Tom  Elrod
>
> I was thinking of paired marshaller/unmarshaller, which would be
> beneficial for more than just this example (compressing payload comes to
> mind).  Would like to be able to declare a chain of marshallers.  For
> example:
> <marshallers>
> <marshaller>org.jboss.remoting.marshall.CompressedMarshaller</marshaller>
> <marshaller>org.jboss.remoting.marshall.InvocationMarshaller</marshaller>
> <marshaller>org.jboss.remoting.marshall.CountingMarshaller</marshaller>
> </marshallers>
> <unmarshallers>
> <unmarshaller>org.jboss.remoting.marshall.InvocationUnMarshaller</unmarshaller>
> <unmarshaller<org.jboss.remoting.marshall.CompressedUnMarshaller</unmarshaller>
> of course packaging and order may not be correct in this example.  Just
> trying to show how would be nice to configure the chain that is used and
> that would not require to by symmetrical if didn't want to.
> In this example, the CompressedMarshaller would compress the payload,
> then write to the InvocationMarshaller, which would write to the
> CountingMarshaller, which would then keep track of number of bytes
> written and send notifications as was being written.  On the server
> side, might not need to know number of bytes being read, so would just
> have the InvocationUnMarshaller, then CompressedUnMarshaller to
> uncompress the payload.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:12:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:12:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-828) Interceptor
	negotiation mechanism
Message-ID: <26398467.1193868775254.JavaMail.jira@cloud.prod.atl2.jboss.com>

Interceptor negotiation mechanism
---------------------------------

                 Key: JBREM-828
                 URL: http://jira.jboss.com/jira/browse/JBREM-828
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
         Assigned To: David Lloyd
             Fix For: Remoting 3 M1


The participants need to negotiate what interceptors should exist on a per-service basis.  Work out further requirements, and implement.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:21:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:21:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-269) Create RMI/IIOP
 transport implementation
Message-ID: <16413833.1193869305497.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-269?page=all ]

David Lloyd closed JBREM-269.
-----------------------------

    Resolution: Rejected

No IIOP transport is planned for Remoting 3.  Probably we need a separate invoker layer that would cover this kind of thing.

If this is wrong, reopen and provide specific requirements.

> Create RMI/IIOP transport implementation
> ----------------------------------------
>
>                 Key: JBREM-269
>                 URL: http://jira.jboss.com/jira/browse/JBREM-269
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>
> We need an RMI/IIOP implementation for ejb3. This should be coming from the remoting implementation. We need to look into porting the existing detached iiop invoker code in the iiop module to a remoting implementation.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:21:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:21:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-324) Facility for
 real-time decision
 on best InvokerLocator by which to contact a given handler.
Message-ID: <13988511.1193869305700.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12385438 ] 
            
David Lloyd commented on JBREM-324:
-----------------------------------

As far as I'm concerned this can be closed, as it is an integral part of the R3 routing API.  Otherwise it should be assigned to a specific version.

> Facility for real-time decision on best InvokerLocator by which to contact a given handler.
> -------------------------------------------------------------------------------------------
>
>                 Key: JBREM-324
>                 URL: http://jira.jboss.com/jira/browse/JBREM-324
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>            Priority: Minor
>
> The basic idea is to be able to communicate with a single handler by way of different InvokerLocators.  For example, if you're working over the internet, compression might be advantageous, but if you're local it might not be.  So you could have two Connectors sharing a handler, one using the compression marshaller and one not.
> How about a client that
> 1. gets the InvokerLocators for all of the Connectors for a certain handler, via a detector,
> 2. sends some sample invocations to each and times them, and
> 3. displays the results.
> It could be used for real time decision making or to collect information for a set of rules.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:23:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:23:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-416) create
 jboss-remoting-client-pda.jar
Message-ID: <5852705.1193869435346.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-416?page=all ]

David Lloyd closed JBREM-416.
-----------------------------

    Resolution: Deferred
      Assignee:     (was: Tom  Elrod)

No plans currently to tackle a J2ME release.  Can be reopened if this is to be put on the roadmap.

> create jboss-remoting-client-pda.jar
> ------------------------------------
>
>                 Key: JBREM-416
>                 URL: http://jira.jboss.com/jira/browse/JBREM-416
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta1
>            Reporter: Tom  Elrod
>
> Need a remoting client distribution that can run within J2ME environment (PDA to be specific).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:23:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:23:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-417) create J2ME
 compatible socket client invoker
Message-ID: <33452540.1193869435470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-417?page=all ]

David Lloyd closed JBREM-417.
-----------------------------

    Resolution: Deferred
      Assignee:     (was: Tom  Elrod)

No plans currently to tackle a J2ME release. Can be reopened if this is to be put on the roadmap.

> create J2ME compatible socket client invoker
> --------------------------------------------
>
>                 Key: JBREM-417
>                 URL: http://jira.jboss.com/jira/browse/JBREM-417
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta1
>            Reporter: Tom  Elrod
>
> There are a few API calls in current SocketClientInvoker that is not allowed in J2ME.  Need to create an extention of the SocketClientInvoker (maybe MicroSocketClientInvoker?) that will remove these calls so can be used within J2ME environment.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:27:51 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:27:51 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-736)
 [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling
 exception, exiting  java.lang.ClassNotFoundException:
 [Ljava.lang.StackTraceElement;
In-Reply-To: <10442416.1176842850531.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25677704.1193869671366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-736?page=all ]

David Lloyd closed JBREM-736.
-----------------------------

    Resolution: Cannot Reproduce Bug

No response from user.

> [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting  java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement; 
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-736
>                 URL: http://jira.jboss.com/jira/browse/JBREM-736
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 1.4.3.GA
>         Environment: Jboss 4.0.4.GA/EJB3/JDK1.6
>            Reporter: Ravi Alagappan
>         Assigned To: David Lloyd
>
> I am throwing custom application exception from bean and trying to catch that in client. But I am getting 
> 2007-04-17 09:57:15,480 DEBUG [org.jboss.remoting.transport.socket.SocketClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker at 16a38b5
> 2007-04-17 09:57:15,558 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
> java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> 	at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
> 	at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> 	at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
> 	at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
> 	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
> 	at org.jboss.remoting.Client.invoke(Client.java:525)
> 	at org.jboss.remoting.Client.invoke(Client.java:488)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> 	at $Proxy0.save(Unknown Source)
> 	at linc.document.service.RepositoryClient.save(RepositoryClient.java:109)
> 	at linc.document.service.DocumentService.save(DocumentService.java:35)
> 	at linc.document.service.DocumentService.main(DocumentService.java:184)
> 2007-04-17 09:57:15,573 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Error loading classes from remote call result.
> java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> 	at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
> 	at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> 	at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
> 	at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
> 	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
> 	at org.jboss.remoting.Client.invoke(Client.java:525)
> 	at org.jboss.remoting.Client.invoke(Client.java:488)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> 	at $Proxy0.save(Unknown Source)
> 	at linc.document.service.RepositoryClient.save(RepositoryClient.java:109)
> 	at linc.document.service.DocumentService.save(DocumentService.java:35)
> 	at linc.document.service.DocumentService.main(DocumentService.java:184)
> But no exception with jdk1.5. With JDK1.5 client able to catch custom exception.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:54:44 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Wed, 31 Oct 2007 18:54:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1712) Make producer
 tests go through the WS stack
In-Reply-To: <22960492.1190516351026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27496979.1193871284830.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=all ]

Chris Laprun resolved JBPORTAL-1712.
------------------------------------

    Resolution: Rejected

Actually, the tests are going through the WS stack as it is and I managed to fix them (by not using the unmarshalled exceptions but directly RemoteException and checking the error code) though I am not quite sure how changing code on the client has an impact on the test result... I suspect it has to do with JBoss WS somewhat flaky support for SOAPFaultException... I guess I will need to investigate this more. Closing this task.

> Make producer tests go through the WS stack
> -------------------------------------------
>
>                 Key: JBPORTAL-1712
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1712
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal WSRP
>    Affects Versions: 2.8 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>             Fix For: 2.6.3 Final, 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 19:14:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 19:14:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5657940.1193872484661.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4923?page=all ]

Scott M Stark resolved JBAS-4923.
---------------------------------

    Resolution: Done

The setting has been moved to the standardjboss.xml 

[starksm at valkyrie jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test one-test
...

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.DocEJBTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 28.953 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcDIIConfiguredC
allTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.062 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcDIIUnconfigure
dCallTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.61 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcEJBTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.188 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcProxyTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.234 sec


> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 19:18:54 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 19:18:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28034430.1193872734931.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Scott M Stark resolved JBAS-4924.
---------------------------------

    Resolution: Done

The tests fail for other reasons than passing a null ejb-class to the class loader.

16:16:42,437 INFO  [TomcatDeployment] deploy, ctxPath=/jaxws-samples-webservicer
ef-servlet-client, vfsUrl=
16:16:43,875 INFO  [ServletClient] doGet: HelloWorld
16:16:45,343 INFO  [TestEndpointImpl] HelloWorld
16:16:45,343 INFO  [TestEndpointImpl] HelloWorld
16:16:45,359 INFO  [TestEndpointImpl] HelloWorld
16:16:45,375 INFO  [TestEndpointImpl] HelloWorld
16:16:45,375 INFO  [TestEndpointImpl] HelloWorld
16:16:45,390 INFO  [TestEndpointImpl] HelloWorld
16:16:45,406 INFO  [TestEndpointImpl] HelloWorld
16:16:45,421 INFO  [TestEndpointImpl] HelloWorld
16:16:45,437 INFO  [TestEndpointImpl] HelloWorld
16:16:45,437 INFO  [TestEndpointImpl] HelloWorld
16:16:45,453 INFO  [TestEndpointImpl] HelloWorld
16:16:45,468 INFO  [TestEndpointImpl] HelloWorld
16:16:45,500 INFO  [TestEndpointImpl] HelloWorld
16:16:45,500 INFO  [TestEndpointImpl] HelloWorld
16:16:45,515 INFO  [TestEndpointImpl] HelloWorld
16:16:45,609 INFO  [TomcatDeployment] undeploy, ctxPath=/jaxws-samples-webservic
eref-servlet-client, vfsUrl=
16:16:45,656 INFO  [TomcatDeployment] undeploy, ctxPath=/jaxws-samples-webservic
eref, vfsUrl=
16:16:45,687 INFO  [DefaultEndpointRegistry] remove: jboss.ws:context=jaxws-samp
les-webserviceref,endpoint=TestEndpoint

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 5.75 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefEJB3TestCase
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 3.078 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefEJB3TestCase FAILED
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefServletTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.094 sec


> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:51:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:51:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-829) SRP SASL Provider
Message-ID: <16521012.1193878304574.JavaMail.jira@cloud.prod.atl2.jboss.com>

SRP SASL Provider
-----------------

                 Key: JBREM-829
                 URL: http://jira.jboss.com/jira/browse/JBREM-829
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: r3 core
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:53:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-830) Remoting 3 API
Message-ID: <32416860.1193878424623.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting 3 API
--------------

                 Key: JBREM-830
                 URL: http://jira.jboss.com/jira/browse/JBREM-830
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:53:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-831) Remoting 3 Core
	Implementation
Message-ID: <588287.1193878424796.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting 3 Core Implementation
------------------------------

                 Key: JBREM-831
                 URL: http://jira.jboss.com/jira/browse/JBREM-831
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-832) JRPP Implementation
Message-ID: <18439719.1193878544710.JavaMail.jira@cloud.prod.atl2.jboss.com>

JRPP Implementation
-------------------

                 Key: JBREM-832
                 URL: http://jira.jboss.com/jira/browse/JBREM-832
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-830) Remoting 3 API
In-Reply-To: <32416860.1193878424623.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18079046.1193878544851.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-830?page=all ]

David Lloyd reassigned JBREM-830:
---------------------------------

    Assignee: David Lloyd

> Remoting 3 API
> --------------
>
>                 Key: JBREM-830
>                 URL: http://jira.jboss.com/jira/browse/JBREM-830
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-829) SRP SASL Provider
In-Reply-To: <16521012.1193878304574.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31764949.1193878544975.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-829?page=all ]

David Lloyd reassigned JBREM-829:
---------------------------------

    Assignee: David Lloyd

> SRP SASL Provider
> -----------------
>
>                 Key: JBREM-829
>                 URL: http://jira.jboss.com/jira/browse/JBREM-829
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: r3 core
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-831) Remoting 3 Core
	Implementation
In-Reply-To: <588287.1193878424796.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22377390.1193878545177.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-831?page=all ]

David Lloyd reassigned JBREM-831:
---------------------------------

    Assignee: David Lloyd

> Remoting 3 Core Implementation
> ------------------------------
>
>                 Key: JBREM-831
>                 URL: http://jira.jboss.com/jira/browse/JBREM-831
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:11:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 21:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-833) HTTP Transport
	Implementation
Message-ID: <16108849.1193879504581.JavaMail.jira@cloud.prod.atl2.jboss.com>

HTTP Transport Implementation
-----------------------------

                 Key: JBREM-833
                 URL: http://jira.jboss.com/jira/browse/JBREM-833
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M2




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:15:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 21:15:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-829) SRP SASL Provider
In-Reply-To: <16521012.1193878304574.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28711532.1193879744579.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-829?page=comments#action_12385452 ] 
            
David Lloyd commented on JBREM-829:
-----------------------------------

Implementation is complete.  Need tests.

> SRP SASL Provider
> -----------------
>
>                 Key: JBREM-829
>                 URL: http://jira.jboss.com/jira/browse/JBREM-829
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: r3 core
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:19:54 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 21:19:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-166) JMXConnectorServer
 will not start if using rmi invoker elsewhere
Message-ID: <25833573.1193879994929.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-166?page=all ]

Ron Sigal updated JBREM-166:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)
         Assignee:     (was: Tom  Elrod)

Adding fix version 2.4.0.Beta1.  

This issue seems to be related to JBAS-3885: JMXConnectorServer not respecting the -b value, recently fixed by Dimitris, who changed the creation of the RMI registry in org.jboss.mx.remoting.service.JMXConnectorServerService.start() to use a ServerSocketFactory that binds to a single host.  Maybe the same needs to be done in org.jboss.remoting.transport.rmi.RMIServerInvoker.

> JMXConnectorServer will not start if using rmi invoker elsewhere
> ----------------------------------------------------------------
>
>                 Key: JBREM-166
>                 URL: http://jira.jboss.com/jira/browse/JBREM-166
>             Project: JBoss Remoting
>          Issue Type: Bug
>          Components: jmx remoting
>    Affects Versions: JMX Remoting 1.0.1
>            Reporter: Tom  Elrod
>             Fix For: JMX Remoting 1.0.2, 2.4.0.Beta1 (Pinto)
>
>
> If have a remoting invoker using rmi transport, it will create a rmi registry.  Then when the JMXConnectorServer starts, it will also try to create one.  Even though is on a different port, will get the following exception:
> java.rmi.server.ExportException: internal error: ObjID already in use
> 	at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> 	at sun.rmi.transport.Transport.exportObject(Transport.java:69)
> 	at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190)
> 	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> 	at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> 	at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
> 	at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
> 	at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
> 	at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
> 	at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:22:45 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 21:22:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBFORUMS-231) Simplify
	ResourceBundle
In-Reply-To: <11029871.1178674432213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19911638.1193880165047.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBFORUMS-231?page=all ]

Ryszard Kozmik updated JBFORUMS-231:
------------------------------------

    Fix Version/s: 1.1.0 Alpha

> Simplify ResourceBundle
> -----------------------
>
>                 Key: JBFORUMS-231
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-231
>             Project: JBoss Forums
>          Issue Type: Task
>          Components: Forum View Layer, Portlet Productization
>            Reporter: Ryszard Kozmik
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC, 1.1.0 Alpha
>
>          Time Spent: 3 hours
>
> There are a lot of useless entries in ResourceBundle for JBoss Forums, those should be deleted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:39:44 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 21:39:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBFORUMS-231) Simplify
	ResourceBundle
In-Reply-To: <11029871.1178674432213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15415639.1193881184735.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBFORUMS-231?page=all ]

Ryszard Kozmik resolved JBFORUMS-231.
-------------------------------------

    Resolution: Done

> Simplify ResourceBundle
> -----------------------
>
>                 Key: JBFORUMS-231
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-231
>             Project: JBoss Forums
>          Issue Type: Task
>          Components: Forum View Layer, Portlet Productization
>            Reporter: Ryszard Kozmik
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC, 1.1.0 Alpha
>
>          Time Spent: 3 hours
>
> There are a lot of useless entries in ResourceBundle for JBoss Forums, those should be deleted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:51:50 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 21:51:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBFORUMS-247) forums and
 commons-fileupload-1.1
In-Reply-To: <1722719.1184003911960.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10107762.1193881910485.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBFORUMS-247?page=comments#action_12385457 ] 
            
Ryszard Kozmik commented on JBFORUMS-247:
-----------------------------------------

Luca the zip archive  patch_multiple_forums_src_1.1.0_30_sep_2007.zip (51 kb) is here only by mistake, right?

> forums and commons-fileupload-1.1
> ---------------------------------
>
>                 Key: JBFORUMS-247
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-247
>             Project: JBoss Forums
>          Issue Type: Bug
>          Components: Portlet Productization, Forum Model Layer
>         Environment: JBoss as from http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_CP06, 
> JBoss Portal from http://anonsvn.jboss.org/repos/portal/trunk since 9 july 2007,
> JBoss Forums from http://anonsvn.jboss.org/repos/labs/labs/jbossforums/branches/forums101P26 since 9 july 2007
>            Reporter: Luca Stancapiano
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC
>
>         Attachments: ForumsJSFPortlet.java, patch_multiple_forums_src_1.1.0_30_sep_2007.zip
>
>
> hi....I send you to see http://jira.jboss.com/jira/browse/JBPORTAL-1550 by me reported. It is the same problem......if you post messages using 'multipart/form-data' through commons-fileupload libs, you miss character encoding because there is a incompatibility between tomcat 5.5.23 and fileupload 1.1, and then if you try to send messages with characters as ?, ?, ?, ?, ? you 'll get problems of decoding with strange characters of response. Also for Forums I send you a patch. I substituted getString() method of org.apache.commons.fileupload.disk.DiskFileItem class with getString( String ...) method, passing inside the character encoding of the request:
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 560
>      I write :
>   
>                newParams.put(item.getFieldName(), new String[]{item.getString(req.getCharacterEncoding())});
>     instead of:
>              newParams.put(item.getFieldName(), new String[]{item.getString()});
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 564
>   
>       I write:
>             String value = item.getString(req.getCharacterEncoding());
>       instead of:
>             String value = item.getString();

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 22:07:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:07:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-834) Remoting 3
 Transaction API/Interceptor
Message-ID: <3086336.1193882864651.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting 3 Transaction API/Interceptor
--------------------------------------

                 Key: JBREM-834
                 URL: http://jira.jboss.com/jira/browse/JBREM-834
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:11:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-835) Interceptor API
Message-ID: <10909073.1193883104599.JavaMail.jira@cloud.prod.atl2.jboss.com>

Interceptor API
---------------

                 Key: JBREM-835
                 URL: http://jira.jboss.com/jira/browse/JBREM-835
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:11:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-835) Interceptor API
In-Reply-To: <10909073.1193883104599.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17196.1193883104766.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-835?page=all ]

David Lloyd updated JBREM-835:
------------------------------

    Fix Version/s: Remoting 3 M1

> Interceptor API
> ---------------
>
>                 Key: JBREM-835
>                 URL: http://jira.jboss.com/jira/browse/JBREM-835
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:16:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 22:16:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4705690.1193883404714.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385458 ] 
            
Ron Sigal commented on JBREM-675:
---------------------------------

The default exception handling behavior is now to return the exception thrown by the invocation handler.  To turn off that behavior, so that an error message is returned, it is necessary to add the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.DONT_RETURN_EXCEPTION (actual value "dont-return-exception") with a value of "true" to the metadata map received by ServerServletInvoker.  For example, "dont-return-exception=true" could be added to the InvokerLocator.

This change is related to JBREM-813 "ServletServerInvoker should return an exception instead of just an error message".

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:23:45 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 22:23:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBFORUMS-247) forums and
 commons-fileupload-1.1
In-Reply-To: <1722719.1184003911960.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10734199.1193883825132.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBFORUMS-247?page=comments#action_12385459 ] 
            
Ryszard Kozmik commented on JBFORUMS-247:
-----------------------------------------

Indeed it helps for ?, ?, ?, ?, ? but it e.g. doesn't for Polish diacritical characters like ?,?,?,?,?,?,?,?. (I have URIEncoding="UTF-8" in my 8080 connector in server.xml of tomcat). Do you have any idea what can be wrong?

> forums and commons-fileupload-1.1
> ---------------------------------
>
>                 Key: JBFORUMS-247
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-247
>             Project: JBoss Forums
>          Issue Type: Bug
>          Components: Portlet Productization, Forum Model Layer
>         Environment: JBoss as from http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_CP06, 
> JBoss Portal from http://anonsvn.jboss.org/repos/portal/trunk since 9 july 2007,
> JBoss Forums from http://anonsvn.jboss.org/repos/labs/labs/jbossforums/branches/forums101P26 since 9 july 2007
>            Reporter: Luca Stancapiano
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC
>
>         Attachments: ForumsJSFPortlet.java, patch_multiple_forums_src_1.1.0_30_sep_2007.zip
>
>
> hi....I send you to see http://jira.jboss.com/jira/browse/JBPORTAL-1550 by me reported. It is the same problem......if you post messages using 'multipart/form-data' through commons-fileupload libs, you miss character encoding because there is a incompatibility between tomcat 5.5.23 and fileupload 1.1, and then if you try to send messages with characters as ?, ?, ?, ?, ? you 'll get problems of decoding with strange characters of response. Also for Forums I send you a patch. I substituted getString() method of org.apache.commons.fileupload.disk.DiskFileItem class with getString( String ...) method, passing inside the character encoding of the request:
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 560
>      I write :
>   
>                newParams.put(item.getFieldName(), new String[]{item.getString(req.getCharacterEncoding())});
>     instead of:
>              newParams.put(item.getFieldName(), new String[]{item.getString()});
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 564
>   
>       I write:
>             String value = item.getString(req.getCharacterEncoding());
>       instead of:
>             String value = item.getString();

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 22:27:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:27:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-836) Remoting
 Endpoint/Listener Deployer
Message-ID: <29335891.1193884064741.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting Endpoint/Listener Deployer
-----------------------------------

                 Key: JBREM-836
                 URL: http://jira.jboss.com/jira/browse/JBREM-836
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd


Deployer for the Microcontainer that creates and configures a Remoting Endpoint.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:27:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:27:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-836) Remoting
 Endpoint/Listener Deployer
In-Reply-To: <29335891.1193884064741.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22377647.1193884064942.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-836?page=all ]

David Lloyd updated JBREM-836:
------------------------------

    Fix Version/s: Remoting 3 M3

> Remoting Endpoint/Listener Deployer
> -----------------------------------
>
>                 Key: JBREM-836
>                 URL: http://jira.jboss.com/jira/browse/JBREM-836
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>             Fix For: Remoting 3 M3
>
>
> Deployer for the Microcontainer that creates and configures a Remoting Endpoint.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:29:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-837) Static
	Discovery/Route Deployer
Message-ID: <25603332.1193884184593.JavaMail.jira@cloud.prod.atl2.jboss.com>

Static Discovery/Route Deployer
-------------------------------

                 Key: JBREM-837
                 URL: http://jira.jboss.com/jira/browse/JBREM-837
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M3


Mechanism to allow static Discoveries to be deployed/undeployed for a given Endpoint.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:40:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 22:40:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1209) Restore
 existing Option to InvocationContext in TreeCache._gravitateData
In-Reply-To: <10112660.1193863724684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30451126.1193884844716.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1209?page=comments#action_12385460 ] 
            
Brian Stansberry commented on JBCACHE-1209:
-------------------------------------------

JBC testsuite ran fine as did the ejb3 clustering tests from AS 4.2.2.

> Restore existing Option to InvocationContext in TreeCache._gravitateData
> ------------------------------------------------------------------------
>
>                 Key: JBCACHE-1209
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1209
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP6
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: TreeCache.patch
>
>
> The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:
> 1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to *that* instance of Option.
> 2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread.  Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread.  But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.
> I'll attach a possible patch in a minute.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:46:48 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 22:46:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7271629.1193885208404.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385461 ] 
            
Ron Sigal commented on JBREM-675:
---------------------------------

Testing:

1. New unit test:  org.jboss.test.remoting.transport.servlet.ServletInvokerNoExceptionTestClient.

2. Ran EJB3 example from wiki page Accessing_EJB3s_over_HTTP_HTTPS, after updating example (see EJBTHREE-1094 "Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0").  It ran with HTTP and HTTPS with the non-APR connector.  With the APR connector, the example ran with HTTP, but there is a problem with HTTPS.  It seems that the APR connector expects the keystore in openssl format.  See also JBREM-825 "Verify that CoyoteInvoker works with Apache Portable Runtime".

3. Created a servlet example in JBossMessaging, parallel to the http example, and it ran correctly.  See JBMESSAGING-1131 "Add configuration for Remoting servlet transport".

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 02:11:41 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 1 Oct 2007 02:11:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-786) String remove()
	method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28478858.1191219101646.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Andrew Rubinger updated EJBTHREE-786:
-------------------------------------

    JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=120053

Stand corrected, revoking "spec violation" argument.

See linked Forum topic.

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: Branch_4_2, HEAD
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 02:27:41 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Mon, 1 Oct 2007 02:27:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1237) Upgrade MVEL
 library to 1.2.final
Message-ID: <5418439.1191220061206.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade MVEL library to 1.2.final
---------------------------------

                 Key: JBRULES-1237
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1237
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.1
            Reporter: Joshua Jackson
         Assigned To: Mark Proctor
            Priority: Minor
             Fix For: 4.0.2


Upgrade the current mvel library that is used by drools to mvel 1.2.final as it has some fixes


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
Message-ID: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>

HTTP session replication failover failures with async buddy replication
-----------------------------------------------------------------------

                 Key: JBAS-4766
                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering, Web (Tomcat) service
    Affects Versions: JBossAS-4.2.0.GA
         Environment: 4 nodes, buddy async replication, 100 clients
            Reporter: Dominik Pospisil
         Assigned To: Brian Stansberry
         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log

Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26504102.1191224141612.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: test.log

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7567825.1191224141761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: driver.log

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:41 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3264253.1191224141926.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf01.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:42 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19808037.1191224142091.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf02.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:35:42 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:35:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11082282.1191224142254.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf03.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 03:37:50 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 1 Oct 2007 03:37:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29884110.1191224270728.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: server-perf04.log.gz

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 04:03:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 04:03:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4764) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <366369.1191043241063.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7605157.1191225821217.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4764?page=all ]

Dimitris Andreadis updated JBAS-4764:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.0.3 SP1)

One a new jira you cannot set fix version one that has already been released.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4764
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4764
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-3.2.8.SP1
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 04:35:42 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 04:35:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4767) Upgrade jbossws to
 2.0.1 (from 1.2.1.GA)
Message-ID: <16412352.1191227742601.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade jbossws to 2.0.1 (from 1.2.1.GA)
----------------------------------------

                 Key: JBAS-4767
                 URL: http://jira.jboss.com/jira/browse/JBAS-4767
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Web Services
            Reporter: Dimitris Andreadis
             Fix For: JBossAS-4.2.2.GA




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:05:45 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:05:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1052)
 getAllTaskInstances(), getAllProcessInstances()
In-Reply-To: <24526709.1189013891148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28673240.1191229545014.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1052?page=comments#action_12379504 ] 
            
Fady Matar commented on JBPM-1052:
----------------------------------

Another solution to avoid probable cross-database differences would be to create the hibernate query that would retrieve all the task instances and allow the "super manager" as stated before to view / perform action on them.

Please note that this query might be an over kill when the existing tasks grow large and there has to be a mechanism to allow ordering, grouping and sorting those tasks to reduce the processing time

> getAllTaskInstances(), getAllProcessInstances()
> -----------------------------------------------
>
>                 Key: JBPM-1052
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1052
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: s b
>         Assigned To: Tom Baeyens
>            Priority: Minor
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Businesses often want a "super manager" to have the ability to see and work on the tasks of all users.  With the current jBPM, it is very difficult to generate a list of all TaskInstances.
> The feature requested is a method for listing all TaskInstances regardless of user.  It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds.
> One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances.  I don't know if that is portable to all databases; it works well for Oracle.
> It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours.
> A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons.
> A criticism is that the method would introduce scalability / performance problems.  That is always an issue that is difficult to avoid completely depending on the application.  For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:16:43 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:16:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1053) jBPM Build Files
 Search for build.properties in ${user.home}/jbpm/build.properties
In-Reply-To: <20341275.1189026614587.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29056963.1191230203324.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1053?page=comments#action_12379506 ] 
            
Fady Matar commented on JBPM-1053:
----------------------------------

jBPM is already defaulted to a sensible configuration file within the system build/build.properties. Users can override this functionality by implementing their creating their own build.properties in their home directories. 

> jBPM Build Files Search for build.properties in ${user.home}/jbpm/build.properties
> ----------------------------------------------------------------------------------
>
>                 Key: JBPM-1053
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1053
>             Project: JBoss jBPM
>          Issue Type: Release
>            Reporter: Christopher Brock
>         Assigned To: Tom Baeyens
>
> This has become a pretty serious problem in our attempts to create automated build and patches for SOA.   It creates a mess by forcing us to have our scripts create directories outside the build structure.  
> It would be helpful if the either a delegate configuration file was introduced to allow us to override this, or better yet, if jBPM simply defaulted to a sensible configuration file inside it's source structure.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:21:41 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 1 Oct 2007 05:21:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1729) AjaxInterceptor
 with a different context root
In-Reply-To: <13290468.1191167861321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15068575.1191230501354.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1729?page=all ]

Thomas Heute updated JBPORTAL-1729:
-----------------------------------

    Fix Version/s: 2.6.3 Final
                       (was: 2.6.2 Final)

> AjaxInterceptor with a different context root
> ---------------------------------------------
>
>                 Key: JBPORTAL-1729
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1729
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.1 Final
>         Environment: fedora 7, eclipse europa, java 5 update 12
>            Reporter: Luca Stancapiano
>             Fix For: 2.6.3 Final
>
>         Attachments: patch_AjaxInterceptor.zip
>
>
> about org.jboss.portal.core.controller.ajax.AjaxInterceptor class
> row 75:
> pageProps.put(DynaConstants.RESOURCE_BASE_URL, "/portal-ajax/dyna");
> It uses a static hard coded link to use portal-ajax application , but if we need to change context root, it points to the same link and so in some cases there can to be redirect problems.
> In my case, I have two portal instances on two different hosts and through mod_jk I redirect the first instance using /portal* path and the second with /two_portal* path.
> I cannot o use /portal-ajax path from the second host because mod_jk see that path and it redirects to the first portal instance, then I need to use a different path else I pay a unnecessary connection.
> To resolve this problem I added a property TargetContextPath (as for org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor class) into AjaxInterceptor and substituted it to /portal-ajax/ link.
> private String targetContextPath = "/portal-ajax";
>    public String getTargetContextPath()
>    {
>       return targetContextPath;
>    }
>    public void setTargetContextPath(String context)
>    {
>       targetContextPath = context;
>    }
> it can to be configured through AjaxInterceptor MBean into META-INF/jboss-service.xml. Here there is an example:
>    <mbean
>       code="org.jboss.portal.core.controller.ajax.AjaxInterceptor"
>       name="portal:service=Interceptor,type=Command,name=Ajax"
>       xmbean-dd=""
>       xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
>       <xmbean/>
>       <attribute name="TargetContextPath">/portal-ajax</attribute>
>    </mbean>

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:24:41 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:24:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1054) deprecate
 expression on action in favour of execute
In-Reply-To: <26830440.1189074491245.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6407296.1191230681470.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1054?page=comments#action_12379507 ] 
            
Fady Matar commented on JBPM-1054:
----------------------------------

Let's create an alias and deprecate the existing expression attribute, we'll maintain the deprecation all along the line of 3.x releases and remove it by version 4. The documentation must reflect those changes as well and the process designer needs to throw out a warning regarding this deprecation

> deprecate expression on action in favour of execute
> ---------------------------------------------------
>
>                 Key: JBPM-1054
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1054
>             Project: JBoss jBPM
>          Issue Type: Task
>    Affects Versions:  jBPM jPDL 3.2.1
>            Reporter: Pete Muir
>         Assigned To: Tom Baeyens
>            Priority: Critical
>
> As discussed on the forum, add an execute attribute (as an alias to expression) to the action element, and (TBD) deprecate the expression.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:24:41 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 05:24:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-601) Parallelizing test
	suite
In-Reply-To: <4314937.1190966381352.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8426757.1191230681610.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-601?page=comments#action_12379508 ] 
            
Bela Ban commented on JGRP-601:
-------------------------------

Comment from Ryan, suggesting Husdon instead of DTF:
The DTF is more than just running jobs in parallel, it's a comprehensive test system with it's own test definition and reporting sub-systems.  So to take full advantage of it, you would want to author your tests in the DTF test specification format.  It can run JUnit tests, but is not particularly better at this than Hudson.  And the reporting and control interfaces are probably worse.

Richard, do you mind sending Bela a link to the documentation we have for the DTF?  This will at least give him an idea of what is required and can be accomplished.

If you just want to parallelize your test suites, you can do that very easily in Hudson without requiring you guys to have to learn how to write tests for the DTF.  For instance, Kabir did this for AOP:

http://hudson.qa.jboss.com/hudson/view/AOP/

He can now run all of his test suites across our "linux" slave pool with the click of a few buttons.

We also use it to run the JBoss test suite across HPUX, Solaris, Windows, and Linux and multiple JVM's on each platform:

http://hudson.qa.jboss.com/hudson/view/EAP/

Steve Ebersole uses it to run the Hibernate test suite across a matrix of DB's and Drivers:

http://hudson.qa.jboss.com/hudson/job/hibernate-3.2/

So if you just want to run JUnit jobs in parallel, or perhaps across a configuration matrix, Hudson is what you want.  
Ryan 

> Parallelizing test suite
> ------------------------
>
>                 Key: JGRP-601
>                 URL: http://jira.jboss.com/jira/browse/JGRP-601
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.x
>
>
> Run the following in parallel
> - functional tests
> - stack-specific tests
> E.g. run UDP tests in parallel with TCP
> Look at DTF (Distributed Test Framework) for 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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:30:41 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:30:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1189) Implement
 JGroups Connect + State Transfer in JBC
In-Reply-To: <18329595.1190729863300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6501380.1191231041840.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1189?page=all ]

Vladimir Blagojevic resolved JBCACHE-1189.
------------------------------------------

    Resolution: Done

Implemented in CacheImpl#internalStart

> Implement JGroups Connect + State Transfer in JBC
> -------------------------------------------------
>
>                 Key: JBCACHE-1189
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1189
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:30:42 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:30:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1189) Implement
 JGroups Connect + State Transfer in JBC
In-Reply-To: <18329595.1190729863300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17872641.1191231042285.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1189?page=comments#action_12379511 ] 
            
Vladimir Blagojevic commented on JBCACHE-1189:
----------------------------------------------

Verified that all state transfer tests pass.

> Implement JGroups Connect + State Transfer in JBC
> -------------------------------------------------
>
>                 Key: JBCACHE-1189
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1189
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:49:45 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 1 Oct 2007 05:49:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-616) prevent duplicate
 form submissions
Message-ID: <16013877.1191232185238.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-616?page=comments#action_12379512 ] 
            
Fady Matar commented on JBPM-616:
---------------------------------

This is purely related to JSF, we need to investigate an existing JSF token implementation or implement our own until this is supported in the next releases of JSF

> prevent duplicate form submissions
> ----------------------------------
>
>                 Key: JBPM-616
>                 URL: http://jira.jboss.com/jira/browse/JBPM-616
>             Project: JBoss jBPM
>          Issue Type: Task
>          Components: Web Interface
>            Reporter: Tom Baeyens
>         Assigned To: David Lloyd
>             Fix For: jBPM 3.3
>
>
> for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:49:45 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:49:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-597) Allow generic view
	payload
In-Reply-To: <25895767.1190794361110.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18967299.1191232185613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-597?page=all ]

Vladimir Blagojevic resolved JGRP-597.
--------------------------------------

    Resolution: Done

Added event PREPARE_VIEW that is passed up/down stack right after we construct a new view. Thus any protocol or building block can append a payload to a new view to be installed.

> Allow generic view payload
> --------------------------
>
>                 Key: JGRP-597
>                 URL: http://jira.jboss.com/jira/browse/JGRP-597
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> View installation is one of the most important events in group/cluster communication. However, currently we do not allow building blocks to append any custom data to views being installed. At coordinator, during view preparation, building block should be notified that a new view is being created so that building block can append payload to the view that is going to be installed for the cluster. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 05:51:41 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 1 Oct 2007 05:51:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-337) Make STOP_FLUSH
 phase in FLUSH asynchronous
In-Reply-To: <26343747.1159867721489.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6962168.1191232301367.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-337?page=all ]

Vladimir Blagojevic resolved JGRP-337.
--------------------------------------

    Resolution: Done

Commit set: 
protocols/pbcast/FLUSH.java 1.67

> Make STOP_FLUSH phase in FLUSH asynchronous
> -------------------------------------------
>
>                 Key: JGRP-337
>                 URL: http://jira.jboss.com/jira/browse/JGRP-337
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.4
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 2.6
>
>
> Revert back from synchronous. Only possible if we make the STOP_FLUSH message *out-of-band* !

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:15:42 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 1 Oct 2007 06:15:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1051) A bean without
 a security domain doesn't propagate caller
In-Reply-To: <25811297.1190098631036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2404851.1191233742684.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1051?page=comments#action_12379519 ] 
            
Carlo de Wolf commented on EJBTHREE-1051:
-----------------------------------------

I fixed the stateless test. It gobled up a NPE, which appears now in testUnsecureToSecureWithoutCredentials. And testUnsecureToSecureWithCredentials is now directly related to this issue.

> A bean without a security domain doesn't propagate caller
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1051
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1051
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Security
>            Reporter: Carlo de Wolf
>         Assigned To: Anil Saldhana
>
> In rev 65440 I changed the stateful unit test so that StatelessBean does have a security domain. But it should also work without one.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:28:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:28:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-259) Activate
 compression in marshaller
Message-ID: <29272003.1191234521301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ]

Tim Fox closed JBMESSAGING-259.
-------------------------------

    Resolution: Rejected

> Activate compression in marshaller
> ----------------------------------
>
>                 Key: JBMESSAGING-259
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Activate compression in marshaller for messages > x bytes. Make it configurable

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:32:52 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:32:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-681) Consolidate
 JMS related aspects into one JMS aspect
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24899560.1191234772760.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=comments#action_12379525 ] 
            
Tim Fox commented on JBMESSAGING-681:
-------------------------------------

We should remove AOP usage from the standard stack, and use java.lang.reflect proxies as EJB3 does to allow users to specify a stack of interceptors on both client and server side.

The functionality currently in the client side JMS aspects should be moved into a set of standard classes:

ConnectionFactory, Connection, Session, Consumer.

Note that this *do not* correspond to JMS connection factory, connection, consumer classes. These are a simpler abstraction.

We maintain the standard JMS object implementations which should delegate to these classes.

> Consolidate JMS related aspects into one JMS aspect
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:32:52 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 06:32:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1190) Eviction
 configuration should consider buddy backup regions as well.
Message-ID: <32922469.1191234772880.JavaMail.jira@cloud.prod.atl2.jboss.com>

Eviction configuration should consider buddy backup regions as well.
--------------------------------------------------------------------

                 Key: JBCACHE-1190
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eviction
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.2.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:32:53 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:32:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor AOP
	usage
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6495778.1191234773089.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

    Summary: Refactor AOP usage  (was: Consolidate JMS related aspects into one JMS aspect)

> Refactor AOP usage
> ------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:34:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:34:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor AOP
	usage
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32471100.1191234881389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)
    Priority: Critical  (was: Major)

> Refactor AOP usage
> ------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:34:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:34:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-25) Microcontainer
	integration
Message-ID: <14762022.1191234882023.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ]

Tim Fox updated JBMESSAGING-25:
-------------------------------

    Description: 
We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.

The microcontainer can also provide MBean interfaces transparently if needed.

This task is critical in allowing an "embedded JBM".

This is critical to kick start ESB.

  was:
We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.

The microcontainer can also provide MBean interfaces transparently if needed.

This task is critical in allowing an "embedded JBM".

This is critical to kick start ESB

       Priority: Critical  (was: Major)

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Aaron Walker
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:36:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-25)
	Microcontainer integration
Message-ID: <19968730.1191235001641.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=comments#action_12379527 ] 
            
Tim Fox commented on JBMESSAGING-25:
------------------------------------

We should also remove all references to JNDI from our core POJOs.

JBM should be usable, embedded without any use of JNDI.

All JNDI usage should occur in a separate layer.

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Aaron Walker
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:36:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-815) Extra message
 created if server fails when send and ACK are synchronized
In-Reply-To: <5708755.1170803906788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29808311.1191235001862.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ]

Tim Fox updated JBMESSAGING-815:
--------------------------------

    Priority: Major  (was: Critical)

> Extra message created if server fails when send and ACK are synchronized
> ------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-815
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-815
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.0.1.SP3
>            Reporter: Clebert Suconic
>             Fix For: 2.0.0 Beta 1
>
>
> MultiThreadFailoverTest::testFailureOnSendReceiveSynchronized fails for this bug
> This test poisons the server to wait consumer and sender to be in a same point before crashing it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:38:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:38:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-406) Enabled local
 persistent storage per node
Message-ID: <13266561.1191235121384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ]

Tim Fox updated JBMESSAGING-406:
--------------------------------

       Summary: Enabled local persistent storage per node  (was: Enable file based persistent stores)
    Issue Type: Task  (was: Feature Request)
      Priority: Critical  (was: Major)

> Enabled local persistent storage per node
> -----------------------------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Implement non shared file based persistent store.
> Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this.
> Also look at HOWL. http://howl.objectweb.org/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:42:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:42:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Enabled
 local persistent storage per node
Message-ID: <26321063.1191235361348.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12379532 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

Currently messages are persisted via a RDBMs which is shared by all nodes in the cluster.

This provides a bottleneck. Also RDBMs are not well suited for persisting queue like data.

Each node should have its own persistent store for performance and scalability.

For failover all persistent stores should available by all nodes on a shared file system (e.g. GFS) - failover then becomes a simple matter of reopening the file based store on a different node on failover.

Where a shared filesystem is not available we will have to consider replicating to a buddy.

The best candidate for implementing local persistence currently is Berkely DB. However, due to the Berkely DB licence we cannot distribute it with JBM, therefore it would be up to the user to drop the Berkely DB jar in manually as part of the install.

We we would also need to provide a very simple JDBC PersistenceManager implementation to allow to run the tests and play about with the default distribution - this can work with HSQLDB.

> Enabled local persistent storage per node
> -----------------------------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Implement non shared file based persistent store.
> Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this.
> Also look at HOWL. http://howl.objectweb.org/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:44:49 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:44:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-608) Add a new
 compatibity and stress test layer based on JMS CTS
In-Reply-To: <13967074.1160688881540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20017340.1191235489517.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-608?page=all ]

Tim Fox updated JBMESSAGING-608:
--------------------------------

    Priority: Minor  (was: Major)

> Add a new compatibity and stress test layer based on JMS CTS
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-608
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-608
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> http://jmscts.sourceforge.net/index.html
> The stress part is especially interesting.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:46:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:46:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-989) Core refactoring
In-Reply-To: <20687334.1181830811626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24277185.1191235601183.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-989?page=all ]

Tim Fox closed JBMESSAGING-989.
-------------------------------

    Resolution: Rejected

We don't really need a separate task for this.

Various core changes will take place via other tasks.

> Core refactoring
> ----------------
>
>                 Key: JBMESSAGING-989
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-989
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Core refactoring-
> The old core classes are in dire need of reviewing and refactoring.
> The hierarchy of channel classes should be collapsed for simplicity, since there is only one real implementation of a channel.
> And the router class should be re-examined - do we need iterator etc
> Do we need iterator on the channel?
> All classes should be made cluster aware (including router).
> We can simplify things a *lot*!

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:46:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:46:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-752) Create safe
 mode where session concurrent access is checked
In-Reply-To: <32776071.1169034952624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23352622.1191235601300.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-752?page=all ]

Tim Fox updated JBMESSAGING-752:
--------------------------------

    Priority: Minor  (was: Major)

> Create safe mode where session concurrent access is checked
> -----------------------------------------------------------
>
>                 Key: JBMESSAGING-752
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-752
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> As per JMS spec, a JMS session is supposed to be only accessed from one thread at a time.
> This is so the implementor does not have to synchronize access which might degrade performance.
> However, users are often unaware of this and use the session concurrent by multiple threads, resulting in subtle or hard to identify bugs.
> We should create a "safeMode", where if enabled, concurrent access is checked.
> safeMode should be turned on for development and off for production, so no performance penalty is incurred in production.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:48:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-873) Down cache
	optimisation
In-Reply-To: <17669332.1172085995882.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21967604.1191235721233.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-873?page=all ]

Tim Fox closed JBMESSAGING-873.
-------------------------------

    Resolution: Out of Date

This is redundance - since using local persistence will involve refactoring of the paging code.

> Down cache optimisation
> -----------------------
>
>                 Key: JBMESSAGING-873
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-873
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> If there are no persistent messages in storage then when paging we can avoid flushing the downCache and loading from the db
> and just transfer from the downcache to the in memory list when loading

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:48:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1039) HTTP poller
	doesn't stop
In-Reply-To: <3265708.1186657442806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28570820.1191235721369.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1039?page=all ]

Tim Fox updated JBMESSAGING-1039:
---------------------------------

    Priority: Minor  (was: Major)

> HTTP poller doesn't stop
> ------------------------
>
>                 Key: JBMESSAGING-1039
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1039
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> I have temporarily commented out clusterviewupdatetst::testUpdateMixedConnectionFactory since, once started, the HTTP poller doesn't stop.
> Maybe this is a bug in remoting - need to investigate.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:48:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1049) Exceptions in
 logs after clustering test run
In-Reply-To: <28422090.1187257381307.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16000172.1191235721552.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1049?page=all ]

Tim Fox updated JBMESSAGING-1049:
---------------------------------

    Priority: Minor  (was: Major)

> Exceptions in logs after clustering test run
> --------------------------------------------
>
>                 Key: JBMESSAGING-1049
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1049
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> After running clustering tests, several exceptions are found in the logs.
> These seem innocuous since the test suite passes but we should investigate.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:50:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-242) Investigate
 requirements for different routing strategies
Message-ID: <28297212.1191235841219.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-242?page=all ]

Tim Fox updated JBMESSAGING-242:
--------------------------------

    Priority: Minor  (was: Major)

> Investigate requirements for different routing strategies
> ---------------------------------------------------------
>
>                 Key: JBMESSAGING-242
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-242
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Investigate whether we need to provide routers with different strategies, a la ReceiversImpl in JBossMQ

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:50:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-806) Allow JBM
 client to run in a jnlp (or other) sandbox
In-Reply-To: <25824752.1170441321637.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32581180.1191235841459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-806?page=all ]

Tim Fox updated JBMESSAGING-806:
--------------------------------

       Summary: Allow JBM client to run in a jnlp (or other) sandbox  (was: JBM is assuming it can look up system properties on the client side)
    Issue Type: Task  (was: Bug)
      Priority: Minor  (was: Major)

> Allow JBM client to run in a jnlp (or other) sandbox
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-806
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.2.0.Beta1, 1.0.1.SP3
>            Reporter: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work.
> This causes an exception to be thrown and the connection is not created.
> Need to catch the exception and set to null.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:52:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:52:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-377) Competing
 consumer on subscriptions
Message-ID: <12151542.1191235961347.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-377?page=all ]

Tim Fox updated JBMESSAGING-377:
--------------------------------

    Priority: Minor  (was: Major)

> Competing consumer on subscriptions
> -----------------------------------
>
>                 Key: JBMESSAGING-377
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-377
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to have competing consumers on (durable) subscriptions. This will allow us to load balance processing of messages from a durable subscription across multiple consumers.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:52:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:52:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1014) Look at
	JGroups anycast
In-Reply-To: <9508348.1184347872500.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26993600.1191235961491.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1014?page=all ]

Tim Fox closed JBMESSAGING-1014.
--------------------------------

    Resolution: Rejected

> Look at JGroups anycast
> -----------------------
>
>                 Key: JBMESSAGING-1014
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1014
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> To avoid issue with having to multicast even when there is only one subscriber

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:52:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:52:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-153) Support for
 very large messages
Message-ID: <23427483.1191235961933.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-153?page=all ]

Tim Fox updated JBMESSAGING-153:
--------------------------------

    Summary: Support for very large messages  (was: JBoss Messaging should be capable of handling real big files (tens of megabytes possibly a hundred))

> Support for very large messages
> -------------------------------
>
>                 Key: JBMESSAGING-153
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-153
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.0.0 alpha PR3
>            Reporter: Karl de Boer
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 4 minutes
>  Remaining Estimate: 4 minutes
>
> As dicussed during JBW Barcelona i want to ask to investigate if it is posible to reliably sent very big messages from one jboss messaging node to another one (most likely on top of HTTPS(S). The business case is: mulitple organisations working in one workflow on digitally signed documents where Quality of Service is extremely important for instance patent applications.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:54:52 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:54:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-180) Improve
 message priority algorithm
Message-ID: <25722780.1191236092545.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-180?page=all ]

Tim Fox updated JBMESSAGING-180:
--------------------------------

    Priority: Minor  (was: Major)

> Improve message priority algorithm
> ----------------------------------
>
>                 Key: JBMESSAGING-180
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-180
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The current message priority strategy is very crude and always delivers higher priority messages first if they exist.
> This can cause starvation of lower priority messages.
> The algorithm should be improved to prevent starvation.
> It may be an idea to make the algorithm pluggable using the strategy pattern.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:54:53 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:54:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-874) INVM
 persistent message optimisation
In-Reply-To: <1124366.1172086122591.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3043316.1191236093340.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-874?page=all ]

Tim Fox updated JBMESSAGING-874:
--------------------------------

    Priority: Minor  (was: Major)

> INVM persistent message optimisation
> ------------------------------------
>
>                 Key: JBMESSAGING-874
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-874
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> For persistent messages sent in vm, the message gets converted to a byte[] before db storage, it then gets converted back to a payload on recepipt - this is unnecessary - for the invm case. We should deal with it optimally.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:56:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:56:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-875) Non durable
 subscription optimisation
In-Reply-To: <8504212.1172086235512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8850294.1191236201226.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-875?page=all ]

Tim Fox closed JBMESSAGING-875.
-------------------------------

    Resolution: Out of Date

> Non durable subscription optimisation
> -------------------------------------
>
>                 Key: JBMESSAGING-875
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-875
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs.
> Basically I think we can acknowledge them before they are sent from server to client.
> This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks.
> On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver.
> This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:56:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:56:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-872) Convert
	destinations to ints
In-Reply-To: <10164095.1172085776484.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5420076.1191236201380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-872?page=all ]

Tim Fox closed JBMESSAGING-872.
-------------------------------

    Resolution: Rejected

I don't see any great gains by doing this

> Convert destinations to ints
> ----------------------------
>
>                 Key: JBMESSAGING-872
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-872
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> Destination implementations JBossQueue and JBossTopic are currently not much more than just Strings identifiers.
> When sending a message the destination (and possibly the replyto) need to be serialized with the message.
> If the Destinations are just identifiers then they could represented as ints making there less bytes to serialize.
> This could be significant for destinations with long names, e.g. 100 bytes -> 4 bytes (per message)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:58:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:58:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-839) Recover
 deliveries does not deal with paged references
In-Reply-To: <27585099.1171499561997.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3666283.1191236321139.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-839?page=all ]

Tim Fox closed JBMESSAGING-839.
-------------------------------

    Resolution: Rejected

Will become redundant with refactored paging

> Recover deliveries does not deal with paged references
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-839
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-839
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> When recovering deliveries ChannelSupport::recoverDeliveries after failover then there is a small possibility that the deliveries are not in memory but paged in storage  - we should cater for this situation.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 06:58:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 06:58:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-312) Refactor
	persistencemanager
Message-ID: <31886620.1191236321386.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ]

Tim Fox closed JBMESSAGING-312.
-------------------------------

    Resolution: Out of Date

> Refactor persistencemanager
> ---------------------------
>
>                 Key: JBMESSAGING-312
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> Refactor PersistenceManager to make less monolithic.
> The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store.
> Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState.
> The TransactionCallback should be removed to it's own java file.
> The locking operations should occur in the caller.
> There should be an abstraction PMTxContext which can be passed into PM operations to group them.
> This should dramatically clarify and simplify things

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:00:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-868) Ordering issue
 when mixing unicast and multicast
In-Reply-To: <6386295.1172060495647.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26932910.1191236441264.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-868?page=all ]

Tim Fox closed JBMESSAGING-868.
-------------------------------

    Resolution: Won't Fix

> Ordering issue when mixing unicast and multicast
> ------------------------------------------------
>
>                 Key: JBMESSAGING-868
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-868
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.CR1
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> When routing a set of messages to nodes in a cluster, if some are routed using unicast and others using multicast (as an optimisation), then earlier messages can "overtake" later sent messages, so they are received in the wrong order on the recipient.
> This caused DefaultClusteredPostOfficeTest::testClusteredNonPersistentRouteWithFilterRecoverable to fail because messages were received out of order

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:00:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-576) Separate paging
 and persistence functionality
In-Reply-To: <17187039.1159815521510.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5872998.1191236441419.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-576?page=all ]

Tim Fox closed JBMESSAGING-576.
-------------------------------

    Resolution: Rejected

> Separate paging and persistence functionality
> ---------------------------------------------
>
>                 Key: JBMESSAGING-576
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-576
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.2.0.Alpha1, 1.0.1.CR5
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Reference management gets complex when we have to take into account messages and refs paged and not paged to storage especially if
> the database is shared, this means we end up having to do extra queries to work out if the ref is alredy in the database etc.
> We should separate the paging functionality out, so it doesn't page to the normal persistent store, but to a separate paging store which
> typically would be a local file based store using HOWL or some other fast logger.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:00:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:00:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-676) Unreliable link
	scenario
In-Reply-To: <29509260.1165555418180.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23220141.1191236442948.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-676?page=all ]

Tim Fox closed JBMESSAGING-676.
-------------------------------

    Resolution: Rejected

> Unreliable link scenario
> ------------------------
>
>                 Key: JBMESSAGING-676
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-676
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Ovidiu Feodorov
>             Fix For: 2.0.0 Beta 1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:02:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4768) TransactionLocal
 cannot be locked when transaction is marked rollback only
Message-ID: <30772673.1191236561517.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------

                 Key: JBAS-4768
                 URL: http://jira.jboss.com/jira/browse/JBAS-4768
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Transaction Manager
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Adrian Brock
         Assigned To: Jonathan Halliday
            Priority: Critical
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA


Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.

Here's the stacktrace of the error:

2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
java.lang.IllegalStateException: Transaction not active
        at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
        at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
        at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
        at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
        at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
        at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
        at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
        at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)

You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-543) Use a file
 based transaction logger instead of logging in the database
In-Reply-To: <4467615.1158151954233.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10589639.1191236561798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-543?page=all ]

Tim Fox closed JBMESSAGING-543.
-------------------------------

    Resolution: Duplicate Issue

> Use a file based transaction logger instead of logging in the database
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-543
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-543
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> Currently we are logging prepared state transactions in the database.
> Instead, we should utilise a tried and tested transaction logger for performance reasons.
> We should evaluate both JBoss TS objectstore, and HOWL to take this role

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:42 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:02:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4768) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <30772673.1191236561517.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11125223.1191236562245.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4768?page=all ]

Dimitris Andreadis deleted JBAS-4768:
-------------------------------------


> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4768
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4768
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1053) Write a test
 for JBMESSAGING-1031
In-Reply-To: <2848037.1187894843075.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4958503.1191236562372.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1053?page=all ]

Tim Fox updated JBMESSAGING-1053:
---------------------------------

    Priority: Minor  (was: Major)

> Write a test for JBMESSAGING-1031
> ---------------------------------
>
>                 Key: JBMESSAGING-1053
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1053
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: diff.patch
>
>
> I have fixed JBMESSAGING-1031 using a manual test.. we need to add a testcase.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1048) Test DB2
 config against Hudson
In-Reply-To: <16680822.1187133001211.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32639393.1191236562736.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1048?page=all ]

Tim Fox updated JBMESSAGING-1048:
---------------------------------

    Priority: Minor  (was: Major)

> Test DB2 config against Hudson
> ------------------------------
>
>                 Key: JBMESSAGING-1048
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1048
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:02:43 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:02:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-26) Standalone
 Messaging configuration.
Message-ID: <4385477.1191236563036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ]

Tim Fox closed JBMESSAGING-26.
------------------------------

    Resolution: Rejected

> Standalone Messaging configuration.
> -----------------------------------
>
>                 Key: JBMESSAGING-26
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. 
> Must have at least the JNDI server, Logging, Remoting and AOP support.
> We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:04:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:04:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-983) Messages can
 be delivered after connection is stopped
In-Reply-To: <20962966.1181209274478.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20081795.1191236681151.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-983?page=all ]

Tim Fox updated JBMESSAGING-983:
--------------------------------

    Priority: Minor  (was: Major)

> Messages can be delivered after connection is stopped
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-983
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-983
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> Stopping a connection does not currently block until all current onMessage invocations are complete, as per JMS spec.
> We need to make sure it does.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:04:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:04:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4769) TransactionLocal
 cannot be locked when transaction is marked rollback only
Message-ID: <2618872.1191236681324.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------

                 Key: JBAS-4769
                 URL: http://jira.jboss.com/jira/browse/JBAS-4769
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Transaction Manager
            Reporter: Dimitris Andreadis
         Assigned To: Adrian Brock
             Fix For:  JBossAS-5.0.0.Beta3


Apply JBAS-4675 fix to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:46 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4769) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <2618872.1191236681324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21682821.1191236806944.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4769?page=all ]

Dimitris Andreadis updated JBAS-4769:
-------------------------------------

    Component/s: JB5-Transaction Manager
                     (was: Transaction Manager)
       Assignee: Jonathan Halliday  (was: Adrian Brock)

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4769
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4769
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Apply JBAS-4675 fix to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1086) Implement
	Database updater
Message-ID: <14676569.1191236807091.JavaMail.jira@cloud.prod.atl2.jboss.com>

Implement Database updater
--------------------------

                 Key: JBMESSAGING-1086
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1086
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 2.0.0 Beta 1


JBM 2.0 will use local persistent storage per node, in most cases non relational.

Some users still like to see their messages in a database.

We should implement a component that can optionally run on each node, that intermittently checks the local storage to new messages / delete messages and updates a shared database with the message data.

Hibernate should be used for this component so it can work with any supported RDBMs.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4675) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <27607648.1189008194281.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22866091.1191236807442.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]

Dimitris Andreadis closed JBAS-4675.
------------------------------------

    Fix Version/s:     (was: JBossAS-4.2.2.GA)
       Resolution: Done

Closing this for 4.2.x. Created a different issue for AS5.

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4675
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4675
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4675) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <27607648.1189008194281.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29782219.1191236807650.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]

Dimitris Andreadis reopened JBAS-4675:
--------------------------------------

             

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4675
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4675
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:47 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:06:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4675) TransactionLocal
 cannot be locked when transaction is marked rollback only
In-Reply-To: <27607648.1189008194281.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5727287.1191236807897.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]

Dimitris Andreadis closed JBAS-4675.
------------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
                       (was:  JBossAS-5.0.0.Beta3)
       Resolution: Done

> TransactionLocal cannot be locked when transaction is marked rollback only
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4675
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4675
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Adrian Brock
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
> the transaction local cannot be locked when the status is ABORT.
> Here's the stacktrace of the error:
> 2007-09-05 17:50:44,899 DEBUG [org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with transaction
> java.lang.IllegalStateException: Transaction not active
>         at com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
>         at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
>         at org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
>         at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
>         at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
>         at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
>         at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
> You shouldn't be able to create a new delegate if the transaction is not active,
> but you should be able to retrieve existing ones.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:06:48 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:06:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16840047.1191236808031.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=all ]

Tim Fox updated JBMESSAGING-544:
--------------------------------

        Summary: Replace client-server transport with NIO based transport  (was: Use NBIO for connection model)
    Description: 
For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.

Unfortunately the JBoss remoting model does not currently allows this.

We can either drive JBoss Remoting to support this model (may take some time)

Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.

This would also solve the problem of providing a functional and performant multiplex transport.

Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.

On top of that we can introduce simple framing in order to provide multiplex functionality.

  was:
For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server.

Unfortunately the JBoss remoting model does not currently allows this.

We can either drive JBoss Remoting to support this model (may take some time)

Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.

This would also solve the problem of providing a functional and performant multiplex transport.

Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.

On top of that we can introduce simple framing in order to provide multiplex functionality.

       Priority: Critical  (was: Major)

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:08:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-848) Incorrect
 mail.smtp.host property + configurable mail from address
In-Reply-To: <17596894.1172162918880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8017960.1191236921890.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-848?page=comments#action_12379543 ] 
            
Tom Baeyens commented on JBPM-848:
----------------------------------

Fady, i don't get your remark.

As far as I remember, it should be possible for people to specify the property jbpm.mail.from.address in their jbpm.cfg.xml file.  Can you try to reproduce and compare the problem report of Sebastian with the docs and the code ?

In case our code is the problem, how do you think we should fix it ?

> Incorrect mail.smtp.host property + configurable mail from address
> ------------------------------------------------------------------
>
>                 Key: JBPM-848
>                 URL: http://jira.jboss.com/jira/browse/JBPM-848
>             Project: JBoss jBPM
>          Issue Type: Patch
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2 beta 2
>            Reporter: Bruno Dumon
>         Assigned To: Tom Baeyens
>             Fix For: jBPM jPDL 3.2.2
>
>         Attachments: mailpatch_20070222.txt, mailpatch_v2.txt
>
>
> jBPM incorrectly sets "jbpm.mail.smtp.host" instead of "mail.smtp.host" in the properties passed to JavaMail. As a consequence, JavaMail always tries to send to localhost. It seems this was introduced by accident here:
> http://fisheye.jboss.com/browse/JBPM/jbpm.3/src/java.jbpm/org/jbpm/mail/Mail.java?r1=1.4&r2=1.5
> The attached patch fixes this.
> Also, the from address for mails is currently hardcoded to "jbpm at noreply". Many SMTP servers don't allow an invalid origin domain name (as do many spam filters), this is the exception I get:
> javax.mail.SendFailedException: Sending failed;
>   nested exception is:
>         class javax.mail.SendFailedException: Invalid Addresses;
>   nested exception is:
>         class javax.mail.SendFailedException: 450 <jbpm at noreply>: Sender address rejected: Domain not found
> The attached patch also makes the from address configurable via jbpm.cfg.xml.
> Patches are against current CVS and taken with the jbpm.3/jpdl directory as root.
> Thanks for taking the time to look at 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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:08:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22576267.1191236922165.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=comments#action_12379544 ] 
            
Tim Fox commented on JBMESSAGING-544:
-------------------------------------

After discusssion with the remoting team and other interested parties, our requirements will eventually be catered for by the new Remoting 3.

However Remoting 3 will not be released in time for JBM 2.0, therefore we will use MINA directly and swap it out later for JBR 3.

We need to make sure that MINA satisfies our requirements for HTTP, HTTPS, SSL etc

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:42 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:08:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
Message-ID: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionLocal.get() not sufficiently pluggable
-------------------------------------------------

                 Key: JBAS-4770
                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JB5-Transaction Manager
            Reporter: Dimitris Andreadis
         Assigned To: Mark Little
             Fix For:  JBossAS-5.0.0.Beta3


JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:08:42 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:08:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1025) Add test in
 GroupManagementTest
In-Reply-To: <24748680.1186597189354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33319407.1191236922508.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1025?page=all ]

Tim Fox updated JBMESSAGING-1025:
---------------------------------

    Priority: Minor  (was: Major)

> Add test in GroupManagementTest
> -------------------------------
>
>                 Key: JBMESSAGING-1025
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1025
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> .... that tests that failover map is created in vew order

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:10:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17893203.1191237041241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4770?page=all ]

Dimitris Andreadis reassigned JBAS-4770:
----------------------------------------

    Assignee: Jonathan Halliday  (was: Mark Little)

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:10:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4748)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <19029355.1190647481599.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9968477.1191237041375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4748?page=all ]

Dimitris Andreadis updated JBAS-4748:
-------------------------------------

        Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
    Affects Version/s:     (was: JBossAS-5.0.0.Beta2)

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4748
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4748
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Jonathan Halliday
>         Assigned To: Jonathan Halliday
>             Fix For: JBossAS-4.2.2.GA
>
>
> per discussion in forum thread ref below, the TransactionLocal.get() method calls storeValue in certain cases. Although the javadoc warns that the method may throw IllegalStateException, not all of the code in the app server that uses it can actually deal with that. With the old delegate implementation it did not need to. With changes to the way the TransactionLocalDelegate is implemented by JBossTS, this stared to cause problems.  Per Adrian's suggestion this is resolved by masking the exception if it occurs.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:10:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4748)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <19029355.1190647481599.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14347409.1191237041512.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4748?page=all ]

Dimitris Andreadis closed JBAS-4748.
------------------------------------

    Resolution: Done

Closed in 4.2.x. Created a separate task for Trunk.

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4748
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4748
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Jonathan Halliday
>         Assigned To: Jonathan Halliday
>             Fix For: JBossAS-4.2.2.GA
>
>
> per discussion in forum thread ref below, the TransactionLocal.get() method calls storeValue in certain cases. Although the javadoc warns that the method may throw IllegalStateException, not all of the code in the app server that uses it can actually deal with that. With the old delegate implementation it did not need to. With changes to the way the TransactionLocalDelegate is implemented by JBossTS, this stared to cause problems.  Per Adrian's suggestion this is resolved by masking the exception if it occurs.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:12:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:12:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1052)
 getAllTaskInstances(), getAllProcessInstances()
In-Reply-To: <24526709.1189013891148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29473795.1191237161277.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1052?page=comments#action_12379546 ] 
            
Tom Baeyens commented on JBPM-1052:
-----------------------------------

Current web app blurs the authorization a bit.  Basically, there is no real authorization scheme yet.  One of the things that certainly should be fixed is that by default users should only be able to see their own task lists.

Maybe we could have a navigation link to the full list of tasks separately, but that link should only be visible/accessible based on a security role manager.  or something like that.

> getAllTaskInstances(), getAllProcessInstances()
> -----------------------------------------------
>
>                 Key: JBPM-1052
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1052
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: s b
>         Assigned To: Tom Baeyens
>            Priority: Minor
>   Original Estimate: 2 days
>  Remaining Estimate: 2 days
>
> Businesses often want a "super manager" to have the ability to see and work on the tasks of all users.  With the current jBPM, it is very difficult to generate a list of all TaskInstances.
> The feature requested is a method for listing all TaskInstances regardless of user.  It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds.
> One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances.  I don't know if that is portable to all databases; it works well for Oracle.
> It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours.
> A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons.
> A criticism is that the method would introduce scalability / performance problems.  That is always an issue that is difficult to avoid completely depending on the application.  For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:12:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:12:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-942) Performance
	comparisons
In-Reply-To: <2148587.1176983619628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1812759.1191237161415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-942?page=all ]

Tim Fox updated JBMESSAGING-942:
--------------------------------

    Fix Version/s: Performance metrics, benchmarks and scalability testing
                       (was: Unscheduled)

> Performance comparisons
> -----------------------
>
>                 Key: JBMESSAGING-942
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-942
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>             Fix For: Performance metrics, benchmarks and scalability testing
>
>
> We need to make perfomance comparisons between JBR and MINA.
> Also between JBM and ActiveMQ and QPid

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:12:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:12:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-942) Performance
	comparisons
In-Reply-To: <2148587.1176983619628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26982150.1191237161536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-942?page=all ]

Tim Fox updated JBMESSAGING-942:
--------------------------------

    Description: Make performance comparisons between JBM and other messaging systems.  (was: We need to make perfomance comparisons between JBR and MINA.

Also between JBM and ActiveMQ and QPid)

> Performance comparisons
> -----------------------
>
>                 Key: JBMESSAGING-942
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-942
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>             Fix For: Performance metrics, benchmarks and scalability testing
>
>
> Make performance comparisons between JBM and other messaging 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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:14:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:14:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-603) Performance
	graphs
In-Reply-To: <23921338.1160165441490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2319217.1191237281271.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-603?page=all ]

Tim Fox closed JBMESSAGING-603.
-------------------------------

    Resolution: Duplicate Issue

> Performance graphs
> ------------------
>
>                 Key: JBMESSAGING-603
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-603
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>             Fix For: Unscheduled
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:14:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 07:14:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1087) Clustering
 scalability tests
Message-ID: <1256813.1191237281609.JavaMail.jira@cloud.prod.atl2.jboss.com>

Clustering scalability tests
----------------------------

                 Key: JBMESSAGING-1087
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1087
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: Performance metrics, benchmarks and scalability testing


Setup clustering scalabiity tests on the clustering lab.

Design metrics and see how performance varies with number of nodes etc.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:17:12 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:17:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1053) jBPM Build Files
 Search for build.properties in ${user.home}/jbpm/build.properties
In-Reply-To: <20341275.1189026614587.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30879988.1191237432326.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1053?page=comments#action_12379547 ] 
            
Tom Baeyens commented on JBPM-1053:
-----------------------------------

Christopher, please explain your requirements a bit more concrete.

This is what we currently have: a cvs structure that performs a full build with defaults in cvs.  The idea is that during continious integration, the cvs sources are fetched as is so that the complete sources can be cleaned and fetched again.  So any specific build configurations by default have to go outside the cvs sources structure.  That is why I don't get your request.  You don't *have* to have a custom build.properties file.  It's only necessary when you want to override default properties.  Maybe the defaults that we have are not as you want.  In that case, be more specific.

> jBPM Build Files Search for build.properties in ${user.home}/jbpm/build.properties
> ----------------------------------------------------------------------------------
>
>                 Key: JBPM-1053
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1053
>             Project: JBoss jBPM
>          Issue Type: Release
>            Reporter: Christopher Brock
>         Assigned To: Tom Baeyens
>
> This has become a pretty serious problem in our attempts to create automated build and patches for SOA.   It creates a mess by forcing us to have our scripts create directories outside the build structure.  
> It would be helpful if the either a delegate configuration file was introduced to allow us to override this, or better yet, if jBPM simply defaulted to a sensible configuration file inside it's source structure.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:17:12 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:17:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1054) deprecate expression
 on action in favour of execute
In-Reply-To: <26830440.1189074491245.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19585034.1191237432484.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1054?page=all ]

Tom Baeyens updated JBPM-1054:
------------------------------

    Fix Version/s: jBPM jPDL 3.2.3

> deprecate expression on action in favour of execute
> ---------------------------------------------------
>
>                 Key: JBPM-1054
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1054
>             Project: JBoss jBPM
>          Issue Type: Task
>    Affects Versions:  jBPM jPDL 3.2.1
>            Reporter: Pete Muir
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> As discussed on the forum, add an execute attribute (as an alias to expression) to the action element, and (TBD) deprecate the expression.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:18:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:18:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPM-616) prevent duplicate
 form submissions
Message-ID: <20429096.1191237521131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-616?page=all ]

Tom Baeyens reassigned JBPM-616:
--------------------------------

    Assignee: Tom Baeyens  (was: David Lloyd)

> prevent duplicate form submissions
> ----------------------------------
>
>                 Key: JBPM-616
>                 URL: http://jira.jboss.com/jira/browse/JBPM-616
>             Project: JBoss jBPM
>          Issue Type: Task
>          Components: Web Interface
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>             Fix For: jBPM 3.3
>
>
> for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:18:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 07:18:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-616) prevent duplicate
	form submissions
Message-ID: <1886975.1191237521270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-616?page=all ]

Tom Baeyens updated JBPM-616:
-----------------------------

    Priority: Minor  (was: Major)

> prevent duplicate form submissions
> ----------------------------------
>
>                 Key: JBPM-616
>                 URL: http://jira.jboss.com/jira/browse/JBPM-616
>             Project: JBoss jBPM
>          Issue Type: Task
>          Components: Web Interface
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>            Priority: Minor
>             Fix For: jBPM 3.3
>
>
> for hints and tips, you can have a look at http://raibledesigns.com/page/rd?anchor=how_does_your_mvc_framework

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:24:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:24:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4667) Wrong logic in
 CachedConnectionManager.getCloseConnectionSynchronization()
In-Reply-To: <33485329.1188920711605.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23262613.1191237881862.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4667?page=all ]

Dimitris Andreadis closed JBAS-4667.
------------------------------------

    Resolution: Done

Closing this task for 4.2.x. Created separate issues to track the changes in JBoss trunk. Essentially we are waiting there for the next jbossts upgrade.

> Wrong logic in CachedConnectionManager.getCloseConnectionSynchronization()
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4667
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4667
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.0.4.GA
>            Reporter: Oleg Nitz
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>         Attachments: testbmtsfsb.zip
>
>
> If the tx is not active (for example it has STATUS_PREPARING), then the method always returns null, even if the associated CloseConnectionSynchronization exists.
> This results in wrong warnings about non-closed connections, since when the close() is called for a connector, in CachedConnectionManager.unregisterConnection() a null value is returned from getCloseConnectionSynchronization() and the connector remains in the list of non-closed resources for the transaction.
> I think this bug was introduced here: http://jira.jboss.com/jira/browse/JBAS-31#action_12310798
> I propose the following solution:
> --- CachedConnectionManager.java.orig	2005-11-22 02:10:41.000000000 +0200
> +++ CachedConnectionManager.java	2007-09-04 18:42:48.000000000 +0300
> @@ -544,13 +544,13 @@
>        try
>        {
>           Transaction tx = tm.getTransaction();
> -         if (TxUtils.isActive(tx))
> +         if (tx != null)
>           {
>              TransactionSynchronizer.lock(tx);
>              try
>              {
>                 CloseConnectionSynchronization cas = (CloseConnectionSynchronization) TransactionSynchronizer.getCCMSynchronization(tx);
> -               if (cas == null && createIfNotFound)
> +               if (cas == null && createIfNotFound && TxUtils.isActive(tx))
>                 {
>                    cas = new CloseConnectionSynchronization();
>                    TransactionSynchronizer.registerCCMSynchronization(tx, cas);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:26:41 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 1 Oct 2007 07:26:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4767) Upgrade jbossws to
 2.0.1 (from 1.2.1.GA)
In-Reply-To: <16412352.1191227742601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32763163.1191238001105.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4767?page=all ]

Dimitris Andreadis reassigned JBAS-4767:
----------------------------------------

    Assignee: Thomas Diesler

> Upgrade jbossws to 2.0.1 (from 1.2.1.GA)
> ----------------------------------------
>
>                 Key: JBAS-4767
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4767
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:37:41 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 07:37:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1237) Upgrade MVEL
 library to 1.2.final
In-Reply-To: <5418439.1191220061206.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11340953.1191238661510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1237?page=all ]

Mark Proctor closed JBRULES-1237.
---------------------------------

    Resolution: Out of Date

4.0.2 will use the latest version of MVEL on it's release, which is already beyond 1.2final.

> Upgrade MVEL library to 1.2.final
> ---------------------------------
>
>                 Key: JBRULES-1237
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1237
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> Upgrade the current mvel library that is used by drools to mvel 1.2.final as it has some fixes

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 07:44:41 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 07:44:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-811) Use
 InvocationContext to avoid multiple searches for a node
In-Reply-To: <31984417.1161791681504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26405054.1191239081200.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-811?page=all ]

Manik Surtani updated JBCACHE-811:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> Use InvocationContext to avoid multiple searches for a node
> -----------------------------------------------------------
>
>                 Key: JBCACHE-811
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-811
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> When an interceptor finds a node, why not throw it in the InvocationContext or something similar and pass it through the stack that way? Subsequent calls to find the node can check the context first before walking the cache tree. Saves redundant walking of the tree.
> We'd need to think very carefully about this, as it exposes 2 paths to access a node -- from a thread's context and from the tree.  Need to ensure concurrent threads always access the same node object for a given Fqn.
> (Side thought -- perhaps disable this for weak isolation levels where the locking behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same Fqn).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:08:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 08:08:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-886) change ejb timers
 from SLSB to an entity bean approach
In-Reply-To: <22781626.1173088271818.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14847136.1191240521299.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-886?page=comments#action_12379554 ] 
            
Tom Baeyens commented on JBPM-886:
----------------------------------

some more explanations:

currently, the EjbSchedulerService will use the ejb timer service of the TimerServiceBean (SLSB) to create an ejb timer.  that way, all ejb timers are created in one single SLSB.

so if later, we need to cancel a timer, we need to scan through all the ejb timers in order to find the right one.  (there is no querying capability in ejb timers)

the solution is can see is that we use one timer entity bean per timer instead of the single SLSB for all timers.

then we can first query the right timer beans, knowing that each timer bean will have exectly 1 timer associated with it.


> change ejb timers from SLSB to an entity bean approach
> ------------------------------------------------------
>
>                 Key: JBPM-886
>                 URL: http://jira.jboss.com/jira/browse/JBPM-886
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> the problem is that all the timers are put on a single slsb.  so we have to loop through all the timers to cancel or find one.  that is a bottleneck.
> we need to change that approach to the use of entity beans.  1 entity bean per job.  so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:10:41 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Mon, 1 Oct 2007 08:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-886) change ejb timers
 from SLSB to an entity bean approach
In-Reply-To: <22781626.1173088271818.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17781158.1191240641216.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-886?page=comments#action_12379555 ] 
            
Tom Baeyens commented on JBPM-886:
----------------------------------

the timer entity bean should leverage the existing JBPM_JOB table.  most difficult part will be to do a flush between the moment when a new job is persisted with the hibernate session and then you need to flush before loading that same record as an  entity bean to schedule the ejb timer on it.

> change ejb timers from SLSB to an entity bean approach
> ------------------------------------------------------
>
>                 Key: JBPM-886
>                 URL: http://jira.jboss.com/jira/browse/JBPM-886
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>            Reporter: Tom Baeyens
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> the problem is that all the timers are put on a single slsb.  so we have to loop through all the timers to cancel or find one.  that is a bottleneck.
> we need to change that approach to the use of entity beans.  1 entity bean per job.  so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:26:43 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 08:26:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-25) Microcontainer
	integration
Message-ID: <13678388.1191241603381.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ]

Tim Fox reassigned JBMESSAGING-25:
----------------------------------

    Assignee: Andy Taylor  (was: Aaron Walker)

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Andy Taylor
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 08:30:43 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 08:30:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1191) Work with
 contributor to translate JBoss Cache documentation into Spanish
Message-ID: <25972580.1191241843360.JavaMail.jira@cloud.prod.atl2.jboss.com>

Work with contributor to translate JBoss Cache documentation into Spanish
-------------------------------------------------------------------------

                 Key: JBCACHE-1191
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1191
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Manik Surtani
         Assigned To: Michael Smith
             Fix For: 2.2.0.GA


See email sent in to the jbosscache-dev list:

http://lists.jboss.org/pipermail/jbosscache-dev/2007-September/002031.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:13:42 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 09:13:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-470) Add a pointcut
 construction to match the field of a Class as being a type
Message-ID: <21666519.1191244422558.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add a pointcut construction to match the field of a Class as being a type
-------------------------------------------------------------------------

                 Key: JBAOP-470
                 URL: http://jira.jboss.com/jira/browse/JBAOP-470
             Project: JBoss AOP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Flavia Rainone


The idea is to allow the especification of a field value of a class as being the type of any pointcut expression.

The idea is to allow 
my.package.MyClass.field

whenever the following constructs are accepted:
- the name of a class
- annotated (@)
- implements
- type def 
- instanceof

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:53 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 09:17:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-910)
 TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
In-Reply-To: <7891202.1166570293319.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4194615.1191244673128.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-910?page=all ]

Manik Surtani resolved JBCACHE-910.
-----------------------------------

    Resolution: Done

> TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
> -----------------------------------------------------
>
>                 Key: JBCACHE-910
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-910
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.ALPHA2
>            Reporter: Elias Ross
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA
>
>
> This method is called by the region manager.
> There's a bunch of Voodoo taking place here, legacy bits mixed with some newer stuff.
> One thing that strikes me as wrong already is this code:
> child = factory.createDataNode(type, name,
>                        subtree.getFqnChild(i + 1),
>                        parent, lock_table, coordinator, null, this.rootSpi);
> For some reason, it is passing the lock_table into the Node as the data to initialize the node with.
> Somehow I think the right way to fix this would be to do a Cache.addChild(Fqn) call in RegionManager and remove this method.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:54 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 09:17:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-989) Create performance
 test suite to test failover
In-Reply-To: <26116759.1172673610805.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2716063.1191244674034.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-989?page=all ]

Manik Surtani updated JBCACHE-989:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> Create performance test suite to test failover
> ----------------------------------------------
>
>                 Key: JBCACHE-989
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-989
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Phillip Thurmond
>             Fix For: 2.2.0.GA
>
>
> Should be ideally integrated into cruise control builds, and should test a variety of configurations including sync and async replication, BR, etc.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:54 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 1 Oct 2007 09:17:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-63) JBossCache
	benchmarks
Message-ID: <5442979.1191244674215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-63?page=all ]

Manik Surtani updated JBCACHE-63:
---------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> JBossCache benchmarks
> ---------------------
>
>                 Key: JBCACHE-63
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-63
>             Project: JBoss Cache
>          Issue Type: Task
>    Affects Versions: 1.2.4SP1
>            Reporter: Bela Ban
>         Assigned To: Phillip Thurmond
>             Fix For: 2.2.0.GA
>
>   Original Estimate: 4 weeks
>  Remaining Estimate: 4 weeks
>
> Also bench against other caches

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:17:54 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 09:17:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-602) Update FLUSH diagrams
 for joining and for state transfer
Message-ID: <16456584.1191244674372.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update FLUSH diagrams for joining and for state transfer
--------------------------------------------------------

                 Key: JGRP-602
                 URL: http://jira.jboss.com/jira/browse/JGRP-602
             Project: JGroups
          Issue Type: Task
            Reporter: Bela Ban
         Assigned To: Bela Ban
            Priority: Minor
             Fix For: 2.6


Update the 2 png files to reflect the new simplified FLUSH protocol

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:26:41 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 09:26:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-470) Add a pointcut
 construction to match the field of a Class as being a type
In-Reply-To: <21666519.1191244422558.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21352050.1191245201219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-470?page=comments#action_12379573 ] 
            
Flavia Rainone commented on JBAOP-470:
--------------------------------------

Consider the typedef expression:
<typedef name="TD" expr="(class(POJO.field)" />

Where POJO class follows:
public class POJO
{
  public POJO2 field;
}

I can think of the following approache to identify the matching objects:
- add a field "Collection<ClassName> isInside<ClassName>_<fieldName>" on the class that is the type of the field <ClassName>.<fieldName> especfied on the pointcut expression. This field would track whether an object is the value  <ClassName>.<fieldName> for one or more instances of ClassName. The goal is to identify positively only when isInside<ClassName>_<fieldName>.size() is larger then 0.

Probably there are other solutions beside this one.

> Add a pointcut construction to match the field of a Class as being a type
> -------------------------------------------------------------------------
>
>                 Key: JBAOP-470
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-470
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Flavia Rainone
>
> The idea is to allow the especification of a field value of a class as being the type of any pointcut expression.
> The idea is to allow 
> my.package.MyClass.field
> whenever the following constructs are accepted:
> - the name of a class
> - annotated (@)
> - implements
> - type def 
> - instanceof

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:36:41 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 09:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-602) Update FLUSH
 diagrams for joining and for state transfer
In-Reply-To: <16456584.1191244674372.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27027765.1191245801829.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-602?page=comments#action_12379580 ] 
            
Bela Ban commented on JGRP-602:
-------------------------------

Also update doc/design/FLUSH.txt

> Update FLUSH diagrams for joining and for state transfer
> --------------------------------------------------------
>
>                 Key: JGRP-602
>                 URL: http://jira.jboss.com/jira/browse/JGRP-602
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.6
>
>
> Update the 2 png files to reflect the new simplified FLUSH protocol

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:42:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 09:42:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-124) implement APR
	transport
Message-ID: <29100667.1191246161566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-124?page=all ]

David Lloyd closed JBREM-124.
-----------------------------

    Resolution: Won't Fix
      Assignee: David Lloyd

This task will not be done directly.  Remoting 3 will depend on MINA, which will ultimately get an APR transport layer, so we'll get this for free.

> implement APR transport
> -----------------------
>
>                 Key: JBREM-124
>                 URL: http://jira.jboss.com/jira/browse/JBREM-124
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: transport
>    Affects Versions: 1.2.0 final
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>            Priority: Critical
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Need to add support of Apache APR based transport.  The APR code (from tomcat-connector project) uses native code to manage threads and sockets.  The end result is a much better performance using a NIO type approach where only have threads in use for processing data off the socket.  When socket is idle, the threads are released and the native code will callback to activate a thread to process the data.  
> This effort has already been started in JBossRemoting on a branch called apr_transport.  Will probably not be fully implemented till after 1.2.0 release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:48:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 09:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-237) There is No String
 and Guage monitors in jboss
Message-ID: <30842737.1191246521522.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-237?page=comments#action_12379584 ] 
            
David Lloyd commented on JBREM-237:
-----------------------------------

If no update is posted to this issue within a week, I will close it.

> There is No String and Guage monitors in jboss
> ----------------------------------------------
>
>                 Key: JBREM-237
>                 URL: http://jira.jboss.com/jira/browse/JBREM-237
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: jmx remoting
>            Reporter: sree roja
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:48:41 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 1 Oct 2007 09:48:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-598) Simplify FLUSH
In-Reply-To: <10363312.1190795201069.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25758910.1191246521914.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-598?page=comments#action_12379586 ] 
            
Bela Ban commented on JGRP-598:
-------------------------------

Update: maybe we nevertheless still need a FLUSH-COMPLETED phase, as someone might send a message in block() and we can only block all members from sending messages when all block()s have been called.

> Simplify FLUSH
> --------------
>
>                 Key: JGRP-598
>                 URL: http://jira.jboss.com/jira/browse/JGRP-598
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.4, 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> #1 Superfluous FLUSH-COMPLETED phase ?
> --------------------------------------
> It seems we don't need the FLUSH-COMPLETED phase, it is sufficient for
> the FLUSH leader to do a START-FLUSH and wait for all FLUSH-OK
> messages. Why ? Because the reconciliation protocol will reconcile
> messages before the view installation (or state transfer).
> Example: {A,B,C}. E sends message M and then crashes. Only C receives
> M.
> - A does a START-FLUSH
> - B and C send a FLUSH-OK back to A. This means that all multicasts
> from B will be seen by A *before* B's FLUSH-OK is received, and all
> multicasts from C will be seen by A before C's FLUSH-OK is received by
> A. HOWEVER, C will not necessarily send M to A before sending the
> FLUSH-OK message. This is only done through the reconciliation
> protocol !
> - FLUSH-COMPLETED can be removed, the digest that's part of
> FLUSH-COMPLETED has to moved to FKLUSH-OK phase.
> - FLUSH-OK is unicast *not* multicast.
> #2 Superfluous STOP-FLUSH-OK phase ?
> ------------------------------------
> Why do we need the acks here ? JGroups guarantees the STOP-FLUSH
> message is delivered to all non-faulty members, so why wait fr the
> STOP-FLUSH-OK ? 
> If we make STOP-FLUSH *OOB* (JGRP-337), then this should work ! We can
> get rid of STOP-FLUSH-OK !! Just send STOP-FLUSH as OOB multicast.
> Note: this requires the concurrent stack, so possibly check for
> concurrent stack. Throw an exception if concurrent stack is not
> present when FLUSH is used. So, these changes cannot be applied to
> 2.4, only to 2.5 and 2.6.
> #3 Timeouts
> -----------
> - ClientGmsImpl: has a hard coded timeout of 4 secs
> - CoordGmsImpl also has a timeout for block()
> - If we *need* timeouts, we should get them from the FLUSH protocol !
> CoorsGmsImpl.startFlush() should *not* have a timeout, this should be
> in FLUSH itself. startFlush() should block forever, until it gets the ack
> #4 Spurious FLUSH-OK in the diagram
> -----------------------------------
> In the JOIN diagram, probably also in the state transfer diagram

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:54:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 09:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-410) look at adding httpc
 as http client invoker
Message-ID: <20405734.1191246881527.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-410?page=all ]

David Lloyd closed JBREM-410.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Won't Fix
         Assignee: David Lloyd

Looks like nhttpc is abandonware at this point.  We'll always have MINA if we need this type of HTTP client.

> look at adding httpc as http client invoker
> -------------------------------------------
>
>                 Key: JBREM-410
>                 URL: http://jira.jboss.com/jira/browse/JBREM-410
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>
> https://nhttpc.dev.java.net/
> NIO HTTP Client
> An HTTP client built using JDK 1.4 NIO. Scales to thousands of
> concurrent client connections per VM with almost no CPU overhead.
> BSD license.
> In particular, need to see if has NTLM support

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 09:54:43 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?Ortwin_Gl=C3=BCck_=28JIRA=29?=)
Date: Mon, 1 Oct 2007 09:54:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-337) EJBException
 should set cause
Message-ID: <15405954.1191246883904.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-337?page=comments#action_12379590 ] 
            
Ortwin Gl?ck commented on EJBTHREE-337:
---------------------------------------

Seems that this bug is also in another place in EJB-3.0RC8 (sorry can't test this on later versions) when an EJBException caused by a NPE is propagated back through another EJB call as a EJBTransactionRolledbackException:

javax.ejb.EJBTransactionRolledbackException: java.lang.NullPointerException
 at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:93)
 at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
 at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:201)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:167)
 at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:100)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
 at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:181)
 at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79)


> EJBException should set cause
> -----------------------------
>
>                 Key: EJBTHREE-337
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-337
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC3
>         Environment: AS-4.0.3SP1, EJB-3.0RC3
>            Reporter: Ortwin Gl?ck
>         Assigned To: William DeCoste
>            Priority: Trivial
>             Fix For: EJB 3.0 RC4 - PFD
>
>
> When a NullPointerException is thrown in a session bean method the EJBException only provides the wrapped exception via getCausedByException()  and not via the Throwable#getCause() method. That causes stack traces to abort at the EJBException and the real exception is lost. It makes debugging harder.
> Caused by: javax.ejb.EJBException: null; CausedByException is:
> 	null
> 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:46)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:70)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:32)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:204)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:107)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:37)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:88)
> Painful Workaround:
> try {
>             bean.method();
> } catch (EJBException e) {
>             if (e.getCause() == null) e.initCause(e.getCausedByException());
>             throw e;
> }

-- 
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

       



From jira-events at lists.jboss.org  Mon Oct  1 10:00:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-103) Transport progress
 notification for client
Message-ID: <24902186.1191247241753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd updated JBREM-103:
------------------------------

    Component/s: r3 api
                     (was: marshall)
       Assignee: David Lloyd  (was: Tom  Elrod)

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:00:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-103) Transport progress
 notification for client
Message-ID: <26747218.1191247241961.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd updated JBREM-103:
------------------------------

    Fix Version/s: 3.0.0.Alpha1 (Otter)
                       (was: 4.0.0.Beta1)

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:02:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:02:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-13) NIO transport
Message-ID: <23841136.1191247365659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-13?page=all ]

David Lloyd closed JBREM-13.
----------------------------

    Fix Version/s: 3.0.0.Alpha1 (Otter)
                       (was: 4.0.0.Beta1)
       Resolution: Won't Fix
         Assignee: David Lloyd  (was: Tom  Elrod)

Remoting 3 will use MINA primarily, so NIO and APR are both free.

> NIO transport
> -------------
>
>                 Key: JBREM-13
>                 URL: http://jira.jboss.com/jira/browse/JBREM-13
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: transport
>    Affects Versions: 1.0.1 alpha
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>            Priority: Optional
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Add NIO transport.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:04:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:04:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-103) Transport progress
 notification for client
Message-ID: <149243.1191247481194.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd closed JBREM-103.
-----------------------------

    Resolution: Done

Implemented in current Remoting 3 API/Core.

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:10:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 10:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-306) Supports
	recovery flag
Message-ID: <1236287.1191247841397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-306?page=all ]

Tim Fox updated JBMESSAGING-306:
--------------------------------

    Priority: Minor  (was: Major)

> Supports recovery flag
> ----------------------
>
>                 Key: JBMESSAGING-306
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-306
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Should have flag "supports XA recovery" on persistencemanager.
> If = false then only tx id, not all xid fields are persisted on prepare. This should improve performance when xa recovery is not required.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:27:42 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 10:27:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-433) point to
 multipoint invocation api
Message-ID: <3512824.1191248862258.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-433?page=comments#action_12379602 ] 
            
David Lloyd commented on JBREM-433:
-----------------------------------

One possible use that came up in recent meetings: The ability to send a request and verify that all replies match, or to send a request and accept the first reply that meets certain criteria.

I still don't know any real-world use cases for this though.

> point to multipoint invocation api
> ----------------------------------
>
>                 Key: JBREM-433
>                 URL: http://jira.jboss.com/jira/browse/JBREM-433
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time.  The responses for each target server would be aggregated into one response as return to the client call.  Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for 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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:47:41 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 10:47:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4572) EJB 3 testsuite 100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25132549.1191250061672.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4572?page=all ]

William DeCoste closed JBAS-4572.
---------------------------------

    Resolution: Done

> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 10:56:55 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 10:56:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3142) Add UnifiedInvoker
 (JBSer and JavaSer) into Version MatrixTestSuite
Message-ID: <17635778.1191250615646.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3142?page=all ]

Clebert Suconic updated JBAS-3142:
----------------------------------

    Priority: Optional  (was: Major)

> Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite
> -------------------------------------------------------------------
>
>                 Key: JBAS-3142
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3142
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Optional
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:00:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 11:00:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-45)   Remoting watchdog
Message-ID: <22931246.1191250841588.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-45?page=all ]

David Lloyd closed JBREM-45.
----------------------------

    Resolution: Out of Date
      Assignee: David Lloyd  (was: Tom  Elrod)

This issue is in three parts:

1) Build in ability for the server to be aware of clients that exist and their status.

Remoting 3 does not have a notion of client vs. server.  That said, an Endpoint will always be aware of the status of its Sessions.

2) Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references.

This is probably out of scope for Remoting 3 - I'm inclined to let this die until a specific issue arises.  Specifically, Remoting 3 doesn't normally utilize the idea of a remote object.  Anything that does, will be built on top of Remoting 3 and will probably be responsible for dealing with this functionality.

3) Need ability to disconnect client from server when there has been an extended period of inactivity.

This would be very specific to the protocol.  Additionally complicated by the addition of Context/Session layers.

>   Remoting watchdog
> -------------------
>
>                 Key: JBREM-45
>                 URL: http://jira.jboss.com/jira/browse/JBREM-45
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.0.1 beta
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> Build in ability for the server to be aware of clients that exist and their status. Will be needed for doing distributed garbage collection, client connection timeout, etc.
> Add distributed garbage collection for clients that maintain a remote stub. Will detect that client is no longer available (via watchdog) and will clean up server side references.
> Need ability to disconnect client from server when there has been an extended period of inactivity.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:12:43 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 11:12:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <33379958.1191251563655.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379620 ] 
            
David Lloyd commented on JBREM-305:
-----------------------------------

Thomas, are there any specific requirements regarding the format of the JMS message?  Or do you just want your message to be moved from one endpoint to another?

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: Tom  Elrod
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:36:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 11:36:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-324) Facility for
 real-time decision
 on best InvokerLocator by which to contact a given handler.
Message-ID: <25880124.1191253001427.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12379624 ] 
            
David Lloyd commented on JBREM-324:
-----------------------------------

The Routing/Discovery API of Remoting 3 should facilitate this ability, if I understand correctly.  It will maintain a list of paths to endpoints, and choose the best one available at any given time.

> Facility for real-time decision on best InvokerLocator by which to contact a given handler.
> -------------------------------------------------------------------------------------------
>
>                 Key: JBREM-324
>                 URL: http://jira.jboss.com/jira/browse/JBREM-324
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.0.Beta1
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 4.0.0.Beta1
>
>
> The basic idea is to be able to communicate with a single handler by way of different InvokerLocators.  For example, if you're working over the internet, compression might be advantageous, but if you're local it might not be.  So you could have two Connectors sharing a handler, one using the compression marshaller and one not.
> How about a client that
> 1. gets the InvokerLocators for all of the Connectors for a certain handler, via a detector,
> 2. sends some sample invocations to each and times them, and
> 3. displays the results.
> It could be used for real time decision making or to collect information for a set of rules.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 11:54:41 2007
From: jira-events at lists.jboss.org (Eric Brennan (JIRA))
Date: Mon, 1 Oct 2007 11:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1731) Document /
 Tutorial Data Display from Database using Hibernate
Message-ID: <2367872.1191254081355.JavaMail.jira@cloud.prod.atl2.jboss.com>

Document / Tutorial Data Display from Database using Hibernate
--------------------------------------------------------------

                 Key: JBPORTAL-1731
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1731
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Reference Guide
    Affects Versions: 2.6.2 Final
         Environment: Portal 2.6.1 GA
Oracle backend. 
            Reporter: Eric Brennan
         Assigned To: Julien Viet
            Priority: Optional


It would be nice to have a tutorial on Displaying records from a Database using hibernate. Could expand the Helloworld example to pull two fields from a database. 

How to configure Hibernate CFG so that it pulls a generic DS. 
Nice to have records displayed bases on login ID. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:15:41 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 1 Oct 2007 12:15:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-759) Client
 username/password
 authentication mechanism to provide JAAS UserPrincipal
In-Reply-To: <22936251.1182273876546.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13061203.1191255341140.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-759?page=comments#action_12379636 ] 
            
David Lloyd commented on JBREM-759:
-----------------------------------

Remoting 3 will definitely support this functionality.

> Client username/password authentication mechanism to provide JAAS UserPrincipal
> -------------------------------------------------------------------------------
>
>                 Key: JBREM-759
>                 URL: http://jira.jboss.com/jira/browse/JBREM-759
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: security
>            Reporter: Clark Updike
>             Fix For: 3.0.0.Alpha1 (Otter)
>
>
> Per the forum thread, Remoting needs a username/password-style authentication mechanism similar to JNDI for situations that require secure authentication but cannot support the infrastructure required for client certificates.  The mechanism should populate a JAAS UserPrinciple that can be used to access the authenticated client identity on the remote side.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:23:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 12:23:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-608) Add a new
 compatibity and stress test layer based on JMS CTS
In-Reply-To: <13967074.1160688881540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21000680.1191255821241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-608?page=all ]

Tim Fox closed JBMESSAGING-608.
-------------------------------

    Resolution: Rejected

We already have JORAM and CTS

> Add a new compatibity and stress test layer based on JMS CTS
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-608
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-608
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: 2.0.0 Beta 1
>
>
> http://jmscts.sourceforge.net/index.html
> The stress part is especially interesting.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:27:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:27:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ
 to Messaging migration guide
Message-ID: <23567470.1191256061244.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ]

Clebert Suconic closed JBMESSAGING-388.
---------------------------------------

    Resolution: Done

> Write a JBossMQ to Messaging migration guide
> --------------------------------------------
>
>                 Key: JBMESSAGING-388
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Documentation and Training
>            Reporter: Ovidiu Feodorov
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:27:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:27:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-388) Write a
 JBossMQ to Messaging migration guide
Message-ID: <31829155.1191256061463.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ]

Clebert Suconic reopened JBMESSAGING-388:
-----------------------------------------

      Assignee: Clebert Suconic
             

> Write a JBossMQ to Messaging migration guide
> --------------------------------------------
>
>                 Key: JBMESSAGING-388
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Documentation and Training
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:29:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:29:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-388) Write a JBossMQ
 to Messaging migration guide
Message-ID: <28377154.1191256181124.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ]

Clebert Suconic closed JBMESSAGING-388.
---------------------------------------

    Resolution: Done

JBM already cover migration (just look at installation docs)

> Write a JBossMQ to Messaging migration guide
> --------------------------------------------
>
>                 Key: JBMESSAGING-388
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: Documentation and Training
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:50:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-641) Make sure smoke
 tests pass on an un-scoped JBoss5/Messaging instance
In-Reply-To: <743036.1163646941500.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6571655.1191257441380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-641?page=all ]

Clebert Suconic closed JBMESSAGING-641.
---------------------------------------

    Resolution: Done
      Assignee: Clebert Suconic

> Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-641
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-641
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> Will take care of this on the second pass of integration with JBoss 5, which will be after 1.2.0 anyway.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 12:50:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 12:50:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-639) AS Integration
In-Reply-To: <12502423.1163644661476.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22080242.1191257441573.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-639?page=all ]

Clebert Suconic closed JBMESSAGING-639.
---------------------------------------

    Resolution: Done

> AS Integration
> --------------
>
>                 Key: JBMESSAGING-639
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-639
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> Container task for anything related to integration.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 13:52:56 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 13:52:56 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1052) doc for SFSB
	removal timeout
In-Reply-To: <33479921.1190342891021.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9854260.1191261176113.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1052?page=all ]

William DeCoste closed EJBTHREE-1052.
-------------------------------------

    Fix Version/s: Branch_4_2
       Resolution: Done

> doc for SFSB removal timeout
> ----------------------------
>
>                 Key: EJBTHREE-1052
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1052
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Mon Oct  1 13:52:56 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 13:52:56 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1035) get latest
	tutorials online
In-Reply-To: <18674529.1187814989070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10352596.1191261176283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1035?page=all ]

William DeCoste closed EJBTHREE-1035.
-------------------------------------

    Resolution: Done

> get latest tutorials online
> ---------------------------
>
>                 Key: EJBTHREE-1035
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1035
>             Project: EJB 3.0
>          Issue Type: Task
>            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

        


From jira-events at lists.jboss.org  Mon Oct  1 15:39:41 2007
From: jira-events at lists.jboss.org (Matt Cristantello (JIRA))
Date: Mon, 1 Oct 2007 15:39:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4747) WebAuthentication
 programmatic login prevents the user from ever logging out
In-Reply-To: <2656556.1190410691242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5335662.1191267581274.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4747?page=all ]

Matt Cristantello closed JBAS-4747.
-----------------------------------

    Resolution: Cannot Reproduce Bug

I can't duplicate this anymore, it must have been an issue with some weird cookies being set in my browser.

Sorry,
~Matt

> WebAuthentication programmatic login prevents the user from ever logging out
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4747
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4747
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: CentOS 3, JDK 1.5.0_12, JBoss Portal 2.6.1.GA with JBoss AS 4.2.1.GA, set up in ClusteredSingleSignOn mode
>            Reporter: Matt Cristantello
>         Assigned To: Scott M Stark
>
> When using the WebAuthentication login(String,String) method, it is not possible to log out even if the logoff() method of the WebAuthentication is called.
> Code:
> auto_login.jsp
> <%@page import="org.jboss.web.tomcat.security.login.WebAuthentication"%>
> <%
> 	WebAuthentication pwl = new WebAuthentication();
> 	pwl.login("user", "user");
> 	
> 	response.sendRedirect("test.jsp");
> %>
> logout.jsp
> <%@page import="org.jboss.web.tomcat.security.login.WebAuthentication"%>
> <%
> 	WebAuthentication pwl = new WebAuthentication();
> 	pwl.logout();
> %>
> <p>Successfully logged out</p>
> test.jsp
> <html>
> <head>
> 	<title>Test Page</title>
> </head>
> <body>
> <p>Username: <%=request.getRemoteUser() %></p>
> <p><a href="logout.jsp">Log Out</a></p>
> </body>
> </html>
> web.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app id="WebApp_ID" version="2.4"
> 	xmlns="http://java.sun.com/xml/ns/j2ee"
> 	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> 	xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
> 	<display-name>test</display-name>
> 	<welcome-file-list>
> 		<welcome-file>index.html</welcome-file>
> 		<welcome-file>index.htm</welcome-file>
> 		<welcome-file>index.jsp</welcome-file>
> 		<welcome-file>default.html</welcome-file>
> 		<welcome-file>default.htm</welcome-file>
> 		<welcome-file>default.jsp</welcome-file>
> 	</welcome-file-list>
> 	<security-constraint>
> 		<web-resource-collection>
> 			<web-resource-name>test</web-resource-name>
> 			<url-pattern>/test.jsp</url-pattern>
> 			<http-method>POST</http-method>
> 			<http-method>GET</http-method>
> 		</web-resource-collection>
> 		<auth-constraint>
> 			<description>Authentication required</description>
> 			<role-name>Authenticated</role-name>
> 		</auth-constraint>
> 	</security-constraint>
> 	<login-config>
> 		<auth-method>FORM</auth-method>
> 		<realm-name>JBoss Portal</realm-name>
> 		<form-login-config>
> 			<form-login-page>/login.jsp</form-login-page>
> 			<form-error-page>/error.jsp</form-error-page>
> 		</form-login-config>
> 	</login-config>
> 	<security-role>
> 		<role-name>Authenticated</role-name>
> 	</security-role>
> </web-app>
> jboss-web.xml
> <?xml version="1.0"?>
> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
> <jboss-web>
> 	<security-domain>java:jaas/portal</security-domain>
> </jboss-web>
> Steps:
> 1. Log in by navigating to auto_login.jsp
> 2. Click the log out link, or otherwise navigate to the logout.jsp page.
> 3. Navigate back to the test.jsp page.
> You will still be logged in.
> This problem also occurs with the JBoss Portal 2.6.1, where I am automatically logged into the JBoss portal after running auto_login.jsp, but I cannot log out of the Portal using its logout button or the logout.jsp provided as an example above.
> I am not seeing any entries in my server.log files when the logout methods are called, even with debug messages being logged.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:01:41 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 16:01:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-471) Method
 enforceArgsConsistency()
 not found on field interception with @Arg-annotated param
Message-ID: <12708972.1191268901563.JavaMail.jira@cloud.prod.atl2.jboss.com>

Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
-----------------------------------------------------------------------------------------

                 Key: JBAOP-471
                 URL: http://jira.jboss.com/jira/browse/JBAOP-471
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
            Reporter: Flavia Rainone
         Assigned To: Flavia Rainone
             Fix For: 2.0.0.beta2


The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
The result:
Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
rgsPOJO.field5]
        at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
        at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
        at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
        at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
        at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
        at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
Caused by: java.lang.RuntimeException: Error creating invokeNext method: {   try{      switch(++super.currentInterceptor){      case 1:enforceArgsConsistency
();    around6.around1(this.arg0);
      break;      case 2:enforceArgsConsistency();    around7.around2(this.arg0);
      break;      case 3:enforceArgsConsistency();    around8.around3(this.arg0);
      break;      case 4:enforceArgsConsistency();    around9.around4(this.arg0);
      break;      case 5:enforceArgsConsistency();    around10.around6(this.arg0);
      break;      default:         this.dispatch();      }   }finally{      --super.currentInterceptor;   }   return null;}
        at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
        at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
        ... 26 more
Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
_16
        at javassist.CtBehavior.setBody(CtBehavior.java:367)
        at javassist.CtBehavior.setBody(CtBehavior.java:334)
        at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
        ... 28 more
Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
        at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
        at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
        at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
        at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
        at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
        at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
        at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
        at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:11:41 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 1 Oct 2007 16:11:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-472) Wrappers lack the
 generic type information
Message-ID: <5055386.1191269501072.JavaMail.jira@cloud.prod.atl2.jboss.com>

Wrappers lack the generic type information
------------------------------------------

                 Key: JBAOP-472
                 URL: http://jira.jboss.com/jira/browse/JBAOP-472
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
            Reporter: Flavia Rainone
             Fix For: 2.0.0.beta2


This issue has already been fixed by Kabir with method wrappers.

This task consists of fixing the issue for all other joinpoint types.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:24:43 2007
From: jira-events at lists.jboss.org (RefuX Zanzeebarr (JIRA))
Date: Mon, 1 Oct 2007 16:24:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JASSIST-36) static flag
 inconsistently applied to clinit
Message-ID: <24683018.1191270283396.JavaMail.jira@cloud.prod.atl2.jboss.com>

static flag inconsistently applied to clinit
--------------------------------------------

                 Key: JASSIST-36
                 URL: http://jira.jboss.com/jira/browse/JASSIST-36
             Project: Javassist
          Issue Type: Bug
            Reporter: RefuX Zanzeebarr
         Assigned To: Shigeru Chiba


In CtClassType we have:
            m = new MethodInfo(cf.getConstPool(), "<clinit>", "()V");
            m.setAccessFlags(AccessFlag.STATIC);

In ProxyFactory
         MethodInfo minfo = new MethodInfo(cp, "<clinit>", "()V");

but no static flag.

We actually ran into this issue because the JVM on the iSeries was very unhappy about the lack of the static flag in clinit. IBM are now updating their JVM to work correctly with the missing static flag.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 16:44:41 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 1 Oct 2007 16:44:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1088) Refactor code
 to use Java 5 generics
Message-ID: <25143580.1191271481231.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor code to use Java 5 generics
------------------------------------

                 Key: JBMESSAGING-1088
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1088
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 2.0.0 Beta 1


In many places the code uses non parameterized collections since we moved recently from Java 1.4 to Java 5.

We should update the code accordingly.

Also use Java 5 enums where appropriate.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 17:10:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 1 Oct 2007 17:10:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-910) upgrade GWT to 1.4
In-Reply-To: <11898024.1181114658622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31242499.1191273041457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-910?page=all ]

Fernando Meyer closed JBRULES-910.
----------------------------------

    Fix Version/s: 4.0.2
                       (was: FUTURE)
       Resolution: Done

Michale got some issues testing on firefox 3 beta, but I got everything wokring fine with FF2, safari and IE 6

> upgrade GWT to 1.4
> ------------------
>
>                 Key: JBRULES-910
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-910
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Michael Neale
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> Would also be nice to use the new RichText widget on the documentation (for the doucmentation widget on the rule editors).
> Also, using the Vertical and horizontal splitters would be awesome for the rule editor (so people can drag stuff around).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 17:14:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 1 Oct 2007 17:14:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1238) Upgrade BRMS to
 use jboss seam version 2.0
Message-ID: <25446154.1191273281034.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade BRMS to use jboss seam version 2.0 
-------------------------------------------

                 Key: JBRULES-1238
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1238
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer
             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Mon Oct  1 17:27:46 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 17:27:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16022452.1191274066025.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

William DeCoste reassigned EJBTHREE-883:
----------------------------------------

    Assignee: William DeCoste

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:17:55 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 18:17:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1239) Fix class loaders
 so that
 creating multiple rulebase with separate class loader hirarchy works
Message-ID: <16578372.1191277075861.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works
----------------------------------------------------------------------------------------------

                 Key: JBRULES-1239
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1239
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, Reteoo
    Affects Versions: 4.0.1
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.0.2


Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:23:41 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 18:23:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1239) Fix class
 loaders so that
 creating multiple rulebase with separate class loader hirarchy works
In-Reply-To: <16578372.1191277075861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16513714.1191277421166.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1239?page=all ]

Edson Tirelli resolved JBRULES-1239.
------------------------------------

    Resolution: Done

commited.

Tag before the commit is here: https://svn.labs.jboss.com/labs/jbossrules/tags/4.0.2_SNAPSHOT_before_classloader_changes/

> Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1239
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1239
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder, Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>
> Fix class loaders so that creating multiple rulebase with separate class loader hirarchy works

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:29:41 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 1 Oct 2007 18:29:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23075090.1191277781249.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

William DeCoste closed EJBTHREE-883.
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 5.0.0.Beta3)
       Resolution: Done

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:31:41 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 18:31:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1212) Rete throws
 NoClassDefFoundError when asserting facts with classess loaded by
 inaccessible classloader.
In-Reply-To: <21352351.1190454754072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11806315.1191277901200.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1212?page=comments#action_12379736 ] 
            
Edson Tirelli commented on JBRULES-1212:
----------------------------------------

Alexander,

I just fixed http://jira.jboss.com/jira/browse/JBRULES-1239 and I think your use case is covered now. I developed 2 tests, as you can see bellow: one using thread context API and the other using drools configuration classes:

    public void testClassLoaderSwitchsUsingConf() throws Exception {
        try {
            // Creates first class loader and use it to load fact classes
            ClassLoader loader1 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                      this.getClass().getClassLoader() );
            Class cheeseClass = loader1.loadClass( "org.drools.Cheese" );

            PackageBuilderConfiguration conf = new PackageBuilderConfiguration( loader1 );
            PackageBuilder builder = new PackageBuilder( conf );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            // must set the classloader for rulebase conf too
            RuleBaseConfiguration rbconf = new RuleBaseConfiguration( loader1 );
            RuleBase ruleBase = RuleBaseFactory.newRuleBase( rbconf );
            Package pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            StatefulSession wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();

            // Creates second class loader and use it to load fact classes
            ClassLoader loader2 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                            this.getClass().getClassLoader() );
            cheeseClass = loader2.loadClass( "org.drools.Cheese" );

            conf = new PackageBuilderConfiguration( loader2 );
            builder = new PackageBuilder( conf );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            rbconf = new RuleBaseConfiguration( loader2 );
            ruleBase = RuleBaseFactory.newRuleBase( rbconf );
            pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();
        } catch ( ClassCastException cce ) {
            cce.printStackTrace();
            fail( "No ClassCastException should be raised." );
        }

    }

    public void testClassLoaderSwitchsUsingContext() throws Exception {
        try {
            // Creates first class loader and use it to load fact classes
            ClassLoader original = Thread.currentThread().getContextClassLoader();
            ClassLoader loader1 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                      this.getClass().getClassLoader() );
            Thread.currentThread().setContextClassLoader( loader1 );
            Class cheeseClass = loader1.loadClass( "org.drools.Cheese" );

            PackageBuilder builder = new PackageBuilder( );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            RuleBase ruleBase = RuleBaseFactory.newRuleBase();
            Package pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            StatefulSession wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();

            // Creates second class loader and use it to load fact classes
            ClassLoader loader2 = new SubvertedClassLoader( new URL[]{getClass().getResource( "/" ).toURI().toURL()},
                                                            this.getClass().getClassLoader() );
            Thread.currentThread().setContextClassLoader( loader2 );
            cheeseClass = loader2.loadClass( "org.drools.Cheese" );

            builder = new PackageBuilder( );
            builder.addPackageFromDrl( new InputStreamReader( getClass().getResourceAsStream( "test_Dynamic1.drl" ) ) );

            ruleBase = RuleBaseFactory.newRuleBase();
            pkg = builder.getPackage();
            ruleBase.addPackage( pkg );

            wm = ruleBase.newStatefulSession();
            wm.insert( cheeseClass.newInstance() );
            wm.fireAllRules();

            Thread.currentThread().setContextClassLoader( original );
        } catch ( ClassCastException cce ) {
            cce.printStackTrace();
            fail( "No ClassCastException should be raised." );
        }
    }

    public class SubvertedClassLoader extends URLClassLoader {

        private static final long serialVersionUID = 400L;

        public SubvertedClassLoader(final URL[] urls,
                                    final ClassLoader parentClassLoader) {
            super( urls,
                   parentClassLoader );
        }

        protected synchronized Class loadClass(String name,
                                               boolean resolve) throws ClassNotFoundException {
            // First, check if the class has already been loaded
            Class c = findLoadedClass( name );
            if ( c == null ) {
                try {
                    c = findClass( name );
                } catch( ClassNotFoundException e ) {
                    c = super.loadClass( name, resolve );
                }
            }
            return c;
        }
    }

    Can you please try out and let us know if it covers your scenarios?

    Thanks,
      Edson

> Rete throws NoClassDefFoundError when asserting facts with classess loaded by inaccessible classloader. 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1212
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1212
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Alexander Gavrilov
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>         Attachments: ReteShadowProxyTest.java
>
>
> We using drools as part of security enfocement engine in our application, based on Tapestry4 framework. Tapestry4 pages and components is abstract classes with some abstract methods, for which tapestry generates implementation at runtime. For example, if i declare page 
> public abstract SomePage extends BasePage  {
> }
> Tapestry will generate class in default package like 
> public SomePage$_0 extends BasePage  {
> }
> On page loading whe using instantiated page objects ans Drools Facts to ensure, that current user has permissions to load this page. In the previos verions we used (3.0.6) all worked fine. After update to version 4.0.1 whe got the NoClassDefFoundError  when triyng to assert Page object into working memory. 
> This is becouse tapestry creates classes for pages in private classloader, which is child of the application classloader. When Drools tries to generate shadowing proxy for generated Page class it generate code like 
> public class SomePage$_0ShadowProxy extends SomePage$_0 {
> }
> Later, when it tries to load this class with MapBackedClassLoader, it can not find definition for class SomePage$_0 and throws NoClassDefFoundError. This type of error does not handled correctly by drools. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:45:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 18:45:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12591030.1191278741235.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Clebert Suconic updated JBREM-811:
----------------------------------

    Attachment: diff.patch

Attaching a patch

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>             Fix For: 2.2.2.SP1
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 18:49:41 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 1 Oct 2007 18:49:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3502) Use
 ProcessExpiresFrequency to speed tests involving session timeout
In-Reply-To: <300803.1155154392870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10212194.1191278981271.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3502?page=all ]

Brian Stansberry reassigned JBAS-3502:
--------------------------------------

    Assignee: Brian Stansberry

> Use ProcessExpiresFrequency to speed tests involving session timeout
> --------------------------------------------------------------------
>
>                 Key: JBAS-3502
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3502
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering, Test Suite
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: JBossAS-5.0.0.GA
>
>
> Tomcat Manager impls expose a property ProcessExpiresFrequency, which controls how often the manager responds to the TC background process thread.  By default it is set to 6, which means the manager does a session cleanup every 6 cycles.  By default the thread runs every 10 secs, so that means session are expired once per minute.
> Need to add ProcessExpiresFrequency=1 to a context.xml deployed with session test webapps so we can reduce the time it takes for tests involving session expiration to 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

        


From jira-events at lists.jboss.org  Mon Oct  1 19:02:41 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 1 Oct 2007 19:02:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13085784.1191279761173.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Clebert Suconic updated JBREM-811:
----------------------------------

    Priority: Blocker  (was: Major)

I'm changing this back to blocker, but the fix is pretty simple.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.2.2.SP1
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 19:29:41 2007
From: jira-events at lists.jboss.org (Remy Maucherat (JIRA))
Date: Mon, 1 Oct 2007 19:29:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBWEB-95) Provide a
 com.sun.net.httpserver.HttpServerProvider implementation
In-Reply-To: <4296152.1190984561683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5079376.1191281381209.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBWEB-95?page=all ]

Remy Maucherat reassigned JBWEB-95:
-----------------------------------

    Assignee: Remy Maucherat  (was: Mladen Turk)

> Provide a com.sun.net.httpserver.HttpServerProvider implementation
> ------------------------------------------------------------------
>
>                 Key: JBWEB-95
>                 URL: http://jira.jboss.com/jira/browse/JBWEB-95
>             Project: JBoss Web
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Tomcat Module
>            Reporter: Scott M Stark
>         Assigned To: Remy Maucherat
>
> To plug jbossweb into jdk6, we need a com.sun.net.httpserver.HttpServerProvider implementation
> http://java.sun.com/javase/6/docs/jre/api/net/httpserver/spec/com/sun/net/httpserver/spi/HttpServerProvider.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 19:37:52 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 19:37:52 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1224) regular
 expressions inside mvel expressions require escaping
In-Reply-To: <8850663.1190828212431.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6981057.1191281872547.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1224?page=all ]

Edson Tirelli closed JBRULES-1224.
----------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done
         Assignee: Edson Tirelli  (was: Mark Proctor)

Fixed.

Thanks for reporting.

> regular expressions inside mvel expressions require escaping
> ------------------------------------------------------------
>
>                 Key: JBRULES-1224
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1224
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Godmar Back
>         Assigned To: Edson Tirelli
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> The documentation states that regular expressions do not require Java-style backslash escaping. However, this only holds for some expressions, not for all.
> For details, read: http://lists.jboss.org/pipermail/rules-users/2007-September/003309.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:19:42 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 20:19:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21822307.1191284382451.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=all ]

Mark Proctor updated JBRULES-1221:
----------------------------------

    Assignee: Michael Neale  (was: Mark Proctor)

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:22:32 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 20:22:32 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1219) Using DSL and
 accumulate in Drools BRMS leads to unexpected results
In-Reply-To: <5139335.1190709101221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31091817.1191284552256.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1219?page=all ]

Mark Proctor updated JBRULES-1219:
----------------------------------

    Assignee: Michael Neale  (was: Mark Proctor)

> Using DSL and accumulate in Drools BRMS leads to unexpected results
> -------------------------------------------------------------------
>
>                 Key: JBRULES-1219
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1219
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05" 
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/Using-DSL-and-accumulate-in-Drools-BRMS-leads-to-unexpected-results-tf4421763.html#a12612164

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:45:42 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 20:45:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1206) ParserException on
 misplaced parenthesis
In-Reply-To: <997956.1190212517082.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23396042.1191285942137.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1206?page=all ]

Edson Tirelli closed JBRULES-1206.
----------------------------------

    Resolution: Done

Done.

Thanks for reporting and providing test case.

> ParserException on misplaced parenthesis
> ----------------------------------------
>
>                 Key: JBRULES-1206
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1206
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>         Environment: Windows XP SP2
>            Reporter: Matija Kejzar
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>         Attachments: wp-rules-exception.txt
>
>
> The following exception is thrown on parsing of the attached rules (see attached file). Take note of the incorrect parenthesis in the eval statement on the WorkerPerformanceContext condition lines. Also, please note these rules were generated by the spreadsheet compiler from an .xls decision table.
> Here is the exception:
> Caused by: org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)
> ... application code

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:53:41 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 1 Oct 2007 20:53:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15363662.1191286421176.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=comments#action_12379754 ] 
            
Michael Neale commented on JBRULES-1221:
----------------------------------------

I haven't been able to get this to happen in 4.0.2 trunk - could you try this again on that? 

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 20:55:41 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 1 Oct 2007 20:55:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1219) Using DSL and
 accumulate in Drools BRMS leads to unexpected results
In-Reply-To: <5139335.1190709101221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10854162.1191286541187.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1219?page=all ]

Edson Tirelli updated JBRULES-1219:
-----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)
         Assignee: Edson Tirelli  (was: Michael Neale)

The "-" feature can not be used with accumulate right now and the fix for that will not make the 4.0.2 cut. So, moving it to FUTURE.

> Using DSL and accumulate in Drools BRMS leads to unexpected results
> -------------------------------------------------------------------
>
>                 Key: JBRULES-1219
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1219
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05" 
>            Reporter: Cristiano Giuffrida
>         Assigned To: Edson Tirelli
>             Fix For: FUTURE
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/Using-DSL-and-accumulate-in-Drools-BRMS-leads-to-unexpected-results-tf4421763.html#a12612164

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 21:01:41 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 1 Oct 2007 21:01:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21239960.1191286901101.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=comments#action_12379756 ] 
            
Michael Neale commented on JBRULES-1221:
----------------------------------------

Have tried in a few different ways, this is probably related to quite a few other fixes since 4.0.1 time (it has been a while). 

Give it a try with the latest snapshot. If it still happens, let me know with some more detail (app server etc).

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 21:18:41 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 1 Oct 2007 21:18:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1221)
 org.drools.base.accumulators.CountAccumulateFunction error when building a
 package with rules including an accumulate construct in Drools BRMS 4.0.1
In-Reply-To: <30553665.1190722961490.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7188519.1191287921284.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1221?page=all ]

Michael Neale closed JBRULES-1221.
----------------------------------

    Resolution: Done

Fixed in 4.0.2 due to incorrect ContentPackageAssembler handling of configuration

> org.drools.base.accumulators.CountAccumulateFunction error when building a package with rules including an accumulate construct in Drools BRMS 4.0.1
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1221
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1221
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: HP-UX java version "1.5.0.05"
>            Reporter: Cristiano Giuffrida
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> Details of this problem are described in the following thread:
> http://www.nabble.com/org.drools.base.accumulators.CountAccumulateFunction-error-with-Drools-BRMS-4.0.1-tf4414590.html#a12592552

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 21:32:41 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 21:32:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1240) Remove Dialect
 state from PackageBuilderConfiguration
Message-ID: <22006922.1191288761051.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove Dialect state from PackageBuilderConfiguration
-----------------------------------------------------

                 Key: JBRULES-1240
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1240
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.1
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2


We are getting issues, particularly in threading scenarios, where PackageBuilderConfiguration holding onto the JavaDialect instance is causing problems. We need to make PackageBuilderConfiguration stateless, or atleast immutable.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:01:41 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 1 Oct 2007 23:01:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1241) Dynamic rules
 should be able
 to lock for a series of updates and fireAllRules should be optional
Message-ID: <31771190.1191294101057.JavaMail.jira@cloud.prod.atl2.jboss.com>

Dynamic rules should be able to lock for a series of updates and fireAllRules should be optional
------------------------------------------------------------------------------------------------

                 Key: JBRULES-1241
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1241
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2


add lock() and unlock() to RuleBase and setup a rulebase listener to progated the fireAllRules calls.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:50:42 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:50:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JASSIST-36) static flag
 inconsistently applied to clinit
In-Reply-To: <24683018.1191270283396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25125826.1191297042500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-36?page=all ]

Shigeru Chiba resolved JASSIST-36.
----------------------------------

    Resolution: Done

Thank you.  I have fixed it.

> static flag inconsistently applied to clinit
> --------------------------------------------
>
>                 Key: JASSIST-36
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-36
>             Project: Javassist
>          Issue Type: Bug
>            Reporter: RefuX Zanzeebarr
>         Assigned To: Shigeru Chiba
>
> In CtClassType we have:
>             m = new MethodInfo(cf.getConstPool(), "<clinit>", "()V");
>             m.setAccessFlags(AccessFlag.STATIC);
> In ProxyFactory
>          MethodInfo minfo = new MethodInfo(cp, "<clinit>", "()V");
> but no static flag.
> We actually ran into this issue because the JVM on the iSeries was very unhappy about the lack of the static flag in clinit. IBM are now updating their JVM to work correctly with the missing static flag.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:50:42 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:50:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JASSIST-36) static flag
 inconsistently applied to clinit
In-Reply-To: <24683018.1191270283396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1287731.1191297042648.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-36?page=all ]

Shigeru Chiba closed JASSIST-36.
--------------------------------


> static flag inconsistently applied to clinit
> --------------------------------------------
>
>                 Key: JASSIST-36
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-36
>             Project: Javassist
>          Issue Type: Bug
>            Reporter: RefuX Zanzeebarr
>         Assigned To: Shigeru Chiba
>
> In CtClassType we have:
>             m = new MethodInfo(cf.getConstPool(), "<clinit>", "()V");
>             m.setAccessFlags(AccessFlag.STATIC);
> In ProxyFactory
>          MethodInfo minfo = new MethodInfo(cp, "<clinit>", "()V");
> but no static flag.
> We actually ran into this issue because the JVM on the iSeries was very unhappy about the lack of the static flag in clinit. IBM are now updating their JVM to work correctly with the missing static flag.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:54:41 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JASSIST-29) StackMapTable
	support
In-Reply-To: <30858754.1162154141561.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11931202.1191297281113.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-29?page=all ]

Shigeru Chiba resolved JASSIST-29.
----------------------------------

    Resolution: Done

by version 3.6.0

> StackMapTable support
> ---------------------
>
>                 Key: JASSIST-29
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-29
>             Project: Javassist
>          Issue Type: Feature Request
>            Reporter: Shigeru Chiba
>         Assigned To: Shigeru Chiba
>            Priority: Blocker
>
> All class files must support StackMapTable in Java SE 6.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  1 23:54:41 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Mon, 1 Oct 2007 23:54:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JASSIST-29) StackMapTable support
In-Reply-To: <30858754.1162154141561.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27749175.1191297281222.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-29?page=all ]

Shigeru Chiba closed JASSIST-29.
--------------------------------


> StackMapTable support
> ---------------------
>
>                 Key: JASSIST-29
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-29
>             Project: Javassist
>          Issue Type: Feature Request
>            Reporter: Shigeru Chiba
>         Assigned To: Shigeru Chiba
>            Priority: Blocker
>
> All class files must support StackMapTable in Java SE 6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:09:59 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Tue, 2 Oct 2007 01:09:59 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1231) Functions do not
 get added to new BRMS package when package imported from drl file
In-Reply-To: <29309043.1190993621096.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13076643.1191301799603.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1231?page=all ]

Michael Neale closed JBRULES-1231.
----------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done
         Assignee: Michael Neale  (was: Mark Proctor)

not really a bug, but done anyway.

> Functions do not get added to new BRMS package when package imported from drl file
> ----------------------------------------------------------------------------------
>
>                 Key: JBRULES-1231
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1231
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: BRMS running on Windows XP SP2, with JBoss 4.2GA
>            Reporter: Shahad Ahmed
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> When you create a new package in the BRMS by importing an existing DRL file then any functions in the DRL file do not get added to the list of functions for the newly created package. Instead, the functions appear along with the import statements in the "header" text box found when you click on "Edit Package configuration" for the new package!
> To recreate:
> Put the example rules below into a .drl file and import it into the BRMS by creating a new package and choosng the option to load it from a .drl file.
> Click on the newly created package com.acme.example in the package browser. Click on the Functions tab for the package. No functions are present. 
> Click on com.acme.example in the package browser and then select "Edit Package configuration". In the Header text box you should see the two functions defined in the example DRL file given below.
> package com.acme.example
> import java.util.Set;
> function int firstFunction ()
> {
>     return 1;
> }
> function int secondFunction ()
> {
>     return 2;
> }
> rule "Rule 1"
> 	when
> 		eval(firstFunction() == 1)
> 	then 
> 	    System.out.println("Function 1");
> end
> rule "Rule 2"
> 	when
> 		eval(secondFunction() == 2)
> 	then 
> 	    System.out.println("Function 2");
> End

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1227) Add
 drools-analytics support to drools-ant
In-Reply-To: <5171179.1190831322186.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29068757.1191302741457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1227?page=all ]

Fernando Meyer closed JBRULES-1227.
-----------------------------------

    Fix Version/s: 4.0.2
                       (was: FUTURE)
       Resolution: Done

> Add drools-analytics support to drools-ant 
> -------------------------------------------
>
>                 Key: JBRULES-1227
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1227
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1238) Upgrade BRMS to
 use jboss seam version 2.0
In-Reply-To: <25446154.1191273281034.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23754585.1191302741785.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1238?page=all ]

Fernando Meyer closed JBRULES-1238.
-----------------------------------

    Resolution: Done

> Upgrade BRMS to use jboss seam version 2.0 
> -------------------------------------------
>
>                 Key: JBRULES-1238
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1238
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:41 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-996) Admin screen option
 to remove archive items
In-Reply-To: <18780102.1184139752013.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32315490.1191302741986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-996?page=all ]

Fernando Meyer closed JBRULES-996.
----------------------------------

    Fix Version/s: 4.0.2
                       (was: FUTURE)
       Resolution: Done

> Admin screen option to remove archive items
> -------------------------------------------
>
>                 Key: JBRULES-996
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-996
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions:  4.0.0.MR3
>            Reporter: Michael Neale
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> This is for V2 (not NOW !). 
> Should have a feature (for admins) to permanently delete all items marked as archived (packages and assets).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 01:25:43 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 2 Oct 2007 01:25:43 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-995) Show archived
 items with option to restore (packages rules)
In-Reply-To: <10034616.1184139631678.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33372883.1191302743101.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-995?page=comments#action_12379790 ] 
            
Fernando Meyer commented on JBRULES-995:
----------------------------------------

It's already done for Assets, just missing this feature for packages

> Show archived items with option to restore (packages rules)
> -----------------------------------------------------------
>
>                 Key: JBRULES-995
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-995
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions:  4.0.0.MR3
>            Reporter: Michael Neale
>         Assigned To: Fernando Meyer
>             Fix For: FUTURE
>
>
> This is for V2 only !
> Should be able to show archived packages, and restore them. With rules, we can search for archived ones, should also be able to restore them (ie if they are archived, have a button to "unarchive" them).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 04:29:15 2007
From: jira-events at lists.jboss.org (Ross McDonald (JIRA))
Date: Tue, 2 Oct 2007 04:29:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1064) mail nodes cannot
 resolve variables with hyphenated names
Message-ID: <18886359.1191313755641.JavaMail.jira@cloud.prod.atl2.jboss.com>

mail nodes cannot resolve variables with hyphenated names
---------------------------------------------------------

                 Key: JBPM-1064
                 URL: http://jira.jboss.com/jira/browse/JBPM-1064
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions:  jBPM jPDL 3.2.1
         Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
            Reporter: Ross McDonald
         Assigned To: Tom Baeyens


In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed.  Changing this variable to be 'myVariable' instead resolves it correctly.  

I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.  

Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 04:48:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <11520876.1191314883372.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379805 ] 
            
Thomas Diesler commented on JBREM-305:
--------------------------------------

It should be possible for WS client to send a SOAP JMS message to a queue/topic in the same way a JMS client would.

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: Tom  Elrod
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 04:50:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 04:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-305) Provide support for
 JMS transport
Message-ID: <20514884.1191315003405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-305?page=all ]

Thomas Diesler reassigned JBREM-305:
------------------------------------

    Assignee: David Lloyd  (was: Tom  Elrod)

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 06:16:03 2007
From: jira-events at lists.jboss.org (Darran Lofthouse (JIRA))
Date: Tue, 2 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4771) Backport
 RoleMappingLoginModule to JBoss 4.0.3.SP1
Message-ID: <6777814.1191320163407.JavaMail.jira@cloud.prod.atl2.jboss.com>

Backport RoleMappingLoginModule to JBoss 4.0.3.SP1
--------------------------------------------------

                 Key: JBAS-4771
                 URL: http://jira.jboss.com/jira/browse/JBAS-4771
             Project: JBoss Application Server
          Issue Type: Support Patch
      Security Level: Public (Everyone can see)
          Components: Security
    Affects Versions: JBossAS-4.0.3 SP1
            Reporter: Darran Lofthouse
         Assigned To: Darran Lofthouse


http://wiki.jboss.org/wiki/Wiki.jsp?page=RoleMappingLoginModule

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 07:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14486524.1191323343305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=all ]

Tim Fox updated JBMESSAGING-1084:
---------------------------------

    Fix Version/s: AS 5.0 Integration

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:11:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
Message-ID: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade to JGroups 2.5
----------------------

                 Key: JBMESSAGING-1089
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration


Update to JGroups 2.5 to take advantage of better throughput.

We need to ensure the post office code is sufficiently thread safe.

We may need to do another release for 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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:11:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1017) Upgrade to
	JGroups 2.5
In-Reply-To: <11640655.1185028990023.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12381236.1191323463410.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1017?page=all ]

Tim Fox closed JBMESSAGING-1017.
--------------------------------

    Resolution: Duplicate Issue

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1017
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1017
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:26:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 2 Oct 2007 07:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPM-1064) mail nodes cannot
 resolve variables with hyphenated names
In-Reply-To: <18886359.1191313755641.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26608331.1191324363717.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1064?page=all ]

Ronald van Kuijk resolved JBPM-1064.
------------------------------------

    Resolution: Rejected

In EL, it is not allowed to have hyphens in names, just like it is not allowed in java names. So it is processed as a mathematical  expression where the hyphen is treated as a minus. 

> mail nodes cannot resolve variables with hyphenated names
> ---------------------------------------------------------
>
>                 Key: JBPM-1064
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1064
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions:  jBPM jPDL 3.2.1
>         Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>
> In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed.  Changing this variable to be 'myVariable' instead resolves it correctly.  
> I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.  
> Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:26:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 2 Oct 2007 07:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBPM-1064) mail nodes cannot
 resolve variables with hyphenated names
In-Reply-To: <18886359.1191313755641.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20956281.1191324363878.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1064?page=all ]

Ronald van Kuijk closed JBPM-1064.
----------------------------------


> mail nodes cannot resolve variables with hyphenated names
> ---------------------------------------------------------
>
>                 Key: JBPM-1064
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1064
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions:  jBPM jPDL 3.2.1
>         Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>
> In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed.  Changing this variable to be 'myVariable' instead resolves it correctly.  
> I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.  
> Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:28:03 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Tue, 2 Oct 2007 07:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1242) Archived package
 assets cannot be restored
Message-ID: <10651989.1191324483301.JavaMail.jira@cloud.prod.atl2.jboss.com>

Archived package assets cannot be restored
------------------------------------------

                 Key: JBRULES-1242
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1242
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets?

The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of  archived assets.



-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 07:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 2 Oct 2007 07:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
Message-ID: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>

org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
-----------------------------------------------------------------------------------------------

                 Key: JBAS-4772
                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Test Suite
            Reporter: Dimitris Andreadis
         Assigned To: Thomas Diesler
            Priority: Critical
             Fix For: JBossAS-4.2.2.GA


See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:06:03 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Tue, 2 Oct 2007 08:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
Message-ID: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add appropriate Exception handling when hitting MaxSize
-------------------------------------------------------

                 Key: JBMESSAGING-1090
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
            Reporter: Jay Howell
         Assigned To: Tim Fox


When using MaxSize for a queue and topic the following behaviors exist

Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.

Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.

What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.

I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  

We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  

Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:06:03 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Tue, 2 Oct 2007 08:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
In-Reply-To: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28548265.1191326763527.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1090?page=all ]

Jay Howell reassigned JBMESSAGING-1090:
---------------------------------------

    Assignee: Jay Howell  (was: Tim Fox)

> Add appropriate Exception handling when hitting MaxSize
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1090
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Jay Howell
>
> When using MaxSize for a queue and topic the following behaviors exist
> Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.
> Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.
> What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.
> I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  
> We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  
> Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:22:35 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:22:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
In-Reply-To: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31972561.1191327755653.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1089?page=comments#action_12379865 ] 
            
Tim Fox commented on JBMESSAGING-1089:
--------------------------------------

This is needed for JBAS 5.0

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1089
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Update to JGroups 2.5 to take advantage of better throughput.
> We need to ensure the post office code is sufficiently thread safe.
> We may need to do another release for 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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:22:35 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:22:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
In-Reply-To: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17372275.1191327755885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1089?page=all ]

Tim Fox updated JBMESSAGING-1089:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: AS 5.0 Integration)

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1089
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Update to JGroups 2.5 to take advantage of better throughput.
> We need to ensure the post office code is sufficiently thread safe.
> We may need to do another release for 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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:27:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1091) Selector
 parser should
 literal strings for DeliveryMode in selector expressions
Message-ID: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>

Selector parser should literal strings for DeliveryMode in selector expressions
-------------------------------------------------------------------------------

                 Key: JBMESSAGING-1091
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:27:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27000367.1191328023844.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=all ]

Tim Fox updated JBMESSAGING-1084:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: AS 5.0 Integration)

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:29:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9556864.1191328143241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox updated JBMESSAGING-1091:
---------------------------------

    Summary: Selector parser should use string literals for DeliveryMode in selector expressions  (was: Selector parser should literal strings for DeliveryMode in selector expressions)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:31:30 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 2 Oct 2007 08:31:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7641129.1191328290776.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox updated JBMESSAGING-1091:
---------------------------------

    Description: In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.  (was: In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should "PERSISTENT" or "NON_PERSISTENT" string literals.)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 08:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
In-Reply-To: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12090202.1191328863387.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4772?page=comments#action_12379872 ] 
            
Thomas Diesler commented on JBAS-4772:
--------------------------------------

What do I need to do to setup the JACC config?
i.e. how can I reproduce this?

> org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4772
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:49:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 2 Oct 2007 08:49:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
In-Reply-To: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29144609.1191329345069.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4772?page=comments#action_12379874 ] 
            
Dimitris Andreadis commented on JBAS-4772:
------------------------------------------

Maybe cd testsuite; build tests-jacc-security  | tests-jacc-securitymgr

> org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4772
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:59:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Tue, 2 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
Message-ID: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>

NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
------------------------------------------------------------------------------

                 Key: JBCOMMON-35
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: common-old
    Affects Versions: 1.0.0.GA
            Reporter: Vicky Kak
         Assigned To: Vicky Kak
             Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA


http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 08:59:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Tue, 2 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4429287.1191329943898.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=all ]

Vicky Kak updated JBCOMMON-35:
------------------------------

    Component/s: common-core

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:07:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Tue, 2 Oct 2007 09:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
Message-ID: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>

ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
----------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBCOMMON-36
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: common-core, common-old
    Affects Versions: 1.0.0.GA
            Reporter: Vicky Kak
         Assigned To: Vicky Kak
             Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA


In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
>>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:11:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1937438.1191330663660.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf reopened EJBTHREE-883:
------------------------------------

             

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:11:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30448357.1191330663861.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf updated EJBTHREE-883:
-----------------------------------

    Fix Version/s: AS 4.2.2.GA
                       (was: Branch_4_2)

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:11:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:11:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15763385.1191330664056.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf resolved EJBTHREE-883.
------------------------------------

    Resolution: Done

> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:13:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Tue, 2 Oct 2007 09:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAOP-471) Method
 enforceArgsConsistency()
 not found on field interception with @Arg-annotated param
In-Reply-To: <12708972.1191268901563.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27146941.1191330783227.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-471?page=all ]

Flavia Rainone resolved JBAOP-471.
----------------------------------

    Resolution: Done

> Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAOP-471
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-471
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
> The result:
> Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
> java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
> rgsPOJO.field5]
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
>         at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
>         at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
> Caused by: java.lang.RuntimeException: Error creating invokeNext method: {   try{      switch(++super.currentInterceptor){      case 1:enforceArgsConsistency
> ();    around6.around1(this.arg0);
>       break;      case 2:enforceArgsConsistency();    around7.around2(this.arg0);
>       break;      case 3:enforceArgsConsistency();    around8.around3(this.arg0);
>       break;      case 4:enforceArgsConsistency();    around9.around4(this.arg0);
>       break;      case 5:enforceArgsConsistency();    around10.around6(this.arg0);
>       break;      default:         this.dispatch();      }   }finally{      --super.currentInterceptor;   }   return null;}
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
>         ... 26 more
> Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
> _16
>         at javassist.CtBehavior.setBody(CtBehavior.java:367)
>         at javassist.CtBehavior.setBody(CtBehavior.java:334)
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
>         ... 28 more
> Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
>         at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
>         at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
>         at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
>         at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
>         at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
>         at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:17:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Tue, 2 Oct 2007 09:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-472) Wrappers lack the
 generic type information
In-Reply-To: <5055386.1191269501072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19090252.1191331023579.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-472?page=all ]

Flavia Rainone reassigned JBAOP-472:
------------------------------------

    Assignee: Flavia Rainone

> Wrappers lack the generic type information
> ------------------------------------------
>
>                 Key: JBAOP-472
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-472
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> This issue has already been fixed by Kabir with method wrappers.
> This task consists of fixing the issue for all other joinpoint types.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:29:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:29:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31987406.1191331755813.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-384?page=all ]

Bela Ban updated JGRP-384:
--------------------------

    Fix Version/s: 2.6
                       (was: 2.7)

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:29:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:29:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <580903.1191331755986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-384?page=all ]

Bela Ban updated JGRP-384:
--------------------------

    Attachment: bla2.java

bla2 is the corrected program, which wraps unlock() into a try-catch clause.

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:33:05 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:33:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28093779.1191331985785.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-384?page=comments#action_12379893 ] 
            
Bela Ban commented on JGRP-384:
-------------------------------

Okay, the program throws an exception on unlock(). If you simply wrap unlock() into a try-catch clause, then the next lock() will be successful and the subsequent unlock() as well (see attached bla2.java program).

The reason unlock() throws an exception is the following:
- {A,B}, A has the lock
- B is killed
- A tries to unlock by asking itself and B for agreement
- However there won't be any response from B, so unlock() fails
- As soon as the failure detector kicks in, B will get kicked out of the group, and a will succeed with lock() and unlock()

I suggest to add FD_SOCK to your stack, because that will detect crashes much faster, therefore the new view {A} will get established much sooner and unlock() won't fail.


> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:35:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15790059.1191332103669.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-384?page=comments#action_12379895 ] 
            
Bela Ban commented on JGRP-384:
-------------------------------

Note that - in order to determine a coordinator - you don't need a cluster wide lock; you could simply take the view, which is the *same on all nodes in a cluster*, and (for example) pick the first (= oldest member) in the list. This is faster and doesn't require communication.

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:35:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 2 Oct 2007 09:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-384)
 DistributedLockManager.unlock()
 throws an exception if one of the group members terminates.
In-Reply-To: <5000538.1166051326404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17986067.1191332103857.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-384?page=all ]

Bela Ban resolved JGRP-384.
---------------------------

    Resolution: Done

> DistributedLockManager.unlock() throws an exception if one of the group members terminates.
> -------------------------------------------------------------------------------------------
>
>                 Key: JGRP-384
>                 URL: http://jira.jboss.com/jira/browse/JGRP-384
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Suse Linux 10.1 Desktop
> java version "1.5.0_07"
> Dell Optiplex GX280
>            Reporter: Sean Landis
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>         Attachments: bla2.java
>
>
> I am trying to use the DLM to implement a failover mechanism. Two
> identical processes are started. One acquires the lock and becomes the
> primary; the other can't acquire the lock and becomes the backup. The
> primary does it's processing. The backup checks periodically if it can
> get the lock. Should the primary fail, the backup will acquire the
> lock and do the processing.
> This works fine. The problem I am having is if both are running, the
> backup fails, and the primary tries to unlock. I get the following
> stack trace:
> Exception in thread "main"
> org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
>        at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
>        at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
>        at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
> I am running version 2.4. Here's a sample program:
> package distlock.examples;
> import org.jgroups.JChannel;
> import org.jgroups.blocks.DistributedLockManager;
> import org.jgroups.blocks.LockNotGrantedException;
> import org.jgroups.blocks.VotingAdapter;
> public class FailoverTest {
>  public static final String SERVER_PROTOCOL_STACK =
>    "UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
>            + "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
>            + ":PING(timeout=500;num_initial_members=1)"
>            + ":FD"
>            + ":VERIFY_SUSPECT(timeout=1500)"
>            + ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
>            + ":UNICAST(timeout=5000)"
>            + ":pbcast.STABLE(desired_avg_gossip=200)"
>            + ":FRAG(frag_size=4096)"
>            + ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
>            +     "shun=false;print_local_addr=false)"
>    ;
>  private void doIt() throws Exception {
>    JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
>    VotingAdapter adapter = new VotingAdapter(channel);
>    channel.connect("cluster");
>    DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
>    String lockId = "theLock";
>    for (int i = 0; i < 40; i++) {
>      while (true) {
>        try {
>          System.out.println("Trying to get lock.");
>          dlm.lock(lockId, channel.getLocalAddress(), 10000);
>          break;
>        } catch (LockNotGrantedException ex) {
>          System.out.println("Could not get lock.");
>        }
>        try {
>          Thread.sleep(5000);
>        } catch(InterruptedException ex) {
>        }
>      }
>      System.out.println("Got lock, sleeping.");
>      try {
>        Thread.sleep(10000);
>      } catch(InterruptedException ex) {
>      }
>      System.out.println("unlocking and sleeping.");
>      dlm.unlock(lockId, channel.getLocalAddress());
>      try {
>        Thread.sleep(5000);
>      } catch(InterruptedException ex) {
>      }
>    }
>    channel.close();
>  }
>  public static void main(String[] args) throws Exception {
>    System.setProperty("java.net.preferIPv4Stack", "true");
>    new FailoverTest().doIt();
>  }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:39:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Tue, 2 Oct 2007 09:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <23258979.1191332343592.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12379897 ] 
            
David Lloyd commented on JBREM-305:
-----------------------------------

OK - but what does Remoting give you then?  After all, the JMS API can send a JMS message, and unlike, say, HTTP, JMS only has one client API (that I know of anyway).

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:59:14 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1243) Pattern matching
 does not allow spaces
Message-ID: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>

Pattern matching does not allow spaces
--------------------------------------

                 Key: JBRULES-1243
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
             Project: JBoss Drools
          Issue Type: Bug
            Reporter: Markus Wolf
         Assigned To: Mark Proctor
            Priority: Blocker


When I have a rule condition like this:
  Something( test matches "abc def")
I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
When I remove the space and replace it with \s it does compile well.

Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 09:59:14 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Tue, 2 Oct 2007 09:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1243) Pattern matching
 does not allow spaces
In-Reply-To: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17202926.1191333554599.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1243?page=all ]

Markus Wolf updated JBRULES-1243:
---------------------------------

    Affects Version/s: 4.0.1
             Priority: Major  (was: Blocker)

> Pattern matching does not allow spaces
> --------------------------------------
>
>                 Key: JBRULES-1243
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> When I have a rule condition like this:
>   Something( test matches "abc def")
> I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
> When I remove the space and replace it with \s it does compile well.
> Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:23:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Tue, 2 Oct 2007 10:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-471) Method
 enforceArgsConsistency()
 not found on field interception with @Arg-annotated param
In-Reply-To: <12708972.1191268901563.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3649404.1191334983258.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-471?page=all ]

Flavia Rainone closed JBAOP-471.
--------------------------------


> Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAOP-471
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-471
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
> The result:
> Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
> java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
> rgsPOJO.field5]
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
>         at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
>         at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
>         at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
> Caused by: java.lang.RuntimeException: Error creating invokeNext method: {   try{      switch(++super.currentInterceptor){      case 1:enforceArgsConsistency
> ();    around6.around1(this.arg0);
>       break;      case 2:enforceArgsConsistency();    around7.around2(this.arg0);
>       break;      case 3:enforceArgsConsistency();    around8.around3(this.arg0);
>       break;      case 4:enforceArgsConsistency();    around9.around4(this.arg0);
>       break;      case 5:enforceArgsConsistency();    around10.around6(this.arg0);
>       break;      default:         this.dispatch();      }   }finally{      --super.currentInterceptor;   }   return null;}
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
>         ... 26 more
> Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
> _16
>         at javassist.CtBehavior.setBody(CtBehavior.java:367)
>         at javassist.CtBehavior.setBody(CtBehavior.java:334)
>         at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
>         ... 28 more
> Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
>         at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
>         at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
>         at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
>         at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
>         at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
>         at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
>         at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:25:17 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 10:25:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-651)
 javax.ejb.SessionContext.getBusinessObject has wrong signature
In-Reply-To: <10970126.1152819852031.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13922528.1191335117059.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-651?page=all ]

Carlo de Wolf reassigned EJBTHREE-651:
--------------------------------------

    Assignee: Carlo de Wolf

> javax.ejb.SessionContext.getBusinessObject has wrong signature
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-651
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-651
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3
>
>
> javax.ejb.SessionContext.getBusinessObject must have the following signature:
> <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException;
> See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getBusinessObject(java.lang.Class)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:25:17 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 10:25:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-651)
 javax.ejb.SessionContext.getBusinessObject has wrong signature
In-Reply-To: <10970126.1152819852031.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32002984.1191335117207.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-651?page=all ]

Carlo de Wolf resolved EJBTHREE-651.
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
       Resolution: Done

> javax.ejb.SessionContext.getBusinessObject has wrong signature
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-651
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-651
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3
>
>
> javax.ejb.SessionContext.getBusinessObject must have the following signature:
> <T> T getBusinessObject(Class<T> businessInterface) throws IllegalStateException;
> See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getBusinessObject(java.lang.Class)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:29:03 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Tue, 2 Oct 2007 10:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1243) Pattern matching
 does not allow spaces
In-Reply-To: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25685389.1191335343277.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1243?page=all ]

Markus Wolf updated JBRULES-1243:
---------------------------------


The given rule is not exactlly, to reproduct one have to use the following condition:
  Something( prop1.prop2 matches "abc def")
I've read that this matching is delegated to MVEL - maybe the bug belongs to MVEL then.

> Pattern matching does not allow spaces
> --------------------------------------
>
>                 Key: JBRULES-1243
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> When I have a rule condition like this:
>   Something( test matches "abc def")
> I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
> When I remove the space and replace it with \s it does compile well.
> Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:37:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 10:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4523) Verify
 installation of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25436566.1191335823296.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4523?page=comments#action_12379914 ] 
            
Heiko Braun commented on JBAS-4523:
-----------------------------------

Testsuite: org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase
Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 0.095 sec
------------- Standard Output ---------------
cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsconsume.sh -k -o /home/hbraun/
dev/prj/jbossws/stack/native/trunk/output/tests/wsconsume/java /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/
tests/resources/jaxws/smoke/tools/wsdl/TestServiceCatalog.wsdl
test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsprovide.sh -k -w -o /home/hbra
un/dev/prj/jbossws/stack/native/trunk/output/tests/wsprovide/java --classpath /home/hbraun/dev/prj/jbossws/stack/nativ
e/trunk/output/tests/classes org.jboss.test.ws.jaxws.smoke.tools.CalculatorBean
test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
------------- ---------------- ---------------

Testcase: testWSConsumeFromCommandLine took 0.006 sec
        Caused an ERROR
java.io.IOException: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsconsume.sh: no
t found
java.io.IOException: java.io.IOException: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA
/bin/wsconsume.sh: not found
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
        at java.lang.Runtime.exec(Runtime.java:591)
        at java.lang.Runtime.exec(Runtime.java:429)
        at java.lang.Runtime.exec(Runtime.java:367)
        at org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase.executeCommand(ScriptTestCase.java:110)
        at org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase.testWSConsumeFromCommandLine(ScriptTestCase.java:69)


> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:41:04 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 2 Oct 2007 10:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13634875.1191336064658.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-570?page=comments#action_12379916 ] 
            
Vladimir Blagojevic commented on JGRP-570:
------------------------------------------

ThreadNamaingPattern is applied to all thread pools. However, there are still leftover short lifespan threads that are not renamed.

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:49:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-553) Run AS (4.x and
 5.x) integration tests with Messaging
In-Reply-To: <27353135.1159216981170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8922364.1191336543453.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-553?page=all ]

Clebert Suconic closed JBMESSAGING-553.
---------------------------------------

    Resolution: Done

> Run AS (4.x and 5.x) integration tests with Messaging
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-553
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-553
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> This is the container task for everthing required to run JBoss AS JMS integration tests with JBoss Messaging. The existing integration test framework should be modified in such a manner to allow interchangeably running the same JMS tests with JBossMQ and JBoss Messaging. None of the existing JBossMQ tests should be removed, they must be at most refactored so the JBossMQ-specific tests will be executed with JBossMQ only (as part of the JBossMQ functional testsuite) and generic JMS tests will be executed with both JBossMQ and JBoss Messaging.
> More details in the sub-tasks.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:51:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1092) Fix the
 JBossHead testsuite
Message-ID: <27131273.1191336663430.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix the JBossHead testsuite
---------------------------

                 Key: JBMESSAGING-1092
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1092
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration



There are still tests failing because of config issues...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:51:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-387) Modify the
 admin console to
 work with Messaging while keeping JBossMQ compatibility
Message-ID: <22530056.1191336663923.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-387?page=all ]

Clebert Suconic closed JBMESSAGING-387.
---------------------------------------

    Resolution: Partially Completed

> Modify the admin console to work with Messaging while keeping JBossMQ compatibility
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-387
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-387
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>             Fix For: AS 5.0 Integration
>
>
> JSR77
> Charles

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:53:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1093) Verify/Update
 the "all" configuration on JBossHead
Message-ID: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>

Verify/Update the "all" configuration on JBossHead
--------------------------------------------------

                 Key: JBMESSAGING-1093
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Tim Fox




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:53:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:53:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-384) Modify
 jboss-head build
 script to include Messaging instead of JBossMQ in the "all" configuration
Message-ID: <30803679.1191336784113.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-384?page=all ]

Clebert Suconic closed JBMESSAGING-384.
---------------------------------------

    Resolution: Done

> Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-384
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-384
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> Make sure JBossMQ still works as an alternate JMS provider

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:53:05 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:53:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1094) Integrate
	JSR-77
Message-ID: <9255952.1191336785142.JavaMail.jira@cloud.prod.atl2.jboss.com>

Integrate JSR-77
----------------

                 Key: JBMESSAGING-1094
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1094
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration, EAP 4.3 Integration




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1093)
 Verify/Update the "all" configuration on JBossHead
In-Reply-To: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25698247.1191336903451.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1093?page=all ]

Clebert Suconic reassigned JBMESSAGING-1093:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Verify/Update the "all" configuration on JBossHead
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1093
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1093) Verify/Update
 the "all" configuration on JBossHead
In-Reply-To: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9473174.1191336903560.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1093?page=all ]

Clebert Suconic updated JBMESSAGING-1093:
-----------------------------------------

    Fix Version/s: AS 5.0 Integration

> Verify/Update the "all" configuration on JBossHead
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1093
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1094) Integrate
	JSR-77
In-Reply-To: <9255952.1191336785142.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23004120.1191336903772.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1094?page=all ]

Clebert Suconic reassigned JBMESSAGING-1094:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Integrate JSR-77
> ----------------
>
>                 Key: JBMESSAGING-1094
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1094
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-382) Make Messaging
 the default JMS provider for JBoss 5.0
Message-ID: <17054107.1191336903979.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-382?page=all ]

Clebert Suconic closed JBMESSAGING-382.
---------------------------------------

    Resolution: Done

> Make Messaging the default JMS provider for JBoss 5.0
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-382
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-382
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:57:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1092) Fix the
 JBossHead testsuite
In-Reply-To: <27131273.1191336663430.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7882484.1191337023387.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1092?page=all ]

Clebert Suconic reassigned JBMESSAGING-1092:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Fix the JBossHead testsuite
> ---------------------------
>
>                 Key: JBMESSAGING-1092
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1092
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>
> There are still tests failing because of config issues...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 10:59:14 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 10:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-726) Write/Ellect
 some
 Clustering tests to go into Integration Testsuite on ApplicationServer
In-Reply-To: <1288401.1168296267440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28763649.1191337154896.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-726?page=all ]

Clebert Suconic updated JBMESSAGING-726:
----------------------------------------

    Fix Version/s: AS 5.0 Integration

> Write/Ellect some Clustering tests to go into Integration Testsuite on ApplicationServer
> ----------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-726
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-726
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.2.0.Beta1
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:03:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 11:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3556) Add non-integration
 based testing to cluster module
In-Reply-To: <8862893.1156352389582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19498659.1191337383408.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3556?page=all ]

Brian Stansberry reassigned JBAS-3556:
--------------------------------------

    Assignee: Brian Stansberry

> Add non-integration based testing to cluster module
> ---------------------------------------------------
>
>                 Key: JBAS-3556
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3556
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Test Suite
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-5.0.1.CR1
>
>
> All the unit tests for the AS cluster module are run via the testsuite tests-clustering target, which starts two AS instances.  This is painful and time consuming and discourages writing of simple unit tests that exercise a particular class, with no need for a larger integration.
> Need to set up a src/tests tree in the cluster module, add simple unit tests to it, and integrate that into the overall testsuite run.  The security module has this kind of setup; look to that to see how the overall testsuite integration is done.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:03:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
Message-ID: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot change roles of user names containing a backslash character
------------------------------------------------------------------

                 Key: JBPORTAL-1732
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Identity
    Affects Versions: 2.6.2 Final
         Environment: Any
            Reporter: Luc Boudreau
            Priority: Critical


In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.

ie. DOMAIN\username

I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.

2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)





-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:03:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5613738.1191337383665.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12379921 ] 
            
Luc Boudreau commented on JBPORTAL-1732:
----------------------------------------

The correct username would have been SIM\boudrel here...

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>            Priority: Critical
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:09:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 2 Oct 2007 11:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16403093.1191337743250.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=all ]

Thomas Heute updated JBPORTAL-1732:
-----------------------------------

    Fix Version/s: 2.6.3 Final
         Priority: Major  (was: Critical)

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:31:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 2 Oct 2007 11:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31936128.1191339063373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf reassigned EJBTHREE-900:
--------------------------------------

    Assignee: Carlo de Wolf

> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:49:12 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:49:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26572771.1191340152876.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12379929 ] 
            
Luc Boudreau commented on JBPORTAL-1732:
----------------------------------------

This bug also affects the user deletion. Probably other functionnalities too.

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:57:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
Message-ID: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>

CMS admin role hardcoded somewhere
----------------------------------

                 Key: JBPORTAL-1733
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal CMS
         Environment: Any
            Reporter: Luc Boudreau
         Assigned To: Sohil Shah


 - Modify platform to use another admin role name
 - Create user with new admin role and old Admin role
 - Change security on root node of CMS and make the new role the manager
 - Change the user's roles by removing the old Admin role
 - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 11:57:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Tue, 2 Oct 2007 11:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2559844.1191340623525.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_12379930 ] 
            
Luc Boudreau commented on JBPORTAL-1733:
----------------------------------------

On the last thing to do, I meant :

 -  - Try to secure the root node : Access Denided

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 12:01:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 2 Oct 2007 12:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27919516.1191340863719.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=all ]

Thomas Heute updated JBPORTAL-1733:
-----------------------------------

        Fix Version/s: 2.6.3 Final
    Affects Version/s: 2.6.2 Final

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:29:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 13:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
Message-ID: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot gravitate data only stored in cache loader
-------------------------------------------------

                 Key: JBCACHE-1192
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eviction, Replication
    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
            Priority: Critical
             Fix For: 1.4.1.SP6, 2.1.0.GA


If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:34:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1190) Eviction
 configuration should consider buddy backup regions as well.
In-Reply-To: <32922469.1191234772880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13515307.1191346443882.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1190?page=all ]

Brian Stansberry updated JBCACHE-1190:
--------------------------------------

    Workaround:   (was: [Workaround Exists])

Removing the suggested workaround; JBCACHE-1192 means it won't work.

> Eviction configuration should consider buddy backup regions as well.
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1190
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:59:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 13:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4523) Verify installation
 of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33252356.1191347943683.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4523?page=all ]

Heiko Braun updated JBAS-4523:
------------------------------

    Comment: was deleted

> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:59:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 13:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4523) Verify
 installation of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30014359.1191347943865.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4523?page=comments#action_12379956 ] 
            
Heiko Braun commented on JBAS-4523:
-----------------------------------

Testing AS 4.2.2:

one-test:
    [junit] Running org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase
    [junit] cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsconsume.sh -k -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsconsume/java /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/resources/jaxws/smoke/tools/wsdl/TestServiceCatalog.wsdl
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] cmd: /home/hbraun/dev/prj/jbossas/branches/Branch_4_2/build/output/jboss-4.2.2.GA/bin/wsprovide.sh -k -w -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsprovide/java --classpath /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/classes org.jboss.test.ws.jaxws.smoke.tools.CalculatorBean
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.564 sec


> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 13:59:04 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 13:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4523) Verify
 installation of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8148466.1191347944047.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4523?page=comments#action_12379957 ] 
            
Heiko Braun commented on JBAS-4523:
-----------------------------------

Testing AS 5.0:

one-test:
    [junit] Running org.jboss.test.ws.jaxws.smoke.tools.ScriptTestCase
    [junit] cmd: /home/hbraun/dev/prj/jbossas/trunk/build/output/jboss-5.0.0.Beta3/bin/wsconsume.sh -k -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsconsume/java /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/resources/jaxws/smoke/tools/wsdl/TestServiceCatalog.wsdl
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] cmd: /home/hbraun/dev/prj/jbossas/trunk/build/output/jboss-5.0.0.Beta3/bin/wsprovide.sh -k -w -o /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/wsprovide/java --classpath /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests/classes org.jboss.test.ws.jaxws.smoke.tools.CalculatorBean
    [junit] test execution dir: /home/hbraun/dev/prj/jbossws/stack/native/trunk/output/tests
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.648 sec


> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:01:08 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 14:01:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4523) Verify installation
 of jbossws tools jars
In-Reply-To: <19718796.1183979371679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32783713.1191348068132.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4523?page=all ]

Heiko Braun resolved JBAS-4523.
-------------------------------

    Resolution: Done

The tests should actually move to the AS code base. I'll create a separate issue for it.

> Verify installation of jbossws tools jars
> -----------------------------------------
>
>                 Key: JBAS-4523
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4523
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Heiko Braun
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:03:03 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 2 Oct 2007 14:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4773) Move the JBossWS
 integration tests to the AS test module
Message-ID: <24000477.1191348183624.JavaMail.jira@cloud.prod.atl2.jboss.com>

Move the JBossWS integration tests to the AS test module
--------------------------------------------------------

                 Key: JBAS-4773
                 URL: http://jira.jboss.com/jira/browse/JBAS-4773
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Test Suite
            Reporter: Heiko Braun
         Assigned To: Heiko Braun
             Fix For: JBossAS-4.2.3.GA


The JBossWS integration test need to reside with the AS. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:05:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 14:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1190) Eviction
 configuration should consider buddy backup regions as well.
In-Reply-To: <32922469.1191234772880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24235989.1191348303293.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1190?page=all ]

Brian Stansberry updated JBCACHE-1190:
--------------------------------------

    Workaround Description:   (was: Explicitly configure parallel eviction policies for all buddy backup Fqn patterns)

> Eviction configuration should consider buddy backup regions as well.
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1190
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1190
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 14:35:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 2 Oct 2007 14:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1192) Cannot
 gravitate data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27277455.1191350103505.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=comments#action_12379970 ] 
            
Brian Stansberry commented on JBCACHE-1192:
-------------------------------------------

Test for this is BuddyReplicationWithCacheLoaderTest.testGravitationOfEvictedNodes()

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication, Eviction
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 1.4.1.SP6
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 15:05:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 15:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4772)
 org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC
 or security manager
In-Reply-To: <1879316.1191326223340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4659551.1191351903700.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4772?page=all ]

Thomas Diesler resolved JBAS-4772.
----------------------------------

    Resolution: Done

Use tests.classpath  instead of tests.compile.classpath

--- imports/server-config.xml   (revision 65767)
+++ imports/server-config.xml   (working copy)
@@ -686,7 +686,7 @@
                <pathelement location="${build.resources}"/>
                <!-- This may need to be externalized -->
                <pathelement location="${build.resources}/security"/>
-               <path refid="tests.compile.classpath"/>
+               <path refid="tests.classpath"/>
             </classpath>


> org.jboss.test.webservice.jbws309.JBWS309TestCase fails when run under JACC or security manager
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4772
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4772
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> See http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-4.2.x-TestSuite-sun15/lastBuild/testReport/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 15:07:15 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 2 Oct 2007 15:07:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4767) Upgrade jbossws to
 2.0.1 (from 1.2.1.GA)
In-Reply-To: <16412352.1191227742601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9685952.1191352035861.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4767?page=all ]

Thomas Diesler resolved JBAS-4767.
----------------------------------

    Resolution: Done

Done.

Please note, jbossws-jboss42.jar must be removed from jbossws.sar during the AS build.

> Upgrade jbossws to 2.0.1 (from 1.2.1.GA)
> ----------------------------------------
>
>                 Key: JBAS-4767
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4767
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 15:51:14 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 2 Oct 2007 15:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4695) Update the release
 notes for JBossAS 4.2.2.GA
In-Reply-To: <21520758.1189414871155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1197145.1191354674968.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4695?page=all ]

Dimitris Andreadis closed JBAS-4695.
------------------------------------

    Resolution: Done

It's ok, needs a final pass.

> Update the release notes for JBossAS 4.2.2.GA
> ---------------------------------------------
>
>                 Key: JBAS-4695
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4695
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 17:31:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Tue, 2 Oct 2007 17:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-812) Specify an API to
 discover services
Message-ID: <11944998.1191360663233.JavaMail.jira@cloud.prod.atl2.jboss.com>

Specify an API to discover services
-----------------------------------

                 Key: JBREM-812
                 URL: http://jira.jboss.com/jira/browse/JBREM-812
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: r3 api
            Reporter: David Lloyd
         Assigned To: David Lloyd
            Priority: Minor
             Fix For: 3.0.0.Alpha1 (Otter)


The Remoting 3 API presently has a mechanism to discover endpoints and supply information about how to connect to discovered endpoints.

A mechanism is also needed to allow a user to find any endpoint that provides a specific service.  This mechanism would preferably work in tandem with the existing discovery API.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 17:58:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 2 Oct 2007 17:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1506310.1191362283374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4180?page=all ]

Galder Zamarreno updated JBAS-4180:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120214

dev forum link added

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:05:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 18:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
Message-ID: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>

ServerPeer won't survive a stop/start of the service
----------------------------------------------------

                 Key: JBMESSAGING-1095
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic


Few NullPointerExceptions would happen..


This won't affect any production system... 

It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:05:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 18:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33011350.1191362703550.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Clebert Suconic updated JBMESSAGING-1095:
-----------------------------------------

        Fix Version/s: 1.4.0.SP1
    Affects Version/s: 1.4.0.GA

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:11:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 18:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <678285.1191363063246.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Clebert Suconic updated JBMESSAGING-1095:
-----------------------------------------

    Fix Version/s: AS 5.0 Integration
                   EAP 4.3 Integration

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 18:25:07 2007
From: jira-events at lists.jboss.org (Ben Truitt (JIRA))
Date: Tue, 2 Oct 2007 18:25:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1235) Multiple
 Criteria break BRMS rule editor
In-Reply-To: <24987902.1191139841173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24789832.1191363907349.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1235?page=comments#action_12380034 ] 
            
Ben Truitt commented on JBRULES-1235:
-------------------------------------

Hi Michael -
 I'm afraid I can't share the jar / source due to IP stuff with my employer.  What I'll try to do is create a trivial example that I can share that reproduces the problem.
-Ben

> Multiple Criteria break BRMS rule editor
> ----------------------------------------
>
>                 Key: JBRULES-1235
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1235
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Ben Truitt
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>         Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg, screenshot3.jpeg
>
>
> In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
> Two ways to trigger:
> 1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
> 2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
> I'll attach screenshots, which should help explain.
> Sorry if this is a dupe - I looked, but didn't find anything like 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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:18:03 2007
From: jira-events at lists.jboss.org (Kris Verlaenen (JIRA))
Date: Tue, 2 Oct 2007 20:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1244) Ruleflows should
 have a package name
Message-ID: <20387486.1191370683368.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ruleflows should have a package name
------------------------------------

                 Key: JBRULES-1244
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1244
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Rule Flow
            Reporter: Kris Verlaenen
         Assigned To: Kris Verlaenen
             Fix For: 4.0.2


Ruleflows should be added as part of their own package.
This allows
 - adding ruleflows before adding rules
 - adding only ruleflows to a package


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:22:03 2007
From: jira-events at lists.jboss.org (Kris Verlaenen (JIRA))
Date: Tue, 2 Oct 2007 20:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1244) Ruleflows should
 have a package name
In-Reply-To: <20387486.1191370683368.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6456595.1191370923247.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1244?page=all ]

Kris Verlaenen resolved JBRULES-1244.
-------------------------------------

    Resolution: Done

Process now has a packageName

> Ruleflows should have a package name
> ------------------------------------
>
>                 Key: JBRULES-1244
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1244
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rule Flow
>            Reporter: Kris Verlaenen
>         Assigned To: Kris Verlaenen
>             Fix For: 4.0.2
>
>
> Ruleflows should be added as part of their own package.
> This allows
>  - adding ruleflows before adding rules
>  - adding only ruleflows to a package

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:29:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
Message-ID: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>

ServletServerInvoker should return an exception instead of just an error message
--------------------------------------------------------------------------------

                 Key: JBREM-813
                 URL: http://jira.jboss.com/jira/browse/JBREM-813
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.4.0.Beta1 (Pinto)


The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  

Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:29:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28273730.1191371343935.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-813?page=all ]

Ron Sigal updated JBREM-813:
----------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:37:13 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:37:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-809) Verify that the
 behavior of the
 HTTPUnMarshaller re stripping CR and LF characters is correct
In-Reply-To: <4580360.1190730941269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29920730.1191371833435.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-809?page=all ]

Ron Sigal updated JBREM-809:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP1
                       2.4.0.Beta1 (Pinto)
                           (was: 2.2.1.GA)

> Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBREM-809
>                 URL: http://jira.jboss.com/jira/browse/JBREM-809
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP1
>            Reporter: Tom Fennelly
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> At the moment, the HTTPUnMarshaller uses a BufferedReader to read a HTTP char stream.  This causes it to modify the message payload by removing the CR and LF characters.  This causes a problem for us on the ESB because it means that signature checks fail on signed SOAP messages since the sig was generated from the message containing the CR and LF chars.  It's even worse than that... it actually corrupts the signature within the message because the canonical form of the sig contains CRLF chars.
> We got around this in the ESB (in the short term) by setting our own modified version of the HTTPUnMarshaller - one that doesn't use a BufferedReader.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:37:13 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:37:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-808) Remove dependencies
 on ObjectNameFactory from JBoss JMX
In-Reply-To: <161557.1189940062854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22118309.1191371833996.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-808?page=all ]

Ron Sigal updated JBREM-808:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP1
                       2.4.0.Beta1 (Pinto)

> Remove dependencies on ObjectNameFactory from JBoss JMX
> -------------------------------------------------------
>
>                 Key: JBREM-808
>                 URL: http://jira.jboss.com/jira/browse/JBREM-808
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP1
>            Reporter: Julien Viet
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> It happens when my POJO has not been bound on the transporter server, it looks like the transporter client is trying to do some fail over.
> This make JBoss Remoting depends on the JBoss JMX implementation. That makes JBoss Remoting more difficult to embed and reuse.
> I think that the ObjectNameFactory class could be easily ported to JBoss Remoting without any harm done. However perhaps JBoss Remoting has more dependencies on JBoss JMX that I don't know that would prevent to remove such dependency.
>    [junit_] Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/mx/util/ObjectNameFactory
>    [junit_]     at org.jboss.remoting.transporter.InternalTransporterServices.<clinit>(InternalTransporterServices.java:41)
>    [junit_]     at org.jboss.remoting.transporter.TransporterClient.findAlternativeTarget(TransporterClient.java:330)
>    [junit_]     at org.jboss.remoting.transporter.TransporterClient.invoke(TransporterClient.java:301)
>    [junit_]     at $Proxy0.getInfo(Unknown Source)
>    [junit_]     at org.jboss.portal.test.framework.driver.remote.RemoteTestDriverClient.getInfo(RemoteTestDriverClient.java:107)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 20:39:06 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 2 Oct 2007 20:39:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-810) coyote.RequestMap
 not storing all request properties in the Map.Entry set
In-Reply-To: <12166936.1190807921122.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31450323.1191371946039.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-810?page=all ]

Ron Sigal updated JBREM-810:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP1
                       2.4.0.Beta1 (Pinto)

> coyote.RequestMap not storing all request properties in the Map.Entry set
> -------------------------------------------------------------------------
>
>                 Key: JBREM-810
>                 URL: http://jira.jboss.com/jira/browse/JBREM-810
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.2.SP1
>            Reporter: Tom Fennelly
>         Assigned To: Trustin Lee
>            Priority: Minor
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> Small thing, but the RequestMap overrides the get method for some of the request properties e.g. "Path" and "HttpVersion".  This is fine if the code using the request Map (from InvocationRequest) accesses the properties via the get method.  However, if it iterates over the Map.Entry set, these values will come back as null because they're not actually stored in the map entry set.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 22:30:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 22:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18997650.1191378603312.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Clebert Suconic closed JBMESSAGING-1095.
----------------------------------------

    Resolution: Done

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 22:36:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 22:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1091) Selector
 parser should
 use string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30453892.1191378963366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Clebert Suconic reassigned JBMESSAGING-1091:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 22:36:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 2 Oct 2007 22:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31683545.1191378963541.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Clebert Suconic closed JBMESSAGING-1091.
----------------------------------------

    Resolution: Done

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  2 23:13:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Tue, 2 Oct 2007 23:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1240) Remove Dialect
 state from PackageBuilderConfiguration
In-Reply-To: <22006922.1191288761051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2050594.1191381183230.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1240?page=all ]

Mark Proctor closed JBRULES-1240.
---------------------------------

    Resolution: Done

> Remove Dialect state from PackageBuilderConfiguration
> -----------------------------------------------------
>
>                 Key: JBRULES-1240
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1240
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> We are getting issues, particularly in threading scenarios, where PackageBuilderConfiguration holding onto the JavaDialect instance is causing problems. We need to make PackageBuilderConfiguration stateless, or atleast immutable.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 00:36:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Wed, 3 Oct 2007 00:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1193) Tests should not
 call Transaction.commit/rollback()
Message-ID: <5880125.1191386163241.JavaMail.jira@cloud.prod.atl2.jboss.com>

Tests should not call Transaction.commit/rollback()
---------------------------------------------------

                 Key: JBCACHE-1193
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1193
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Jason T. Greene
         Assigned To: Jason T. Greene
             Fix For: 2.1.0.GA


The JTA spec says that the thread association of a transaction can only be controlled by TransactionManager. The reason is that a Transaction can be bound to multple threads. In order to be compliant, and work with JBoss JTA, we need to ensure that all operations go through TransactionManager

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 00:58:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Wed, 3 Oct 2007 00:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4696) Arrange community
 documents for 4.2.2.GA
In-Reply-To: <25461197.1189416611004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20967489.1191387483421.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4696?page=comments#action_12380057 ] 
            
Michael Smith commented on JBAS-4696:
-------------------------------------

Status Update:
===========
Step 1: Move JBEAP4.2 forked content (x6 languages) back into upstream Target is 28 Sept and branch as Enterprise.
   |_DONE: Enterprise branch is JBEAP42CP01. Note will only build on linux with the documentation-devel package

Step 2: Create test branch and rearchitect to build with Maven2
   |_DONE: Content in trunk has been moved across and can be built with maven plugin.
      |_Installation_Guide: Ported the 4.2 content
      |_Getting_Started_Guide:  Ported BRANCH_4_0_4  
      |_Clustering_Guide: Ported BRANCH_4_0_4
      |_Server_Configuration_Guide: Ported JBEAP42CP01

*NOTE* The Installation Guide and Getting Started Guide work done for the Enterprise Platform was independant of the previous AS content.
*NOTE* Your team can now pull down the content from trunk and build with the maven plugin.

Step 3: Cleaning Each Guide: Each book needs to be gone through to clean up the output with Maven. 
   |_IN PROCESS: Maven presents the content differently than the previous Ant version. I am budgeting 1 day per book. ETA should be Tuesday, 9th Oct.

> Arrange community documents for 4.2.2.GA
> ----------------------------------------
>
>                 Key: JBAS-4696
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4696
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Michael Smith
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> We *must* produce community documents for AS.
> At the moment, the only 4.2.x documentation that exists is the EAP one.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 03:40:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Wed, 3 Oct 2007 03:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1191) Work with
 contributor to translate JBoss Cache documentation into Spanish
In-Reply-To: <25972580.1191241843360.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1629440.1191397203370.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1191?page=comments#action_12380075 ] 
            
Michael Smith commented on JBCACHE-1191:
----------------------------------------

Thanks, Manik.

We have a process set up for Japan. Let me contact the individual and initiate the same process. 

> Work with contributor to translate JBoss Cache documentation into Spanish
> -------------------------------------------------------------------------
>
>                 Key: JBCACHE-1191
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1191
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Michael Smith
>             Fix For: 2.2.0.GA
>
>
> See email sent in to the jbosscache-dev list:
> http://lists.jboss.org/pipermail/jbosscache-dev/2007-September/002031.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 03:44:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Wed, 3 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1727) CLONE -CMS
 saves pages in
 native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then
 national leters are damaged
In-Reply-To: <31403760.1190983541148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30670835.1191397443288.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1727?page=comments#action_12380076 ] 
            
Mariusz Smykula commented on JBPORTAL-1727:
-------------------------------------------

Patch for issue JBPORTAL-832 is resolving this problem too.

> CLONE -CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1727
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1727
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>         Environment: jboss4.2 (bundled version) and 4.0.5.GA
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged.
> I think that I have to encode the request in UTF-8 ??? 
> ---------------------------------------------
>  create file.html in Ru (in cms admin) with this text
> abc???
> then look at the last record of JBP_CMS_VERSION_BINVAL
> (six bytes in BINVAL_DATA field):
> 61 62 63 e0 e1 e2
> it is cp1251 encoding !!!!
> why this text non unicoded ???
> then when i retrive it i have - 'abc???'
> I think that problem isn't in ContentTypeInterceptor because it succefully
> sets UTF8, because localized resources seems right (in russian).
> may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ???
> -----------------------------------------------------------
> but when I upload file on UTF-8 with russian characters - all correct.
> I think that cms saves the content in one byte encoding (cp1250 or same). 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 03:46:08 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Wed, 3 Oct 2007 03:46:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1727) CLONE -CMS saves
 pages in
 native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then
 national leters are damaged
In-Reply-To: <31403760.1190983541148.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5776654.1191397568192.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1727?page=all ]

Mariusz Smykula updated JBPORTAL-1727:
--------------------------------------

    Affects Version/s: 2.6.2 Final

> CLONE -CMS saves pages in native encoding (ISO-8859-1 or Cp1251) but retrieve it in UTF-8. then national leters are damaged
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1727
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1727
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final, 2.6.2 Final
>         Environment: jboss4.2 (bundled version) and 4.0.5.GA
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> When I input ru-characters in the text area it has been puted into table in native encoding (cp1251) - !!! not UTF-8. But pages are sends in UTF-8, and it damaged.
> I think that I have to encode the request in UTF-8 ??? 
> ---------------------------------------------
>  create file.html in Ru (in cms admin) with this text
> abc???
> then look at the last record of JBP_CMS_VERSION_BINVAL
> (six bytes in BINVAL_DATA field):
> 61 62 63 e0 e1 e2
> it is cp1251 encoding !!!!
> why this text non unicoded ???
> then when i retrive it i have - 'abc???'
> I think that problem isn't in ContentTypeInterceptor because it succefully
> sets UTF8, because localized resources seems right (in russian).
> may be it is need to store text in CLobs insdead blobs ??? (a use Derby) or customize Jackrabbit ???
> -----------------------------------------------------------
> but when I upload file on UTF-8 with russian characters - all correct.
> I think that cms saves the content in one byte encoding (cp1250 or same). 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:29:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
Message-ID: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>

FLUSH: problems with TCP and concurrent startup/shutdowns
---------------------------------------------------------

                 Key: JGRP-603
                 URL: http://jira.jboss.com/jira/browse/JGRP-603
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Vladimir Blagojevic


The attached ZIP file has code that reproduces this.

Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.

To reproduce:
- Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
- This works fine without FLUSH

- With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
- Randomly kill and restart instances




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:29:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 04:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4572) EJB 3 testsuite 100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22297808.1191400143605.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4572?page=all ]

Dimitris Andreadis reopened JBAS-4572:
--------------------------------------

             
Reopening the issue to see how to deal with the failures that appeared after the jbossws-2.0 upgrade:

Both hudsons agree on the results, we have 8 failures:
http://dev45.qa.atl.jboss.com:8585/hudson/view/EJB3/job/ejb3-4.2-testsuite/lastBuild/testReport/
http://wolf.nerdnet.nl:8280/hudson/job/JBoss_EJB3_4.2/93/testReport/

org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(BR-enabled).testStatefulPassivation
org.jboss.ejb3.test.ejbthree832.unit.EntityTestCase.test1
org.jboss.ejb3.test.iiop.unit.IiopRemoteUnitTestCase(jacorb).testTxPropegation
org.jboss.ejb3.test.interceptors2.unit.InterceptorsTestCase.testOverrideOrdering
org.jboss.ejb3.test.jacc.unit.JaccTestCase.testSomeEntity
org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testClientAccessRPC
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef3
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef4 

We need to create subtasks for the individual failures and resolve by the end of the week (9/5th).

> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:31:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2861242.1191400263310.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: jgtest.zip

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <677799.1191400383292.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Fix Version/s: 2.6
         Priority: Critical  (was: Major)

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:43:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-603) FLUSH: problems
 with TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26994108.1191400983371.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12380083 ] 
            
Bela Ban commented on JGRP-603:
-------------------------------

Actually, this works really well with "udp" (I probably tested "tcp" when I thought I was testing "udp")...
But there are definitely issues with "tcp". Most issues are with "tcp-nio", and we should look into those, although tcp-nio has not yet been really well tested (and supported).

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:51:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 04:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11054206.1191401463368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1732:
---------------------------------------------

    Assignee: Boleslaw Dawidowicz

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:51:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 04:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1707) New
 UserModule/RoleModule finders
In-Reply-To: <6276632.1190228243214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20320732.1191401463738.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1707?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1707:
---------------------------------------------

    Assignee: Boleslaw Dawidowicz  (was: Julien Viet)

> New UserModule/RoleModule finders
> ---------------------------------
>
>                 Key: JBPORTAL-1707
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1707
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final
>            Reporter: Andrew Oliver
>         Assigned To: Boleslaw Dawidowicz
>
> While working with clients using the portal API some efficiency issues with regards to finders have become apparent:
> It is presently possible to find users having a role by calling MembershipModule.getUsers(role).  However it is not possible to get a list of users with a set of roles, a list of users who do NOT have a role or set of roles.  (there are ways in both HQL and LDAP to construct each type of query).  I suggest something similar to hibernate conditions.
> MembershipModule.getUsers().addCondition(
>    Condition.and(
>         Condition.not(roleSet), Condition.with(roleSet)
>    )
> )
> this would result in roughly:
> from Users where roles in (:roleSet) and roles not in (:roleSet2)
> and something like 
> (& (|(role=roleName)(role=roleName)  )
>      (&(!role=roleName)(!role=roleName) )
> )
> in LDAP
> the attribute name can be based on the type.  As it stands you have to do something like:
> 		try {			
> 			Role roleApproved = rolemodule.findRoleByName("approved");
> 			Role roleUsers = rolemodule.findRoleByName("User");
> 			//todo create transient wrapper set.
> 		    Set users = membership.getUsers(roleUsers);
> 		    dirtyStinkyHackToGetAroundPortalAPIBugACO(users);
> 		    System.err.println("Total number of users with User Role  : " + users.size() );
> 		    Set temp = new HashSet();
> 		    temp = dirtyStinkyHackToGetAroundPortalAPIBugACO(users); //because the hibernate set doesn't have removeall
> 		    users = temp;
> 			Set usersApproved = membership.getUsers(roleApproved);
> 			System.err.println("number of users with approved role: "+usersApproved.size());
> 			users.removeAll(usersApproved);
> 			System.err.println("Total number of users with User Role and NO approved role : " + users.size() );
> 			Map profiles = profiles(users);
> 			response.setRenderParameter("op", "new");
> 			request.getPortletSession().setAttribute("users", users);
> 			request.getPortletSession().setAttribute("profiles", profiles);
> 		} catch (IdentityException e) {
> 			//todo type this and catch it up higher to make a 
> 			//smarter error message
> 			throw new RuntimeException(e);
> 		}
> 	private Map profiles(Set users) throws IdentityException {
> 		Iterator i = users.iterator();
> 		Map retval = new HashMap();
> 		while(i.hasNext()) {
> 			User user = (User) i.next();
> 			retval.put(user, profileModule.getProperties(user));
> 		}
> 		return retval;
> 	}
> 	
> 	private Set dirtyStinkyHackToGetAroundPortalAPIBugACO(Set users) {
> 		Iterator i = users.iterator();
> 		Set retval = new HashSet();
> 		while(i.hasNext()) {
> 			User u = (User)i.next();
> 			u.getUserName();
> 			retval.add(u);
> 		}
> 		return retval;
> 	}
> Just to get the list of users who DONT have the "approved" role.  For our immediate needs:
> UserModule.getUsersWithout(role) would work...until next time.
> -Andy

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 04:55:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 04:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31461216.1191401703958.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380084 ] 
            
Boleslaw Dawidowicz commented on JBPORTAL-1732:
-----------------------------------------------

what is your LDAP server and identity configuration? I wonder why this goes thru HibernateUserModuleImpl.

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:00:14 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:00:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32423617.1191402014565.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380085 ] 
            
Thomas Heute commented on JBPORTAL-1732:
----------------------------------------

It happens with plain DB actually.
It might be a core-identity bug though, i just quickly tried.



> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:02:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 3 Oct 2007 05:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-603) FLUSH: problems
 with TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18466159.1191402123582.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12380086 ] 
            
Bela Ban commented on JGRP-603:
-------------------------------

Okay, tcp and tcp-nio now work too if the following changes are made:
- Remove UNICAST from the tcp and tcp-nio stacks
- Set suspect_on_send_failure="true" in TCP and TCP_NIO

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:04:03 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 05:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1245) class cast
	exception
Message-ID: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>

class cast exception
--------------------

                 Key: JBRULES-1245
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.2
         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
            Reporter: ekkehard gentz
         Assigned To: Mark Proctor
            Priority: Critical
             Fix For: 4.0.2


Package.readExternalPackage gives me this exception

java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
	at org.drools.rule.Package.readExternal(Package.java:180)

----
running 4.0.1 it works well

ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:11:21 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 05:11:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13006245.1191402681342.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380087 ] 
            
Boleslaw Dawidowicz commented on JBPORTAL-1732:
-----------------------------------------------

I'm asking about LDAP because I know that in MSAD you authenticate providing DOMAINNAME\USERNAME which doesn't mean that user entry looks like that.

Thomas. So you are saying that portal DB configuration doesn't handle properly user names that contain backslashes?

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:22:14 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:22:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17808004.1191403334713.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380091 ] 
            
Thomas Heute commented on JBPORTAL-1732:
----------------------------------------

Actually the problem is in the new UI portlets.
The workaround is to keep using the former User and Role portlets till 2.6.3  (I just tried to make sure)

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:24:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19394701.1191403444343.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=all ]

Thomas Heute updated JBPORTAL-1732:
-----------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:28:04 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 05:28:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
Message-ID: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>

HomeHandleImplIIOP not using the HandleDelegate
-----------------------------------------------

                 Key: JBAS-4801
                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: IIOP service
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Adrian Brock
         Assigned To: Adrian Brock
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA


The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.

This is because the read/writeObject methods are public when they should be private to be invoked by
Serialization.

Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
currently writing the ior), we need a system property such that people can revert to the previous
serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 05:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1053) State changes in
 @PrePassivate don't get replicated if passivate before
 replication is disabled
Message-ID: <24689323.1191403685280.JavaMail.jira@cloud.prod.atl2.jboss.com>

State changes in @PrePassivate don't get replicated if passivate before replication is disabled
-----------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1053
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1053
             Project: EJB 3.0
          Issue Type: Bug
          Components: Clustering
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


Passivation doesn't trigger replication, so a bean might get passivated on 1 node and not on another. If the bean provider does state changes in pre-passivate these will not be visible on the other node.

By default replication does trigger passivation, so a bean first gets passivated and then replicated. Thus the problem only occurs if passivate before replication is explicitly disabled.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:28:05 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 05:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33170883.1191403685599.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

Adrian Brock updated JBAS-4801:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120219

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:32:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 3 Oct 2007 05:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24257466.1191403924493.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380095 ] 
            
Thomas Heute commented on JBPORTAL-1732:
----------------------------------------

I meant "in the new Identity portlets"

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:34:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 05:34:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1054) Buddy
 replication can lead to a memory leak
Message-ID: <23615598.1191404044129.JavaMail.jira@cloud.prod.atl2.jboss.com>

Buddy replication can lead to a memory leak
-------------------------------------------

                 Key: EJBTHREE-1054
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


JBC passivation code is broken with buddy replication enabled.
Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:34:05 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 05:34:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28627084.1191404045377.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=comments#action_12380097 ] 
            
ekkehard gentz commented on JBRULES-1245:
-----------------------------------------

btw: this was the scenario:
....
ois = new ObjectInputStream(fis);
.....
final Package p = new Package();
p.readExternal(ois);
....

running 4.0.1 there was no problem

ekke

> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 05:34:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 05:34:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1054) Buddy
 replication can lead to a memory leak
In-Reply-To: <23615598.1191404044129.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5674459.1191404046103.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1054?page=all ]

Carlo de Wolf updated EJBTHREE-1054:
------------------------------------

              Component/s: Clustering
    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120207

> Buddy replication can lead to a memory leak
> -------------------------------------------
>
>                 Key: EJBTHREE-1054
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>
> JBC passivation code is broken with buddy replication enabled.
> Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:15:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 06:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
Message-ID: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>

WebServiceContext is not injected before post construct is called
-----------------------------------------------------------------

                 Key: EJBTHREE-1055
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf


JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:17:15 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 06:17:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11573518.1191406635237.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4801?page=comments#action_12380111 ] 
            
Adrian Brock commented on JBAS-4801:
------------------------------------

This has been done.

It will now serialize via the delegate.

There is a system property which can be set
-Dorg.jboss.proxy.ejb.old.homehandle.serialization=true
if this change causes problems.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:19:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 3 Oct 2007 06:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26070396.1191406743369.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

Adrian Brock reassigned JBAS-4801:
----------------------------------

    Assignee: William DeCoste  (was: Adrian Brock)

Passed to Bill to confirm this fixes the problem he was seeing.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:23:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3331194.1191406983482.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4801?page=comments#action_12380113 ] 
            
Dimitris Andreadis commented on JBAS-4801:
------------------------------------------

Adrian, thanks a bunch for the quick response.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 06:32:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 06:32:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4572) EJB 3 testsuite
	100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30451213.1191407522963.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4572?page=comments#action_12380116 ] 
            
Dimitris Andreadis commented on JBAS-4572:
------------------------------------------

I created "depends" links to the EJB3 issue that *must* be solved, and "related" links to the known failures, according to Carlo's input:


> > org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(BR-enabled).testStatefulPassivation 
EJBTHREE-1053 + EJBTHREE-1054 (to some extend)

> > org.jboss.ejb3.test.ejbthree832.unit.EntityTestCase.test1
EJBTHREE-832: known issue

> > org.jboss.ejb3.test.iiop.unit.IiopRemoteUnitTestCase(jacorb).testTxPropegation
EJBTHREE-892: known issue

> > org.jboss.ejb3.test.interceptors2.unit.InterceptorsTestCase.testOverrideOrdering
EJBTHREE-896: known issue

> > org.jboss.ejb3.test.jacc.unit.JaccTestCase.testSomeEntity
EJBTHREE-894: known issue

> > org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testClientAccessRPC
EJBTHREE-757: is sessionContext.getMessageContext supposed to work? It's
for JAX-RPC which is obsolete, right?
Rephrase: do we do JAX-RPC with EJB 3?

> > org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef3
> > org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef4
EJBTHREE-899: web service ref injection via dd

I've added a test for the post construct issue: EJBTHREE-1055.


> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 07:32:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 3 Oct 2007 07:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1246) Package deploy to
 deploy source drl as option (alternative to .pkg)
Message-ID: <18576826.1191411123242.JavaMail.jira@cloud.prod.atl2.jboss.com>

Package deploy to deploy source drl as option (alternative to .pkg)
-------------------------------------------------------------------

                 Key: JBRULES-1246
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1246
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE


Would be nice to be able to exppose .drl the way we do .pkg now - so that means some systems can just build their own rules (will require changes to the agent). Could solve some hassles with version incompatabilities. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 08:16:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 3 Oct 2007 08:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1235) Multiple
 Criteria break BRMS rule editor
In-Reply-To: <24987902.1191139841173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16254070.1191413763542.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1235?page=comments#action_12380130 ] 
            
Michael Neale commented on JBRULES-1235:
----------------------------------------

Thanks ben. Perhaps create a new fact class with the same private variables. My guess is that there is some data type that is tripping up the code that introspects and builds a model for the GUI. 

PS, I was thinking how awesome your contributions were about a year ago - they are still alive and kicking today ! 

> Multiple Criteria break BRMS rule editor
> ----------------------------------------
>
>                 Key: JBRULES-1235
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1235
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Ben Truitt
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>         Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg, screenshot3.jpeg
>
>
> In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
> Two ways to trigger:
> 1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
> 2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
> I'll attach screenshots, which should help explain.
> Sorry if this is a dupe - I looked, but didn't find anything like 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

        


From jira-events at lists.jboss.org  Wed Oct  3 08:24:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 3 Oct 2007 08:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <572936.1191414243305.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=comments#action_12380131 ] 
            
Mark Proctor commented on JBRULES-1245:
---------------------------------------

there where binary changes between 4.0.0, 4.0.1 and 4.0.2, you'll have to re-create your packages again. The BRMs is able to re-publish all binary packages, I believe.

> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 09:55:03 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 09:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20141226.1191419703543.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=comments#action_12380158 ] 
            
ekkehard gentz commented on JBRULES-1245:
-----------------------------------------

thanks for the info, Mark,

now my Unit-tests are green again :-)

I wasn't aware of those possible changes. good to know, because I want to store my streams in a database.
but its no problem - I'll add a step to re-create all streams after upgrading to new versions and I have to verify,
that all users have to use the same versions.

thanks for soon help

ekke


> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 09:57:23 2007
From: jira-events at lists.jboss.org (ekkehard gentz (JIRA))
Date: Wed, 3 Oct 2007 09:57:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1245) class cast
	exception
In-Reply-To: <16263435.1191402243337.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2524693.1191419843103.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1245?page=all ]

ekkehard gentz closed JBRULES-1245.
-----------------------------------

    Resolution: Done

after recreating the package streams with 4.0.2 Snapshot I was able to re-import them without an exception.

> class cast exception
> --------------------
>
>                 Key: JBRULES-1245
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1245
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>         Environment: build832-rev15510-20071002-0845  4.0.2 snapshot, eclipse 3.3, osx 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.0.2
>
>
> Package.readExternalPackage gives me this exception
> java.lang.ClassCastException: java.util.Collections$EmptyMap cannot be cast to java.util.List
> 	at org.drools.rule.Package.readExternal(Package.java:180)
> ----
> running 4.0.1 it works well
> ekke

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 11:22:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 11:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4572) EJB 3 testsuite
	100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10240746.1191424923552.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4572?page=comments#action_12380199 ] 
            
Dimitris Andreadis commented on JBAS-4572:
------------------------------------------

The current list of failures after the know failures were excluded:
http://dev45.qa.atl.jboss.com:8585/hudson/view/EJB3/job/ejb3-4.2-testsuite/lastBuild/testReport/

org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testService2
org.jboss.ejb3.test.jaxws.unit.ContextEJBTestCase.testClientAccessRPC
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef3
org.jboss.ejb3.test.webservices.unit.JSR181TestCase.testWebServiceRef4 


> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 11:26:16 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 3 Oct 2007 11:26:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28245086.1191425176168.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=comments#action_12380202 ] 
            
Andrew Rubinger commented on EJBTHREE-785:
------------------------------------------

All fixes and tests committed to trunk.

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: Branch_4_2, HEAD
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 11:49:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 3 Oct 2007 11:49:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1054) Buddy
 replication can lead to a memory leak
In-Reply-To: <23615598.1191404044129.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3257588.1191426545864.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1054?page=all ]

Carlo de Wolf updated EJBTHREE-1054:
------------------------------------

    Workaround Description: To 'force' eviction of a bean make sure there is an explicit removal timeout set.
                Workaround: [Workaround Exists]

> Buddy replication can lead to a memory leak
> -------------------------------------------
>
>                 Key: EJBTHREE-1054
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1054
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>
> JBC passivation code is broken with buddy replication enabled.
> Whenever a bean is replicated it's copied to a backup region. This backup region is never evicted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 12:52:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 3 Oct 2007 12:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1180172.1191430323695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=all ]

William DeCoste reassigned EJBTHREE-899:
----------------------------------------

    Assignee: William DeCoste

> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 13:23:03 2007
From: jira-events at lists.jboss.org (Luc Boudreau (JIRA))
Date: Wed, 3 Oct 2007 13:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1732) Cannot change
 roles of user names containing a backslash character
In-Reply-To: <30465756.1191337383532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25129985.1191432183801.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1732?page=comments#action_12380248 ] 
            
Luc Boudreau commented on JBPORTAL-1732:
----------------------------------------

Doesn't matter which LDAP I'm using, the user record is properly synchrinized with the database.

Just for the info, we are not using LDAP directly, we are using a custom CAS server which sends back the roles data.

> Cannot change roles of user names containing a backslash character
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1732
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1732
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>
> In our LDAP directory, the usernames are prefixed with the domain name followed by a backslash followed by the username.
> ie. DOMAIN\username
> I get the following error while changing the roles of such a user. Clearly, the backslash is interpreted as-is ans creates an escaped character.
> 2007-10-02 10:59:47,735 ERROR [STDERR] org.jboss.portal.identity.NoSuchUserException: No such user No such user SIoudrel
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.portal.identity.db.HibernateUserModuleImpl.findUserByUserName(HibernateUserModuleImpl.java:97)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor513.invoke(Unknown Source)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2007-10-02 10:59:47,736 ERROR [STDERR]  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at $Proxy249.findUserByUserName(UnknownSource)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.common.IdentityUserBean.findUserByUserName(IdentityUserBean.java:140)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at org.jboss.portal.core.identity.ui.actions.AssignRoleAction.assignRoles(AssignRoleAction.java:111)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-10-02 10:59:47,737 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 14:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 14:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30752375.1191437643363.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380264 ] 
            
Dimitris Andreadis commented on JBCOMMON-35:
--------------------------------------------

Are you committing soon? I want to release 2.2.2.GA.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 14:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 14:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <258429.1191437643521.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380265 ] 
            
Dimitris Andreadis commented on JBCOMMON-35:
--------------------------------------------

Are you committing soon? I want to release 2.2.2.GA.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 15:02:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 15:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28413435.1191438123287.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=all ]

Dimitris Andreadis updated JBCOMMON-35:
---------------------------------------

    Comment: was deleted

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 15:04:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 3 Oct 2007 15:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6926585.1191438243755.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=comments#action_12380266 ] 
            
Dimitris Andreadis commented on JBCOMMON-36:
--------------------------------------------

Are you committing soon? I want to release 2.2.2.GA.

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 15:30:18 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 3 Oct 2007 15:30:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4802) FirstAvailable
 target should not be transient
Message-ID: <32958772.1191439818126.JavaMail.jira@cloud.prod.atl2.jboss.com>

FirstAvailable target should not be transient
---------------------------------------------

                 Key: JBAS-4802
                 URL: http://jira.jboss.com/jira/browse/JBAS-4802
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor


If a bean proxy that already has a target established gets serialized (e.g. passed through a remote call), the sticky target is lost on the other end.  This can lead to invocations against the same target bean on multiple servers.

I don't see any reason for FirstAvailable.electedTarget to be transient.

Problem here is changing this changes the serialized form of the class, breaking interoperability.  Class also does not implement Externalizable.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 17:53:23 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 3 Oct 2007 17:53:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10325955.1191448403961.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Brian Stansberry updated JBAS-4766:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120331

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 17:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Wed, 3 Oct 2007 17:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1096) Document
 bisocket and
 remove references from the old Callback Manager on the documentation
Message-ID: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>

Document bisocket and remove references from the old Callback Manager on the documentation
------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1096
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic


Documentation still refer the old callback mechanism:

http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback


We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 17:55:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Wed, 3 Oct 2007 17:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1096) Document
 bisocket and
 remove references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15389998.1191448503520.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Clebert Suconic updated JBMESSAGING-1096:
-----------------------------------------

          Component/s: Documentation and Training
        Fix Version/s: 1.4.0.SP1
    Affects Version/s: 1.4.0.GA

> Document bisocket and remove references from the old Callback Manager on the documentation
> ------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:14:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20946572.1191453243345.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal updated JBREM-811:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)
                       (was: 2.2.2.SP1)

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:19:03 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Wed, 3 Oct 2007 19:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1640) provide OpenSSO
	integration
In-Reply-To: <21988026.1187645118595.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25356071.1191453543301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1640?page=all ]

Boleslaw Dawidowicz resolved JBPORTAL-1640.
-------------------------------------------

    Fix Version/s: 2.6.2 Final
                       (was: 2.8 Final)
                       (was: 2.6.3 Final)
       Resolution: Done

Setup described here: http://jbossportal.blogspot.com/2007/10/jboss-portal-with-opensso-and-opends.html

> provide OpenSSO integration
> ---------------------------
>
>                 Key: JBPORTAL-1640
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1640
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.6.2 Final
>
>
> Provide integration with OpenSSO using tomcat valve mechanism

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:27:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 3 Oct 2007 19:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1241) Dynamic rules
 should be able to
 lock for a series of updates and fireAllRules should be optional
In-Reply-To: <31771190.1191294101057.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16451161.1191454023237.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1241?page=all ]

Mark Proctor closed JBRULES-1241.
---------------------------------

    Resolution: Done

> Dynamic rules should be able to lock for a series of updates and fireAllRules should be optional
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1241
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1241
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> add lock() and unlock() to RuleBase and setup a rulebase listener to progated the fireAllRules calls.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:31:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19973127.1191454263417.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal updated JBREM-811:
----------------------------

        Fix Version/s: 2.2.2.SP2
                       2.2.2.GA_CP01
    Affects Version/s: 2.4.0.Beta1 (Pinto)

This fix should be available for EAP 4.2.0.GA_CP02, AS 4.2.3 (?) and AS 5.0.0.Beta3.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:31:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25473422.1191454268653.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal reopened JBREM-750:
-----------------------------

             
This issue needs to be fixed in a CP release for EAP 4.2.0.GA_CP02.

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:33:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26523020.1191454383320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal updated JBREM-750:
----------------------------

    Fix Version/s: 2.2.2.GA_CP01

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1, 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:33:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-814) CLONE -Logger in
 HTTPClientInvoker should be static.
Message-ID: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>

CLONE -Logger in HTTPClientInvoker should be static.
----------------------------------------------------

                 Key: JBREM-814
                 URL: http://jira.jboss.com/jira/browse/JBREM-814
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.2.2.SP1, 2.2.2.GA_CP01


When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.

The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:35:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4943019.1191454503330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal updated JBREM-750:
----------------------------

    Fix Version/s:     (was: 2.2.2.GA_CP01)

Instead of reopening this issue for 2.2.2.GA_CP01, cloned it.

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 19:41:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 19:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-814) CLONE -Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16089617.1191454863246.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-814?page=all ]

Ron Sigal updated JBREM-814:
----------------------------

    Fix Version/s:     (was: 2.2.2.SP1)

> CLONE -Logger in HTTPClientInvoker should be static.
> ----------------------------------------------------
>
>                 Key: JBREM-814
>                 URL: http://jira.jboss.com/jira/browse/JBREM-814
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-750) Logger in
 HTTPClientInvoker should be static.
In-Reply-To: <13768399.1180747148427.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3319205.1191456783317.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-750?page=all ]

Ron Sigal closed JBREM-750.
---------------------------

    Resolution: Done

> Logger in HTTPClientInvoker should be static.
> ---------------------------------------------
>
>                 Key: JBREM-750
>                 URL: http://jira.jboss.com/jira/browse/JBREM-750
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP1
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-814) Logger in
 HTTPClientInvoker should be static (CLONE of JBREM-750)
In-Reply-To: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22751817.1191456783450.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-814?page=all ]

Ron Sigal updated JBREM-814:
----------------------------

    Summary: Logger in HTTPClientInvoker should be static (CLONE of JBREM-750)  (was: CLONE -Logger in HTTPClientInvoker should be static.)

> Logger in HTTPClientInvoker should be static (CLONE of JBREM-750)
> -----------------------------------------------------------------
>
>                 Key: JBREM-814
>                 URL: http://jira.jboss.com/jira/browse/JBREM-814
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:26:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 3 Oct 2007 20:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24651634.1191457563739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Andrew Rubinger resolved EJBTHREE-785.
--------------------------------------

    Resolution: Done

Fixes Merged and Verified in Branch 4.2

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: Branch_4_2, HEAD
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:32:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
Message-ID: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>

allow user to set content-type for http responses (CLONE of JBREM-653)
----------------------------------------------------------------------

                 Key: JBREM-815
                 URL: http://jira.jboss.com/jira/browse/JBREM-815
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: transport
    Affects Versions: 2.2.2.GA
            Reporter: Tom  Elrod
         Assigned To: Ron Sigal
             Fix For: 2.2.2.SP1


Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.

Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:34:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
In-Reply-To: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24215336.1191458043316.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-815?page=comments#action_12380334 ] 
            
Ron Sigal commented on JBREM-815:
---------------------------------

Comment by Tom Fennelly:

This issue is really a bug as far as JBossESB is concerned. JBossESB supports a number of transports/connectors via JBossRemoting. A number of other features also rely on JBossRemoting e.g. SOAP/HTTP. Therefore, in the case of webservices support, not being able to set the Content-Type on http responses effectively means we can't guarantee interoperability since many clients will refuse to process responses that don't have indicate an appropriate Content-Type. 

> allow user to set content-type for http responses (CLONE of JBREM-653)
> ----------------------------------------------------------------------
>
>                 Key: JBREM-815
>                 URL: http://jira.jboss.com/jira/browse/JBREM-815
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
> Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:34:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
In-Reply-To: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17046746.1191458043473.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-815?page=all ]

Ron Sigal updated JBREM-815:
----------------------------

    Fix Version/s: 2.2.2.GA_CP01
                       (was: 2.2.2.SP1)

> allow user to set content-type for http responses (CLONE of JBREM-653)
> ----------------------------------------------------------------------
>
>                 Key: JBREM-815
>                 URL: http://jira.jboss.com/jira/browse/JBREM-815
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
> Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:36:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25820431.1191458163263.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-813?page=all ]

Ron Sigal updated JBREM-813:
----------------------------

    Fix Version/s: 2.2.2.SP2
                   2.2.2.GA_CP01

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct  3 20:36:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 3 Oct 2007 20:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24702814.1191458163379.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12380335 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Arose in support case https://na1.salesforce.com/50030000003iBdA.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 00:29:24 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Thu, 4 Oct 2007 00:29:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9545552.1191472164778.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380345 ] 
            
Vicky Kak commented on JBCOMMON-35:
-----------------------------------

I am planning to fix it by this weekend , how soon do you want it to be done .

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 00:31:03 2007
From: jira-events at lists.jboss.org (Vicky Kak (JIRA))
Date: Thu, 4 Oct 2007 00:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5111485.1191472263230.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=comments#action_12380346 ] 
            
Vicky Kak commented on JBCOMMON-36:
-----------------------------------

I am planning to fix it by this weekend , how soon do you want it to be done .

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:03:26 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 4 Oct 2007 03:03:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4696) Arrange community
 documents for 4.2.2.GA
In-Reply-To: <25461197.1189416611004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30304185.1191481406590.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4696?page=comments#action_12380348 ] 
            
Michael Smith commented on JBAS-4696:
-------------------------------------

Mark,

Steps 1-3 Complete. Porting and retrofit to build with maven is complete.
========================================================

Next Steps:
=========
Step 4: Mark, I need you to pull down trunk, build with maven and do a cursory glance to make sure I retrofitted the right content. (Mark)

Step 5: Build a stage for the HTML/PDF docs for tech review (Mark)

Step 6: Once you give me a green light on Step 4, Samson and I will begin the re-write. Our process will be simple: once a chapter is ready for tech-review, we will open a Jira declaring that chapter X is ready for techreview and inform the project mailing list with a link to the chapter on the stage. (Mike & Samson)

> Arrange community documents for 4.2.2.GA
> ----------------------------------------
>
>                 Key: JBAS-4696
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4696
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Michael Smith
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> We *must* produce community documents for AS.
> At the moment, the only 4.2.x documentation that exists is the EAP one.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:08:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 03:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-37) Add jboss-common
 1.2.1.GA to the JBoss maven repository
Message-ID: <28010800.1191481683727.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add jboss-common 1.2.1.GA to the JBoss maven repository
-------------------------------------------------------

                 Key: JBCOMMON-37
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
             Project: JBoss Common
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 1.2.1.GA
         Environment: n/a
            Reporter: Anders Hammar
         Assigned To: Dimitris Andreadis


I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. I'm For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.



-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:15:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 03:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-37) Add jboss-common
 1.2.1.GA to the JBoss maven repository
In-Reply-To: <28010800.1191481683727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22416175.1191482103412.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-37?page=all ]

Anders Hammar updated JBCOMMON-37:
----------------------------------

    Description: 
I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.



  was:
I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. I'm For the transitive dependency to work, the jboss-common artifact is needed.
Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.




> Add jboss-common 1.2.1.GA to the JBoss maven repository
> -------------------------------------------------------
>
>                 Key: JBCOMMON-37
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
>             Project: JBoss Common
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.1.GA
>         Environment: n/a
>            Reporter: Anders Hammar
>         Assigned To: Dimitris Andreadis
>
> I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. For the transitive dependency to work, the jboss-common artifact is needed.
> Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:30:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14046273.1191483003405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf updated EJBTHREE-900:
-----------------------------------

    Fix Version/s: AS 4.2.2.GA
                       (was: Branch_4_2)

> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:32:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1684086.1191483123395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf resolved EJBTHREE-900.
------------------------------------

    Resolution: Done

> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:44:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-124)
 @PersistenceContext(EXTENDED) should follow new Spec defined rules
Message-ID: <27213328.1191483843352.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ]

Carlo de Wolf updated EJBTHREE-124:
-----------------------------------

    Fix Version/s:     (was: AS 4.2.2.GA)

> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-124
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:44:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-124)
 @PersistenceContext(EXTENDED) should follow new Spec defined rules
Message-ID: <31191240.1191483843496.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ]

Carlo de Wolf reassigned EJBTHREE-124:
--------------------------------------

    Assignee: Carlo de Wolf

> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-124
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:44:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-124)
 @PersistenceContext(EXTENDED) should follow new Spec defined rules
Message-ID: <26247021.1191483843707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ]

Carlo de Wolf closed EJBTHREE-124.
----------------------------------

    Resolution: Deferred

> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
>                 Key: EJBTHREE-124
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 03:58:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 03:58:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-757)
 getMessageContext Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5253252.1191484685544.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=comments#action_12380355 ] 
            
Thomas Diesler commented on EJBTHREE-757:
-----------------------------------------

AFAIK

EJB3 only supports JAX-WS
EJB21 only supports JAX-RPC

IMHO it is illegal for an EJB3 endpoint to obtain a JAX-RPC MessageContext via the SessionContext. 
The way to obtain a JAX-WS MessageContext is via injection.


> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:00:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 04:00:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8428744.1191484804779.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=comments#action_12380357 ] 
            
Thomas Diesler commented on EJBTHREE-899:
-----------------------------------------

This should be supported

> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:10:34 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 04:10:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext
 Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5015458.1191485434574.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf updated EJBTHREE-757:
-----------------------------------

    Fix Version/s: AS 4.2.2.GA
                       (was: Branch_4_2)

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:30:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 04:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-757)
 getMessageContext Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4640106.1191486603426.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf resolved EJBTHREE-757.
------------------------------------

    Resolution: Rejected

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:32:14 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Thu, 4 Oct 2007 04:32:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30815270.1191486734259.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

David Roberts updated GPD-169:
------------------------------

        Summary: GPD Diagram node and text positioning not saving.  (was: Transition text position not saving)
    Description: 
Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:

When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.

Transition text also has a problem:
All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

  was:
Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:

All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 

I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 


I thought it was just the transition text positioning that was not saving correctly. I found that node positions are also not saving correctly.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 04:57:03 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Thu, 4 Oct 2007 04:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25394616.1191488223905.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

David Roberts updated GPD-169:
------------------------------

    Attachment: Before and After.jpg

Here are two images of a process definition. The first is when I line up my nodes etc into a logical order, and save it. The second is after I have closed the process definition, and re-opened it.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:01:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6962612.1191488463331.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=comments#action_12380367 ] 
            
Thomas Diesler commented on EJBTHREE-1055:
------------------------------------------

Yes, this should be supported as it is in AS5.0

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 05:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30096564.1191489003334.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf reassigned EJBTHREE-1055:
---------------------------------------

    Assignee: Thomas Diesler

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Thomas Diesler
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:15:09 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:15:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6671284.1191489309863.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=comments#action_12380371 ] 
            
Thomas Diesler commented on EJBTHREE-1055:
------------------------------------------

InvocationHandlerEJB3 is the integration point. It lives in the AS code base and should probably be modified to handle context injection properly.

         MethodInfo info = container.getMethodInfo(method);
         EJBContainerInvocation<StatelessContainer, StatelessBeanContext> ejb3Inv = new EJBContainerInvocation<StatelessContainer, StatelessBeanContext>(info);
         ejb3Inv.setAdvisor(container);
         ejb3Inv.setArguments(args);
         ejb3Inv.setContextCallback(new CallbackImpl(epInv));



> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Thomas Diesler
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:20:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 05:20:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-757)
 getMessageContext Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30167083.1191489604531.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf reopened EJBTHREE-757:
------------------------------------

             
Cheered too soon.
EJB 3 3.5.2 defines the use of JAX-RPC clients.

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:20:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:20:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19697468.1191489605604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Thomas Diesler reassigned EJBTHREE-1055:
----------------------------------------

    Assignee: Carlo de Wolf  (was: Thomas Diesler)

Carlo, please call me to discuss this.


> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:26:12 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Thu, 4 Oct 2007 05:26:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17207412.1191489972984.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12380379 ] 
            
David Roberts commented on GPD-169:
-----------------------------------

I said above that "Each time I open my process definition", the nodes are re-ordered. My mistake, it's not each time for the nodes, it's each time for the text positioning. The node positioning problem is intermittent, and has only happened a few times. However, the text position is every time I re-open.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 05:26:13 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 05:26:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <6054286.1191489973144.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380380 ] 
            
Thomas Diesler commented on JBREM-305:
--------------------------------------

Yes, but clients want to use the JAX-WS API to send a web service request. The transport (i.e. JMS) should be a configurable aspect and should not require usage of a different API.

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 06:11:22 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 06:11:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-938) Expired messages
 are being delivered
In-Reply-To: <22096346.1175683086452.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2357423.1191492682052.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-938?page=all ]

Carlo de Wolf resolved EJBTHREE-938.
------------------------------------

    Resolution: Won't Fix

JBoss MQ is no longer being supported.

> Expired messages are being delivered
> ------------------------------------
>
>                 Key: EJBTHREE-938
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-938
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: mdb unit test
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** ExpirationTestMDB onMessage 1 in org.jboss.ejb3.test.mdb.ExpirationTestMDB at 27977433
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** now = 1175680736566
> 2007-04-04 11:58:56,567 INFO  [STDOUT] *** message = SpyTextMessage {
> Header {
>    jmsDestination  : QUEUE.expirationtest
>    jmsDeliveryMode : 1
>    jmsExpiration   : 1175680735655
>    jmsPriority     : 4
>    jmsMessageID    : ID:436-11756807355552
>    jmsTimeStamp    : 1175680735555
>    jmsCorrelationID: null
>    jmsReplyTo      : null
>    jmsType         : null
>    jmsRedelivered  : false
>    jmsProperties   : {foo=bar, currentTest=testExpiration, null=null}
>    jmsPropReadWrite: false
>    msgReadOnly     : true
>    producerClientId: ID:436
> }
> Body {
>    text            :expire on server
> }

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 06:52:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 4 Oct 2007 06:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCOMMON-37) Add jboss-common
 1.2.1.GA to the JBoss maven repository
In-Reply-To: <28010800.1191481683727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31190739.1191495123805.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-37?page=all ]

Dimitris Andreadis reassigned JBCOMMON-37:
------------------------------------------

    Assignee: Paul Gier  (was: Dimitris Andreadis)

JBoss common 1.2.x is not mavenized itself.

The sources for 1.2.1.GA can be found here:
https://svn.jboss.org/repos/common/common-old/tags/JBossCommon_1_2_1_GA/

The binaries are uploaded in this location:
https://svn.jboss.org/repos/repository.jboss.org/jboss/common/1.2.1.GA/

If Paul can generate the maven2 artifacts to put there:
https://svn.jboss.org/repos/repository.jboss.org/maven2/jboss/jboss-common/

that would be great.


> Add jboss-common 1.2.1.GA to the JBoss maven repository
> -------------------------------------------------------
>
>                 Key: JBCOMMON-37
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-37
>             Project: JBoss Common
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.1.GA
>         Environment: n/a
>            Reporter: Anders Hammar
>         Assigned To: Paul Gier
>
> I'd like the jboss-common artifact for version 1.2.1.GA to be added to the JBoss maven repository. This artifact is used by jboss-aop v1.5.6. For the transitive dependency to work, the jboss-common artifact is needed.
> Today, several jboss-common artifacts exist in the repository (http://repository.jboss.org/maven2/jboss/jboss-common/), but v1.2.1.GA is missing.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:06:16 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 4 Oct 2007 07:06:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27684437.1191495977006.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=comments#action_12380421 ] 
            
Dimitris Andreadis commented on JBCOMMON-35:
--------------------------------------------

It doesn't look a fix is need when running under jdk5.

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:17:26 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 4 Oct 2007 07:17:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8674517.1191496646953.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=comments#action_12380424 ] 
            
Dimitris Andreadis commented on JBCOMMON-36:
--------------------------------------------

Before doing any commit, has anyone reviewed what you propose?

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.2.2.GA, 2.0.6.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:34:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 07:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9845984.1191497643222.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf updated EJBTHREE-1055:
------------------------------------

        Fix Version/s: AS 4.2.2.GA
    Affects Version/s: AS 4.2.1.GA

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:38:10 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Thu, 4 Oct 2007 07:38:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1247) Bug during rule
	parsing
Message-ID: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>

Bug during rule parsing
-----------------------

                 Key: JBRULES-1247
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
             Project: JBoss Drools
          Issue Type: Bug
            Reporter: Markus Wolf
         Assigned To: Mark Proctor
            Priority: Blocker


org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:38:10 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Thu, 4 Oct 2007 07:38:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4379610.1191497890777.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Markus Wolf updated JBRULES-1247:
---------------------------------

    Affects Version/s: 4.0.1
             Priority: Major  (was: Blocker)

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:53:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Thu, 4 Oct 2007 07:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1248)
 <literal-restriction> requires
 an 'value' attribute, but it can't be null
Message-ID: <83704.1191498783244.JavaMail.jira@cloud.prod.atl2.jboss.com>

<literal-restriction> requires an 'value' attribute, but it can't be null 
--------------------------------------------------------------------------

                 Key: JBRULES-1248
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1248
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.1,  4.0.0.GA,  4.0.0.MR3, 4.0.0.MR2
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer
             Fix For: 4.0.2


<literal-restriction> requires an 'value' attribute, but the parser fails when we use a null value. 

The parser should be able to parse this xml rule. 

<?xml version="1.0"?>
<rule name="Check_NotNullof_rfqId">
  <rule-attribute name="agenda-group" value="Check"/>
  <lhs>
    <pattern object-type="RFQBean">
      <or-constraint-connective>
        <field-constraint field-name="m_rfqId">
          <literal-restriction evaluator="==" value="null"/>
        </field-constraint>
        <field-constraint field-name="m_rfqId">
          <literal-restriction evaluator="==" value=""/>
        </field-constraint>
      </or-constraint-connective>
    </pattern>
  </lhs>
  <rhs> response.setStatus("For RFQ Bean: The value of m_rfqId is null.");

System.out.println(response.getStatus());

</rhs>
</rule>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 07:59:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Thu, 4 Oct 2007 07:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1248)
 <literal-restriction>
 requires an 'value' attribute, but it can't be null
In-Reply-To: <83704.1191498783244.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29542350.1191499143239.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1248?page=all ]

Fernando Meyer resolved JBRULES-1248.
-------------------------------------

    Resolution: Done

> <literal-restriction> requires an 'value' attribute, but it can't be null 
> --------------------------------------------------------------------------
>
>                 Key: JBRULES-1248
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1248
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.0.MR2,  4.0.0.MR3,  4.0.0.GA, 4.0.1
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> <literal-restriction> requires an 'value' attribute, but the parser fails when we use a null value. 
> The parser should be able to parse this xml rule. 
> <?xml version="1.0"?>
> <rule name="Check_NotNullof_rfqId">
>   <rule-attribute name="agenda-group" value="Check"/>
>   <lhs>
>     <pattern object-type="RFQBean">
>       <or-constraint-connective>
>         <field-constraint field-name="m_rfqId">
>           <literal-restriction evaluator="==" value="null"/>
>         </field-constraint>
>         <field-constraint field-name="m_rfqId">
>           <literal-restriction evaluator="==" value=""/>
>         </field-constraint>
>       </or-constraint-connective>
>     </pattern>
>   </lhs>
>   <rhs> response.setStatus("For RFQ Bean: The value of m_rfqId is null.");
> System.out.println(response.getStatus());
> </rhs>
> </rule>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 08:49:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 4 Oct 2007 08:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <9575392.1191502143281.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380443 ] 
            
David Lloyd commented on JBREM-305:
-----------------------------------

For the user, of course they should be able to use the JAX-WS API - but Remoting does not provide this API.  My question is, what does Remoting add here?  It sounds like you want Remoting to act not so much as a remote invocation layer, but rather more as a generic transport facade.  Is this accurate?

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:03:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 09:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-473) Add 1.5.6 artifacts
 to the JBoss Maven respository
Message-ID: <10357650.1191502983487.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add 1.5.6 artifacts to the JBoss Maven respository
--------------------------------------------------

                 Key: JBAOP-473
                 URL: http://jira.jboss.com/jira/browse/JBAOP-473
             Project: JBoss AOP
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 1.5.6.GA
         Environment: n/a
            Reporter: Anders Hammar
         Attachments: jboss-aop-1.5.6.GA.pom, jboss-aop-jdk50-1.5.6.GA.pom

Please add the jdk1.4 and jdk5.0 artifacts of jboss-aop 1.5.6.GA to the maven repository. I've attached the pom files for both artifacts.

To be consistent with the deployed 1.5.0.GA artifact, I've keept the "jboss.jboss-aop" groupId and I also kept the "jboss-aop" artifactId for the jdk1.4 artifact. The jdk5.0 artifact uses the "jboss-aop-jdk50" artifactId to be consistent with the jar file in the distribution zip. (While this is not artifact naming standard used in 2.0.0.beta1.)


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:03:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Thu, 4 Oct 2007 09:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-473) Add 1.5.6 artifacts
 to the JBoss Maven respository
In-Reply-To: <10357650.1191502983487.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25859987.1191502983599.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-473?page=all ]

Anders Hammar updated JBAOP-473:
--------------------------------

    Attachment: jboss-aop-1.5.6.GA.pom
                jboss-aop-jdk50-1.5.6.GA.pom

> Add 1.5.6 artifacts to the JBoss Maven respository
> --------------------------------------------------
>
>                 Key: JBAOP-473
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-473
>             Project: JBoss AOP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.6.GA
>         Environment: n/a
>            Reporter: Anders Hammar
>         Attachments: jboss-aop-1.5.6.GA.pom, jboss-aop-jdk50-1.5.6.GA.pom
>
>
> Please add the jdk1.4 and jdk5.0 artifacts of jboss-aop 1.5.6.GA to the maven repository. I've attached the pom files for both artifacts.
> To be consistent with the deployed 1.5.0.GA artifact, I've keept the "jboss.jboss-aop" groupId and I also kept the "jboss-aop" artifactId for the jdk1.4 artifact. The jdk5.0 artifact uses the "jboss-aop-jdk50" artifactId to be consistent with the jar file in the distribution zip. (While this is not artifact naming standard used in 2.0.0.beta1.)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:12:03 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Thu, 4 Oct 2007 09:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23149661.1191503523377.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Markus Wolf updated JBRULES-1247:
---------------------------------


The above exception was caused by 'agenda-group = "action"'.
Maybe the error message could be a bit more specific.

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:12:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 4 Oct 2007 09:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-305) Provide support
 for JMS transport
Message-ID: <17342448.1191503523566.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-305?page=comments#action_12380454 ] 
            
Thomas Diesler commented on JBREM-305:
--------------------------------------

Whatever you want to call it, I'd like to use a jms like connection URI

jms://foo

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 09:44:04 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Thu, 4 Oct 2007 09:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-600) Investigate
 Multiplexer locking scopes
In-Reply-To: <8898592.1190881737185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20861180.1191505444329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-600?page=all ]

Vladimir Blagojevic resolved JGRP-600.
--------------------------------------

    Resolution: Done

Resolved by simplifying both JChannelFactory and Multiplexer. Commit set:
JChannelFactory.java 1.48
Multiplexer.java 1.75

> Investigate Multiplexer locking scopes
> --------------------------------------
>
>                 Key: JGRP-600
>                 URL: http://jira.jboss.com/jira/browse/JGRP-600
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> It seems that we are holding locks more that we need to in Multiplexer building block. Review all synchronization blocks and make changes if appropriate.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 10:50:06 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 4 Oct 2007 10:50:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-587) Lightweight FLUSH for
 state transfer
In-Reply-To: <33510599.1188575598551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13720765.1191509406217.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-587?page=all ]

Bela Ban updated JGRP-587:
--------------------------

    Description: 
We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected. 

For Multiplexer, JOIN's will still need to block everyone, because we're actually creating the underlying JChannel.

For state transfer on the Multiplexer, the example should be:
- Members {A,B,C}. A and B have services X and Y, C has only service Y
- Service B.X requests a state transfer (MuxChannel.getState())
- The FLUSH needs to be qualified with the service-id: FLUSH(X)
- A, B and C receive a START-FLUSH(X) message, which invokes A.X.block(), B.X.block().
- For C, since there is no X service, Multiplexer.block() simply returns
- When A has received all FLUSH-OK messages from A, B and C, we transfer the state from A.X to B.X
- Then we terminate the FLUSH by sending a STOP-FLUSH(x) to {A,B,C}
- This again calls A.X.unblock(), B.X.unblock() and is a no-op for C

This allows other services, e.g. Y, to be unaffected (ie., non-blocked) by the flushing of A.X

  was:We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected. 


> Lightweight FLUSH for state transfer
> ------------------------------------
>
>                 Key: JGRP-587
>                 URL: http://jira.jboss.com/jira/browse/JGRP-587
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.7
>
>
> We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected. 
> For Multiplexer, JOIN's will still need to block everyone, because we're actually creating the underlying JChannel.
> For state transfer on the Multiplexer, the example should be:
> - Members {A,B,C}. A and B have services X and Y, C has only service Y
> - Service B.X requests a state transfer (MuxChannel.getState())
> - The FLUSH needs to be qualified with the service-id: FLUSH(X)
> - A, B and C receive a START-FLUSH(X) message, which invokes A.X.block(), B.X.block().
> - For C, since there is no X service, Multiplexer.block() simply returns
> - When A has received all FLUSH-OK messages from A, B and C, we transfer the state from A.X to B.X
> - Then we terminate the FLUSH by sending a STOP-FLUSH(x) to {A,B,C}
> - This again calls A.X.unblock(), B.X.unblock() and is a no-op for C
> This allows other services, e.g. Y, to be unaffected (ie., non-blocked) by the flushing of A.X

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 11:21:03 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Thu, 4 Oct 2007 11:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (HIBERNATE-20) JDK Compatiblity
 Issue with Hibernate Tools project
Message-ID: <751956.1191511263679.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/HIBERNATE-20?page=all ]

Max Andersen closed HIBERNATE-20.
---------------------------------

    Resolution: Out of Date

> JDK Compatiblity Issue with Hibernate Tools project
> ---------------------------------------------------
>
>                 Key: HIBERNATE-20
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-20
>             Project: Hibernate
>          Issue Type: Bug
>         Environment: JDK1.4
>            Reporter: hari prasad
>         Assigned To: Gavin King
>
> In the latest release of Hibernate Tools, the DAO code generated is compatible ONLY to JDK1.5. Please provide a drop that generates 1.4 compatible code also.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 11:43:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 4 Oct 2007 11:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1193) Tests should not
 call Transaction.commit/rollback()
In-Reply-To: <5880125.1191386163241.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32052175.1191512583244.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1193?page=all ]

Jason T. Greene resolved JBCACHE-1193.
--------------------------------------

    Resolution: Done

> Tests should not call Transaction.commit/rollback()
> ---------------------------------------------------
>
>                 Key: JBCACHE-1193
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1193
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Jason T. Greene
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA
>
>
> The JTA spec says that the thread association of a transaction can only be controlled by TransactionManager. The reason is that a Transaction can be bound to multple threads. In order to be compliant, and work with JBoss JTA, we need to ensure that all operations go through TransactionManager

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:01:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 4 Oct 2007 12:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1056) Redo
 NestedBeanUnitTestCase.testConsistentPassivatedState()
Message-ID: <6265694.1191513663349.JavaMail.jira@cloud.prod.atl2.jboss.com>

Redo NestedBeanUnitTestCase.testConsistentPassivatedState()
-----------------------------------------------------------

                 Key: EJBTHREE-1056
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1056
             Project: EJB 3.0
          Issue Type: Sub-task
          Components: Clustering
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor


NestedBeanUnitTestCase.testConsistentPassivatedState() is a pretty weak test for the EJBTHREE-1053 condition; when the parent issue is fixed, replace this test with something better.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:18:03 2007
From: jira-events at lists.jboss.org (kavipriya gnanasambandam (JIRA))
Date: Thu, 4 Oct 2007 12:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
Message-ID: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>

Transaction Manager issue in JBOss Application Server 4.2.1
-----------------------------------------------------------

                 Key: JBAS-4803
                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Transaction Manager
    Affects Versions: JBossAS-4.2.1.GA
         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
            Reporter: kavipriya gnanasambandam
         Assigned To: Adrian Brock
            Priority: Critical


I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.

Please find the below log
org.springframework.transaction.NoTransactionException: No active JTA transaction
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:24:18 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 12:24:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1493674.1191515058700.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=comments#action_12380514 ] 
            
William DeCoste commented on EJBTHREE-899:
------------------------------------------

It's broken, but I am working on this. 

> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:28:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 4 Oct 2007 12:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7480051.1191515283648.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4803?page=all ]

Adrian Brock closed JBAS-4803.
------------------------------

    Resolution: Incomplete Description

This is not a bug report.

> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 12:37:03 2007
From: jira-events at lists.jboss.org (kavipriya gnanasambandam (JIRA))
Date: Thu, 4 Oct 2007 12:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21839773.1191515823459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4803?page=all ]

kavipriya gnanasambandam reopened JBAS-4803:
--------------------------------------------

             
Yes, jboss 4.2.1 causes org.springframework.transaction.NoTransactionException. 

The integration between Spring and JBOSS does not work properly anymore after upgrading jboss from 4.0.4 to 4.2.1.

In spring I'm using the JTA transaction manager as follows: 

Code: 
<bean id="txManager"
class="org.springframework.transaction.jta.JtaTransactionManager">
        <property name="transactionManagerName" value="java:/TransactionManager"/>
        <property name="userTransactionName" value="UserTransaction"/>
</bean>
 
I have a problem with a org.springframework.transaction.NoTransactionExcep tion when throwing an exception inside a bean that is wrapped with a TransactionProxyFactoryBean.
I'm using JBoss with Arjuna transaction manager When you use the org.springframework.transaction.jta.JtaTransaction Manager (which I'm using), then the Spring declarative transaction management should be integrated perfectly with JTA.This means that Spring does not roll back the transaction, but just marks it for rollback and then the Hibernate should not do anything about it because it is an application exception what I'm throwing from the spring bean (not a Runtime exception). Finally the JTA should rollback the transaction.
This was working on jboss 4.0.4, but is not working anymore on JBoss 4.2.1.


> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:06:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 4 Oct 2007 13:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4803) Transaction Manager
 issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19251010.1191517563293.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4803?page=all ]

Adrian Brock closed JBAS-4803.
------------------------------

    Resolution: Incomplete Description

If you re-open this again without using the forums thread I'll delete this issue.

> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:44:03 2007
From: jira-events at lists.jboss.org (kavipriya gnanasambandam (JIRA))
Date: Thu, 4 Oct 2007 13:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4803) Transaction
 Manager issue in JBOss Application Server 4.2.1
In-Reply-To: <24743655.1191514683537.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5540969.1191519843308.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4803?page=comments#action_12380535 ] 
            
kavipriya gnanasambandam commented on JBAS-4803:
------------------------------------------------

Delete this issue

> Transaction Manager issue in JBOss Application Server 4.2.1
> -----------------------------------------------------------
>
>                 Key: JBAS-4803
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4803
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.1.GA
>         Environment: JBoss Application Server 4.2.1 with Spring and Hibernate
>            Reporter: kavipriya gnanasambandam
>         Assigned To: Adrian Brock
>            Priority: Critical
>   Original Estimate: 7 weeks
>  Remaining Estimate: 7 weeks
>
> I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate.
> I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction.
> Please find the below log
> org.springframework.transaction.NoTransactionException: No active JTA transaction
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
> 2007-10-04 11:40:15,309 ERROR [STDERR] 	at $Proxy86.isAborted(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:46:03 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Thu, 4 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29504924.1191519963575.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=comments#action_12380536 ] 
            
Andrew Oliver commented on JBPORTAL-1713:
-----------------------------------------

common...an up or down vote baby and hopefully application :-)

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:49:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 13:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-786) String remove()
	method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6136737.1191520143838.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Carlo de Wolf updated EJBTHREE-786:
-----------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                   AS 4.2.2.GA
                       (was: Branch_4_2)
                       (was: HEAD)

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:51:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 4 Oct 2007 13:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32995919.1191520263867.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Carlo de Wolf updated EJBTHREE-785:
-----------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                   AS 4.2.2.GA
                       (was: Branch_4_2)
                       (was: HEAD)

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 13:57:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 4 Oct 2007 13:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29020950.1191520623322.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=comments#action_12380538 ] 
            
Thomas Heute commented on JBPORTAL-1713:
----------------------------------------

We'll apply it, or move to maven before don't worry...

Did you sign the contributor agreement ;)

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 16:45:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 16:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-899) WebServiceRef
 injection from DD doesn't work
In-Reply-To: <193888.1172746148967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9792897.1191530703460.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-899?page=comments#action_12380576 ] 
            
William DeCoste commented on EJBTHREE-899:
------------------------------------------

Several problems here:

1) ServiceRefMetaData does not expose injection-target, so we don't know if and where to inject the service. Injectors are not being created for service-refs with injection-targets that come from xml
2) ServiceRefMetaData does not expose merge capability to combine metadata from ejb-jar.xml and jboss.xml



> WebServiceRef injection from DD doesn't work
> --------------------------------------------
>
>                 Key: EJBTHREE-899
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> Specifying a service-ref in ejb-jar.xml like this doesn't work.
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar
>         xmlns="http://java.sun.com/xml/ns/javaee"
>         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>                             http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
>         version="3.0">
>    <description>jBoss test application </description>
>    <display-name>Test</display-name>
>    <enterprise-beans>
>       <session>
>          <ejb-name>StatelessBean</ejb-name>
>          <service-ref>
> 		    <service-ref-name>service/Endpoint3</service-ref-name>
> 		    <service-interface>org.jboss.ejb3.test.webservices.jsr181.EndpointInterface</service-interface>
> 		    <mapped-name>jbossws-client/service/TestService</mapped-name>
> 		    <injection-target>
>                <injection-target-class>org.jboss.ejb3.test.webservices.jsr181.StatelessBean</injection-target-class>
>                <injection-target-name>endpoint3</injection-target-name>
>             </injection-target>
> 		 </service-ref>
>       </session>
>    </enterprise-beans>
> </ejb-jar>

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 17:35:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 17:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25556244.1191533703440.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

William DeCoste resolved JBAS-4801.
-----------------------------------

    Resolution: Done

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 17:37:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 17:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14815556.1191533823883.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4801?page=comments#action_12380584 ] 
            
William DeCoste commented on JBAS-4801:
---------------------------------------

I've confirmed the latest fix resolves the EJB3 IIOP test issue and resovled the JIRA. Thanks.

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 18:07:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Thu, 4 Oct 2007 18:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4801) HomeHandleImplIIOP
 not using the HandleDelegate
In-Reply-To: <221152.1191403684548.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31725585.1191535623526.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4801?page=all ]

William DeCoste updated JBAS-4801:
----------------------------------

    Comment: was deleted

> HomeHandleImplIIOP not using the HandleDelegate
> -----------------------------------------------
>
>                 Key: JBAS-4801
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4801
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Adrian Brock
>         Assigned To: William DeCoste
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>
>
> The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization.
> This is because the read/writeObject methods are public when they should be private to be invoked by
> Serialization.
> Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of 
> currently writing the ior), we need a system property such that people can revert to the previous
> serialization if it causes them problems.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 18:54:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 4 Oct 2007 18:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32296905.1191538445438.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=comments#action_12380591 ] 
            
Mark Proctor commented on JBRULES-1247:
---------------------------------------

there doesn't need to be an =

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 18:54:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 4 Oct 2007 18:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28878941.1191538445609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Mark Proctor updated JBRULES-1247:
----------------------------------

    Fix Version/s: 4.0.2

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 20:02:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 4 Oct 2007 20:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-786) String remove()
 method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <407673.1191542523880.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=comments#action_12380596 ] 
            
Andrew Rubinger commented on EJBTHREE-786:
------------------------------------------

Passing in Branch 4.2, awaiting merge back to trunk before resolution.

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 21:05:03 2007
From: jira-events at lists.jboss.org (Len DiMaggio (JIRA))
Date: Thu, 4 Oct 2007 21:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
Message-ID: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>

com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
-----------------------------------------------------------------------------------------------------

                 Key: JBPM-1065
                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Web Interface
         Environment: soa-standalone.zip (oct 1 2007) 

RHEL5 

java 
version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)

            Reporter: Len DiMaggio
         Assigned To: Tom Baeyens
            Priority: Minor


These errors are reported when the jBPM console is accessed - the console seems to run however.

10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct  4 21:37:03 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Thu, 4 Oct 2007 21:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11880220.1191548223320.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=comments#action_12380601 ] 
            
Andrew Oliver commented on JBPORTAL-1713:
-----------------------------------------

Yes.  And it is work for hire for your customer done on your dime anyhow.

You're moving to maven...now I'm worried.  I've never understood masochism.

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 01:03:09 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Fri, 5 Oct 2007 01:03:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1220) Integration with
 jBPM does not work
In-Reply-To: <6567124.1190714261119.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17142817.1191560589662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1220?page=all ]

Jiri Pechanec reopened JBRULES-1220:
------------------------------------

             

> Integration with jBPM does not work
> -----------------------------------
>
>                 Key: JBRULES-1220
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1220
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
> 		workingMemory.setGlobalResolver(new GlobalResolver() {
> 			private static final long serialVersionUID = 1L;
> 			public Object resolveGlobal(String identifier) {
> 				System.out.println("!!!!!!!!!! resolve " + identifier);
> 				return ci.getVariable(identifier);
> 			}
> 			public void setGlobal(String identifier, Object value) {
> 				System.out.println("!!!!!!!!!! set " + identifier);
> 				ci.setVariable(identifier, value);
> 			}
> 		});
> And a rule file that serves as test
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> The output of the test is as expected
> 11:50:51,226 INFO  [STDOUT] !!!!!!!!!! resolve shipper
> 11:50:51,227 INFO  [STDOUT] None
> 11:50:51,227 INFO  [STDOUT] !!!!!!!!!! set shipper
> 11:50:51,227 INFO  [STDOUT] ship via FEDX 
> But if we modify the rule file to
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		eval ("None".equals(shipper))
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> then nothing is printed - no attempt to resolve shipper global variable

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 02:13:15 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Fri, 5 Oct 2007 02:13:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-474) Synchronize jar file
 names in distribution zip and maven repo
Message-ID: <109522.1191564795812.JavaMail.jira@cloud.prod.atl2.jboss.com>

Synchronize jar file names in distribution zip and maven repo
-------------------------------------------------------------

                 Key: JBAOP-474
                 URL: http://jira.jboss.com/jira/browse/JBAOP-474
             Project: JBoss AOP
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
         Environment: n/a
            Reporter: Anders Hammar


To avoid confusion, the jar file names in the distribution zip and the artifacts in the maven repository should be the same.
In the distribution file, the aop jar file for jdk1.4 is called "jboss-aop.jar" and the one for jdk5.0 is called "jboss-aop-jdk50.jar". However, in the maven repo the artifact "jboss-aop" refers to the jdk5.0 jar (and there is no jdk1.4 artifact).


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 02:18:03 2007
From: jira-events at lists.jboss.org (Anders Hammar (JIRA))
Date: Fri, 5 Oct 2007 02:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-474) Synchronize jar
 file names in distribution zip and maven repo
In-Reply-To: <109522.1191564795812.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30500966.1191565083246.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-474?page=comments#action_12380630 ] 
            
Anders Hammar commented on JBAOP-474:
-------------------------------------

My suggestion is to use the "jboss-aop.jar" for the jdk5.0 version and name the jdk1.4 version "jboss-aop-jdk14.jar". This means changing the naming convention (for the aop jars) in the distribution zip. However, is seems as that would be consistent with the naming convention for jboss-common-core and jboss-container.


> Synchronize jar file names in distribution zip and maven repo
> -------------------------------------------------------------
>
>                 Key: JBAOP-474
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-474
>             Project: JBoss AOP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>         Environment: n/a
>            Reporter: Anders Hammar
>
> To avoid confusion, the jar file names in the distribution zip and the artifacts in the maven repository should be the same.
> In the distribution file, the aop jar file for jdk1.4 is called "jboss-aop.jar" and the one for jdk5.0 is called "jboss-aop-jdk50.jar". However, in the maven repo the artifact "jboss-aop" refers to the jdk5.0 jar (and there is no jdk1.4 artifact).

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:39:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 03:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
Message-ID: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>

SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
---------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1057
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf
             Fix For: AS 4.2.2.GA


SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
(Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:42:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 5 Oct 2007 03:42:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-604) ENCRYPT: issues with
	keystore
Message-ID: <17961930.1191570135647.JavaMail.jira@cloud.prod.atl2.jboss.com>

ENCRYPT: issues with keystore
-----------------------------

                 Key: JGRP-604
                 URL: http://jira.jboss.com/jira/browse/JGRP-604
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.7
         Attachments: tmp2.xml

If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception:

09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message
javax.crypto.BadPaddingException: Given final block not properly padded
	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
	at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
	at javax.crypto.Cipher.doFinal(DashoA12275)
	at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837)
	at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830)
	at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673)
	at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533)
	at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573)
	at org.jgroups.protocols.UNICAST.up(UNICAST.java:247)
	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704)
	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
	at org.jgroups.protocols.FD.up(FD.java:322)
	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:309)
	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:613)


To reproduce:
- Create a configuration with the following entries present:
  <ENCRYPT key_store_name="defaultStore.keystore"  store_password="changeit" alias="myKey"/>	
  <FRAG2 frag_size="60000"/>
- Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2).

Note that this error does not occur with
<ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/>



-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:42:15 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 5 Oct 2007 03:42:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-604) ENCRYPT: issues with
	keystore
In-Reply-To: <17961930.1191570135647.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4033930.1191570135773.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-604?page=all ]

Bela Ban updated JGRP-604:
--------------------------

    Attachment: tmp2.xml

Use this config with RpcDispatcher.testLargeReturnValue() to reproduce the issue.

> ENCRYPT: issues with keystore
> -----------------------------
>
>                 Key: JGRP-604
>                 URL: http://jira.jboss.com/jira/browse/JGRP-604
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7
>
>         Attachments: tmp2.xml
>
>
> If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception:
> 09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message
> javax.crypto.BadPaddingException: Given final block not properly padded
> 	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
> 	at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
> 	at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
> 	at javax.crypto.Cipher.doFinal(DashoA12275)
> 	at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837)
> 	at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830)
> 	at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673)
> 	at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533)
> 	at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:247)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:309)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:613)
> To reproduce:
> - Create a configuration with the following entries present:
>   <ENCRYPT key_store_name="defaultStore.keystore"  store_password="changeit" alias="myKey"/>	
>   <FRAG2 frag_size="60000"/>
> - Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2).
> Note that this error does not occur with
> <ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/>

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 03:59:13 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 5 Oct 2007 03:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-786) String remove()
 method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1539693.1191571153379.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Andrew Rubinger resolved EJBTHREE-786.
--------------------------------------

    Resolution: Done

Fixes resolved/merged in both Branch 4.2 and trunk.

> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:04:14 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:04:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12955514.1191571454362.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=comments#action_12380642 ] 
            
Carlo de Wolf commented on EJBTHREE-1057:
-----------------------------------------

EJB 3 4.3.3: The getEJBObject method returns the session bean's remote interface. Only session beans with a remote EJBObject interface can call this method.

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:23:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 5 Oct 2007 04:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
Message-ID: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
-------------------------------------------------------------------------------

                 Key: EJBTHREE-1058
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 5.0.0.Beta3, HEAD
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: AS 5.0.0.Beta3, HEAD


Assuming:

public interface StatefulRemote extends EJBObject{...}

...and:

@Stateful
@Remote(StatefulRemote.class)
@RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
public class StatefulRemoteBean

..when invoking:

Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
EJBObject ejbObject = (EJBObject) obj;
ejbObject.remove();

...the following exception is encountered:

Could not resolve beanClass method from proxy call
java.lang.RuntimeException: Could not resolve beanClass method from proxy call
	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
	at org.jboss.remoting.Client.invoke(Client.java:1634)
	at org.jboss.remoting.Client.invoke(Client.java:548)
	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1009) Add
 configurale defaults
 on ServerPeer for FullSize, PageSize, and DownCacheSize
In-Reply-To: <19490210.1183659547941.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28850207.1191573005291.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1009?page=all ]

Tim Fox updated JBMESSAGING-1009:
---------------------------------

    Fix Version/s: Unscheduled

> Add configurale defaults on ServerPeer for FullSize, PageSize, and DownCacheSize
> --------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1009
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1009
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.3.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I see all the other defaults on the ServerPeer, but there seems to be no way to set the defaults for all the queues for the paging.  I would ask that we add the following as properties on the serverpeer
> DefaultFullSize
> DefaultPageSize
> and Default DownCacheSize
> These constants should probably be taken out of org.jboss.jms.server.destination.ManagedDestination and put into the server peer as defaults.  It would be ok to put these defaults in the Serverpeer as default values, but they need to be able to be overridden by default configuration settings.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-784) Add
 Active/Passive
 deployment feature for JBoss Messaging in 2 node cluster (Need HA part and
 not Clustering part)
In-Reply-To: <7151892.1169843757653.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2003899.1191573005456.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-784?page=all ]

Tim Fox updated JBMESSAGING-784:
--------------------------------

    Fix Version/s: Unscheduled

> Add Active/Passive deployment feature for JBoss Messaging in 2 node cluster (Need HA part and not Clustering part)
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-784
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-784
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: JMS Clustering
>    Affects Versions: 1.4.0 CR3
>            Reporter: Rohit Chowdhary
>             Fix For: Unscheduled
>
>
> Need to be able to deploy JBoss Messaging nodes in a HA configuration, but not load-balanced. 
> Such that only one node is actively serving all the requests, if the current active node goes down, then the passive node picks up the load.
> Reason would be: To use the available h/w resources at best. 
> We have one dedicated physical server for running JBoss msg. Another physical server that hosts existing JBoss instance running some application. We want to use this second server running a passive JBossMsg instance. So in case when the dedicated JBossMsg goes down, then the second shared server can take the load temporarily automatically, till we bring back the dedicated up again. 
> Other reason would be that we bring down the dedicated JBossMsg server for OS level patching, essentially minimizing the app downtime and increase availablity.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1500988.1191573006029.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox updated JBMESSAGING-1047:
---------------------------------

    Fix Version/s: Unscheduled

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:08 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1081) Allow
 configuration of
 distribution policy for queues with multiple consumers
In-Reply-To: <16868356.1190815661831.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31569399.1191573008885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1081?page=all ]

Tim Fox updated JBMESSAGING-1081:
---------------------------------

    Fix Version/s: Unscheduled

> Allow configuration of distribution policy for queues with multiple consumers
> -----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1081
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1081
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The distribution policy for queues is currently hardwired to RoundRobinDistributor (in MessagingQueue.java) like this:
>    	localDistributor = new DistributorWrapper(new RoundRobinDistributor());   	
>    	remoteDistributor = new DistributorWrapper(new RoundRobinDistributor());   	
>    	distributor = new ClusterRoundRobinDistributor(localDistributor, remoteDistributor); 
> This is a good default for when multiple clients are consuming a queue for purposes of load balancing. However, when there are multiple consumers for purposes of fail-over it can be desirable to use the FirstReceiverDistributor policy instead so that a second consumer only gets messages when the first consumer fails. (I am aware that this is simplifying matters a bit, FirstReceiverDistributor makes no such guarantees.)
> This policy can currently only be changed by patching the source code and recompiling. It would be great if it would be possible to configure the distribution policy in a configuration file instead, ideally on a per-queue basis in destinations-service.xml.
> This would ideally allow specifying arbitrary class names so that it's possible to install custom distributors.
> All of this would obviously be useful for topics as well once JBMESSAGING-377 is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:09 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-979) Servlet
 transport for JBoss Messaging
In-Reply-To: <3826403.1180702448685.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28365174.1191573009551.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-979?page=all ]

Tim Fox updated JBMESSAGING-979:
--------------------------------

    Fix Version/s: Unscheduled

> Servlet transport for JBoss Messaging
> -------------------------------------
>
>                 Key: JBMESSAGING-979
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-979
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.SP1
>         Environment: Windows 2003 with IIS as front-end web server.
>            Reporter: Daniel Weeks
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> Although there is an https transport for JBoss Messaging, it does not support going over the same port that Tomcat is using like the JBoss MQ jbossmq-httpil.sar does.  This capability is required for environments in which port 443 is the only port that is open for communication.  Although url proxying/forwarding could be used under Apache to work around this issue, there is not a good solution for doing this with IIS (or for applications that don't use a front-end web server and are limited to port 443).  Many enterprise PKI solutions (such as DoD) favor the use of IIS over Apache due to cost of COTS products, so this is a show stopper for JBoss Messaging in those environments.
> This issue is preventing us from migrating an enterprise application that runs in the DoD environment to to JBoss Messaging.  The application makes heavy use of JMS and would benefit greatly from the improved performance that JBoss Messaging provides.
> This feature request is originating from a JBoss Customer Support Portal case at the following URL: 
> https://network.jboss.com/jbossnetwork/restricted/caseDetail.html?caseId=500300000034tnzAAA&viewType=comments

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:09 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1057)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
In-Reply-To: <17912445.1187942898273.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2377547.1191573009719.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1057?page=all ]

Tim Fox updated JBMESSAGING-1057:
---------------------------------

    Fix Version/s: Unscheduled

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
> -------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1057
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1057
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.SP1
>         Environment: boss-4.0.5.GA, java 1.4.2_07 , jboss messaging 1.2.0.SP1
>            Reporter: gerald zhou
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(Unknown Source)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>         at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
>         at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:245)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:958)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.access$000(LeasePinger.java:20)
>         at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:315)
>         at java.util.TimerThread.mainLoop(Timer.java:432)
>         at java.util.TimerThread.run(Timer.java:382)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:10 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1064) MessageID
 changes when the
 message is transfered over the cluster with JBM 1.3.0GA
In-Reply-To: <15594223.1188809418325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16615010.1191573010157.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1064?page=all ]

Tim Fox updated JBMESSAGING-1064:
---------------------------------

    Fix Version/s: Unscheduled

> MessageID changes when the message is transfered over the cluster with JBM 1.3.0GA
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1064
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1064
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.3.0.GA
>            Reporter: Daniel Bevenius
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> I'm seeing the same bug that was reported by JIRA:http://jira.jboss.com/jira/browse/JBMESSAGING-1063 with JBM 1.3.0GA.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:10 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-634) If Server is
 restarted, client leases IDs might be out of sync
In-Reply-To: <9440951.1162870121664.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9766847.1191573010291.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-634?page=all ]

Tim Fox updated JBMESSAGING-634:
--------------------------------

    Fix Version/s: Unscheduled

> If Server is restarted, client leases IDs might be out of sync
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-634
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>             Fix For: Unscheduled
>
>
> This is the scenario I have:
> I start the server...
> I have clients opening/closing connections in a loop...
> I kill the server...
> (will ignore the errors on client until I get restarted)
> I restart the server....
> I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs)
> Kill the client...
> after some time.. .the server gets into an unexpected state, after we have seen this exception:
> 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.access$300(Lease.java:39)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)
> I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-923) Creating
 queue/topic with
 JNDI subcontexts fails, e.g. names such as queue/foo/bar
In-Reply-To: <16664219.1173999154492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2990110.1191573011370.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-923?page=all ]

Tim Fox updated JBMESSAGING-923:
--------------------------------

    Fix Version/s: Unscheduled

> Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-923
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-923
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Elias Ross
>             Fix For: Unscheduled
>
>
> The following service.xml will generate an exception:
> <server>
>    <loader-repository>
>         jboss.messaging:loader=ScopedLoaderRepository
>         <loader-repository-config>
>                 java2ParentDelegation=false
>         </loader-repository-config>
>    </loader-repository>
>    <mbean code="org.jboss.jms.server.destination.QueueService"
>         name="jboss.messaging.destination:service=Queue,name=ppm/mt"
>         xmbean-dd="xmdesc/Queue-xmbean.xml">
>         <depends optional-attribute-name="ServerPeer">jboss.messaging:service=Se
> rverPeer</depends>
>       <depends>jboss.messaging:service=PostOffice</depends>
>    </mbean>
> </server>
> 15:46:12,205 ERROR [ExceptionUtil] Queue[/queue/ppm/bridge/mqube, name=ppm/bridg
> e/mqube] startService
> javax.naming.NameNotFoundException: ppm not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:165)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:168)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477)
>         at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(Destin
> ationJNDIMapper.java:146)
>         at org.jboss.jms.server.destination.QueueService.startService(QueueServi
> ce.java:142)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1013) Manual merge
 queue feature via JMX
In-Reply-To: <4003720.1184269443903.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30444658.1191573011817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1013?page=all ]

Tim Fox updated JBMESSAGING-1013:
---------------------------------

    Fix Version/s: Unscheduled

> Manual merge queue feature via JMX
> ----------------------------------
>
>                 Key: JBMESSAGING-1013
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1013
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management, JMS Clustering
>         Environment: Clustering/load balancing 
>            Reporter: Evgueni Smoliar
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> In a case of disaster recovery you are obliged always to recover last running cluster node. Otherwise some messages will remain in the queue waiting for this node to startup. Idd there is a workaround for this, but it's not always easy to do. Would me much nicer to have a manual function to merge queues ( or reallocate messages) preferably available via JMX.
> For more detail please check forum.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
In-Reply-To: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22660450.1191573011953.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1090?page=all ]

Tim Fox updated JBMESSAGING-1090:
---------------------------------

    Fix Version/s: Unscheduled

> Add appropriate Exception handling when hitting MaxSize
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1090
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Jay Howell
>             Fix For: Unscheduled
>
>
> When using MaxSize for a queue and topic the following behaviors exist
> Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.
> Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.
> What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.
> I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  
> We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  
> Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1076) Missing
 annotation parameter in example "web-service"
In-Reply-To: <11829604.1190281769508.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12702723.1191573012159.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1076?page=all ]

Tim Fox updated JBMESSAGING-1076:
---------------------------------

    Fix Version/s: Unscheduled

> Missing annotation parameter in example "web-service"
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-1076
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1076
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.CR2
>         Environment: jbossws-native-2.0.0.GA
>            Reporter: Pavel Kadlec
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>         Attachments: WebServiceExampleImpl-patch.java
>
>
> WebService annotation does not have determined parameter "serviceName" in example "web-service". The container (jbossws-native-2.0.0.GA) assigns serviceName, by default "WebServiceExampleImplService".  Client asks for service "JMSSampleService".   
> The full annotation should look like
> @WebService(serviceName="JMSSampleService", name="JMSSample")

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-977)
 JMSRemotingConnection.setFailed() has a redundant call to
 org.jboss.remoting.Client.disconnect()
In-Reply-To: <30695488.1180595168474.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2810946.1191573012367.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-977?page=all ]

Tim Fox updated JBMESSAGING-977:
--------------------------------

    Fix Version/s: Unscheduled

> JMSRemotingConnection.setFailed() has a redundant call to org.jboss.remoting.Client.disconnect()
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-977
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-977
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The call client.disconnect() occurs twice, and the first one should be removed.  The result of the first call is that the subsequent call to client.removeListener(callbackManager) fails:
> 2007-05-25 11:52:12,956 415134 DEBUG [org.jboss.jms.client.remoting.JMSRemotingConnection] (Thread-353:) JMSRemotingConnection[bisocket://10.5.2.224:4457/?NumberOfCallRetries=10&clientMaxPoolSize=100&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=5&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat] failed to cleanly remove callback manager from the client
> java.lang.Exception: Can not remove callback listener as remoting client is not connected to server.
> at org.jboss.remoting.Client.removeListener(Client.java:1090)
> at org.jboss.jms.client.remoting.JMSRemotingConnection.setFailed(JMSRemotingConnection.java:340)
> at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:100)
> at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:57)
> at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83)
> at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:346) 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-998) Implement
 security for temporary destinations
In-Reply-To: <6697586.1182343252095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3781590.1191573012554.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-998?page=all ]

Tim Fox updated JBMESSAGING-998:
--------------------------------

    Fix Version/s: Unscheduled

> Implement security for temporary destinations
> ---------------------------------------------
>
>                 Key: JBMESSAGING-998
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-998
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Security
>            Reporter: Sergey Koshcheyev
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> There should probably be some attribute on the ConnectionFactory to set permissions required to use temporary destinations. See the forum thread for discussion.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-662) Implement
 XAResource.forget()
In-Reply-To: <4832867.1164977697064.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10305047.1191573012691.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-662?page=all ]

Tim Fox updated JBMESSAGING-662:
--------------------------------

    Fix Version/s: Unscheduled

> Implement XAResource.forget()
> -----------------------------
>
>                 Key: JBMESSAGING-662
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-662
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Juha Lindfors
>             Fix For: Unscheduled
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> This is currently a no-op.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-965) JBoss
 Messaging client fails to reconnect after restart of the server
In-Reply-To: <29935925.1179359942450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18277096.1191573013038.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-965?page=all ]

Tim Fox updated JBMESSAGING-965:
--------------------------------

    Fix Version/s: Unscheduled

> JBoss Messaging client fails to reconnect after restart of the server
> ---------------------------------------------------------------------
>
>                 Key: JBMESSAGING-965
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-965
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.SP1
>         Environment: java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, 
> java.runtime.version=1.5.0_10-b03, 
> java.vm.version=1.5.0_10-b03, 
> java.vm.vendor=Sun Microsystems Inc., 
> java.vm.name=Java HotSpot(TM) Client VM, 
> java.vm.specification.name=Java Virtual Machine Specification, 
> java.vm.specification.vendor=Sun Microsystems Inc., 
> java.specification.name=Java Platform API Specification, 
> java.specification.version=1.5, 
> java.vendor=Sun Microsystems Inc., 
> os.name=Windows 2000, 
> os.version=5.0, 
> os.arch=x86, 
> sun.os.patch.level=Service Pack 4, 
> JBossAS version: 4.0.5
>            Reporter: pgervais
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> There seem to be a clean up problem with the client JBoss Messaging QueueConnection.
> When following these steps, everything works fine:
> Sequence A:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. close the connection
> 7. shutdown the JBoss server
> 8. restart the JBoss server
> 9. execute step 1-6
> Everything works fine
> But following these steps:
> Sequence B:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. shutdown the JBoss server
> 7. close the connection (I get an exception, it should be normal)
> 8. restart the JBoss server
> 9. execute step 1, I get an exception, this should not be normal
> Exception received in step 7 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:200)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$closing$aop(ClientConnectionDelegate.java:158)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java)
> 	at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:82)
> 	at TestJmsClient.main(TestJmsClient.java:32)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://142.117.14.44:4457/?NumberOfCallRetries=2&clientMaxPoolSize=50&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=1&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.remoting.Client.invoke(Client.java:518)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
> 	... 17 more
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:346)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:796)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:521)
> 	... 23 more
> Exception received in step 9 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:179)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
> 	at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
> 	at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
> 	at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:54)
> 	at TestJmsClient.main(TestJmsClient.java:36)
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at java.net.Socket.connect(Socket.java:469)
> 	at java.net.Socket.<init>(Socket.java:366)
> 	at java.net.Socket.<init>(Socket.java:179)
> 	at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:217)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:328)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.addCallbackListener(Client.java:1613)
> 	at org.jboss.remoting.Client.addListener(Client.java:907)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:221)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:287)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146)
> 	... 13 more
> After investigating, I think that the problem happens when the close is executed in the second case. It seems that an exception is thrown before all the clean up has been done, because I see a thread named WorkerThread#1[142.117.14.44:3421] (which is my machine address and what seems to be the port on which the thread is listening). That thread was not present in the first case, it disappeared after executing close on the QueueConnection.  
> After further investigation, it seems that the problem is due to a clean up problem with the org.jboss.remoting.InvokerRegistry. The client invoker and server invoker from the previously created connection are not unregistered when the close method fails.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-927)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid
 for deserialization
In-Reply-To: <17070968.1174574674654.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21057489.1191573013221.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-927?page=all ]

Tim Fox updated JBMESSAGING-927:
--------------------------------

    Fix Version/s: Unscheduled

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-927
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-927
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.GA
>         Environment: jboss 4.2.0CR1, java 1.5, jboss messaging 1.2.0ga
>            Reporter: David
>             Fix For: Unscheduled
>
>         Attachments: dave-jms.tar.bz2
>
>
> 09:58:12,495 ERROR [ServerThread] failed
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> 	at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
> 	at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1205)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:72)
> 	at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:307)
> 	at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:641)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id 5c4o1w13-o9260j-ezjuc4ur-1-ezjuc5w1-4, but no collection of clients have been set.
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id null, but no collection of clients have been set.
> That exception can be caused when using the jboss-messaging-client.jar that ships with the jboss-messaging release.   The jboss-messaging-client.jar contains a version of EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment that implements Serializable.  However, the jboss app server contains a "concurrent.jar" that has a version of ConcurrentHashMap$Segment  that does not implement Serializable.  Replacing the version of lib/concurrent.jar with a version of concurrent.jar that contains a ConcurrentHashMap$Segment that implements Serializable will solve this issue.
> This situation occurs when you have a remote client that sends a message to a Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-814) MBean class is
 incorrect at performance framework
In-Reply-To: <26839623.1170789019738.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11410243.1191573014115.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-814?page=all ]

Tim Fox updated JBMESSAGING-814:
--------------------------------

    Fix Version/s: Unscheduled

> MBean class is incorrect at performance framework
> -------------------------------------------------
>
>                 Key: JBMESSAGING-814
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-814
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Tests and Performance
>    Affects Versions: 1.2.0.Beta2
>            Reporter: Vinicius Carvalho
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I have downloaded the performance tests from svn trunk today. Trying to get it running I was getting the following error from my jboss instance: No ClassLoaders found for: org.jboss.jms.server.destination.Queue. When checking the artifacts/message-destinations-service.xml I've noticied that instead of org.jboss.jms.server.destination.QueueService for my mbean classes it contains: org.jboss.jms.server.destination.Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1073) JMS messages
 are not taken from the queue after database connection recovery
In-Reply-To: <22436968.1190115251065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5604923.1191573013993.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1073?page=all ]

Tim Fox updated JBMESSAGING-1073:
---------------------------------

    Fix Version/s: Unscheduled

> JMS messages are not taken from the queue after database connection recovery
> ----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1073
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1073
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.3.0.GA
>         Environment: JBoss.4.2.1 JBossMessaging 1.3GA Oracle 10g database jdk 1.5 on solaris intel
>            Reporter: Evgueni Smoliar
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> We have  2 jboss server running in the cluster. Messaging is also configured with clustered queues. 
> At one moment we had a database crash. Database was recovered in 5 minutes and connections from jboss were reestablished . All applications works OK, new messages processed correctly. The problem is with the messages processed during the crash time. JMS could not commit them and couldn't rollback at the time. After reestablishing of the connection this messages are not redelivered anymore. 
> The only way to get those message delivered is to restart jboss servers. 
> This is strange problem which we never experienced with old jboss-jms implementation.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1003) Update queue
 and topic smoke tests to work with new message redistribution
In-Reply-To: <20452317.1183071484090.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2254193.1191573014285.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1003?page=all ]

Tim Fox updated JBMESSAGING-1003:
---------------------------------

    Fix Version/s: Unscheduled

> Update queue and topic smoke tests to work with new message redistribution
> --------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1003
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1003
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1018) Possibly fix
 timeout due
 to bug in remoting that may allow clients to hang forever.
In-Reply-To: <23514132.1185206447289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8211520.1191573014503.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1018?page=all ]

Tim Fox updated JBMESSAGING-1018:
---------------------------------

    Fix Version/s: Unscheduled

> Possibly fix timeout due to bug in remoting that may allow clients to hang forever.
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1018
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1018
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Remoting
>    Affects Versions: 1.3.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> This goes back to JBMESSAGING-171, when we changed the timeout on the bisocket to 0.  That would have meant that it would wait forever which is what we want.  There is now a bug in remoting that if this is set to 0 and the client is unreachable, then it is possible that it will hang.  We may have one case of this now, but it is still unverified.  The remoting bug is JBREM-767.  This is fixed in the 2.4 beta of remoting, but it may present a problem before we can integrate that version in.  We may want to consider changing this to a high number, so it doesn't timeout easily, but so it will timeout.    Just want to put it up for concideration.  The other route is to get the remoting team to put out another sp version with.  They could put it in  2.2.0.SP4_CP02, but that will only go out as part of the Platform 4.2 CR release, so we may want to ask them to put it out as an 2.2.0SP5, so it will go into general population where Messaging has alot of customers.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:34:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
In-Reply-To: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19097472.1191573243521.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1058?page=all ]

Carlo de Wolf updated EJBTHREE-1058:
------------------------------------

        Fix Version/s:     (was: HEAD)
    Affects Version/s:     (was: AS 5.0.0.Beta3)
                           (was: HEAD)

> Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
> -------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1058
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Assuming:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean
> ..when invoking:
> Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
> EJBObject ejbObject = (EJBObject) obj;
> ejbObject.remove();
> ...the following exception is encountered:
> Could not resolve beanClass method from proxy call
> java.lang.RuntimeException: Could not resolve beanClass method from proxy call
> 	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1634)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
> 	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:34:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-923) Creating
 queue/topic with
 JNDI subcontexts fails, e.g. names such as queue/foo/bar
In-Reply-To: <16664219.1173999154492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2509463.1191573243960.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-923?page=all ]

Tim Fox closed JBMESSAGING-923.
-------------------------------

    Resolution: Rejected

> Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-923
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-923
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Elias Ross
>             Fix For: Unscheduled
>
>
> The following service.xml will generate an exception:
> <server>
>    <loader-repository>
>         jboss.messaging:loader=ScopedLoaderRepository
>         <loader-repository-config>
>                 java2ParentDelegation=false
>         </loader-repository-config>
>    </loader-repository>
>    <mbean code="org.jboss.jms.server.destination.QueueService"
>         name="jboss.messaging.destination:service=Queue,name=ppm/mt"
>         xmbean-dd="xmdesc/Queue-xmbean.xml">
>         <depends optional-attribute-name="ServerPeer">jboss.messaging:service=Se
> rverPeer</depends>
>       <depends>jboss.messaging:service=PostOffice</depends>
>    </mbean>
> </server>
> 15:46:12,205 ERROR [ExceptionUtil] Queue[/queue/ppm/bridge/mqube, name=ppm/bridg
> e/mqube] startService
> javax.naming.NameNotFoundException: ppm not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:165)
>         at org.jnp.server.NamingServer.rebind(NamingServer.java:168)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510)
>         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477)
>         at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(Destin
> ationJNDIMapper.java:146)
>         at org.jboss.jms.server.destination.QueueService.startService(QueueServi
> ce.java:142)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:34:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:34:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-634) If Server is
 restarted, client leases IDs might be out of sync
In-Reply-To: <9440951.1162870121664.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15817026.1191573244215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-634?page=all ]

Tim Fox closed JBMESSAGING-634.
-------------------------------

    Resolution: Out of Date

> If Server is restarted, client leases IDs might be out of sync
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-634
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>             Fix For: Unscheduled
>
>
> This is the scenario I have:
> I start the server...
> I have clients opening/closing connections in a loop...
> I kill the server...
> (will ignore the errors on client until I get restarted)
> I restart the server....
> I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs)
> Kill the client...
> after some time.. .the server gets into an unexpected state, after we have seen this exception:
> 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.access$300(Lease.java:39)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)
> I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:36:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-965) JBoss Messaging
 client fails to reconnect after restart of the server
In-Reply-To: <29935925.1179359942450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8224859.1191573363542.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-965?page=all ]

Tim Fox closed JBMESSAGING-965.
-------------------------------

    Resolution: Out of Date

> JBoss Messaging client fails to reconnect after restart of the server
> ---------------------------------------------------------------------
>
>                 Key: JBMESSAGING-965
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-965
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.SP1
>         Environment: java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, 
> java.runtime.version=1.5.0_10-b03, 
> java.vm.version=1.5.0_10-b03, 
> java.vm.vendor=Sun Microsystems Inc., 
> java.vm.name=Java HotSpot(TM) Client VM, 
> java.vm.specification.name=Java Virtual Machine Specification, 
> java.vm.specification.vendor=Sun Microsystems Inc., 
> java.specification.name=Java Platform API Specification, 
> java.specification.version=1.5, 
> java.vendor=Sun Microsystems Inc., 
> os.name=Windows 2000, 
> os.version=5.0, 
> os.arch=x86, 
> sun.os.patch.level=Service Pack 4, 
> JBossAS version: 4.0.5
>            Reporter: pgervais
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> There seem to be a clean up problem with the client JBoss Messaging QueueConnection.
> When following these steps, everything works fine:
> Sequence A:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. close the connection
> 7. shutdown the JBoss server
> 8. restart the JBoss server
> 9. execute step 1-6
> Everything works fine
> But following these steps:
> Sequence B:
> 1. create a QueueConnection
> 2. create a QueueSender
> 3. send a message
> 4. create QueueReceiver (on the same queue as the QueueSender)
> 5. receive the sent message
> 6. shutdown the JBoss server
> 7. close the connection (I get an exception, it should be normal)
> 8. restart the JBoss server
> 9. execute step 1, I get an exception, this should not be normal
> Exception received in step 7 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:200)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$closing$aop(ClientConnectionDelegate.java:158)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
> 	at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate$closing_N1847373599029068216.invokeNext(ClientConnectionDelegate$closing_N1847373599029068216.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionDelegate.closing(ClientConnectionDelegate.java)
> 	at org.jboss.jms.client.JBossConnection.close(JBossConnection.java:131)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:82)
> 	at TestJmsClient.main(TestJmsClient.java:32)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://142.117.14.44:4457/?NumberOfCallRetries=2&clientMaxPoolSize=50&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=1&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat]
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.remoting.Client.invoke(Client.java:518)
> 	at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
> 	... 17 more
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:346)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:796)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:521)
> 	... 23 more
> Exception received in step 9 of sequence B:
> org.jboss.jms.util.MessagingNetworkFailureException
> 	at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:220)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:179)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
> 	at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
> 	at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
> 	at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
> 	at TestJmsClient.sendMessage(TestJmsClient.java:54)
> 	at TestJmsClient.main(TestJmsClient.java:36)
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at java.net.Socket.connect(Socket.java:469)
> 	at java.net.Socket.<init>(Socket.java:366)
> 	at java.net.Socket.<init>(Socket.java:179)
> 	at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:217)
> 	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:328)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1544)
> 	at org.jboss.remoting.Client.addCallbackListener(Client.java:1613)
> 	at org.jboss.remoting.Client.addListener(Client.java:907)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:221)
> 	at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:287)
> 	at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:146)
> 	... 13 more
> After investigating, I think that the problem happens when the close is executed in the second case. It seems that an exception is thrown before all the clean up has been done, because I see a thread named WorkerThread#1[142.117.14.44:3421] (which is my machine address and what seems to be the port on which the thread is listening). That thread was not present in the first case, it disappeared after executing close on the QueueConnection.  
> After further investigation, it seems that the problem is due to a clean up problem with the org.jboss.remoting.InvokerRegistry. The client invoker and server invoker from the previously created connection are not unregistered when the close method fails.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:36:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1064) MessageID
 changes when the
 message is transfered over the cluster with JBM 1.3.0GA
In-Reply-To: <15594223.1188809418325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24892458.1191573363886.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1064?page=all ]

Tim Fox closed JBMESSAGING-1064.
--------------------------------

    Resolution: Duplicate Issue

> MessageID changes when the message is transfered over the cluster with JBM 1.3.0GA
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1064
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1064
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.3.0.GA
>            Reporter: Daniel Bevenius
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> I'm seeing the same bug that was reported by JIRA:http://jira.jboss.com/jira/browse/JBMESSAGING-1063 with JBM 1.3.0GA.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:40:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1003) Update queue
 and topic smoke tests to work with new message redistribution
In-Reply-To: <20452317.1183071484090.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21024500.1191573603479.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1003?page=all ]

Tim Fox closed JBMESSAGING-1003.
--------------------------------

    Resolution: Out of Date

> Update queue and topic smoke tests to work with new message redistribution
> --------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1003
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1003
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:40:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1057)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
In-Reply-To: <17912445.1187942898273.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6140427.1191573604286.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1057?page=all ]

Tim Fox closed JBMESSAGING-1057.
--------------------------------

    Resolution: Duplicate Issue

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
> -------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1057
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1057
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.SP1
>         Environment: boss-4.0.5.GA, java 1.4.2_07 , jboss messaging 1.2.0.SP1
>            Reporter: gerald zhou
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(Unknown Source)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:324)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
>         at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80)
>         at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:245)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:958)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.access$000(LeasePinger.java:20)
>         at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:315)
>         at java.util.TimerThread.mainLoop(Timer.java:432)
>         at java.util.TimerThread.run(Timer.java:382)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:40:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-927)
 java.io.IOException:
 EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid
 for deserialization
In-Reply-To: <17070968.1174574674654.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32598430.1191573604460.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-927?page=all ]

Tim Fox closed JBMESSAGING-927.
-------------------------------

    Resolution: Duplicate Issue

> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-927
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-927
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.2.0.GA
>         Environment: jboss 4.2.0CR1, java 1.5, jboss messaging 1.2.0ga
>            Reporter: David
>             Fix For: Unscheduled
>
>         Attachments: dave-jms.tar.bz2
>
>
> 09:58:12,495 ERROR [ServerThread] failed
> java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
> 	at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
> 	at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1205)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:72)
> 	at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:307)
> 	at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:641)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id 5c4o1w13-o9260j-ezjuc4ur-1-ezjuc5w1-4, but no collection of clients have been set.
> 09:58:14,711 WARN  [Lease] Tried to terminate lease for session id null, but no collection of clients have been set.
> That exception can be caused when using the jboss-messaging-client.jar that ships with the jboss-messaging release.   The jboss-messaging-client.jar contains a version of EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment that implements Serializable.  However, the jboss app server contains a "concurrent.jar" that has a version of ConcurrentHashMap$Segment  that does not implement Serializable.  Replacing the version of lib/concurrent.jar with a version of concurrent.jar that contains a ConcurrentHashMap$Segment that implements Serializable will solve this issue.
> This situation occurs when you have a remote client that sends a message to a Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:42:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-977)
 JMSRemotingConnection.setFailed() has a redundant call to
 org.jboss.remoting.Client.disconnect()
In-Reply-To: <30695488.1180595168474.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5018319.1191573723688.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-977?page=all ]

Tim Fox closed JBMESSAGING-977.
-------------------------------

    Resolution: Out of Date

> JMSRemotingConnection.setFailed() has a redundant call to org.jboss.remoting.Client.disconnect()
> ------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-977
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-977
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> The call client.disconnect() occurs twice, and the first one should be removed.  The result of the first call is that the subsequent call to client.removeListener(callbackManager) fails:
> 2007-05-25 11:52:12,956 415134 DEBUG [org.jboss.jms.client.remoting.JMSRemotingConnection] (Thread-353:) JMSRemotingConnection[bisocket://10.5.2.224:4457/?NumberOfCallRetries=10&clientMaxPoolSize=100&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=5&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat] failed to cleanly remove callback manager from the client
> java.lang.Exception: Can not remove callback listener as remoting client is not connected to server.
> at org.jboss.remoting.Client.removeListener(Client.java:1090)
> at org.jboss.jms.client.remoting.JMSRemotingConnection.setFailed(JMSRemotingConnection.java:340)
> at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:100)
> at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:57)
> at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83)
> at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:346) 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:44:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 04:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-814) MBean class is
 incorrect at performance framework
In-Reply-To: <26839623.1170789019738.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31951646.1191573843463.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-814?page=all ]

Tim Fox closed JBMESSAGING-814.
-------------------------------

    Resolution: Out of Date

> MBean class is incorrect at performance framework
> -------------------------------------------------
>
>                 Key: JBMESSAGING-814
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-814
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Tests and Performance
>    Affects Versions: 1.2.0.Beta2
>            Reporter: Vinicius Carvalho
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I have downloaded the performance tests from svn trunk today. Trying to get it running I was getting the following error from my jboss instance: No ClassLoaders found for: org.jboss.jms.server.destination.Queue. When checking the artifacts/message-destinations-service.xml I've noticied that instead of org.jboss.jms.server.destination.QueueService for my mbean classes it contains: org.jboss.jms.server.destination.Queue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-815) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
In-Reply-To: <995728.1166795738121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1731344.1191574563890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-815?page=all ]

Carlo de Wolf resolved EJBTHREE-815.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-815
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-815
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> Testcase: testQuerySingleResultExceptions took 0.058 sec
>         Caused an ERROR
> javax.persistence.NoResultException: No entity found for query
> javax.ejb.EJBException: javax.persistence.NoResultException: No entity found for query
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: javax.persistence.NoResultException: No entity found for query
>         at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:82)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySingleResultExceptions(ExceptionTestBean.java:269)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySingleResultExceptions(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySingleResultExceptions(EntityExceptionTestCa
> se.java:96)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-816) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
In-Reply-To: <23148785.1166796163032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12841527.1191574564050.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-816?page=all ]

Carlo de Wolf resolved EJBTHREE-816.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-816
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-816
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> Testcase: testQuerySetHintAndParameter took 0.035 sec
>         Caused an ERROR
> java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
> javax.ejb.EJBException: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterDescriptor(ParameterMetadata.java:55)
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterExpectedType(ParameterMetadata.java:61)
>         at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:397)
>         at org.hibernate.impl.AbstractQueryImpl.setParameter(AbstractQueryImpl.java:369)
>         at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:234)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySetHintAndParameter(ExceptionTestBean.java:311)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySetHintAndParameter(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySetHintAndParameter(EntityExceptionTestCase.
> java:103)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-817) test failure -
 org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
In-Reply-To: <25680060.1166796342815.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12143958.1191574564205.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-817?page=all ]

Carlo de Wolf resolved EJBTHREE-817.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-817
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-817
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> Testcase: testRuntimeException took 2.058 sec
>         FAILED
> expected:<1> but was:<0>
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
>         at org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase.testRuntimeException(MDBUnitTestCase.java:292)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-818) test failure -
 org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
In-Reply-To: <1942068.1166797118725.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11543412.1191574564369.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-818?page=all ]

Carlo de Wolf resolved EJBTHREE-818.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-818
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-818
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> Testcase: testRollback took 5.05 sec
>         FAILED
> null
> junit.framework.AssertionFailedError
>         at org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase.testRollback(MDBUnitTestCase.java:128)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-819) test failure -
 org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
In-Reply-To: <4167073.1166798501804.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11617612.1191574564551.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-819?page=all ]

Carlo de Wolf resolved EJBTHREE-819.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-819
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-819
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> Testcase: testSSLBindings took 35.731 sec
>         Caused an ERROR
> Could not dereference object
> javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.remoting.CannotConnectException: Can not 
> get connection to server.  Problem establishing socket connection.]
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase.testSSLBindings(SSLUnitTestCase.java:68)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server.  Problem establishing socket connection.
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:267)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:48)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
>         at $Proxy1.createProxy(Unknown Source)
>         at org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:52)
>         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
>         at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
>         ... 25 more
> Caused by: java.lang.reflect.InvocationTargetException
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createClientSocket(SocketClientInvoker.java:518)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.getConnection(SocketClientInvoker.java:485)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:263)
>         ... 38 more
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:742)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:678)
>         at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
>         at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2213)
>         at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
>         at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)
>         at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:761)
>         at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
>         at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
>         at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:83)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
>         ... 45 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>         at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-838) test failure -
 org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
In-Reply-To: <8353072.1169064476539.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30373431.1191574564707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-838?page=all ]

Carlo de Wolf resolved EJBTHREE-838.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> -------------------------------------------------------------------
>
>                 Key: EJBTHREE-838
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-838
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: [java.version: 1.5.0_08]
> [java.vendor: BEA Systems, Inc.]
> [java.vm.version: R27.1.0-109-73164-1.5.0_08-20061129-1418-linux-ia32]
> [java.vm.name: BEA JRockit(R)]
> [java.vm.info: compiled mode]
> [os.name: Linux]
> [os.arch: i386]
> [os.version: 2.6.9-42.0.3.ELsmp]
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> Test:        testStackTrace
> Type:        failure
> Exception:   junit.framework.AssertionFailedError
> junit.framework.AssertionFailedError
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testStackTrace(RemoteUnitTestCase.java:250)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-865) test failure -
 org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with
 Sun 1.5.0_11
In-Reply-To: <12695397.1170729619498.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17705177.1191574564966.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-865?page=all ]

Carlo de Wolf resolved EJBTHREE-865.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure - org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with Sun 1.5.0_11 
> -------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-865
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-865
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: Boss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.webservices.unit.WsUnitTestCase
> Test:        testDeployment
> Type:        error
> Exception:   org.jboss.deployment.DeploymentException
> Message:     Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ej
> b3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.tes
> t.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> org.jboss.deployment.DeploymentException: Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> 	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:991)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:471)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.processWebMethod(JSR181MetaDataBuilder.java:568)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:193)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75)
> 	at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy30.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	... 53 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: org.jboss.ws.jaxrpc.ParameterWrapping$WrapperType
> 	at javassist.CtClassType.getClassFile2(CtClassType.java:204)
> 	at javassist.CtClassType.getConstructorsCache(CtClassType.java:892)
> 	at javassist.CtClassType.getDeclaredConstructors(CtClassType.java:878)
> 	at javassist.CtNewClass.inheritAllConstructors(CtNewClass.java:87)
> 	at javassist.CtNewClass.toBytecode(CtNewClass.java:63)
> 	at javassist.CtClass.toBytecode(CtClass.java:1181)
> 	at javassist.ClassPool.toClass(ClassPool.java:883)
> 	at javassist.ClassPool.toClass(ClassPool.java:846)
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:467)
> 	... 67 more

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 04:56:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 04:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-866) test failure -
 org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) -
 with Sun 1.5.0_11
In-Reply-To: <31270078.1170729763045.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30759789.1191574565172.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-866?page=all ]

Carlo de Wolf resolved EJBTHREE-866.
------------------------------------

    Fix Version/s: AS 4.2.2.GA
       Resolution: Done
         Assignee: William DeCoste

> test failure -  org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) - with Sun 1.5.0_11 
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-866
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-866
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase
> Test:        testEJBServlet
> Type:        error
> Exception:   java.io.IOException
> Message:     Expected reply code:200, actual=500
> Expected reply code:200, actual=500
> java.io.IOException: Expected reply code:200, actual=500
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:140)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:109)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:97)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:83)
> 	at org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase.testEJBServlet(EarServletUnitTestCase.java:49)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:02:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:02:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-880) Non persistent
 messages can be sent one way
In-Reply-To: <13732117.1172086955491.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27702553.1191574924213.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-880?page=all ]

Tim Fox closed JBMESSAGING-880.
-------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: 2.0.0 Beta 1)
       Resolution: Done

Added temporary solution for this until we get MINA in

> Non persistent messages can be sent one way
> -------------------------------------------
>
>                 Key: JBMESSAGING-880
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-880
>             Project: JBoss Messaging
>          Issue Type: Sub-task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> When sending non persistent messages from client to server. They can be sent oneway, i.e. no need to wait for a response that the message has been receive on the server.
> This should massively increase performance since we will not be hostage to networks with large RTT.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:21:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:21:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-754) Allow for
 multiple service containers to be started in same VM
In-Reply-To: <972857.1169053192768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24509222.1191576075022.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-754?page=all ]

Tim Fox updated JBMESSAGING-754:
--------------------------------

    Summary: Allow for multiple service containers to be started in same VM  (was: Allow for multiple service containes to be started in same VM)

> Allow for multiple service containers to be started in same VM
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-754
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-754
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> ServerManagement currently allows multiple remote ServiceContainers to be started and stopped, but it does not allow multiple ServiceContainers to be started and stopped in the same VM.
> This means tests like the bridge tests can only be run in remote 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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:31:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-662) Implement
 XAResource.forget()
In-Reply-To: <4832867.1164977697064.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1057780.1191576663329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-662?page=all ]

Tim Fox updated JBMESSAGING-662:
--------------------------------

    Fix Version/s: 2.0.0 Beta 1
                       (was: Unscheduled)

> Implement XAResource.forget()
> -----------------------------
>
>                 Key: JBMESSAGING-662
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-662
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Messaging Core
>            Reporter: Juha Lindfors
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> This is currently a no-op.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:33:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 5 Oct 2007 05:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21732641.1191576783696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox closed JBMESSAGING-1047.
--------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)
       Resolution: Done

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:35:03 2007
From: jira-events at lists.jboss.org (Dirk Gfroerer (JIRA))
Date: Fri, 5 Oct 2007 05:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4484)
 org.jboss.security.auth.callback.MapCallback not serializable
In-Reply-To: <10497493.1181723591903.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19205401.1191576903793.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4484?page=all ]

Dirk Gfroerer updated JBAS-4484:
--------------------------------

    Affects Version/s: JBossAS-4.2.1.GA

> org.jboss.security.auth.callback.MapCallback not serializable
> -------------------------------------------------------------
>
>                 Key: JBAS-4484
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4484
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.2.1.GA
>         Environment: Linux ghlx06 2.4.21-50.EL #1 SMP Tue May 8 17:10:00 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> RHEL 3 x86_64
>            Reporter: Dirk Gfroerer
>         Assigned To: Scott M Stark
>
> I'm securing access to my EJBs via a security domain. Everything was working fine until I had to add a second login module to my application-policy in login-config.xml. I now do have to login-modules both of them are flagged as being sufficient. However if now a user tries to login and uses an invalid account / password I get the following exception:
> Exception in thread "main" java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: 
> 	java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback
> 	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217)
> 	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
> 	at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
> 	at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
> 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
> 	at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
> 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
> 	at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
> 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
> 	at $Proxy0.create(Unknown Source)
> 	at de.guhsoft.eDHR.OrderManager.testclient.GetUserInformation.doAction(GetUserInformation.java:71)
> 	at de.guhsoft.eDHR.OrderManager.testclient.GetUserInformation.main(GetUserInformation.java:92)
> Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
> 	... 12 more
> Caused by: java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
> 	at java.lang.Throwable.writeObject(Throwable.java:648)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
> 	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
> 	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:343)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:159)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> 	at java.lang.Thread.run(Thread.java:619)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:45:03 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Fri, 5 Oct 2007 05:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21142466.1191577503299.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4766?page=all ]

Dominik Pospisil updated JBAS-4766:
-----------------------------------

    Attachment: buddy-sync-20s.tgz

Attaching test run logs of failed test with sync buddy replication. Buddy communication timeout set to 20s.

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: buddy-sync-20s.tgz, driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 05:49:06 2007
From: jira-events at lists.jboss.org (thilker (JIRA))
Date: Fri, 5 Oct 2007 05:49:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23020311.1191577746350.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12380663 ] 
            
thilker commented on GPD-169:
-----------------------------

I have the same problem here.
I had nodes with simular names in my workflow, like "CalculateAmount1", "CalculateAmount2", ..
So I thought the fact that the first letters are the same is the problem.
I renamed the nodes to "N001CalculateAmount",  "N002CalculateAmount", ...
Since I did this the problem disappeared.

But in your example the node-names are completely different.
Strange.

Regards,

Thorsten

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:06:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4689) Upgrade JBoss
 messaging to 1.4.0.GA
In-Reply-To: <16306175.1189160291086.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10100436.1191578763348.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4689?page=all ]

Dimitris Andreadis closed JBAS-4689.
------------------------------------

    Resolution: Done

I suppose we can close this. There are still a lot of failures in the AS testsuite related to jboss messaging:

http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/lastBuild/testReport/

> Upgrade JBoss messaging to 1.4.0.GA
> -----------------------------------
>
>                 Key: JBAS-4689
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4689
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Dimitris Andreadis
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> We are currently at 1.4.0.CR2

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:06:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4716) Update common-core
	to 2.2.2.GA
In-Reply-To: <9279917.1189681040331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31193525.1191578763510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4716?page=all ]

Dimitris Andreadis reassigned JBAS-4716:
----------------------------------------

    Assignee: Dimitris Andreadis

> Update common-core to 2.2.2.GA
> ------------------------------
>
>                 Key: JBAS-4716
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4716
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Common-core has fixes we need. Since further fixes are possible maybe move to a 2.2.2-snapshot release first.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:19:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22686925.1191579543319.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4688?page=all ]

Dimitris Andreadis reopened JBAS-4688:
--------------------------------------

             
Re-using this task to track upgrade to S 4.3.beta2 (from beta1).

Jonathan, when the release is available, please let me know, thanks.

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:23:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9581424.1191579783309.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12380669 ] 
            
Jonathan Halliday commented on JBAS-4688:
-----------------------------------------

oops, sorry. JBossTS release has been out since Tuesday. I still need to put a fix into the transactions-spi and release that too though.

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13013799.1191580263320.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12380671 ] 
            
Dimitris Andreadis commented on JBAS-4688:
------------------------------------------

Where does the transaction-spi live ?

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:33:24 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 06:33:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23401514.1191580404105.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12380672 ] 
            
Jonathan Halliday commented on JBAS-4688:
-----------------------------------------

It's part of https://svn.jboss.org/repos/jbossas/projects/integration/trunk

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:45:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4660) Fix
 jboss-head-testsuite-sun-1.5
 regression when the testsuite runs under hudson
In-Reply-To: <9933141.1188908538489.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7543478.1191581103647.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4660?page=all ]

Dimitris Andreadis updated JBAS-4660:
-------------------------------------

    Priority: Major  (was: Critical)

> Fix jboss-head-testsuite-sun-1.5 regression when the testsuite runs under hudson
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4660
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4660
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Rajesh Rajasekaran wrote:
> > >> Dimitris,
> > >>
> > >> This looks like a bug in the web layer, when the server is bound to an
> > >> ip (onn hudson). Please take a look at all the web related tests.
> > >> http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/lastSuccessfulBuild/artifact/trunk/testsuite/output/reports/html/index.html
> > >>
> > >>
> > >> whereas on CC the testsuite is run on localhost and these errors dont
> > >> show up.
> > >> http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-sun-1.5/20070829063207/results/index.html
> > >>
> > >>
> > >> If you think the same, i will make this run on hudson public, with 871
> > >> failures as regressions.
> > >> All other runs, jboss-3.x, 4.0.x, 4.2.x are stable on  hudson and
> > >> ready to be public.
> > >> All CC runs will be shutdown then.
> > >> And then you can have as many runs as you want  :) 
> > >>
> > >> Thanks
> > >> rajesh
> > >>
> > >> Dimitris Andreadis wrote:
> >> >>> I'm not sure why, but Hudson seems to produce different error counts:
> >> >>>
> >> >>> 871 failures
> >> >>> http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/lastSuccessfulBuild/testReport/
> >> >>>
> >> >>>
> >> >>> vs CC 334 failures
> >> >>> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5?log=log20070829063207

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:47:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2149)
	ByValueContainerInvoker
Message-ID: <7994404.1191581223392.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2149?page=all ]

Dimitris Andreadis updated JBAS-2149:
-------------------------------------

    Comment: was deleted

> ByValueContainerInvoker
> -----------------------
>
>                 Key: JBAS-2149
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2149
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Remove the use of ByValueInvokerInterceptor from the testsuite.
> This was deprecated in JBoss4 and removed in JBoss5, it should be using the MarshalledInvokerInterceptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:49:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:49:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-2145) Testsuite JBossMQ
 destination deployment is broken
Message-ID: <2821403.1191581355890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2145?page=all ]

Dimitris Andreadis closed JBAS-2145.
------------------------------------

    Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
       Resolution: Out of Date

I suppose this is not current anymore?

> Testsuite JBossMQ destination deployment is broken
> --------------------------------------------------
>
>                 Key: JBAS-2145
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2145
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Adrian Brock
>         Assigned To: Sacha Labourey
>
> The change to only deploy destinations as part of the testsuite run
> is broken. e.g.
> 2005-08-19 15:03:28,885 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/scratch/cruisecontrol/checkout/jboss-head-testsuite/testsuite/outp
> ut/resources/messaging/test-destinations-full-service.xml
> org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:name=A,service=Queue
>         at org.jboss.system.ServiceCreator.install(ServiceCreator.java:72)
>         at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:429)
>         at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:151)
>         at org.jboss.system.ServiceController.install(ServiceController.java:216)
>         at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
> Sacha, why did you change this?
> This needs fixing properly anyway such that the tests run against both JBossMQ and JBoss Messaging.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:51:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3151) Convert HA-JNDI
 stubs to Remoting
Message-ID: <18969963.1191581463549.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3151?page=all ]

Dimitris Andreadis reassigned JBAS-3151:
----------------------------------------

    Assignee: Ron Sigal  (was: Tom  Elrod)

Assign to Ron. It could also be rescheduled.

> Convert HA-JNDI stubs to Remoting
> ---------------------------------
>
>                 Key: JBAS-3151
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3151
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Naming, Remoting
>            Reporter: Brian Stansberry
>         Assigned To: Ron Sigal
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code.  We should convert this to use Remoting.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:51:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4644) fix
 org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC) - 5 errors
In-Reply-To: <9681728.1188322458268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13616430.1191581463778.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4644?page=comments#action_12380677 ] 
            
Dimitris Andreadis commented on JBAS-4644:
------------------------------------------

The fix for this needs to be brought in from Branch_4_2.

> fix org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC) - 5 errors
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4644
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4644
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Problem appears either as:
> testRoleSecuredServiceAccess Error Call invocation failed; nested exception is: java.io.IOException: Could not transmit message
> java.rmi.RemoteException: Call invocation failed; nested exception is: 
> 	java.io.IOException: Could not transmit message
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536)
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
> 	at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151)
> 	at $Proxy4.getContactInfo(Unknown Source)
> 	at org.jboss.test.webservice.jbws309.JBWS309TestCase.testRoleSecuredServiceAccess(JBWS309TestCase.java:190)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> Caused by: java.io.IOException: Could not transmit message
> 	at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:204)
> 	at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77)
> 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337)
> 	at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
> 	... 25 more
> Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:332)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183)
> 	... 28 more
> Caused by: org.jboss.ws.WSException: Invalid HTTP server response [401] - Unauthorized
> 	at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:77)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304)
> 	... 33 more
> Or
> testRoleSecuredSLSB Error SecurityException; nested exception is: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> java.rmi.AccessException: SecurityException; nested exception is: 
> 	javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> 	at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
> 	at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136)
> 	at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
> 	at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640)
> 	at org.jboss.ejb.Container.invoke(Container.java:1006)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:230)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
> 	at $Proxy14.invoke(Unknown Source)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> Caused by: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
> 	at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:212)
> 	at org.jboss.security.auth.spi.UsersRolesLoginModule.login(UsersRolesLoginModule.java:152)
> 	at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
> 	at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
> 	at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
> 	at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
> 	at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:524)
> 	at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:458)
> 	at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:353)
> 	at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(SecurityInterceptor.java:317)
> 	at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:185)
> 	at org.jboss.ejb.plugins.security.PreSecurityInterceptor.invokeHome(PreSecurityInterceptor.java:140)
> 	at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132)
> 	at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107)
> 	at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:640)
> 	at org.jboss.ejb.Container.invoke(Container.java:1006)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at org.jboss.invocation.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:230)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> 	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201)
> 	at $Proxy14.invoke(Unknown Source)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:161)
> 	at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:244)
> 	at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:181)
> 	at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
> 	at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:86)
> 	at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
> 	at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101)
> 	at $Proxy1.create(Unknown Source)
> 	at org.jboss.test.webservice.jbws309.JBWS309TestCase.testRoleSecuredSLSB(JBWS309TestCase.java:93)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
>  

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:55:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:55:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-59) JCA work for
	JBoss-5.0.0Beta
Message-ID: <24998505.1191581707886.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-59?page=comments#action_12380678 ] 
            
Dimitris Andreadis commented on JBAS-59:
----------------------------------------

What other work relates to this task? The only subtask is scheduled for CR1.

> JCA work for JBoss-5.0.0Beta
> ----------------------------
>
>                 Key: JBAS-59
>                 URL: http://jira.jboss.com/jira/browse/JBAS-59
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>            Reporter: Adrian Brock
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Schedule 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 06:58:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 5 Oct 2007 06:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4720) Ensure
 security-domain is picked up by JCA Deployer
In-Reply-To: <25591894.1189710491347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <782831.1191581883274.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4720?page=all ]

Dimitris Andreadis updated JBAS-4720:
-------------------------------------

    Priority: Critical  (was: Major)

This should be critical as it affects a great deal of the testsuite, right?

> Ensure security-domain is picked up by JCA Deployer
> ---------------------------------------------------
>
>                 Key: JBAS-4720
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4720
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Anil Saldhana
>         Assigned To: Weston Price
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Ensure that the security-domain settings are read into the metadata to be used by ConnectionManager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:06:07 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Fri, 5 Oct 2007 07:06:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1249) Allow repository
 location to be specified in BRMS web client
Message-ID: <26599863.1191582367386.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow repository location to be specified in BRMS web client
------------------------------------------------------------

                 Key: JBRULES-1249
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1249
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


At present, any custom location of the repository is set in a components.xml file inside the WEB-INF directory of the BRMS war file. It would be better if the user could specify the location using the BRMS web client itself, rather than have to unzip, modify and zip up the WAR file. Perhaps this functionality could be added to the Admin section of the BRMS.

One advantage of this is that users could also then work with multiple repositories (e.g. for different projects). In effect there would be an option to create a new repository (specified by a directory given by the user), open an existing repository and close a repository.


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:10:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 07:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30599167.1191582603387.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4770?page=comments#action_12380681 ] 
            
Jonathan Halliday commented on JBAS-4770:
-----------------------------------------

per 

The current TransactionLocal.get() implementation in the app server actually tries to write the value in certain cases. If it's called after transaction resolution, that storeValue now throws an IllegalStateException, causing get() to blow up.

I've changed the behavior so the exception is masked and the result of initialValue() is returned from the get in such cases. 

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:10:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Fri, 5 Oct 2007 07:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4770)
 TransactionLocal.get() not sufficiently pluggable
In-Reply-To: <26111494.1191236922382.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21630492.1191582603569.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4770?page=comments#action_12380682 ] 
            
Jonathan Halliday commented on JBAS-4770:
-----------------------------------------

oops forgot the link: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119313 

> TransactionLocal.get() not sufficiently pluggable
> -------------------------------------------------
>
>                 Key: JBAS-4770
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4770
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> JBAS-4748 applied to trunk.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:12:03 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Fri, 5 Oct 2007 07:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1250) Allow option to
 completely remove an asset from the repository
Message-ID: <16475001.1191582723288.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow option to completely remove an asset from the repository
--------------------------------------------------------------

                 Key: JBRULES-1250
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1250
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


If you use the archive feature to remove a rule or package from the BRMS it is not really seen as gone, as if you attempt to create a new rule or package with the same name as the archived rules or package then you get an error saying that the rule or package already exists (looking at the  source code, the repository does not care if an item is archived or not, so it will always throw an error if an asset with an existing name is created).

I'm assuming this is the designed behaviour and not a bug (I've asked about this a couple of times on the user list and got no replies to the contrary).

However, it would be very useful to be able to remove a rule or package so that you can then recreate it (e.g by importing new versions from a drl file). At present, you have to laboriously rename the rules and packages you want to remove, so that when they are archived their names do not clash with the new versions of the rules and packages you want to import or recreate. Perhaps all that is involved in implementing this new remove feature is to just automatically rename the package and its rules before archiving it?


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 07:24:03 2007
From: jira-events at lists.jboss.org (Shahad Ahmed (JIRA))
Date: Fri, 5 Oct 2007 07:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1251) Cannot remove a
 category if it was used in an archived rule
Message-ID: <29917794.1191583443584.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot remove a category if it was used in an archived rule
-----------------------------------------------------------

                 Key: JBRULES-1251
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1251
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Shahad Ahmed
         Assigned To: Mark Proctor


The BRMS manual says you can delete a category if it is not in use by any current version of a rule. However, if you archive a rule that uses a category X, say, then you cannot remove category X in the Admin section, even if no other rules in the repository use category X. You get the following error message:

"The category still has some assets linked to it. You will need to remove the links so you can delete the cateogory"

(PS not the spelling mistake cateogory in the error message)

Either the manual (Section 9.4.2.2) should be updated with a warning that you cannot remove a category used by archived rules, or is there is a bug in the remove category functionality for archived assets, as you can remove categories which are only used in old versions of a rule?


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:09:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 5 Oct 2007 08:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
In-Reply-To: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5193201.1191586143296.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1058?page=all ]

Carlo de Wolf updated EJBTHREE-1058:
------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091956

> Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
> -------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1058
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Assuming:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean
> ..when invoking:
> Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
> EJBObject ejbObject = (EJBObject) obj;
> ejbObject.remove();
> ...the following exception is encountered:
> Could not resolve beanClass method from proxy call
> java.lang.RuntimeException: Could not resolve beanClass method from proxy call
> 	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1634)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
> 	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:29:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Fri, 5 Oct 2007 08:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
In-Reply-To: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13183389.1191587343334.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1065?page=comments#action_12380690 ] 
            
David Lloyd commented on JBPM-1065:
-----------------------------------

They're not errors, they are actually JDK logging messages reported by Facelets.  In the older JBossAS versions (< 4.2.0 for sure), JDK logging messages go to STDERR, and so log4j grabs them an logs them at level ERROR.  Notice how after the timestamp and the "ERROR [STDERR]" part, there's another timestamp, the log category, and the word "INFO" - this is the REAL log level of the message.

Probably the easiest fix is to provide a JDK logging configuration file that disables logging.

> com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1065
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>         Environment: soa-standalone.zip (oct 1 2007) 
> RHEL5 
> java 
> version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>            Reporter: Len DiMaggio
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> These errors are reported when the jBPM console is accessed - the console seems to run however.
> 10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
> 10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
> 10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
> 10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
> 10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
> 10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
> 10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
> 10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
> 10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
> 10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
> 10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
> 10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
> 10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
> 10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
> 10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:31:03 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Fri, 5 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-305) Provide support for
	JMS transport
Message-ID: <24528029.1191587463283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-305?page=all ]

David Lloyd updated JBREM-305:
------------------------------

    JBoss Forum Reference: http://jboss.com/index.html?module=bb&op=viewtopic&t=120444

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>             Fix For: 4.0.0.Beta1
>
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:43:03 2007
From: jira-events at lists.jboss.org (Tyronne Wickramarathne (JIRA))
Date: Fri, 5 Oct 2007 08:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1097) Cleaning JBM
 Tables During Startup
Message-ID: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cleaning JBM Tables During Startup
----------------------------------

                 Key: JBMESSAGING-1097
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: Messaging Core Persistence
    Affects Versions: 1.4.0.GA
         Environment: JBossAS-4.2.0-GA
JBossMessaging-1.4.0-GA
            Reporter: Tyronne Wickramarathne
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 08:49:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 5 Oct 2007 08:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4520) Remove testsuite
 dependency on old transaction manager
In-Reply-To: <10023540.1183572471230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2146330.1191588543397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4520?page=all ]

Adrian Brock closed JBAS-4520.
------------------------------

    Resolution: Done

> Remove testsuite dependency on old transaction manager
> ------------------------------------------------------
>
>                 Key: JBAS-4520
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4520
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The parts of the testsuite that depend upon the old transaction manager need removing.
> They should either be replaced with JBossTM as an in-memory transaction manager (this could be done
> by changing the TransactionManagerLocator in the jboss-integration project)
> or the tests need moving to run inside the appserver.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:28:03 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Fri, 5 Oct 2007 10:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1252) DrlDumper does
 not dump import functions
Message-ID: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>

DrlDumper does not dump import functions
----------------------------------------

                 Key: JBRULES-1252
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: Damien Delautre
         Assigned To: Mark Proctor


When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:30:14 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Fri, 5 Oct 2007 10:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2073705.1191594614994.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Damien Delautre updated JBRULES-1252:
-------------------------------------

    Attachment: DrlDumper.patch

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Mark Proctor
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:32:03 2007
From: jira-events at lists.jboss.org (Ross McDonald (JIRA))
Date: Fri, 5 Oct 2007 10:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1066) equivalent of
 pooled-actors group functionality in mailnodes
Message-ID: <17576409.1191594724032.JavaMail.jira@cloud.prod.atl2.jboss.com>

equivalent of pooled-actors group functionality in mailnodes
------------------------------------------------------------

                 Key: JBPM-1066
                 URL: http://jira.jboss.com/jira/browse/JBPM-1066
             Project: JBoss jBPM
          Issue Type: Feature Request
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2,  jBPM jPDL 3.2.1
         Environment: any
            Reporter: Ross McDonald
         Assigned To: Tom Baeyens
            Priority: Minor


It would be nice to be able to specify a group to mail to within mail nodes, to save having to put semicolon separated actors in.  This would enable the database to control who is going to be emailed, and avoid the need to keep updating processes etc

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 10:54:03 2007
From: jira-events at lists.jboss.org (Francisco Reverbel (JIRA))
Date: Fri, 5 Oct 2007 10:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4519) The IIOP dependency
 on the old transaction needs removing
In-Reply-To: <2125312.1183572351674.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4756265.1191596043378.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4519?page=all ]

Francisco Reverbel closed JBAS-4519.
------------------------------------

    Resolution: Done

The hardcoded references to TxServerInterceptor have been removed from the CORBA servants in svn trunk. Now all three servants (the EJB3 one included) use the InboundTransactionCurrent SPI, which has been added to the integration project. The dependencies of the server-side tx interceptors (TxServerInterceptor and TxServerClientInterceptor) on DTM classes have also been removed, so that these interceptors can be used after the removal of the transaction module.

> The IIOP dependency on the old transaction needs removing
> ---------------------------------------------------------
>
>                 Key: JBAS-4519
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4519
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Adrian Brock
>         Assigned To: Francisco Reverbel
>             Fix For: JBossAS-5.0.0.GA
>
>
> The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 11:20:04 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Fri, 5 Oct 2007 11:20:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1233) Solver should
 use slf4j, like jbrms
In-Reply-To: <4568209.1191092801253.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22705001.1191597604385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1233?page=all ]

Geoffrey De Smet resolved JBRULES-1233.
---------------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done

Speed difference is minimal, maybe even better.

> Solver should use slf4j, like jbrms
> -----------------------------------
>
>                 Key: JBRULES-1233
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1233
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Solver
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>            Priority: Optional
>             Fix For: 4.0.2
>
>
> which can use log4j behind it

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:35:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:35:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1223) Concurrent problem
	in MVEL
In-Reply-To: <29709918.1190755901447.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2291185.1191602105395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1223?page=all ]

Mark Proctor closed JBRULES-1223.
---------------------------------

    Resolution: Done

no further help on reproducing this. So I'm closing until someone can reproduce the problem.

> Concurrent problem in MVEL
> --------------------------
>
>                 Key: JBRULES-1223
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1223
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>         Environment: Jboss 4.0.5 GA
>            Reporter: Ramses Gomez
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> java.util.ConcurrentModificationException: concurrent access to HashMap attempted by Thread[WorkManager(3)-6,5,JBoss Pooled Threads]
>         at java.util.HashMap.onExit(HashMap.java:217)
>         at java.util.HashMap.transfer(HashMap.java:514)
>         at java.util.HashMap.resize(HashMap.java:500)
>         at java.util.HashMap.addEntry(HashMap.java:800)
>         at java.util.HashMap.put(HashMap.java:441)
>         at org.mvel.AbstractParser._loadLanguageFeaturesByLevel(AbstractParser.java:1360)
>         at org.mvel.AbstractParser.setLanguageLevel(AbstractParser.java:1291)
>         at org.drools.rule.builder.dialect.mvel.MVELDialect.init(MVELDialect.java:127)
>         at org.drools.compiler.DialectRegistry.initAll(DialectRegistry.java:49)
>         at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:137)
>         at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:104)
>         at com.accenture.adsj.soa.spf.brp.BusinessRuleProcessor.createPackage(BusinessRuleProcessor.java:65)
>         at com.accenture.adsj.soa.spf.brp.BusinessRuleProcessor.getStatefulSession(BusinessRuleProcessor.java:53)
>         at com.accenture.adsj.soa.spf.brp.BusinessRuleProcessor.registerBO(BusinessRuleProcessor.java:115)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:35:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1212) Rete throws
 NoClassDefFoundError when asserting facts with classess loaded by
 inaccessible classloader.
In-Reply-To: <21352351.1190454754072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20371104.1191602104587.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1212?page=all ]

Mark Proctor closed JBRULES-1212.
---------------------------------

    Resolution: Done

not heard this isn't fixed, so closing now.

> Rete throws NoClassDefFoundError when asserting facts with classess loaded by inaccessible classloader. 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1212
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1212
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Alexander Gavrilov
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>         Attachments: ReteShadowProxyTest.java
>
>
> We using drools as part of security enfocement engine in our application, based on Tapestry4 framework. Tapestry4 pages and components is abstract classes with some abstract methods, for which tapestry generates implementation at runtime. For example, if i declare page 
> public abstract SomePage extends BasePage  {
> }
> Tapestry will generate class in default package like 
> public SomePage$_0 extends BasePage  {
> }
> On page loading whe using instantiated page objects ans Drools Facts to ensure, that current user has permissions to load this page. In the previos verions we used (3.0.6) all worked fine. After update to version 4.0.1 whe got the NoClassDefFoundError  when triyng to assert Page object into working memory. 
> This is becouse tapestry creates classes for pages in private classloader, which is child of the application classloader. When Drools tries to generate shadowing proxy for generated Page class it generate code like 
> public class SomePage$_0ShadowProxy extends SomePage$_0 {
> }
> Later, when it tries to load this class with MapBackedClassLoader, it can not find definition for class SomePage$_0 and throws NoClassDefFoundError. This type of error does not handled correctly by drools. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:35:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:35:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1217) RuleFlow Editor ->
 Constraint Editor -> Imports Editor context help
In-Reply-To: <20335396.1190661521138.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2253668.1191602105671.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1217?page=all ]

Mark Proctor closed JBRULES-1217.
---------------------------------

    Resolution: Done
      Assignee: Kris Verlaenen  (was: Mark Proctor)

I believe this is done now.

> RuleFlow Editor -> Constraint Editor -> Imports Editor context help
> -------------------------------------------------------------------
>
>                 Key: JBRULES-1217
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1217
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>         Environment: drools 4.0.1, OSX 10.4.10, Eclipse 3.3
>            Reporter: ekkehard gentz
>         Assigned To: Kris Verlaenen
>             Fix For: 4.0.2
>
>
> if you're using the eclipse RuleFlow Editor
> * opening Constraint editor
> ** then opening Imports editor
> the imports editor doesn't support context assist to find imports like the normal drl editor
> if you have a complex environment, then its very helpful to get context assist for import statements
> btw: the Constraint editor works well and supports context assist

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1213) Context assist in
 .drl when different to then
In-Reply-To: <564085.1190466911146.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16247662.1191602223813.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1213?page=all ]

Mark Proctor updated JBRULES-1213:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)
         Assignee: Kris Verlaenen  (was: Mark Proctor)

yes they use two different apis to achieve the code completion, its a lot of work to maintain both to the same level, this will have to be marked as a FUTURE for now.

> Context assist in .drl when different to then
> ---------------------------------------------
>
>                 Key: JBRULES-1213
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1213
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>         Environment: Drools 4.0.1, Eclipse 3.3, OSX 10.4.10
>            Reporter: ekkehard gentz
>         Assigned To: Kris Verlaenen
>             Fix For: FUTURE
>
>
> context assist in .drl editor has different behaviour in "when" section compared to "then"
> using drools examples
> StateExampleUsingSalience.drl
> when ... State.  only shows (), null
> doing the same in
> then... State. shows class, this, FINISHED, NOT_RUN
> because in many cases tests in the LHS are against constants it would be good to show them

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1173)
 java.lang.ArrayIndexOutOfBoundsException: 2 in file named
 "TupleIndexHashTable.java" in toArray() Method. I have fix and works fine.
In-Reply-To: <3665950.1189032371957.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4471900.1191602224090.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1173?page=all ]

Mark Proctor updated JBRULES-1173:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

no futher help on reproducing this problem, so marking as a FUTURE for now.

> java.lang.ArrayIndexOutOfBoundsException: 2 in file named "TupleIndexHashTable.java" in toArray() Method. I have fix and works fine.
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1173
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1173
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions:  4.0.0.MR3
>         Environment: windows XP
>            Reporter: Nageshwar Kunichetty
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> Sometimes while asserting specific facts I get the following exception in drools-core-4.0.0 :
> > java.lang.ArrayIndexOutOfBoundsException: 26
> >         at org.drools.util.TupleIndexHashTable.toArray(TupleIndexHashTable.java:178)
> >         at org.drools.reteoo.CollectNode.assertObject(CollectNode.java:212)
> >         at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:317)
> >         at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:183)
> >         at org.drools.reteoo.Rete.assertObject(Rete.java:121)
> >         at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1174) debug steps into
 "when" statement
In-Reply-To: <22684591.1189043771218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11096039.1191602224553.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1174?page=all ]

Mark Proctor closed JBRULES-1174.
---------------------------------

    Resolution: Done

will re-create if further problems found.

> debug steps into "when" statement 
> ----------------------------------
>
>                 Key: JBRULES-1174
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1174
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>            Reporter: Mark Proctor
>         Assigned To: Ahti Kitsik
>             Fix For: 4.0.2
>
>         Attachments: .log, moz-screenshot-44.jpg
>
>
> I've re-created where it stepped into the "when" part, although it seems to do it on random.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1163) Update ORG
 homepage to be more up to date with 4.0
In-Reply-To: <14396251.1188797970409.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21985987.1191602225096.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1163?page=all ]

Mark Proctor closed JBRULES-1163.
---------------------------------

    Resolution: Done

done as much as needed for now, so closing.

> Update ORG homepage to be more up to date with 4.0
> --------------------------------------------------
>
>                 Key: JBRULES-1163
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1163
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: 4.0.1
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:37:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1124) Code completion
 does not work for 'with' blocks
In-Reply-To: <28780786.1188006918343.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8508865.1191602225284.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1124?page=all ]

Mark Proctor closed JBRULES-1124.
---------------------------------

    Resolution: Done

will re-create if further problems found.

> Code completion does not work for 'with' blocks
> -----------------------------------------------
>
>                 Key: JBRULES-1124
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1124
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions:  4.0.0.GA
>            Reporter: Mark Proctor
>         Assigned To: Philippe Ombredanne
>             Fix For: 4.0.2
>
>         Attachments: withCodeCompletion.JPG
>
>
> code completion should work for 'with' blocks. We also use a macro to make 'with' work with the 'modify' keyword.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:39:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1138) MVEL code
 completion does not work for nested expressions
In-Reply-To: <8066703.1188217998377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24357163.1191602343901.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1138?page=all ]

Mark Proctor closed JBRULES-1138.
---------------------------------

    Resolution: Done

will re-create if further problems found.

> MVEL code completion does not work for nested expressions
> ---------------------------------------------------------
>
>                 Key: JBRULES-1138
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1138
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>            Reporter: Mark Proctor
>         Assigned To: Philippe Ombredanne
>             Fix For: 4.0.2
>
>         Attachments: screenshot-1.jpg, screenshot-2.jpg
>
>
> code completion does not work for parameters.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:39:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:39:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1235) Multiple Criteria
 break BRMS rule editor
In-Reply-To: <24987902.1191139841173.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22649526.1191602344845.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1235?page=all ]

Mark Proctor updated JBRULES-1235:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

> Multiple Criteria break BRMS rule editor
> ----------------------------------------
>
>                 Key: JBRULES-1235
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1235
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Ben Truitt
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>         Attachments: screenshot.jpeg, screenshot1.jpeg, screenshot2.jpeg, screenshot3.jpeg
>
>
> In the BRMS - when creating a brl asset - more than one criteria causes the interface to not work properly.
> Two ways to trigger:
> 1) Under the fact, choose "All of (AND)", then add two criteria - adding the second is the bug
> 2) Under the fact, add one criteria, then use the '+' icon to add another - adding the second is the bug.
> I'll attach screenshots, which should help explain.
> Sorry if this is a dupe - I looked, but didn't find anything like 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

        


From jira-events at lists.jboss.org  Fri Oct  5 12:39:07 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 12:39:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11165403.1191602347331.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Mark Proctor updated JBRULES-1247:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:01:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Fri, 5 Oct 2007 13:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
In-Reply-To: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1239652.1191603663667.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1065?page=all ]

Ronald van Kuijk resolved JBPM-1065.
------------------------------------

    Resolution: Won't Fix

The last remark of David is true. But these 'errors' also appear in seam apps etc.. so personally I'd close this issue and mark it as 'won't fix' At least not in jBPM (if JBoss AS provides something for this, it's fine) 

> com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1065
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>         Environment: soa-standalone.zip (oct 1 2007) 
> RHEL5 
> java 
> version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>            Reporter: Len DiMaggio
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> These errors are reported when the jBPM console is accessed - the console seems to run however.
> 10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
> 10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
> 10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
> 10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
> 10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
> 10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
> 10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
> 10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
> 10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
> 10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
> 10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
> 10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
> 10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
> 10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
> 10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:01:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Fri, 5 Oct 2007 13:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBPM-1065)
 com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported
 when jBPM console is accessed
In-Reply-To: <16200871.1191546303408.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4227516.1191603663817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1065?page=all ]

Ronald van Kuijk closed JBPM-1065.
----------------------------------


n/t

> com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors reported when jBPM console is accessed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1065
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1065
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>         Environment: soa-standalone.zip (oct 1 2007) 
> RHEL5 
> java 
> version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
>            Reporter: Len DiMaggio
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> These errors are reported when the jBPM console is accessed - the console seems to run however.
> 10:31:47,121 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
> 10:31:47,142 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
> 10:31:47,173 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl.taglib.xml
> 10:31:47,186 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf-compat.taglib.xml
> 10:31:47,971 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-data.taglib.xml
> 10:31:47,992 ERROR [STDERR] Oct 2, 2007 10:31:47 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/identity.taglib.xml
> 10:31:48,030 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
> 10:31:48,036 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tfl-compat.taglib.xml
> 10:31:48,058 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-action.taglib.xml
> 10:31:48,064 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-nav.taglib.xml
> 10:31:48,074 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
> 10:31:48,103 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
> 10:31:48,109 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/tf.taglib.xml
> 10:31:48,163 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-simple.taglib.xml
> 10:31:48,211 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/jbpm4jsf.jar!/META-INF/core.taglib.xml
> 10:31:48,226 ERROR [STDERR] Oct 2, 2007 10:31:48 AM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
> INFO: Added Library from: jar:file:/opt/SOA-standalone/server/default/tmp/deploy/tmp47297jbpm-console-exp.war/WEB-INF/lib/gravel.jar!/META-INF/gravel-compat.taglib.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:46:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 5 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-81) Identity Trust
 context should handle security domain also
Message-ID: <17880822.1191606363435.JavaMail.jira@cloud.prod.atl2.jboss.com>

Identity Trust context should handle security domain also
---------------------------------------------------------

                 Key: SECURITY-81
                 URL: http://jira.jboss.com/jira/browse/SECURITY-81
             Project: JBoss Security and Identity Management
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JBossSX
    Affects Versions: 2.0.1-BETA1
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-BETA2


ITC can handle a security context that belongs to a different security domain.

Hence ITC needs to know the sec domain for the Identity Trust Manager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 13:46:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 5 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-81) Identity Trust
 context should handle security domain also
In-Reply-To: <17880822.1191606363435.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15794214.1191606363549.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-81?page=all ]

Anil Saldhana updated SECURITY-81:
----------------------------------

    Component/s: Security SPI

> Identity Trust context should handle security domain also
> ---------------------------------------------------------
>
>                 Key: SECURITY-81
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-81
>             Project: JBoss Security and Identity Management
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.1-BETA1
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-BETA2
>
>
> ITC can handle a security context that belongs to a different security domain.
> Hence ITC needs to know the sec domain for the Identity Trust Manager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 14:39:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 14:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1220) Integration
 with jBPM does not work
In-Reply-To: <6567124.1190714261119.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9785515.1191609543323.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1220?page=comments#action_12380802 ] 
            
Mark Proctor commented on JBRULES-1220:
---------------------------------------

Have you verified the global resolver it is using is the jbpm one, and that it hasn't lost the configuration and gone back to the drools default?

> Integration with jBPM does not work
> -----------------------------------
>
>                 Key: JBRULES-1220
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1220
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
> 		workingMemory.setGlobalResolver(new GlobalResolver() {
> 			private static final long serialVersionUID = 1L;
> 			public Object resolveGlobal(String identifier) {
> 				System.out.println("!!!!!!!!!! resolve " + identifier);
> 				return ci.getVariable(identifier);
> 			}
> 			public void setGlobal(String identifier, Object value) {
> 				System.out.println("!!!!!!!!!! set " + identifier);
> 				ci.setVariable(identifier, value);
> 			}
> 		});
> And a rule file that serves as test
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> The output of the test is as expected
> 11:50:51,226 INFO  [STDOUT] !!!!!!!!!! resolve shipper
> 11:50:51,227 INFO  [STDOUT] None
> 11:50:51,227 INFO  [STDOUT] !!!!!!!!!! set shipper
> 11:50:51,227 INFO  [STDOUT] ship via FEDX 
> But if we modify the rule file to
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		eval ("None".equals(shipper))
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> then nothing is printed - no attempt to resolve shipper global variable

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 14:52:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 14:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29452760.1191610323581.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

    Fix Version/s: 4.0.2

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 14:58:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 5 Oct 2007 14:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
Message-ID: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>

GenericHeaderAuthenticator injection of ssoid, sessioncookie name
-----------------------------------------------------------------

                 Key: JBAS-4804
                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Anil Saldhana
         Assigned To: Stefan Guilhen
             Fix For: JBossAS-4.2.3.GA


http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication


Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.

Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 15:14:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 5 Oct 2007 15:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
Message-ID: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>

DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
---------------------------------------------------------------

                 Key: JBCACHE-1194
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.4.1.SP5
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
            Priority: Critical
             Fix For: 1.4.1.SP6


It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4726.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 15:14:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 5 Oct 2007 15:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
In-Reply-To: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22237429.1191611644381.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1194?page=comments#action_12380810 ] 
            
Brian Stansberry commented on JBCACHE-1194:
-------------------------------------------

JBC trunk uses GroupRequest.GET_ALL.

> DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
> ---------------------------------------------------------------
>
>                 Key: JBCACHE-1194
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6
>
>
> It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4726.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 15:14:08 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 5 Oct 2007 15:14:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
In-Reply-To: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18749215.1191611648551.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1194?page=all ]

Brian Stansberry updated JBCACHE-1194:
--------------------------------------

    Description: It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4766.  (was: It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4726.)

> DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
> ---------------------------------------------------------------
>
>                 Key: JBCACHE-1194
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6
>
>
> It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4766.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 18:20:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 5 Oct 2007 18:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1220) Integration with
 jBPM does not work
In-Reply-To: <6567124.1190714261119.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29607097.1191622803278.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1220?page=all ]

Mark Proctor closed JBRULES-1220.
---------------------------------

    Resolution: Rejected

You cannot set the global resolver AFTER the facts have been inserted, it must be done before.

> Integration with jBPM does not work
> -----------------------------------
>
>                 Key: JBRULES-1220
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1220
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2
>
>
> We had a code that intgrates JBoss Rules Global Resolver with jBPM variable pool
> 		workingMemory.setGlobalResolver(new GlobalResolver() {
> 			private static final long serialVersionUID = 1L;
> 			public Object resolveGlobal(String identifier) {
> 				System.out.println("!!!!!!!!!! resolve " + identifier);
> 				return ci.getVariable(identifier);
> 			}
> 			public void setGlobal(String identifier, Object value) {
> 				System.out.println("!!!!!!!!!! set " + identifier);
> 				ci.setVariable(identifier, value);
> 			}
> 		});
> And a rule file that serves as test
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> The output of the test is as expected
> 11:50:51,226 INFO  [STDOUT] !!!!!!!!!! resolve shipper
> 11:50:51,227 INFO  [STDOUT] None
> 11:50:51,227 INFO  [STDOUT] !!!!!!!!!! set shipper
> 11:50:51,227 INFO  [STDOUT] ship via FEDX 
> But if we modify the rule file to
> package org.jbpm.action
>  
> import org.jbpm.resolveraction.Customer;
> import org.jbpm.resolveraction.Order;
> import org.jbpm.context.exe.ContextInstance;
> global java.lang.String shipper
> rule "Determine Shipper"
> 	when
> 		eval ("None".equals(shipper))
> 		Customer( region >= 1 )
> 		Order( totalAmount >= 0 )
> 	then
> 		System.out.println(shipper);
> 		drools.getWorkingMemory().setGlobal( "shipper", "FEDX" );
> 		System.out.println("ship via FEDX " );
> end
> then nothing is printed - no attempt to resolve shipper global variable

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 19:53:06 2007
From: jira-events at lists.jboss.org (s b (JIRA))
Date: Fri, 5 Oct 2007 19:53:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1067)
 token.getAvailableTransitions()
 -- need equivalent that returns ordered list.
Message-ID: <14222518.1191628386527.JavaMail.jira@cloud.prod.atl2.jboss.com>

token.getAvailableTransitions() -- need equivalent that returns ordered list.
-----------------------------------------------------------------------------

                 Key: JBPM-1067
                 URL: http://jira.jboss.com/jira/browse/JBPM-1067
             Project: JBoss jBPM
          Issue Type: Feature Request
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
         Environment: All OS
            Reporter: s b
         Assigned To: Tom Baeyens


This feature request is requesting:

1)  API which adds a version of token.getAvailableTransitions() which returns an ordered List that preserves the order of the transitions as defined in the processdefinition.xml file for the node, rather than returning an unordered Set object. 

2)  Also request that TaskInstance.getAvailableTransitions() be modified to return an ordered list rather than a randomly ordered list by calling the new method.

For example:

------------------------
public class TaskInstance extends VariableContainer implements Assignable {

...

public List getAvailableTransitions() {
    List transitions = null;
    if ( (! isLast())
         && (token!=null)
       ) {
      transitions = token.getAvailableTransitionsList(); // using new method
    }
    return transitions;
  }

...

----------------------------------------

Problem:

node.getLeavingTransitions() appears to preserve the order, but the order is apparently lost when the transistions are added to the Set which is returned by token.getAvailableTransitions(). 

Preserving the ordering is highly useful when implementing a minimal data-driven interface which presents the user with the transitions to choose from. The designer could exercise some control over the presentation of the choices if only the order were preserved as defined in the processdefinition.xml file. 

Solution:

Make a clone of "token.getAvailableTransitions()", name it "token.getAvailableTransitionsList()", and add the filtered transitions to a List instead of to a Collection, and return the list.  Make sure the order is preserved the same as the transitions were defined in the "processdefinition.xml" file.

Modify "TaskInstance.getAvailableTransitions()" to call token.getAvailableTransitionsList().

Summary:

Although workarounds exist with existing code, it would be very helpful (and consistent I think) to provide an API that retrieves a list of the "available transitions" that is ordered as defined in the processdefinition.xml file instead of an unordered Set or List as is currently available.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct  5 22:05:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 5 Oct 2007 22:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
Message-ID: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>

drools-examples-drl  does not work under Java 6 as-is
-----------------------------------------------------

                 Key: JBRULES-1253
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
    Affects Versions: 4.0.2
         Environment: Eclipse 3.2.2, at least XP (possibly others)
            Reporter: Justin Wick
         Assigned To: Mark Proctor
            Priority: Blocker


The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 00:01:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Sat, 6 Oct 2007 00:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
In-Reply-To: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12654649.1191643263344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1253?page=all ]

Fernando Meyer updated JBRULES-1253:
------------------------------------

    Assignee: Philippe Ombredanne  (was: Mark Proctor)
    Priority: Optional  (was: Blocker)

Hey Philipe, could you please check if is possible have a generic JRE configuration for eclipse projects ?

> drools-examples-drl  does not work under Java 6 as-is
> -----------------------------------------------------
>
>                 Key: JBRULES-1253
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2.2, at least XP (possibly others)
>            Reporter: Justin Wick
>         Assigned To: Philippe Ombredanne
>            Priority: Optional
>
> The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 18:36:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 18:36:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21217433.1191710164021.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal reopened JBREM-687:
-----------------------------

             
Want to make this fix available in 2.2.2.SP2 (and possible 2.2.2.GA_CP01).

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 18:36:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 18:36:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2642655.1191710164173.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal updated JBREM-687:
----------------------------

    Fix Version/s: 2.2.2.SP2
                   2.2.2.GA_CP01

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 18:41:05 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 18:41:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24464869.1191710465444.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12380853 ] 
            
Ron Sigal commented on JBAS-4704:
---------------------------------

I've created a new release, 2.2.2.SP2, targeted for the next release of community AS 4.2.x (which looks like 4.2.3) and I've reopened JBREM-687 and added 2.2.2.SP2 as a fix version.

Two questions: 

1)  What is the time frame for the release of AS 4.2.3, and

2)  Does anyone know if this problem has ever appeared in a support case?  If so, I'll target the fix for a CP release as well.

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct  6 20:30:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sat, 6 Oct 2007 20:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-809) Verify that the
 behavior of the
 HTTPUnMarshaller re stripping CR and LF characters is correct
In-Reply-To: <4580360.1190730941269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12758501.1191717003335.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-809?page=comments#action_12380855 ] 
            
Ron Sigal commented on JBREM-809:
---------------------------------

I think the appropriate solution is to make the behavior (to include or not include the CR/LF characters) configurable, with the current behavior the default.

> Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBREM-809
>                 URL: http://jira.jboss.com/jira/browse/JBREM-809
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.SP1
>            Reporter: Tom Fennelly
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> At the moment, the HTTPUnMarshaller uses a BufferedReader to read a HTTP char stream.  This causes it to modify the message payload by removing the CR and LF characters.  This causes a problem for us on the ESB because it means that signature checks fail on signed SOAP messages since the sig was generated from the message containing the CR and LF chars.  It's even worse than that... it actually corrupts the signature within the message because the canonical form of the sig contains CRLF chars.
> We got around this in the ESB (in the short term) by setting our own modified version of the HTTPUnMarshaller - one that doesn't use a BufferedReader.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 02:05:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sun, 7 Oct 2007 02:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-816) Add instructions to
 Remoting Guide for overriding a transport or create a new transport
Message-ID: <10644669.1191737103385.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add instructions to Remoting Guide for overriding a transport or create a new transport
---------------------------------------------------------------------------------------

                 Key: JBREM-816
                 URL: http://jira.jboss.com/jira/browse/JBREM-816
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP1
            Reporter: Ron Sigal
         Assigned To: Trustin Lee
            Priority: Minor
             Fix For: 2.4.0.CR1 (Pinto)


Client and server invokers are created by the org.jboss.remoting.InvokerRegistry class, which will look for classes called TransportClientFactory and TransportServerFactory in the directory org/jboss/remoting/transport/<transport> and use them to create client and server invokers for the <transport> transport.

The current discussion of this facility in the Remoting Guide is rather brief.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 02:25:17 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Sun, 7 Oct 2007 02:25:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4456) Replace
 JRMPProxyService with a remoting based bean.
In-Reply-To: <33088772.1180642388459.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8650810.1191738317063.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4456?page=comments#action_12380870 ] 
            
Ron Sigal commented on JBAS-4456:
---------------------------------

>From Jay Howell:

Customers have
asked for a way to select the host name by the incoming client name.
For instance, if the incoming client address is 10.12.15.x, then I want
this client to use this host name for contacting the server.  They would
also like selection based on the domain name of the client. 

> Replace JRMPProxyService with a remoting based bean.
> ----------------------------------------------------
>
>                 Key: JBAS-4456
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4456
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> We need a pojo component that generates aop remoting proxies given a target and exposed interfaces, client aspects.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 10:12:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 10:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1254)
 drools-repository/jbrms should
 not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
Message-ID: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>

drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
-----------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1254
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
            Reporter: Geoffrey De Smet
         Assigned To: Mark Proctor
             Fix For: 4.0.2


log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
In examples you'll probably want to make them runtime scoped.

slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.

See drools-repository/pom.xml where I 've commented what I propose to change:
 <dependency>
          <groupId>org.slf4j</groupId>
          <artifactId>slf4j-api</artifactId>
        </dependency>
        <dependency>
          <groupId>org.slf4j</groupId>
          <artifactId>slf4j-log4j12</artifactId>
          <scope>test</scope>
        </dependency>
        <dependency>
          <groupId>log4j</groupId>
          <artifactId>log4j</artifactId>
          <scope>test</scope>
        </dependency>


-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 11:54:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 11:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
In-Reply-To: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5839708.1191772443347.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1253?page=all ]

Mark Proctor updated JBRULES-1253:
----------------------------------

    Fix Version/s: 4.0.2

> drools-examples-drl  does not work under Java 6 as-is
> -----------------------------------------------------
>
>                 Key: JBRULES-1253
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2.2, at least XP (possibly others)
>            Reporter: Justin Wick
>         Assigned To: Philippe Ombredanne
>            Priority: Optional
>             Fix For: 4.0.2
>
>
> The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 11:56:08 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 11:56:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1255) add alternating
 coloured rows
 for rule analysis reporting and allow for user provided css
Message-ID: <17212584.1191772568224.JavaMail.jira@cloud.prod.atl2.jboss.com>

add alternating coloured rows for rule analysis reporting and allow for user provided css
-----------------------------------------------------------------------------------------

                 Key: JBRULES-1255
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1255
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Mark Proctor
         Assigned To: Fernando Meyer
             Fix For: 4.0.2


Mark the rows in the table alternate, use a nice software light pastel colour - like green or prink. Use a CSS to declare style so users can provide alternative css.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 11:58:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 11:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1256) publish source
	jars with maven
Message-ID: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>

publish source jars with maven
------------------------------

                 Key: JBRULES-1256
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Mark Proctor
         Assigned To: Fernando Meyer
             Fix For: 4.0.2


While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 12:05:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 12:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10244122.1191773103639.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 12:07:07 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 12:07:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1254)
 drools-repository/jbrms should
 not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13773732.1191773227659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=all ]

Mark Proctor updated JBRULES-1254:
----------------------------------

    Assignee: Michael Neale  (was: Mark Proctor)

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 13:02:10 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 13:02:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1256) publish source
 jars with maven
In-Reply-To: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3698494.1191776530718.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1256?page=comments#action_12380874 ] 
            
Geoffrey De Smet commented on JBRULES-1256:
-------------------------------------------

I am pretty sure I 've solved this, after the 4.0.1 release:

Look into the parent pom, for these sections:

       <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-source-plugin</artifactId>
          <version>2.0.2</version>
	        <executions>
	          <execution>
	            <goals>
	              <goal>jar</goal>
                  <goal>test-jar</goal>
	            </goals>
	          </execution>
	        </executions>
        </plugin>

    <plugins>
        <plugin>
          <!-- Entry needed to create, install and deploy sources jars -->
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-source-plugin</artifactId>
        </plugin>
    </plugins>

> publish source jars with maven
> ------------------------------
>
>                 Key: JBRULES-1256
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 13:02:10 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 13:02:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1256) publish source
 jars with maven
In-Reply-To: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19202243.1191776530871.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1256?page=comments#action_12380875 ] 
            
Geoffrey De Smet commented on JBRULES-1256:
-------------------------------------------

btw, AFAIK there's no cmd line switch to do this, only pom configuration :)

> publish source jars with maven
> ------------------------------
>
>                 Key: JBRULES-1256
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 13:12:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 7 Oct 2007 13:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1254)
 drools-repository/jbrms
 should not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25796200.1191777123280.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=comments#action_12380876 ] 
            
Geoffrey De Smet commented on JBRULES-1254:
-------------------------------------------

it looks like jbrms is also used straight out of the box, as a war.
And not just extended by a company x's war, who will want to choose their logging implementation.

In the first case, they will want an out of the box logging implementation,
so you might want to make
slf4j-log4j12 and log4j scope "runtime" and optional "true".
This means they will be included in the "standalone jbrms war", but by default excluded if company x extends the jbrms war (and allow company x to choose their logging implementation).

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: 4.0.2
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 15:05:05 2007
From: jira-events at lists.jboss.org (Nicolas Doye (JIRA))
Date: Sun, 7 Oct 2007 15:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4491) Server startup
 failure with JDK 1.6
In-Reply-To: <30746220.1182198611683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14481850.1191783905064.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12380878 ] 
            
Nicolas Doye commented on JBAS-4491:
------------------------------------

Another data point - this issue is also there with JDK 6 on Linux. (All other reporters mention versions of Windows).

> Server startup failure with JDK 1.6
> -----------------------------------
>
>                 Key: JBAS-4491
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4491
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: Windows
>            Reporter: Greg Zoller
>         Attachments: Signature.java
>
>
> An out-of-the-box installation of JBoss 5.0.0 Beta2 running with JDK 1.6 produces the following exception upon startup.  Not sure the whys or wherefores but am pretty sure its not a good thing.
> 13:24:13,467 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
> 13:24:13,467 INFO  [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017)
> 13:24:13,467 INFO  [ServerImpl] Home Dir: C:\Program Files\jboss-5.0.0.Beta2
> 13:24:13,467 INFO  [ServerImpl] Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/
> 13:24:13,467 INFO  [ServerImpl] Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/lib/
> 13:24:13,467 INFO  [ServerImpl] Patch URL: null
> 13:24:13,467 INFO  [ServerImpl] Server Name: default
> 13:24:13,467 INFO  [ServerImpl] Server Home Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:13,467 INFO  [ServerImpl] Server Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/
> 13:24:13,467 INFO  [ServerImpl] Server Data Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\data
> 13:24:13,467 INFO  [ServerImpl] Server Temp Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\tmp
> 13:24:13,467 INFO  [ServerImpl] Server Config URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/
> 13:24:13,467 INFO  [ServerImpl] Server Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/lib/
> 13:24:13,467 INFO  [ServerImpl] Root Deployment Filename: jboss-service.xml
> 13:24:13,499 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml
> 13:24:14,831 INFO  [ProfileImpl] Using profile root:C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:15,913 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter state=Described
> java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125)
> 	at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292)
> 	at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138)
> 	at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280)
> 	at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
> 	at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
> 	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
> 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
> 	at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBootstrap.java:295)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:222)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at java.net.URLClassLoader$1.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170)
> 	... 35 more
> 13:24:16,258 INFO  [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
> 13:24:16,305 INFO  [JMXKernel] Legacy JMX core initialized
> Failed to boot JBoss:
> java.lang.RuntimeException: Exception during Bootstrap
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
> VFSBootstrapScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeployerScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeploymentScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> *** CONTEXTS IN ERROR: Name -> Error
> DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileServiceBootstrap.java:389)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	... 5 more

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct  7 23:59:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 7 Oct 2007 23:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1257) Add Banking
 Example from John Dunning
Message-ID: <21119646.1191815943276.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add Banking Example from John Dunning
-------------------------------------

                 Key: JBRULES-1257
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1257
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2


John Dunny has blogged a nice banking tutorial at:
http://web.mac.com/johndunning/Life_on_a_Laptop/Drools/Entries/2007/10/7_Banking_on_DROOLS.html
And has kindly given us permission to add it to the manual.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 02:05:04 2007
From: jira-events at lists.jboss.org (Vt Ysh (JIRA))
Date: Mon, 8 Oct 2007 02:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1068) Possibility of
 UITaskFormButtonBase to use child action tags such as it done with
 h:commandButton
Message-ID: <20958100.1191823504155.JavaMail.jira@cloud.prod.atl2.jboss.com>

Possibility of UITaskFormButtonBase to use child action tags such as it done with h:commandButton
-------------------------------------------------------------------------------------------------

                 Key: JBPM-1068
                 URL: http://jira.jboss.com/jira/browse/JBPM-1068
             Project: JBoss jBPM
          Issue Type: Feature Request
          Components: Web Interface
    Affects Versions:  jBPM jPDL 3.2.1
            Reporter: Vt Ysh
         Assigned To: Tom Baeyens
            Priority: Optional


If i am trying to put custom action tags between for example <tf:saveButton value="Save"></tf:saveButton > such as it can be done with h:commandButton i am getting NullPointer exception with the next stack trace:

java.lang.NullPointerException
        at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.getEnclosingForm(UITask
FormButtonBase.java:30)
        at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.addActionListener(UITas
kFormButtonBase.java:44)
        at org.jbpm.jsf.core.handler.AbstractHandler.apply(AbstractHandler.java:
64)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH
andler.java:314)
        at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java
:169)
        at com.sun.facelets.tag.ui.DefineHandler.apply(DefineHandler.java:58)
        at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j
ava:128)
        at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(Def
aultFaceletContext.java:306)
        at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(Default
FaceletContext.java:279)
        at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at test.facelets.IfHandler.apply(IfHandler.java:33)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav
a:49)
        at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa
ndler.java:47)
        at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:
25)
        at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)

        at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)

        at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)

        at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFac
eletContext.java:143)
        at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j
ava:113)
        at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav
a:49)
        at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:
25)
        at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
        at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java
:503)
        at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav
a:546)
        at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrap
per.java:178)
        at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha
se.java:106)
        at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
        at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
        at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi
lter.java:96)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:202)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit
yAssociationValve.java:175)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:74)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
        at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
kerThread.java:112)
        at java.lang.Thread.run(Thread.java:595)

Seems that problem can be in HtmlCommandButton.getParent() method. Is there any suggestions how to fix this issue?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 04:03:03 2007
From: jira-events at lists.jboss.org (Tim McCune (JIRA))
Date: Mon, 8 Oct 2007 04:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (HIBERNATE-73) @OneToOne with
 @PrimaryKeyJoinColumn does not work right
Message-ID: <20389741.1191830583574.JavaMail.jira@cloud.prod.atl2.jboss.com>

@OneToOne with @PrimaryKeyJoinColumn does not work right
--------------------------------------------------------

                 Key: HIBERNATE-73
                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-73
             Project: Hibernate
          Issue Type: Bug
         Environment: JBoss 4.2.1
            Reporter: Tim McCune
         Assigned To: Steve Ebersole


Given the following code:

@Entity
public class Employee {
  @Id Integer id;
    
  @OneToOne @PrimaryKeyJoinColumn
  EmployeeInfo info;
  ...
}

@Entity
 public class EmployeeInfo {
   @Id Integer id;
        ...
}

Hibernate creates EMPLOYEE and EMPLOYEEINFO tables, but does not create a foreign key relationship from EMPLOYEEINFO to EMPLOYEE.

Furthermore, Hibernate does not set the EmployeeInfo's id correctly when persisting it.  The following code:

EmployeeInfo info = new EmployeeInfo();
employee.setInfo(info);

does insert a new row into EMPLOYEEINFO, but it has an id of "1" when it should have an id that is the same as the corresponding Employee.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 05:19:09 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 8 Oct 2007 05:19:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1069) Include common-io and
 common-fileupload in the ear configuration
Message-ID: <22824913.1191835149906.JavaMail.jira@cloud.prod.atl2.jboss.com>

Include common-io and common-fileupload in the ear configuration
----------------------------------------------------------------

                 Key: JBPM-1069
                 URL: http://jira.jboss.com/jira/browse/JBPM-1069
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
            Reporter: Fady Matar
         Assigned To: Tom Baeyens
            Priority: Trivial
             Fix For: jBPM 3.3


Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file)

The ear files can be appended to the JBoss AS configuration or can be packaged within the ear

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 05:25:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 8 Oct 2007 05:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1734) "edit mode"
 could be checked for authorization
Message-ID: <4615781.1191835503517.JavaMail.jira@cloud.prod.atl2.jboss.com>

"edit mode" could be checked for authorization
----------------------------------------------

                 Key: JBPORTAL-1734
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1734
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Julien Viet
             Fix For: 2.8 Final


An admin should be able to define which roles have access to the edit mode for a particular portlet.

Since it would break backward compatibility, it has to be part of a major release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:17:10 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 06:17:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-209) Trim string
	value
Message-ID: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>

Trim string value
-----------------

                 Key: JBMICROCONT-209
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: MetaData
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta5


In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:17:10 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 06:17:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-209) Trim string
	value
In-Reply-To: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26879124.1191838630537.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-209?page=all ]

Ales Justin resolved JBMICROCONT-209.
-------------------------------------

    Resolution: Done

You can now set trim=true|false on property or parameter.

> Trim string value
> -----------------
>
>                 Key: JBMICROCONT-209
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: MetaData
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:22:19 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 8 Oct 2007 06:22:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1059) Return a
 business interface from a home create method must not be allowed
Message-ID: <30915920.1191838939062.JavaMail.jira@cloud.prod.atl2.jboss.com>

Return a business interface from a home create method must not be allowed
-------------------------------------------------------------------------

                 Key: EJBTHREE-1059
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1059
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


EJB 3 4.6.8: The return type for a create<METHOD> method must be the session bean's remote interface type.

Using the proxy as if it would be an EJBObject results in class cast exceptions.

java.lang.ClassCastException: $Proxy9
	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject(RemoteUnitTestCase.java:208)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 8 Oct 2007 06:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1055)
 WebServiceContext is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18011799.1191839043270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf resolved EJBTHREE-1055.
-------------------------------------

    Resolution: Done

Resurrected the old injection code

> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:25:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 8 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1059) Return a
 business interface from a home create method must not be allowed
In-Reply-To: <30915920.1191838939062.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21690070.1191839103970.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1059?page=all ]

Carlo de Wolf updated EJBTHREE-1059:
------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091956

> Return a business interface from a home create method must not be allowed
> -------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1059
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1059
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>
> EJB 3 4.6.8: The return type for a create<METHOD> method must be the session bean's remote interface type.
> Using the proxy as if it would be an EJBObject results in class cast exceptions.
> java.lang.ClassCastException: $Proxy9
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject(RemoteUnitTestCase.java:208)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 06:58:03 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 06:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-210) Change
 KernelBus implementation
Message-ID: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>

Change KernelBus implementation
-------------------------------

                 Key: JBMICROCONT-210
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
             Project: JBoss MicroContainer
          Issue Type: Task
          Components: Kernel
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta5


Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:00:08 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 8 Oct 2007 07:00:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-210) Change
 KernelBus implementation
In-Reply-To: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15388928.1191841208044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-210?page=all ]

Ales Justin resolved JBMICROCONT-210.
-------------------------------------

    Resolution: Done

Changed BasicKernelBus to check for installed contexts.
Added BeanKernelRegistryEntry which implements AttributeDispatchContext.

> Change KernelBus implementation
> -------------------------------
>
>                 Key: JBMICROCONT-210
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
> Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:11:13 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 8 Oct 2007 07:11:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-560) Message greater
 than 16286 bytes is not received on MaxOS
In-Reply-To: <2848013.1184741447091.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32018620.1191841873081.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-560?page=comments#action_12380916 ] 
            
Manik Surtani commented on JGRP-560:
------------------------------------

While Jason's fix above does work, keep in mind that *some* OS X updates reset MTU settings for lo0!  Something I just noticed.  

> Message greater than 16286 bytes is not received on MaxOS
> ---------------------------------------------------------
>
>                 Key: JGRP-560
>                 URL: http://jira.jboss.com/jira/browse/JGRP-560
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> I'm new to JGroups, and I have a Mac OS X (10.4)-specific question. I've used
> JGroups 2.4.1sp3, 2.5.0CR1, and the new 2.5.0GA - I see the same issue with
> all versions.
> I've noticed that, for UDP, there seems to be a max message size of 16286
> bytes (a little less than 16K). This is using the default udp.xml config,
> and just a simple message to another node like:
> JChannel ch = new JChannel("udp.xml");
> ch.setReceiver(this);
> ch.connect("TEST");		
> //
> // 'target' is another group member besides myself
> //
> byte[] buf = new byte[size];
> Arrays.fill(buf, (byte)77);
> echo("Sending message: " + size + " bytes");
> Message msg = new Message(target, null, buf);
> ch.send(msg);
> A receiver node will NOT receive the message if 'size' is greater than
> 16286. In fact, after sending a too-large message, the receiver sees no
> message trafffic so it starts doing heartbeats and view changes). I've
> attached some debug output below.
> TCP transport does not have this problem.
> I'm aware of the tos="8" attribute warning in OS X, and changing the value
> to 0 to avoid the warning doesn't affect the max size issue. Though perhaps
> it's the same Mac quirk causing both problems...
> I've searched around, but haven't seen anything about this. Is it a known
> issue? Is there a workaround? Am I doing something wrong?
> Thanks in advance,
> Rick Pike
> Debug output:
> -------------------------
> SENDER:
> (Sends increasing size messages, 2 sec apart. As soon as the size goes
> beyond 16286, it notices a problem).
> Sending message: 16284 bytes
> Sending message: 16285 bytes
> Sending message: 16286 bytes
> 2007-07-17 12:06:25,934 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51607 (own address=192.168.2.71:51610)
> 2007-07-17 12:06:25,936 [DEBUG] FD received ack from 192.168.2.71:51607
> Sending message: 16287 bytes
> Sending message: 16288 bytes
> RECEIVER:
> (Gets messages OK until 16287. I assume FD starts because it sees no message
> traffic.)
> Received message: 16284 bytes
> Received message: 16285 bytes
> Received message: 16286 bytes
> 2007-07-17 12:06:25,876 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51610 (own address=192.168.2.71:51607)
> 2007-07-17 12:06:25,884 [DEBUG] FD received ack from 192.168.2.71:51610
> 2007-07-17 12:06:29,305 [DEBUG] MERGE2
> initial_mbrs=[[own_addr=192.168.2.71:51610, coord_addr=192.168.2.71:51607,
> is_server=true], [own_addr=192.168.2.71:51607,
> coord_addr=192.168.2.71:51607, is_server=true]]
> 2007-07-17 12:06:35,877 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51610 (own address=192.168.2.71:51607)
> 2007-07-17 12:06:35,880 [DEBUG] FD received ack from 192.168.2.71:51610
> 2007-07-17 12:06:42,496 [DEBUG] MERGE2
> initial_mbrs=[[own_addr=192.168.2.71:51610, coord_addr=192.168.2.71:51607,
> is_server=true], [own_addr=192.168.2.71:51607,
> coord_addr=192.168.2.71:51607, is_server=true]]
> 2007-07-17 12:06:45,879 [DEBUG] FD sending are-you-alive msg to
> 192.168.2.71:51610 (own address=192.168.2.71:51607)
> 2007-07-17 12:06:45,880 [DEBUG] FD received ack from 192.168.2.71:51610
> 2007-07-17 12:06:50,453 [DEBUG] FD_SOCK peer closed socket normally
> 2007-07-17 12:06:50,453 [DEBUG] FD_SOCK pinger thread terminated

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:52:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 07:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
Message-ID: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>

Message headers not preserved on bridged message
------------------------------------------------

                 Key: JBMESSAGING-1098
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 07:58:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 07:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1097) Cleaning JBM
 Tables During Startup
In-Reply-To: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28312464.1191844683348.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1097?page=all ]

Tim Fox updated JBMESSAGING-1097:
---------------------------------

    Fix Version/s: Unscheduled
                       (was: 1.4.0.SP1)
         Priority: Minor  (was: Major)

> Cleaning JBM Tables During Startup
> ----------------------------------
>
>                 Key: JBMESSAGING-1097
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.GA
>         Environment: JBossAS-4.2.0-GA
> JBossMessaging-1.4.0-GA
>            Reporter: Tyronne Wickramarathne
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 08:00:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 08:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1097) Cleaning
 JBM Tables During Startup
In-Reply-To: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24602892.1191844803380.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1097?page=comments#action_12380926 ] 
            
Tim Fox commented on JBMESSAGING-1097:
--------------------------------------

Can you explain what the motivation for this is?

If you don't want messages to survive server shutdown/startup then maybe you should be using non persistent messages, not persistent messages?

> Cleaning JBM Tables During Startup
> ----------------------------------
>
>                 Key: JBMESSAGING-1097
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.GA
>         Environment: JBossAS-4.2.0-GA
> JBossMessaging-1.4.0-GA
>            Reporter: Tyronne Wickramarathne
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 08:00:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 08:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22070410.1191844803764.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox closed JBMESSAGING-1098.
--------------------------------

    Resolution: Done

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:40:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 09:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3142) Add UnifiedInvoker
 (JBSer and JavaSer) into Version MatrixTestSuite
Message-ID: <8516922.1191850804330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3142?page=all ]

Dimitris Andreadis updated JBAS-3142:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

> Add UnifiedInvoker (JBSer and JavaSer) into Version MatrixTestSuite
> -------------------------------------------------------------------
>
>                 Key: JBAS-3142
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3142
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Optional
>             Fix For: JBossAS-4.2.3.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:56:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 09:56:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15853152.1191851773203.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox reopened JBMESSAGING-1098:
----------------------------------

             

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:56:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 09:56:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31520777.1191851773340.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox updated JBMESSAGING-1098:
---------------------------------

    Priority: Minor  (was: Major)

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 09:56:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 09:56:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1098) Message
 headers not preserved on bridged message
In-Reply-To: <19986733.1191844323226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30785556.1191851773462.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1098?page=all ]

Tim Fox closed JBMESSAGING-1098.
--------------------------------

    Resolution: Done

> Message headers not preserved on bridged message
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1098
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1098
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Some message headers not preserved on bridge.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 10:55:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 10:55:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4572) EJB 3 testsuite 100%
In-Reply-To: <18407225.1185179387272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29242432.1191855305183.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4572?page=all ]

Dimitris Andreadis closed JBAS-4572.
------------------------------------

    Resolution: Done

Updated the depends/related list. The "depends" are solved. The "related" are still open, but known. The ejb3 suite passes.

> EJB 3 testsuite 100%
> --------------------
>
>                 Key: JBAS-4572
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4572
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:01:06 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 11:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33159470.1191855666371.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12380979 ] 
            
Dimitris Andreadis commented on JBAS-4704:
------------------------------------------

4.2.3 probably sometime around Feb/08.

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-42) Container Task for
 JBoss RULES Integration with JBoss Security
In-Reply-To: <20259928.1175689858488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19058604.1191857523833.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-42?page=all ]

Anil Saldhana updated SECURITY-42:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Container Task for JBoss RULES Integration with JBoss Security
> --------------------------------------------------------------
>
>                 Key: SECURITY-42
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-42
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JEMS Integration
>    Affects Versions: 1.x
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Container Task for JBoss Rules integration with JBoss Security.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-24) Get OpenSaml2
 snapshot libraries into the JBoss repository
In-Reply-To: <26707524.1164815335686.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2730086.1191857524130.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-24?page=all ]

Anil Saldhana updated SECURITY-24:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Get OpenSaml2 snapshot libraries into the JBoss repository
> ----------------------------------------------------------
>
>                 Key: SECURITY-24
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-24
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: OnDemand, Repository
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-54) Technical White
 Paper: Single Sign On Options with JBoss
In-Reply-To: <8576238.1179338332302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10331074.1191857524344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-54?page=all ]

Anil Saldhana updated SECURITY-54:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Technical White Paper: Single Sign On Options with JBoss
> --------------------------------------------------------
>
>                 Key: SECURITY-54
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-54
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
> This wiki page has been the central focus of Single Sign On options with the JBoss Application Server.
> The proposed Technical White Paper should consolidate all the options into a single place.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-34) Container Task:
 Formalize Kerberos offering
In-Reply-To: <33197347.1173287004217.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13153922.1191857524814.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-34?page=all ]

Anil Saldhana updated SECURITY-34:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Container Task: Formalize Kerberos offering
> -------------------------------------------
>
>                 Key: SECURITY-34
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-34
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x, 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Spoken to Chris Delashmutt about formalizing the initial work he did for Kerberos/spnego.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=NegotiateKerberos
> This jira task is a container task for overall kerberos silent authentication tasks.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-74) Policy Management
 Console using JBoss SEAM
In-Reply-To: <14814510.1186178449283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28565157.1191857524995.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-74?page=all ]

Anil Saldhana updated SECURITY-74:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Policy Management Console using JBoss SEAM
> ------------------------------------------
>
>                 Key: SECURITY-74
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-74
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossXACML-Console
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Need for a progressive Policy Management console using JBoss SEAM.  The JAXB2 object model provided with JBoss XACML can be used to construct the policies.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-33) White Paper on
	Kerberos
In-Reply-To: <26768130.1173286648778.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2585422.1191857525247.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-33?page=all ]

Anil Saldhana updated SECURITY-33:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> White Paper on Kerberos 
> ------------------------
>
>                 Key: SECURITY-33
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-33
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> We have some kerberos/spnego interface available in JBoss as part of the initial work done by Chris DeLashmutt.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=NegotiateKerberos
> Need to bring this contribution to some formality and get a white paper out.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-29) Validate Jacc
 Policy Module handles all run-as scenarios
In-Reply-To: <25155900.1173285622888.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1923047.1191857525633.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-29?page=all ]

Anil Saldhana updated SECURITY-29:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Validate Jacc Policy Module handles all run-as scenarios
> --------------------------------------------------------
>
>                 Key: SECURITY-29
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-29
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.0.BETA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> With the roles being added to the security context via the mapping framework (for example), there may be cases where in run-as scenarios may not be adequately tested with the new Jacc authorization stuff.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-50) XACML EJB Layer:
 Role Reference Checks
In-Reply-To: <17517802.1178655352366.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15691616.1191857525849.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-50?page=all ]

Anil Saldhana updated SECURITY-50:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> XACML EJB Layer: Role Reference Checks
> --------------------------------------
>
>                 Key: SECURITY-50
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-50
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.0.BETA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Provide a mechanism to do EJBContext.isCallerInRole checks when xacml is enabled.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-65) Kerberos Aware
	Authenticators
In-Reply-To: <24662911.1183485481866.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32677509.1191857526061.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-65?page=all ]

Anil Saldhana updated SECURITY-65:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Kerberos Aware Authenticators
> -----------------------------
>
>                 Key: SECURITY-65
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-65
>             Project: JBoss Security and Identity Management
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Provide authenticators that can do negotiate headers back to the browser and fall back on the web app configured auth method (BASIC/FORM).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-8) LdapExtLoginModule
 should detect communication failures midstream
In-Reply-To: <1391642.1158350795955.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12997118.1191857526613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-8?page=all ]

Anil Saldhana updated SECURITY-8:
---------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

>  LdapExtLoginModule should detect communication failures midstream
> ------------------------------------------------------------------
>
>                 Key: SECURITY-8
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-8
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> http://jira.jboss.com/jira/browse/JBAS-3661
> There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the:
> http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotificationListener.html
> such that it can do graceful processing. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-60) XACML SPI
In-Reply-To: <16066515.1181580431734.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24893776.1191857526777.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-60?page=all ]

Anil Saldhana updated SECURITY-60:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> XACML SPI
> ---------
>
>                 Key: SECURITY-60
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-60
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Provide a XACML SPI in the JBossSX implementation such that external xacml implementations can be plugged in. The XACML module should make use of this spi.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-61) Use JBossSubject
 rather than JAAS Subject
In-Reply-To: <28927019.1181583131596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11513205.1191857527004.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-61?page=all ]

Anil Saldhana updated SECURITY-61:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Use JBossSubject rather than JAAS Subject
> -----------------------------------------
>
>                 Key: SECURITY-61
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-61
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> The JAAS Subject is quite inflexible.  There is a need for a customized Subject.  Let us call it JBossSubject which can internally hold a Jaas Subject.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-36) SASL Authentication
In-Reply-To: <20174150.1173881912358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12305340.1191857527542.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-36?page=all ]

Anil Saldhana updated SECURITY-36:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> SASL Authentication
> -------------------
>
>                 Key: SECURITY-36
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-36
>             Project: JBoss Security and Identity Management
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x
>         Environment: JBossAS: 4.0
>            Reporter: Michael Barker
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>         Attachments: sasl-cram-md5-patch.txt
>
>
> This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security.  Currently only supports CRAM-MD5.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:32:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:32:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-46) SASL Implementation
In-Reply-To: <28027983.1178057310177.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6215540.1191857527691.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-46?page=all ]

Anil Saldhana updated SECURITY-46:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> SASL Implementation  
> ---------------------
>
>                 Key: SECURITY-46
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-46
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, JEMS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Need to get an implementation of SASL for client/server kind of setup for JBoss AS.  This will work off of the Security Client implementation and then security managers on the server side.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:34:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-32) White Paper on
	Clustered SSO
In-Reply-To: <19027403.1173286522201.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12949159.1191857643354.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-32?page=all ]

Anil Saldhana updated SECURITY-32:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> White Paper on Clustered SSO
> ----------------------------
>
>                 Key: SECURITY-32
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-32
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Sakthi Samabsivam
>             Fix For: NO_VERSION
>
>
> White paper on the Clustered SSO offering from JBoss.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
> http://wiki.jboss.org/wiki/Wiki.jsp?page=BuddyReplicationAndClusteredSSO
> This is important because many customers are using this along with http session replication.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:36:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 11:36:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-38) Container Task for
 JBoss SEAM Integration with JBoss Security
In-Reply-To: <22124889.1174015112880.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20692485.1191857766921.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-38?page=all ]

Anil Saldhana updated SECURITY-38:
----------------------------------

    Fix Version/s: NO_VERSION
                       (was: 2.0.1-GA)

> Container Task for JBoss SEAM Integration with JBoss Security
> -------------------------------------------------------------
>
>                 Key: SECURITY-38
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-38
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JEMS Integration
>    Affects Versions: 1.x
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> Container Task to link all the issues that are related to JBoss Seam's integration with JBoss Security.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:49:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 8 Oct 2007 11:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock
 could be not released after async transaction rollback
In-Reply-To: <19139966.1189557851483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2771268.1191858543452.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]

Manik Surtani updated JBCACHE-1183:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

Not observed in trunk (2.1.0)

> Acquired WL lock could be not released after async transaction rollback
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-1183
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: WindowsXP, jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: AsyncRollbackTxLockTest.java
>
>
> In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 11:42:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 8 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1168) Sometimes
 acquired locks are not released
In-Reply-To: <30832886.1187878698592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9596431.1191858123825.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1168?page=all ]

Manik Surtani updated JBCACHE-1168:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

Cannot reproduce in trunk (2.1.0)

> Sometimes acquired locks are not released
> -----------------------------------------
>
>                 Key: JBCACHE-1168
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4
>         Environment: Windows XP, jrockit90_150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: jbosscache.log, output.txt, TransactionStormTest.java
>
>
> Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache.
> Main loop:
> 		while (true) {
> 			for (int x = 0; x < 2; x++) {
> 				WorkThread t = new WorkThread(x == 1);
> 				threads.add(t);
> 				t.start();
> 			}
> 			for (WorkThread separateThread : threads) {
> 				separateThread.join();
> 				if (separateThread.getException() != null) {
> 					//separateThread.getException().getMessage();
> 				}
> 			}
> 			int locksNum = getNumberOfLocksHeld();
> //			System.out.println("Locks="+locksNum);
> 			// checkpoint
> 			if (cache.getNumberOfLocksHeld()>0){
> 				System.out.println("ERROR, locks="+locksNum);
> 				doDomethingOnCache(1);
> 			}
> 			assertEquals(0, locksNum);
> 		}
> Exception - after //checkpoint line numberOfLocks is grater than 0!
> JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 12:34:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 8 Oct 2007 12:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1252) DrlDumper does not
 dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21808404.1191861243320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Fernando Meyer closed JBRULES-1252.
-----------------------------------

    Resolution: Done

Patch applied and added support for function import into xml

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 12:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 8 Oct 2007 12:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18932841.1191862623533.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12381007 ] 
            
Dimitris Andreadis commented on JBAS-4754:
------------------------------------------

Rajesh, I think we are ready.

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:02:20 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 8 Oct 2007 13:02:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11480488.1191862940467.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12381011 ] 
            
Rajesh Rajasekaran commented on JBAS-4754:
------------------------------------------

The runs are on the way.
http://hudson.qa.jboss.com/hudson/view/TCK14-AS4.2.x/
A couple of modules need to be looked at as far as the setup on hudson is concerned.
Will send out a report once there is a complete run.

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Critical
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:22:05 2007
From: jira-events at lists.jboss.org (Michael Barker (JIRA))
Date: Mon, 8 Oct 2007 13:22:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (SECURITY-36) SASL
	Authentication
In-Reply-To: <20174150.1173881912358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18554828.1191864125394.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/SECURITY-36?page=comments#action_12381021 ] 
            
Michael Barker commented on SECURITY-36:
----------------------------------------

Feel free to close this JIRA task.  Given the time scale for implementation we are not going to require SASL authentication.

> SASL Authentication
> -------------------
>
>                 Key: SECURITY-36
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-36
>             Project: JBoss Security and Identity Management
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x
>         Environment: JBossAS: 4.0
>            Reporter: Michael Barker
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>         Attachments: sasl-cram-md5-patch.txt
>
>
> This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security.  Currently only supports CRAM-MD5.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:37:06 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 8 Oct 2007 13:37:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-475) Add a Dynamic AOP
	injboss example
Message-ID: <33115954.1191865026557.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add a Dynamic AOP injboss example
---------------------------------

                 Key: JBAOP-475
                 URL: http://jira.jboss.com/jira/browse/JBAOP-475
             Project: JBoss AOP
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Flavia Rainone
            Priority: Optional


Add a dynamic AOP example in jboss to our tutorial, where we show the power of dynamic AOP on a deployed application.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:44:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 13:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1258) serialising a
 package breaks function removal
Message-ID: <23220508.1191865443258.JavaMail.jira@cloud.prod.atl2.jboss.com>

serialising a package breaks  function removal
----------------------------------------------

                 Key: JBRULES-1258
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1258
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: FUTURE


DynamicRulesTest.testDynamicFunction breaks if you serialise the package first before use. On inspection I cannot initially see what is going wrong. The code seems to be successfully recreating the new classloader and re-writing all invokers, yet it still fails :(

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 13:52:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 8 Oct 2007 13:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1097) Cleaning
 JBM Tables During Startup
In-Reply-To: <1822766.1191588183457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1436429.1191865923904.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1097?page=comments#action_12381031 ] 
            
Tim Fox commented on JBMESSAGING-1097:
--------------------------------------

"because the customer insists" is not a good enough reason for implementing this.

> Cleaning JBM Tables During Startup
> ----------------------------------
>
>                 Key: JBMESSAGING-1097
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1097
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core Persistence
>    Affects Versions: 1.4.0.GA
>         Environment: JBossAS-4.2.0-GA
> JBossMessaging-1.4.0-GA
>            Reporter: Tyronne Wickramarathne
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> need to remove persisted messages during the server startup from the database, without processing them. it becomes a very resource intensive operation as the volume of the persisted messages increased. eg : when this amount exceeds 100K+  during the startup, there should be a mechanism to flush, instead of forcing the subscribers to process them, potentially taking hours, only to require a more intensive system resources.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:23:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 8 Oct 2007 14:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1255) add alternating
 coloured rows
 for rule analysis reporting and allow for user provided css
In-Reply-To: <17212584.1191772568224.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2018156.1191867783356.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1255?page=all ]

Fernando Meyer closed JBRULES-1255.
-----------------------------------

    Resolution: Done

> add alternating coloured rows for rule analysis reporting and allow for user provided css
> -----------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1255
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1255
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> Mark the rows in the table alternate, use a nice software light pastel colour - like green or prink. Use a CSS to declare style so users can provide alternative css.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:29:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 8 Oct 2007 14:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-476) Hotswap on JBoss AS
Message-ID: <32821412.1191868143225.JavaMail.jira@cloud.prod.atl2.jboss.com>

Hotswap on JBoss AS
-------------------

                 Key: JBAOP-476
                 URL: http://jira.jboss.com/jira/browse/JBAOP-476
             Project: JBoss AOP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Flavia Rainone
            Priority: Optional


Add support to hotswap on JBoss AS.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:33:05 2007
From: jira-events at lists.jboss.org (Philippe Ombredanne (JIRA))
Date: Mon, 8 Oct 2007 14:33:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1253)
 drools-examples-drl does not work under Java 6 as-is
In-Reply-To: <8680262.1191636303331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14785177.1191868385544.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1253?page=all ]

Philippe Ombredanne resolved JBRULES-1253.
------------------------------------------

    Resolution: Done

Fixed in rev 15659

> drools-examples-drl  does not work under Java 6 as-is
> -----------------------------------------------------
>
>                 Key: JBRULES-1253
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1253
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2.2, at least XP (possibly others)
>            Reporter: Justin Wick
>         Assigned To: Philippe Ombredanne
>            Priority: Optional
>             Fix For: 4.0.2
>
>
> The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 14:56:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 8 Oct 2007 14:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-477)
 javassist.NotFoundException on Singleton Undeployment
Message-ID: <22512285.1191869763203.JavaMail.jira@cloud.prod.atl2.jboss.com>

javassist.NotFoundException on Singleton Undeployment
-----------------------------------------------------

                 Key: JBAOP-477
                 URL: http://jira.jboss.com/jira/browse/JBAOP-477
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 1.5.5.GA
            Reporter: Flavia Rainone


JBoss AOP is getting a javassist.NotFoundException on undeployment of ha-singleton components.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 15:49:14 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 15:49:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-82) MappingContext
 needs usage of MappingResult to obtain the mapped object
Message-ID: <6173441.1191872954438.JavaMail.jira@cloud.prod.atl2.jboss.com>

MappingContext needs usage of MappingResult to obtain the mapped object
-----------------------------------------------------------------------

                 Key: SECURITY-82
                 URL: http://jira.jboss.com/jira/browse/SECURITY-82
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: JBossSX, Security SPI
    Affects Versions: 2.0.1-BETA1
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-BETA2


Currently the api in MappingContext

performMapping(Map contextMap, T mappedObject)

will not work for Principal objects etc.

Introduce a MappingResult class in the MappingContext as a holder for the mapped object.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 15:59:14 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 8 Oct 2007 15:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28202815.1191873554610.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12381062 ] 
            
Ron Sigal commented on JBAS-4704:
---------------------------------

>From Dimitris:  I don't personally know of a support case around this issue.

>From Carlo:  The issue pop-ed in directly from Jira. I can't find any related support cases or forum posts.

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 16:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-82) MappingContext
 needs usage of MappingResult to obtain the mapped object
In-Reply-To: <6173441.1191872954438.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3624985.1191874023661.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-82?page=all ]

Anil Saldhana closed SECURITY-82.
---------------------------------

    Resolution: Done

> MappingContext needs usage of MappingResult to obtain the mapped object
> -----------------------------------------------------------------------
>
>                 Key: SECURITY-82
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-82
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.1-BETA1
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-BETA2
>
>
> Currently the api in MappingContext
> performMapping(Map contextMap, T mappedObject)
> will not work for Principal objects etc.
> Introduce a MappingResult class in the MappingContext as a holder for the mapped object.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 16:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-28) JACC:
 <role-name>*</role-name>
 in web.xml should allow configurable authorization bypass
In-Reply-To: <7468972.1172167373750.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11810913.1191874023977.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-28?page=all ]

Anil Saldhana updated SECURITY-28:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-BETA2)

> JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass
> ----------------------------------------------------------------------------------------
>
>                 Key: SECURITY-28
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-28
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> JBAS-1824

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 8 Oct 2007 16:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-81) Identity Trust
 context should handle security domain also
In-Reply-To: <17880822.1191606363435.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30762753.1191874023455.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-81?page=all ]

Anil Saldhana closed SECURITY-81.
---------------------------------

    Resolution: Done

> Identity Trust context should handle security domain also
> ---------------------------------------------------------
>
>                 Key: SECURITY-81
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-81
>             Project: JBoss Security and Identity Management
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>    Affects Versions: 2.0.1-BETA1
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-BETA2
>
>
> ITC can handle a security context that belongs to a different security domain.
> Hence ITC needs to know the sec domain for the Identity Trust Manager.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 16:52:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 8 Oct 2007 16:52:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3196513.1191876724630.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-687?page=comments#action_12381081 ] 
            
Ron Sigal commented on JBREM-687:
---------------------------------

Applied changes to branch remoting_2_2_0_GA for release 2.2.2.SP2.

Note:  In addition to invokerLocator and ServerInvoker, a change is also made to org.jboss.remoting.transport.Connector.

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 17:58:03 2007
From: jira-events at lists.jboss.org (Lukasz Wiktor (JIRA))
Date: Mon, 8 Oct 2007 17:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-254)
 ClassCastException in
 org.jboss.portlet.forums.ui.PortalUtil in function getPoster
Message-ID: <28414572.1191880683450.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException in org.jboss.portlet.forums.ui.PortalUtil in function getPoster
----------------------------------------------------------------------------------

                 Key: JBFORUMS-254
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-254
             Project: JBoss Forums
          Issue Type: Bug
    Affects Versions: 1.0.0 GA
         Environment: JBoss Portal 2.6.1.GA bundled with JBoss AS 4.2.1 and  integrated with OpenLDAP
            Reporter: Lukasz Wiktor
         Assigned To: Ryszard Kozmik


In class org.jboss.portlet.forums.ui.PortalUtil in function getPoster() userId is casted to Long. That causes ClassCastException when userId is for example type of String (in LDAP).

2007-10-04 15:35:07,700 ERROR [org.jboss.portlet.forums.ui.JSFUtil] org.jboss.portlet.forums.ui.JSFUtil
java.lang.ClassCastException: java.lang.String
	at org.jboss.portlet.forums.ui.PortalUtil.getPoster(PortalUtil.java:467)
             ...

It prevents from e.g. creating new topic.

See my posts on the forum. I have proposed the solution.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 20:24:12 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 20:24:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1257) Add Banking
 Example from John Dunning
In-Reply-To: <21119646.1191815943276.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15577804.1191889452673.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1257?page=all ]

Mark Proctor closed JBRULES-1257.
---------------------------------

    Resolution: Done

> Add Banking Example from John Dunning
> -------------------------------------
>
>                 Key: JBRULES-1257
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1257
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> John Dunny has blogged a nice banking tutorial at:
> http://web.mac.com/johndunning/Life_on_a_Laptop/Drools/Entries/2007/10/7_Banking_on_DROOLS.html
> And has kindly given us permission to add it to the manual.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 20:26:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 20:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1254)
 drools-repository/jbrms should
 not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3535916.1191889563321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=all ]

Mark Proctor updated JBRULES-1254:
----------------------------------

    Fix Version/s: FUTURE
                       (was: 4.0.2)

We've decided to leave this as is for 4.0.2. But we'll look to apply this after the branch is made.

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 20:48:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 8 Oct 2007 20:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1259) JBoss Drools
	4.0.2GA Release
Message-ID: <32091951.1191890883474.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Drools 4.0.2GA Release
----------------------------

                 Key: JBRULES-1259
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1259
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 21:18:15 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Mon, 8 Oct 2007 21:18:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
Message-ID: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>

Include eclipse JDT library in drools-eclipse IDE plugin
--------------------------------------------------------

                 Key: JBRULES-1260
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
    Affects Versions: 4.0.1
            Reporter: Joshua Jackson
         Assigned To: Mark Proctor
             Fix For: 4.0.2


Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:

org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
	at com.sample.DroolsTest.main(DroolsTest.java:21)
Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 21:55:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 21:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31703547.1191894903305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=all ]

Mark Proctor closed JBRULES-1260.
---------------------------------

    Fix Version/s: 4.0.3
                       (was: 4.0.2)
       Resolution: Done

It should get the JDT Compiler from Eclipse itself, I've not heard of others having this problem, you'll need to supply more details.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 21:57:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 21:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1261) Update to JDK1.5
	minimum
Message-ID: <20527685.1191895023212.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update to JDK1.5 minimum
------------------------

                 Key: JBRULES-1261
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1261
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.1.0.




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 22:01:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 8 Oct 2007 22:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1261) Update to JDK1.5
	minimum
In-Reply-To: <20527685.1191895023212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31492656.1191895263498.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1261?page=all ]

Mark Proctor closed JBRULES-1261.
---------------------------------

    Resolution: Done

> Update to JDK1.5 minimum
> ------------------------
>
>                 Key: JBRULES-1261
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1261
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct  8 22:30:03 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Mon, 8 Oct 2007 22:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13002741.1191897003327.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381109 ] 
            
Joshua Jackson commented on JBRULES-1260:
-----------------------------------------

I used eclipse 3.3 europa
- dropped in the 4.0.1 drools-eclipse plugin
- create new rules project and add the sample HelloWorld
- run the DroolsTest as java program
- and then I received that exception message

But when I inserted the eclipse jdt library that is provided by drools, it worked.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 02:44:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 9 Oct 2007 02:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-36) SASL Authentication
In-Reply-To: <20174150.1173881912358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14020830.1191912243495.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-36?page=all ]

Anil Saldhana closed SECURITY-36.
---------------------------------

    Resolution: Won't Fix

> SASL Authentication
> -------------------
>
>                 Key: SECURITY-36
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-36
>             Project: JBoss Security and Identity Management
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 1.x
>         Environment: JBossAS: 4.0
>            Reporter: Michael Barker
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>         Attachments: sasl-cram-md5-patch.txt
>
>
> This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security.  Currently only supports CRAM-MD5.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 03:51:03 2007
From: jira-events at lists.jboss.org (M H (JIRA))
Date: Tue, 9 Oct 2007 03:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1262) DSL Parser "eval"
Message-ID: <29036708.1191916263283.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL Parser "eval"
-----------------

                 Key: JBRULES-1262
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1262
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: M H
         Assigned To: Mark Proctor


[when]of type Item=Item()
[when]- Title equals "{value}"=eval(title.isEqual("{value}")
[when]- Event equals "{value}"=eval(id.isEqual("{value}")
[then]Log : "{message}"=System.out.println("{message}");



the dslr File:

expander Test.dsl

rule "Your First Rule"
     when
            $p : of type Item
               - Title equals "test"
               - Event equals "test"
     then
           #actions
end

resolves to (could be seen in the drl viewer)

rule "Your First Rule"

       when
               $p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) )
       then
               #actions

end


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:46:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-161) Overwriting a node in
 the source yields an out-of-sync diagram
In-Reply-To: <28293293.1189441931051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25672452.1191919563426.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-161?page=all ]

Koen Aers updated GPD-161:
--------------------------

    Component/s: jpdl

> Overwriting a node in the source yields an out-of-sync diagram
> --------------------------------------------------------------
>
>                 Key: GPD-161
>                 URL: http://jira.jboss.com/jira/browse/GPD-161
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> 3.1.0cr1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>         Attachments: cheat.txt, processdefinition.xml, websale.par
>
>
> I edited the source xml by pasting in the Decision Node from the cheat.txt (attached) over the "Evaluate web order" found in the example websale process.  When I switched back to visual mode, I found an unattached Decision Node with no name and the "Evaluate web order" remained as before.
> I'll attach the before and after JPDL as well as the substitution text after I open this bug.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:48:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-162) Deploying a process
 does not pull in necessary Java classes
In-Reply-To: <31205902.1189443251838.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29055941.1191919683400.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-162?page=all ]

Koen Aers updated GPD-162:
--------------------------

    Component/s: jpdl

> Deploying a process does not pull in necessary Java classes
> -----------------------------------------------------------
>
>                 Key: GPD-162
>                 URL: http://jira.jboss.com/jira/browse/GPD-162
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> GPD 3.1.0.CR1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>         Attachments: websale.par
>
>
> When I try to deploy a process from the GPD, the class files referenced in the definition do not come across properly.
> 1) Modified an existing process (as per GPD 161).
> 2) Save the process. (.par will be attached)
> 3) Use the Deployment tab to deploy the updated process.
> 4) Execute the process and you get the following error:
> In the web page:
> Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown.
> On the console:
> 12:48:35,403 ERROR [Delegation] couldn't instantiate delegation class 'org.jbpm.websale.DeciderHandler'
> java.lang.NullPointerException
>         at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105)
>         at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:48)
>         at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:163)
>         at org.jbpm.instantiation.Delegation$$FastClassByCGLIB$$6bae1598.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.instantiation.Delegation$$EnhancerByCGLIB$$a8c02805.instantiate(<generated>)
>         at org.jbpm.graph.node.Decision.execute(Decision.java:87)
>         at org.jbpm.graph.def.Node.enter(Node.java:318)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.enter(<generated>)
>         at org.jbpm.graph.def.Transition.take(Transition.java:151)
>         at org.jbpm.graph.def.Node.leave(Node.java:393)
>         at org.jbpm.graph.node.StartState.leave(StartState.java:70)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.leave(<generated>)
>         at org.jbpm.graph.exe.Token.signal(Token.java:194)
>         at org.jbpm.graph.exe.Token.signal(Token.java:139)
>         at org.jbpm.graph.exe.Token$$FastClassByCGLIB$$74df1c6e.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5a16e027.signal(<generated>)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:476)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:390)
>         at org.jbpm.jsf.core.action.CompleteTaskActionListener.handleAction(CompleteTaskActionListener.java:47)
>         at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82)
>         at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
>         at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758)
>         at javax.faces.component.UICommand.broadcast(UICommand.java:368)
>         at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.broadcast(UITaskFormButtonBase.java:56)
>         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
>         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
>         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
>         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
>         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
>         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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:48:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-154) process image rendered
 incorrectly for large process definition
In-Reply-To: <2916967.1186754521287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22943779.1191919683579.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-154?page=all ]

Koen Aers updated GPD-154:
--------------------------

    Component/s: jpdl

> process image rendered incorrectly for large process definition
> ---------------------------------------------------------------
>
>                 Key: GPD-154
>                 URL: http://jira.jboss.com/jira/browse/GPD-154
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: mac osx,  tomcat 5.0.28
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>            Priority: Minor
>
> Hi,
> then I create a large process, and extend to the left beyond the original boundary, by placing and element in the designer and dragging, so scrollbars appear, the image when rendered in the console is offset incorrectly while on any given node,
> cheers
> Ross

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:48:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-170) misspelling: Assignmnet
In-Reply-To: <814774.1190993382986.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1022536.1191919683712.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-170?page=all ]

Koen Aers updated GPD-170:
--------------------------

    Component/s: jpdl

> misspelling: Assignmnet
> -----------------------
>
>                 Key: GPD-170
>                 URL: http://jira.jboss.com/jira/browse/GPD-170
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Chris Whalen
>         Assigned To: Koen Aers
>
> "Assignment" misspelled on task and swimlane configuration tabs.
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/TaskConfigurationComposite.java   and
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/SwimlaneConfigurationComposite.java

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:53 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 04:50:53 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1060)
 getInvokedBusinessInterface doesn't return correct interface
Message-ID: <22610729.1191919853782.JavaMail.jira@cloud.prod.atl2.jboss.com>

getInvokedBusinessInterface doesn't return correct interface
------------------------------------------------------------

                 Key: EJBTHREE-1060
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf
         Assigned To: Andrew Rubinger


When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface.

@Stateless
@Remote({Remote1.class, Remote2.class})

interface Remote1 extends CommonRemote

interface Remote2 extends CommonRemote

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:54 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:50:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-168) feature not recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33400339.1191919854215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-168?page=all ]

Koen Aers updated GPD-168:
--------------------------

    Component/s: jpdl

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:55 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 9 Oct 2007 04:50:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23279965.1191919855121.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

Koen Aers updated GPD-169:
--------------------------

    Component/s: jpdl

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 04:50:55 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 04:50:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1060)
 getInvokedBusinessInterface doesn't return correct interface
In-Reply-To: <22610729.1191919853782.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24237381.1191919855520.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1060?page=comments#action_12381130 ] 
            
Carlo de Wolf commented on EJBTHREE-1060:
-----------------------------------------

The invoked interface can be inferred when enc setup is done:

@EJB Remote1 bean;

or

<ejb-ref>
  <remote>Remote1</remote>
</ejb-ref>

> getInvokedBusinessInterface doesn't return correct interface
> ------------------------------------------------------------
>
>                 Key: EJBTHREE-1060
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>
> When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface.
> @Stateless
> @Remote({Remote1.class, Remote2.class})
> interface Remote1 extends CommonRemote
> interface Remote2 extends CommonRemote

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:18:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 9 Oct 2007 05:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
Message-ID: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>

InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
----------------------------------------------------------------------------------

                 Key: JBAS-4805
                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: EJB3
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Galder Zamarreno
         Assigned To: Carlo de Wolf
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA


org.jboss.ejb3.InitialContextFactory.getHAContext() contains:

env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
InitialContext haCtx = new InitialContext(env);

The code should not have hardcoded localhost because as soon as someone binds JBoss 
to something different, a localhost lookup will fail.

This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:24:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 05:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17284430.1191921843385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]

Dimitris Andreadis updated JBAS-4805:
-------------------------------------

    Fix Version/s:     (was:  JBossAS-5.0.0.Beta3)
                       (was: JBossAS-4.2.2.GA)

Don't set the fix versions!

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:26:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 9 Oct 2007 05:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29505110.1191921963278.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381139 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

Ok, ok, ok... :)

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:46:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 05:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1735) Add metadata to
 include portlet's icons
Message-ID: <4578399.1191923163632.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add metadata to include portlet's icons
---------------------------------------

                 Key: JBPORTAL-1735
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1735
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Thomas Heute
             Fix For: 2.6.3 Final


The Portlet spec doesn't define metadata to specify an icon for a portlet.
We could add this in our vendor specific jboss-portlet.xml descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 05:54:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 05:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-670) PreDestroy called
 multiple times
In-Reply-To: <14081580.1154512271311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11810544.1191923643943.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-670?page=all ]

Carlo de Wolf updated EJBTHREE-670:
-----------------------------------

    Affects Version/s: EJB 3.0 RC9 - Patch 1

> PreDestroy called multiple times
> --------------------------------
>
>                 Key: EJBTHREE-670
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-670
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD, AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: EJB 3.0 RC9 - FD
>
>
> The PreDestroy callback is called multiple times.
> Once from the container and once from the pool.
> IMHO only the pool should call PreDestroy. 
> Other callbacks are already handled by the pool.
> Unit test is in regression/ejbthree...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:03:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1735) Add metadata to
 include portlet's icons
In-Reply-To: <4578399.1191923163632.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29170130.1191924183226.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1735?page=all ]

Thomas Heute resolved JBPORTAL-1735.
------------------------------------

    Resolution: Done

> Add metadata to include portlet's icons
> ---------------------------------------
>
>                 Key: JBPORTAL-1735
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1735
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> The Portlet spec doesn't define metadata to specify an icon for a portlet.
> We could add this in our vendor specific jboss-portlet.xml descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:14:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1597) i18n display
 name for portlet instances
In-Reply-To: <18247414.1184788607107.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2464530.1191924843392.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1597?page=all ]

Thomas Heute updated JBPORTAL-1597:
-----------------------------------

    Description:     (was: This should be done using declared properties having a key such as $PREFIX.$LOCALE_ID where prefix needs to be determined and locale id is like 'fr_FR'. Also I am worried that getting a cascaded value would be difficult programatically.
)

> i18n display name for portlet instances
> ---------------------------------------
>
>                 Key: JBPORTAL-1597
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1597
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:16:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1736) Site structure
	i18n
Message-ID: <11410482.1191924963437.JavaMail.jira@cloud.prod.atl2.jboss.com>

Site structure i18n
-------------------

                 Key: JBPORTAL-1736
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1736
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final


Portals, pages and windows (portal objects) should be i18nable. (So far only pages are, and not in a good manner)


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 06:18:18 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 9 Oct 2007 06:18:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1737) Themes should be
 able to display text with the correct locale
Message-ID: <16743422.1191925098787.JavaMail.jira@cloud.prod.atl2.jboss.com>

Themes should be able to display text with the correct locale
-------------------------------------------------------------

                 Key: JBPORTAL-1737
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1737
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core, Portal Theme
            Reporter: Thomas Heute
         Assigned To: Thomas Heute
             Fix For: 2.6.3 Final


Not sure what's the current state 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

        


From jira-events at lists.jboss.org  Tue Oct  9 07:04:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 07:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1078) TCK strict
	behavior
In-Reply-To: <14693809.1190323871017.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18092347.1191927843345.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1078?page=comments#action_12381148 ] 
            
Tim Fox commented on JBMESSAGING-1078:
--------------------------------------

I have extended this by allowing strictTck to be specified on the server peer and as a system property.

System property if true overrides server peer if true overrides connection factory.

> TCK strict behavior
> -------------------
>
>                 Key: JBMESSAGING-1078
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1078
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Clebert Suconic
>         Assigned To: Andy Taylor
>             Fix For: 1.4.0.GA
>
>         Attachments: testcase.patch
>
>
> By TCK Tests, we should set the JMSDestination on foreign messages, but some providers don't play well with that. (ActiveMQ for instance)
> So, we will create a setting for TCK STrict behavior, for things like setting the destination on Foreign message.
> This will be a setting on ServerPeer or on the ConnectionFactory.
> (I"m attaching a patch for a failing test because 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

        


From jira-events at lists.jboss.org  Tue Oct  9 07:32:03 2007
From: jira-events at lists.jboss.org (David Schlechtweg (JIRA))
Date: Tue, 9 Oct 2007 07:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1738) can not access a
 member of
 class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag
Message-ID: <20884325.1191929523783.JavaMail.jira@cloud.prod.atl2.jboss.com>

can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag
-------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1738
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1738
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Portlet
    Affects Versions: 2.6.2 Final
            Reporter: David Schlechtweg
         Assigned To: Julien Viet


Hi, 
 
i get a IllegalAccessException when i use a jsp tag in freemarker: 
 
<#assign portlet=JspTaglibs["http://java.sun.com/portlet"]>  
<#import "/spring.ftl" as spring /> 
<@portlet.actionURL var="postURL"> 
<@portlet.param name="action" value="newQuery" /> 
</@portlet.actionURL> 
 
I use freemarker 2.3.10 in jboss-portal-2.6.2.GA 
 
java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public" 
The problematic instruction: 
---------- 
==> user-directive portlet.actionURL [on line 3, column 1 in template/search/simple/view.ftl] 
---------- 
 
Java backtrace for programmers: 
---------- 
freemarker.template.TemplateModelException: java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public" 
at freemarker.ext.jsp.TagTransformModel.getWriter(TagTransformModel.java:177) 
at freemarker.core.Environment.visit(Environment.java:220) 
at freemarker.core.UnifiedCall.accept(UnifiedCall.java:116) 
at freemarker.core.Environment.visit(Environment.java:196) 
at freemarker.core.MixedContent.accept(MixedContent.java:92) 
at freemarker.core.Environment.visit(Environment.java:196) 
at freemarker.core.Environment.process(Environment.java:176) 
at freemarker.template.Template.process(Template.java:232) 
at org.springframework.web.servlet.view.freemarker.FreeMarkerView.processTemplate(FreeMarkerView.java:344) 
 
any ideas? 

My hunch is that the class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag is not public, and you're trying to invoke a method on it that though itself is public, it is not declared in any public superclass of GenerateURLTag, or public interface that GenerateURLTag implements.  

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 08:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
Message-ID: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
-----------------------------------------------------------------------------------------------------

                 Key: JBAS-4806
                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: IIOP service
            Reporter: Dimitris Andreadis
         Assigned To: Francisco Reverbel
            Priority: Blocker
             Fix For: JBossAS-4.2.2.GA


I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
string has not been updated, so the jacorb library will still identify itself
as "JacORB 2.3.0 (JBoss patch 4)". See

http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch

While this is a minor thing, it may cause confusion as the version string
is printed out when JacORB is used in a verbose logging level. In order to
avoid support troubles, you guys may want to fix the patch number in the
version string before AS 4.2.2 goes out. *If* you do this, then update also
the patch number in the README file, which is at patch 3:

http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)

Regards,

Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 08:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29957118.1191932283652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4806?page=all ]

Dimitris Andreadis reassigned JBAS-4806:
----------------------------------------

    Assignee: Patrick Macdonald  (was: Francisco Reverbel)

Patrick, who can take up this task, it's relatively urgent.

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Patrick Macdonald
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 08:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4754) Do a full CTS1.4 run
 to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20584642.1191932283832.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4754?page=all ]

Dimitris Andreadis updated JBAS-4754:
-------------------------------------

    Priority: Blocker  (was: Critical)

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 08:24:03 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 9 Oct 2007 08:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7622546.1191932643243.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-570?page=comments#action_12381157 ] 
            
Vladimir Blagojevic commented on JGRP-570:
------------------------------------------

The best way to rename leftover short lifespan thread names is to use java.util.concurrent.ThreadFactory. We keep ThreadFactory in a well known place (ProtocolStack?) and then anyone who needs a Thread can create it from this factory. When ThreadNamingPattern is sent up the stack it is applied to this ThreadFactory. No need to chase individual threads and rename threads one by one.

Consider moving to 2.7.

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:24:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 09:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1090) Add
 appropriate Exception handling when hitting MaxSize
In-Reply-To: <9488820.1191326763359.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9601184.1191936243281.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1090?page=all ]

Tim Fox updated JBMESSAGING-1090:
---------------------------------

    Issue Type: Feature Request  (was: Bug)
      Priority: Minor  (was: Major)

> Add appropriate Exception handling when hitting MaxSize
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1090
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1090
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Jay Howell
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> When using MaxSize for a queue and topic the following behaviors exist
> Queue - When a queue hits MaxSize, the delivery returned in Channel Support is null.  This triggers a very generic JMSException to be thrown by looking at the delivery and seeing if it's null in the ServerConnectionEndpoint.
> Topic - When a subscription hits the MaxSize(defined in the topic), the delivery returned will be null, but no check is done and no JMSException is thrown in the ServerConnectionEndpoint.
> What this means is that anyone who wants to put hooks in to gather the messages dropped can't.  Either because the exception is too generic or because one is not thrown at all.
> I would purpose that we put proper exception handling down in the ChannelSupport where MaxSize is checked for both queues and subscriptions.  
> We would need to Change the The two methods in channel support for send and sendInternal to throw a JMSException.  Then we throw a checked Exception in ChannelSupport for MaxSize violations(make a new exception derived from MessagingJMSException).  
> Adding proper exception handling to these would allow users to add aspects and notifications when messages are dropped due to MaxSize.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Tue, 9 Oct 2007 09:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1244) Ruleflows
 should have a package name
In-Reply-To: <20387486.1191370683368.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16372596.1191937683375.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1244?page=comments#action_12381169 ] 
            
Mark Proctor commented on JBRULES-1244:
---------------------------------------

All existing ruleflows will need to have their package name added, or it will fail to load. This should be a standard property, much like how the ruleflow name is added.

> Ruleflows should have a package name
> ------------------------------------
>
>                 Key: JBRULES-1244
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1244
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rule Flow
>            Reporter: Kris Verlaenen
>         Assigned To: Kris Verlaenen
>             Fix For: 4.0.2
>
>
> Ruleflows should be added as part of their own package.
> This allows
>  - adding ruleflows before adding rules
>  - adding only ruleflows to a package

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:52:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 09:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-3441) Request to include
 log4j version 1.2.13 in next JBoss AS release
In-Reply-To: <22073956.1154041931506.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27069502.1191937923301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3441?page=all ]

Dimitris Andreadis closed JBAS-3441.
------------------------------------

    Resolution: Out of Date
      Assignee: Dimitris Andreadis  (was: Scott M Stark)

We have already upgraded 4.2.x and 5.x to log4j 1.2.14, and there is no intention of another 4.0.x version, so this issue is out-of-date.

> Request to include log4j version 1.2.13 in next JBoss AS release
> ----------------------------------------------------------------
>
>                 Key: JBAS-3441
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3441
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: All OS's.
>            Reporter: Khiem Tang
>         Assigned To: Dimitris Andreadis
>
> We have one component that depends on log4j-1.2.13 but the one that ships with JBoss is older. We currently use this log4j version in our JBoss stack and it seems to work fine. It would help us if JBoss put the same version (1.2.13) in the packages.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 09:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 09:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2231194.1191938043559.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4806?page=all ]

Dimitris Andreadis reassigned JBAS-4806:
----------------------------------------

    Assignee: Deepak Bhole  (was: Patrick Macdonald)

Deepak, can you look at this task?

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Deepak Bhole
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:03:04 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 9 Oct 2007 10:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-168) feature not
	recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29957323.1191938584394.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-168?page=comments#action_12381174 ] 
            
Ronald van Kuijk commented on GPD-168:
--------------------------------------

I have no problem here... did you do a "eclipse.exe -clean" ? 

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:15:03 2007
From: jira-events at lists.jboss.org (Joachim Neubert (JIRA))
Date: Tue, 9 Oct 2007 10:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-168) feature not
	recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22451414.1191939303311.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-168?page=comments#action_12381177 ] 
            
Joachim Neubert commented on GPD-168:
-------------------------------------

I think I didn't. In the meantime my configuration changed, and now the version delivered with JBoss Tools 2.0 beta4 is up and running.

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:17:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 10:17:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1061) Look into
 StatefulUnitTestCase, determine purpose
Message-ID: <7131874.1191939425385.JavaMail.jira@cloud.prod.atl2.jboss.com>

Look into StatefulUnitTestCase, determine purpose
-------------------------------------------------

                 Key: EJBTHREE-1061
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1061
             Project: EJB 3.0
          Issue Type: Task
    Affects Versions: HEAD
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


Ensure the 7 tests in StatefulUnitTestCase are valid, testing for their intentions, and report any inconsistancies to Brian.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 10:57:03 2007
From: jira-events at lists.jboss.org (Steve Miner (JIRA))
Date: Tue, 9 Oct 2007 10:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1152) my unit tests
 are hanging with drools 4.0.1
In-Reply-To: <1213410.1188511518355.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19443798.1191941823467.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1152?page=comments#action_12381190 ] 
            
Steve Miner commented on JBRULES-1152:
--------------------------------------

I confirmed that Drools 4.0.2 fixes my problem.  Also, my original unit tests now work again as they did with 4.0.

> my unit tests are hanging with drools 4.0.1
> -------------------------------------------
>
>                 Key: JBRULES-1152
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1152
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>         Environment: Java 1.5, Mac OX X 10.4.10, Drools 4.0.1
>            Reporter: Steve Miner
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>         Attachments: drools1152-v2.zip, drools1152.zip
>
>
> Sorry, I don't have very specific information.  Some of my project's unit tests are hanging with drools 4.0.1.  No error, just not completing.  I tried to debug a bit but could not figure it out.  Consider this an early warning until I can gather more info.
> Everything worked fine with 4.0 so I went back to that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 11:16:04 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 9 Oct 2007 11:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1256) publish source
 jars with maven
In-Reply-To: <29818339.1191772683275.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18948292.1191942964465.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1256?page=all ]

Fernando Meyer resolved JBRULES-1256.
-------------------------------------

    Resolution: Done

> publish source jars with maven
> ------------------------------
>
>                 Key: JBRULES-1256
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1256
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Proctor
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>
> While publishing the maven jars we should also publish the source jars with it, maven has a command line switch for this. Although it may not copy the jars to a central target like it does the other jars, you'll need to check.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 11:18:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 9 Oct 2007 11:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1259) JBoss Drools
	4.0.2GA Release
In-Reply-To: <32091951.1191890883474.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18993207.1191943083314.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1259?page=all ]

Fernando Meyer resolved JBRULES-1259.
-------------------------------------

    Fix Version/s: 4.0.2
       Resolution: Done

> JBoss Drools 4.0.2GA Release
> ----------------------------
>
>                 Key: JBRULES-1259
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1259
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:13:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 9 Oct 2007 12:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1152) my unit tests are
 hanging with drools 4.0.1
In-Reply-To: <1213410.1188511518355.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11352825.1191946383908.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1152?page=all ]

Edson Tirelli closed JBRULES-1152.
----------------------------------


Thanks for the feedback.

> my unit tests are hanging with drools 4.0.1
> -------------------------------------------
>
>                 Key: JBRULES-1152
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1152
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1
>         Environment: Java 1.5, Mac OX X 10.4.10, Drools 4.0.1
>            Reporter: Steve Miner
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2
>
>         Attachments: drools1152-v2.zip, drools1152.zip
>
>
> Sorry, I don't have very specific information.  Some of my project's unit tests are hanging with drools 4.0.1.  No error, just not completing.  I tried to debug a bit but could not figure it out.  Consider this an early warning until I can gather more info.
> Everything worked fine with 4.0 so I went back to that.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:31:20 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 12:31:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
Message-ID: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>

Potential deadlock in shutting down server
------------------------------------------

                 Key: JBMESSAGING-1099
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:39:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 9 Oct 2007 12:39:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9365565.1191947944280.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Anil Saldhana updated JBMESSAGING-1099:
---------------------------------------

    Priority: Critical  (was: Major)

I have to make this issue "Critical" because I have seen the case when JMS destination authorization fails, the server just hangs.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 12:51:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 12:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28917374.1191948663447.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12381223 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

If you can replicate this, please add instructions to this task.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1034) Port
 ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to
 Branch_4_2
In-Reply-To: <22376933.1187730452121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13780659.1191953403574.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1034?page=all ]

Carlo de Wolf updated EJBTHREE-1034:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2
> ------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1034
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1034
>             Project: EJB 3.0
>          Issue Type: Patch
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Frank Langelage
>             Fix For: Branch_4_2
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Port the changes made on ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java in Head to Branch 4.2.
> Using an ear with seperated session and entity beans (different ejb-modules) I got the exception "There is no default persistence nit in this deployment." when using "@PersistenceContext private EntityManager entityManager;" in my Session Bean.
> Using the head version of the source file within my 4.2.2.GA cvs checkout the problem went away.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1034) Port
 ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to
 Branch_4_2
In-Reply-To: <22376933.1187730452121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4664691.1191953403848.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1034?page=all ]

Carlo de Wolf updated EJBTHREE-1034:
------------------------------------

     Original Estimate:     (was: 1 hour)
    Remaining Estimate:     (was: 1 hour)
            Complexity:   (was: Low)

> Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2
> ------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1034
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1034
>             Project: EJB 3.0
>          Issue Type: Patch
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Frank Langelage
>             Fix For: Branch_4_2
>
>
> Port the changes made on ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java in Head to Branch 4.2.
> Using an ear with seperated session and entity beans (different ejb-modules) I got the exception "There is no default persistence nit in this deployment." when using "@PersistenceContext private EntityManager entityManager;" in my Session Bean.
> Using the head version of the source file within my 4.2.2.GA cvs checkout the problem went away.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:16:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 14:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1100) Non durable
 topic
 subscribers with noLocal=true  result in message build up on server
Message-ID: <8358901.1191953763435.JavaMail.jira@cloud.prod.atl2.jboss.com>

Non durable topic subscribers with noLocal=true  result in message build up on server
-------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1100
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1100
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


If you create a non durable topic subscription with noLocal = true, then send a lot of local messages. They build in the subscription queue on the server.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:16:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
Message-ID: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>

Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
----------------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1062
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


The following doesn't work:

@Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}

interface ExpectedLocalInterface {}

class SuperBean implements OtherInterface {}

interface OtherInterface {}

Based on the spec ExpectedLocalInterface is expected to become the local business interface.

EJB 3 4.6.6:
If bean class implements a single interface, that interface is assumed to be the busi-
ness interface of the bean. This business interface will be a local interface unless the
interface is designated as a remote business interface by use of the Remote annota-
tion on the bean class or interface or by means of the deployment descriptor.


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:18:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 9 Oct 2007 14:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1061) Look into
 StatefulUnitTestCase, determine purpose
In-Reply-To: <7131874.1191939425385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26175540.1191953883419.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1061?page=all ]

Carlo de Wolf updated EJBTHREE-1061:
------------------------------------

    Affects Version/s:     (was: HEAD)

> Look into StatefulUnitTestCase, determine purpose
> -------------------------------------------------
>
>                 Key: EJBTHREE-1061
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1061
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Ensure the 7 tests in StatefulUnitTestCase are valid, testing for their intentions, and report any inconsistancies to Brian.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:35:07 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 9 Oct 2007 14:35:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1100) Non durable
 topic
 subscribers with noLocal=true  result in message build up on server
In-Reply-To: <8358901.1191953763435.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10899956.1191954907149.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1100?page=all ]

Tim Fox closed JBMESSAGING-1100.
--------------------------------

    Resolution: Done

> Non durable topic subscribers with noLocal=true  result in message build up on server
> -------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1100
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1100
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> If you create a non durable topic subscription with noLocal = true, then send a lot of local messages. They build in the subscription queue on the server.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 14:52:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 9 Oct 2007 14:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1033) Add EJB2.x JMX
 metrics to EJB3
In-Reply-To: <19347205.1187704052441.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4022292.1191955923379.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1033?page=all ]

William DeCoste resolved EJBTHREE-1033.
---------------------------------------

    Resolution: Done

> Add EJB2.x JMX metrics to EJB3
> ------------------------------
>
>                 Key: EJBTHREE-1033
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1033
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: EJB 3.0 RC9 - Patch 1
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 5.0.0.Beta3
>
>
> Stateless: AvailableCount, MaxSize, CurrentSize, CreateCount, RemoveCount
> Stateful: CacheSize, PassivatedCount, CreateCount, RemoveCount, AvailableSize, CurrentSize, MaxSize
> MDB: MinPoolSize, MaxPoolSize, MaxMessages, KeepAliveMillis

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:06:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes for Anil
Message-ID: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure EJBSpecUnitTestCase Passes for Anil
------------------------------------------

                 Key: EJBTHREE-1063
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
             Project: EJB 3.0
          Issue Type: Task
    Affects Versions: HEAD
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:06:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15538771.1191960365795.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=all ]

Andrew Rubinger updated EJBTHREE-1063:
--------------------------------------

    Summary: Ensure EJBSpecUnitTestCase Passes  (was: Ensure EJBSpecUnitTestCase Passes for Anil)

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:08:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:08:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23116809.1191960485547.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=comments#action_12381263 ] 
            
Andrew Rubinger commented on EJBTHREE-1063:
-------------------------------------------

Prioritize successful deployment of test case archives

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:16:07 2007
From: jira-events at lists.jboss.org (Deepak Bhole (JIRA))
Date: Tue, 9 Oct 2007 16:16:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8847648.1191960967212.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4806?page=all ]

Deepak Bhole resolved JBAS-4806.
--------------------------------

    Resolution: Done

New jacorb has been uploaded to repository. There were differences in the following classes:

org/jacorb/idl/IdlSymbol.class
org/jacorb/idl/parser.class
org/jacorb/orb/giop/CodeSet.class
org/jacorb/orb/ORB.class
org/jacorb/orb/portableInterceptor/ORBInitInfoImpl.class
org/jacorb/util/BuildVersion.class
org/jacorb/util/Version.class

jcf-dump shows that all differences are either related to the version string, or the build time, both of which are acceptable.

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Deepak Bhole
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 16:26:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 9 Oct 2007 16:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23523610.1191961563894.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Andrew Rubinger reopened EJBTHREE-785:
--------------------------------------

             
After reinterpretation on forum, going to remove from tests the bearing of interface hierarchy, and instead focus on the following construct:

@Remote
public interface MyBusiness{}

public MySuper implements MyBusiness{}

@Stateless
public class MyBusinessBean extends MySuper{}





> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 17:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 17:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4806) Update the version
 string in
 jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
In-Reply-To: <32131730.1191932283397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13475808.1191963663621.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4806?page=comments#action_12381280 ] 
            
Dimitris Andreadis commented on JBAS-4806:
------------------------------------------

Thanks!

> Update the version string in jacorb 2.3.0jboss.patch5 and rebuild the 2.3.0jboss.patch5-brew artifact
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4806
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4806
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Dimitris Andreadis
>         Assigned To: Deepak Bhole
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> I have just noticed a minor glitch in jacorb 2.3.0jboss.patch5: the version
> string has not been updated, so the jacorb library will still identify itself
> as "JacORB 2.3.0 (JBoss patch 4)". See
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/jacorb-2.3.0-version.patch
> While this is a minor thing, it may cause confusion as the version string
> is printed out when JacORB is used in a verbose logging level. In order to
> avoid support troubles, you guys may want to fix the patch number in the
> version string before AS 4.2.2 goes out. *If* you do this, then update also
> the patch number in the README file, which is at patch 3:
> http://repository.jboss.com/jacorb/2.3.0jboss.patch5-brew/src/README ;-)
> Regards,
> Francisco 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 17:04:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 17:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4657) Upgrade JBossWeb
 to 2.1.0.CR4 (from 2.0.1.CR7)
In-Reply-To: <614928.1188830958251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14427164.1191963843380.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4657?page=comments#action_12381281 ] 
            
Dimitris Andreadis commented on JBAS-4657:
------------------------------------------

Using 2.1.0.CR6

> Upgrade JBossWeb to 2.1.0.CR4 (from 2.0.1.CR7)
> ----------------------------------------------
>
>                 Key: JBAS-4657
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4657
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>            Reporter: Dimitris Andreadis
>         Assigned To: Remy Maucherat
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Component upgrades need to be tracked in JIRA.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 17:11:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 9 Oct 2007 17:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4716) Update common-core to
	2.2.2.GA
In-Reply-To: <9279917.1189681040331.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3819762.1191964263468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4716?page=all ]

Dimitris Andreadis closed JBAS-4716.
------------------------------------

    Resolution: Done

Done

> Update common-core to 2.2.2.GA
> ------------------------------
>
>                 Key: JBAS-4716
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4716
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Common-core has fixes we need. Since further fixes are possible maybe move to a 2.2.2-snapshot release first.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:33:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-817) Release 2.2.2.SP2
Message-ID: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>

Release 2.2.2.SP2
-----------------

                 Key: JBREM-817
                 URL: http://jira.jboss.com/jira/browse/JBREM-817
             Project: JBoss Remoting
          Issue Type: Release
      Security Level: Public (Everyone can see)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-811) Privileged Block
 to create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5987584.1191969543594.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-811?page=comments#action_12381294 ] 
            
Ron Sigal commented on JBREM-811:
---------------------------------

Fix applied to branch remoting_2_2_0_GA for release 2.2.2.SP2.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.2.2.GA, 2.4.0.Beta1 (Pinto)
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.2.2.GA_CP01, 2.2.2.SP2, 2.4.0.Beta1 (Pinto)
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-817) Release 2.2.2.SP2
In-Reply-To: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32006576.1191969543360.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-817?page=all ]

Ron Sigal updated JBREM-817:
----------------------------

        Fix Version/s: 2.2.2.SP2
    Affects Version/s: 2.2.2.SP2

> Release 2.2.2.SP2
> -----------------
>
>                 Key: JBREM-817
>                 URL: http://jira.jboss.com/jira/browse/JBREM-817
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.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

        


From jira-events at lists.jboss.org  Tue Oct  9 18:41:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 18:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13059570.1191969663380.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381296 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Fix applied to branch remoting_2_2_0_GA for release 2.2.2.SP2.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 19:46:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Tue, 9 Oct 2007 19:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1739) Replace use to
 QName constuctor to use of QName.valueOf where appropriate.
Message-ID: <25711751.1191973563369.JavaMail.jira@cloud.prod.atl2.jboss.com>

Replace use to QName constuctor to use of QName.valueOf where appropriate.
--------------------------------------------------------------------------

                 Key: JBPORTAL-1739
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1739
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core, Portal WSRP
    Affects Versions: 2.6.3 Final, 2.8 Final
            Reporter: Chris Laprun
         Assigned To: Chris Laprun
            Priority: Minor
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 21:36:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Tue, 9 Oct 2007 21:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-453)
 maven-jbossaop-plugin requires
 artifact maven-jbossaop-plugin on compile classpath
In-Reply-To: <31000254.1186523875263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20921485.1191980163557.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-453?page=comments#action_12381313 ] 
            
Jason T. Greene commented on JBAOP-453:
---------------------------------------

This plugin _MUST_ use  the projects dependencies.  Otherwise how can AOP process all known class files?

Consider the simple scenario of a project class inheriting a class in a dependent library. Since the classpath only contains the output directory, it will not be loaded, and thus aopc will fail. If you define all of this in the plugin config, then will end up duplicating every dependency in your project twice.

> maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath
> ----------------------------------------------------------------------------------
>
>                 Key: JBAOP-453
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-453
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: maven 2
>            Reporter: Anders Andersen
>         Assigned To: Stale Pedersen
>
> In order to use the plugin I have to add the following dependencies to the client artifact dependency list.
>     <dependency>
>       <groupId>org.jboss.maven.plugins</groupId>
>       <artifactId>maven-jbossaop-plugin</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-aop</artifactId>
>       <version>2.0.0.alpha2</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-common</artifactId>
>       <version>4.0.2</version>
>     </dependency>
>     <dependency>
>       <groupId>concurrent</groupId>
>       <artifactId>concurrent</artifactId>
>       <version>1.3.4</version>
>     </dependency>
> This is relative wrong, because all maven internal artifacts ends up being nested dependent om the runtime artifact.
> See lists below.
> I think the statement
>       cl.addArguments(new String[] { "-cp", createClassPathList(project.getArtifacts())});
> is wrong.
> I tried to include only project.getPluginArtifacts(), but it gave me a NPE
> So I am not 100% sure what the code solution should be
> but it is not good to having maven artifacts in the resulting dependency list of the client-artifact
> list: (resulting depenency list)
> The ** marked should not be there
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.jar
> /Users/aka/.m2/repository/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-opends/2.6.1-SNAPSHOT/portal-test-opends-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/isorelax/isorelax/20020414/isorelax-20020414.jar
> /Users/aka/.m2/repository/jgroups/jgroups-all/2.2.7/jgroups-all-2.2.7.jar
> /Users/aka/.m2/repository/jboss/jboss-common/4.0.2/jboss-common-4.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-xml-binding/5.0.0.Alpha/jboss-xml-binding-5.0.0.Alpha.jar
> /Users/aka/.m2/repository/jboss/jboss-cache/1.2.2/jboss-cache-1.2.2.jar
> /Users/aka/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar
> /Users/aka/.m2/repository/jboss/jboss-j2se/200504122039/jboss-j2se-200504122039.jar
> /Users/aka/.m2/repository/jboss/jbossha/4.0.2/jbossha-4.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-minimal/4.0.2/jboss-minimal-4.0.2.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-common-client/4.0.4.GA/jboss-common-client-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server/2.6.1-SNAPSHOT/portal-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-saaj/4.0.4.GA/jboss-saaj-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-system/4.0.4.GA/jboss-system-4.0.4.GA.jar
> /Users/aka/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar
> /Users/aka/.m2/repository/org/jboss/portal/core/portal-core/2.6.1-SNAPSHOT/portal-core-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/javassist/3.4.ga/javassist-3.4.ga.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test/2.6.1-SNAPSHOT/portal-test-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/format/portal-format/2.6.1-SNAPSHOT/portal-format-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.jar
> /Users/aka/.m2/repository/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar
> /Users/aka/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> /Users/aka/.m2/repository/jboss/jboss-system/4.0.2/jboss-system-4.0.2.jar
> /Users/aka/.m2/repository/javax/mail/mail/1.4/mail-1.4.jar
> /Users/aka/.m2/repository/hibernate/hibernate/3.2.0/hibernate-3.2.0.jar
> /Users/aka/.m2/repository/jboss/jboss-j2ee/4.0.4.GA/jboss-j2ee-4.0.4.GA.jar
> /Users/aka/.m2/repository/jaxen/jaxen/1.0-FCS/jaxen-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server-test-framework/2.6.1-SNAPSHOT/portal-server-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-project/2.0.2/maven-project-2.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-microcontainer/4.0.4.GA/jboss-microcontainer-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common/2.6.1-SNAPSHOT/portal-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/selenium/selenium-java-client-driver/0.0/selenium-java-client-driver-0.0.jar
> /Users/aka/.m2/repository/javax/portlet/portlet-api/1.0/portlet-api-1.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/theme/portal-theme/2.6.1-SNAPSHOT/portal-theme-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.jar
> /Users/aka/.m2/repository/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss/4.0.4.GA/jboss-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
> /Users/aka/.m2/repository/wsdl4j/wsdl4j/1.5.1/wsdl4j-1.5.1.jar
> /Users/aka/.m2/repository/concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/jboss/jboss-backport-concurrent/2.1.0.GA/jboss-backport-concurrent-2.1.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jbosssx/4.0.4.GA/jbosssx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> /Users/aka/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> /Users/aka/.m2/repository/trove/trove/1.1-beta-5/trove-1.1-beta-5.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/2.0.0.alpha2/jboss-aop-2.0.0.alpha2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-model/2.0.2/maven-model-2.0.2.jar
> /Users/aka/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar
> /Users/aka/.m2/repository/log4j/log4j/1.2.8/log4j-1.2.8.jar
> /Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet/2.6.1-SNAPSHOT/portal-portlet-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/jboss-aspect-library/1.5/jboss-aspect-library-1.5.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-server/portal-portlet-server/2.6.1-SNAPSHOT/portal-portlet-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jmx/4.0.4.GA/jboss-jmx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-impl/1.1.1/myfaces-impl-1.1.1.jar
> /Users/aka/.m2/repository/org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/jboss-aop/1.5.0.GA/jboss-aop-1.5.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common-junit/2.6.1-SNAPSHOT/portal-common-junit-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-profile/2.0.2/maven-profile-2.0.2.jar
> /Users/aka/.m2/repository/org/visigoths/freemaker/freemarker/2.3.9/freemarker-2.3.9.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-agent/2.6.1-SNAPSHOT/portal-test-agent-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-dependency/4.0.4.GA/jboss-dependency-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-federation/portal-portlet-federation/2.6.1-SNAPSHOT/portal-portlet-federation-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/msv/msv/20020414/msv-20020414.jar
> /Users/aka/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
> /Users/aka/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
> /Users/aka/.m2/repository/slide/webdavlib/2.0/webdavlib-2.0.jar
> **/Users/aka/.m2/repository/org/jboss/maven/plugins/maven-jbossaop-plugin/1.0-SNAPSHOT/maven-jbossaop-plugin-1.0-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/web/portal-web/2.6.1-SNAPSHOT/portal-web-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-api/1.1.1/myfaces-api-1.1.1.jar
> /Users/aka/.m2/repository/org/jboss/portal/wsrp/portal-wsrp-gen/2.6.1-SNAPSHOT/portal-wsrp-gen-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/jems/portal-jems/2.6.1-SNAPSHOT/portal-jems-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/registration/portal-registration/2.6.1-SNAPSHOT/portal-registration-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jaxrpc/4.0.4.GA/jboss-jaxrpc-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/security/portal-security/2.6.1-SNAPSHOT/portal-security-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/api/portal-api/2.6.1-SNAPSHOT/portal-api-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar
> /Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> /Users/aka/.m2/repository/dom4j/dom4j/1.4/dom4j-1.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/identity/portal-identity/2.6.1-SNAPSHOT/portal-identity-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/explode-common/2.6.1-SNAPSHOT/explode-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet-test-framework/2.6.1-SNAPSHOT/portal-portlet-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.2/plexus-utils-1.4.2.jar
> /Users/aka/.m2/repository/jboss/jnpserver/3.2.3/jnpserver-3.2.3.jar
> /Users/aka/.m2/repository/opends/opends/0.0/opends-0.0.jar

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 21:59:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Tue, 9 Oct 2007 21:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1254)
 drools-repository/jbrms
 should not force log4j and slf4j-log4j12 (it should be test scoped), only
 slf4j-api
In-Reply-To: <5430326.1191766323392.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28058368.1191981543284.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1254?page=comments#action_12381315 ] 
            
Michael Neale commented on JBRULES-1254:
----------------------------------------

What geoffrey says makes sense. but 99% of the time they will use the war as a "self contained" unit anyway. 

> drools-repository/jbrms should not force log4j and slf4j-log4j12 (it should be test scoped), only slf4j-api
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1254
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1254
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Geoffrey De Smet
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>
> log4j and slf4j-log4j12 should be test scoped, because only for the tests they are needed, but users can choose their logging implementation themselves.
> In examples you'll probably want to make them runtime scoped.
> slf4j-api is a direct compile time dependency, although currently it's retrieved as a "pseudo transitive dependency" through slf4j-log4j12 which explains why it currently compiles anyway.
> See drools-repository/pom.xml where I 've commented what I propose to change:
>  <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-api</artifactId>
>         </dependency>
>         <dependency>
>           <groupId>org.slf4j</groupId>
>           <artifactId>slf4j-log4j12</artifactId>
>           <scope>test</scope>
>         </dependency>
>         <dependency>
>           <groupId>log4j</groupId>
>           <artifactId>log4j</artifactId>
>           <scope>test</scope>
>         </dependency>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 22:56:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 22:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-817) Release 2.2.2.SP2
In-Reply-To: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8292922.1191984963265.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-817?page=comments#action_12381318 ] 
            
Ron Sigal commented on JBREM-817:
---------------------------------

A 2.2.2.SP2 directory has been created in the repository, with a jboss-remoting.jar built with jdk 1.4.

> Release 2.2.2.SP2
> -----------------
>
>                 Key: JBREM-817
>                 URL: http://jira.jboss.com/jira/browse/JBREM-817
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.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

        


From jira-events at lists.jboss.org  Tue Oct  9 22:58:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 22:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21211517.1191985083220.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381319 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

The default behavior remains the same.  To get the new behavior, the server should be configured with the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.RETURN_EXCEPTION (actual value "return-exception")  set to true.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct  9 23:08:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 9 Oct 2007 23:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4714) Upgrade
 JBossRemoting to 2.2.2.SP1 (from 2.2.0.GA)
In-Reply-To: <17799303.1189663991032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13703743.1191985683485.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4714?page=all ]

Ron Sigal reopened JBAS-4714:
-----------------------------

             
Remoting 2.2.2.SP2 is now available.  It includes fixes for the following:

JBREM-687: allow binding to 0.0.0.0	 
JBREM-811: Privileged Block to create Class Loader 	 
JBREM-813: ServletServerInvoker should return an exception instead of just an error message

> Upgrade JBossRemoting to 2.2.2.SP1 (from 2.2.0.GA)
> --------------------------------------------------
>
>                 Key: JBAS-4714
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4714
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The upgrade from Remoting 2.2.0.GA to 2.2.2.GA is occasioned largely by a set of features and fixes for JBossMessaging 1.4. 
> The further upgrade to 2.2.2.SP1 consists of fixes for JBREM-653 and JBREM-750.  The fix for JBREM-750 was supposed to go into 2.2.2.GA but was overlooked.  The fix for JBREM-653 is needed for ESB 4.2.1.
> These fixes have been applied to the remoting_2_2_0_GA branch from which 2.2.2.GA was released.  As soon as the related unit tests pass on cruisecontrol, the branch will be tagged remoting_2_2_2_SP1.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 01:02:12 2007
From: jira-events at lists.jboss.org (Peter Lynch (JIRA))
Date: Wed, 10 Oct 2007 01:02:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12029956.1191992532506.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381325 ] 
            
Peter Lynch commented on JBRULES-1260:
--------------------------------------

I can confirm this happened for me as well with the same setup.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 01:14:03 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Wed, 10 Oct 2007 01:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19845735.1191993243344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=all ]

Joshua Jackson reopened JBRULES-1260:
-------------------------------------

             
Can we please re-test this again as another user has confirmed that this also happens to him.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 02:03:04 2007
From: jira-events at lists.jboss.org (Roland Bali (JIRA))
Date: Wed, 10 Oct 2007 02:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4491) Server startup
 failure with JDK 1.6
In-Reply-To: <30746220.1182198611683.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20003992.1191996184791.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12381328 ] 
            
Roland Bali commented on JBAS-4491:
-----------------------------------

This might be obvious since it seems to be a 1.6 bug but the error persists on JDK 1.6.0_03-b05 in Windows.

> Server startup failure with JDK 1.6
> -----------------------------------
>
>                 Key: JBAS-4491
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4491
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: Windows
>            Reporter: Greg Zoller
>         Attachments: Signature.java
>
>
> An out-of-the-box installation of JBoss 5.0.0 Beta2 running with JDK 1.6 produces the following exception upon startup.  Not sure the whys or wherefores but am pretty sure its not a good thing.
> 13:24:13,467 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
> 13:24:13,467 INFO  [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017)
> 13:24:13,467 INFO  [ServerImpl] Home Dir: C:\Program Files\jboss-5.0.0.Beta2
> 13:24:13,467 INFO  [ServerImpl] Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/
> 13:24:13,467 INFO  [ServerImpl] Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/lib/
> 13:24:13,467 INFO  [ServerImpl] Patch URL: null
> 13:24:13,467 INFO  [ServerImpl] Server Name: default
> 13:24:13,467 INFO  [ServerImpl] Server Home Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:13,467 INFO  [ServerImpl] Server Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/
> 13:24:13,467 INFO  [ServerImpl] Server Data Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\data
> 13:24:13,467 INFO  [ServerImpl] Server Temp Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\tmp
> 13:24:13,467 INFO  [ServerImpl] Server Config URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/
> 13:24:13,467 INFO  [ServerImpl] Server Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/lib/
> 13:24:13,467 INFO  [ServerImpl] Root Deployment Filename: jboss-service.xml
> 13:24:13,499 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml
> 13:24:14,831 INFO  [ProfileImpl] Using profile root:C:\Program Files\jboss-5.0.0.Beta2\server\default
> 13:24:15,913 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter state=Described
> java.lang.IllegalStateException: Class not found: [Ljava.lang.String;
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125)
> 	at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292)
> 	at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138)
> 	at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280)
> 	at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152)
> 	at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103)
> 	at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197)
> 	at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136)
> 	at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> 	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724)
> 	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555)
> 	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289)
> 	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272)
> 	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119)
> 	at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76)
> 	at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBootstrap.java:295)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:222)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at java.net.URLClassLoader$1.run(Unknown Source)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at java.lang.ClassLoader.loadClass(Unknown Source)
> 	at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170)
> 	... 35 more
> 13:24:16,258 INFO  [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc.
> 13:24:16,258 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
> 13:24:16,305 INFO  [JMXKernel] Legacy JMX core initialized
> Failed to boot JBoss:
> java.lang.RuntimeException: Exception during Bootstrap
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99)
> 	at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
> 	at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
> 	at org.jboss.Main.boot(Main.java:210)
> 	at org.jboss.Main$1.run(Main.java:522)
> 	at java.lang.Thread.run(Unknown Source)
> Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
> VFSBootstrapScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeployerScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> VFSDeploymentScanner
>  -> DeploymentFilter{Configured:**ERROR**}
> *** CONTEXTS IN ERROR: Name -> Error
> DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String;
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileServiceBootstrap.java:389)
> 	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236)
> 	at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> 	... 5 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 02:28:03 2007
From: jira-events at lists.jboss.org (Tuomas Kiviaho (JIRA))
Date: Wed, 10 Oct 2007 02:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1263) Mark
 xml-apis/xercesImpl as
 optional dependencies in drools-compiler pom.xml
Message-ID: <31321311.1191997683967.JavaMail.jira@cloud.prod.atl2.jboss.com>

Mark xml-apis/xercesImpl as optional dependencies in drools-compiler pom.xml
----------------------------------------------------------------------------

                 Key: JBRULES-1263
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1263
             Project: JBoss Drools
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Tuomas Kiviaho
         Assigned To: Mark Proctor


As commented in JBRULES-992 jdk provides xml-apis already so the declaration could be marked as optional or dropped completely. Marking of xercesImpl as optional requires compile time dependency check. Dropping it completely requires also verification that it isn't used anywhere at runtime.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:02:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 04:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1073) JMS messages
 are not taken from the queue after database connection recovery
In-Reply-To: <22436968.1190115251065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9566890.1192003323317.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1073?page=all ]

Tim Fox closed JBMESSAGING-1073.
--------------------------------

    Resolution: Cannot Reproduce Bug

User cannot reproduce with 1.4.0.GA

> JMS messages are not taken from the queue after database connection recovery
> ----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1073
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1073
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.3.0.GA
>         Environment: JBoss.4.2.1 JBossMessaging 1.3GA Oracle 10g database jdk 1.5 on solaris intel
>            Reporter: Evgueni Smoliar
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> We have  2 jboss server running in the cluster. Messaging is also configured with clustered queues. 
> At one moment we had a database crash. Database was recovered in 5 minutes and connections from jboss were reestablished . All applications works OK, new messages processed correctly. The problem is with the messages processed during the crash time. JMS could not commit them and couldn't rollback at the time. After reestablishing of the connection this messages are not redelivered anymore. 
> The only way to get those message delivered is to restart jboss servers. 
> This is strange problem which we never experienced with old jboss-jms implementation.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:38:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 10 Oct 2007 04:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29327421.1192005483526.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Carlo de Wolf updated EJBTHREE-1062:
------------------------------------

    Priority: Critical  (was: Major)

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>            Priority: Critical
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:40:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 10 Oct 2007 04:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12312897.1192005603702.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Carlo de Wolf reassigned EJBTHREE-1062:
---------------------------------------

    Assignee: Andrew Rubinger

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 04:40:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 10 Oct 2007 04:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32689183.1192005603888.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Carlo de Wolf updated EJBTHREE-1062:
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 05:41:05 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 05:41:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1740) cms admin
 portlet checks for hardcoded role named 'admin'
Message-ID: <26476529.1192009265578.JavaMail.jira@cloud.prod.atl2.jboss.com>

cms admin portlet checks for hardcoded role named 'admin'
---------------------------------------------------------

                 Key: JBPORTAL-1740
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1740
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final
            Reporter: Tobias Roth
         Assigned To: Sohil Shah


See also http://jira.jboss.com/jira/browse/JBPORTAL-1646

I found another hardcoded use of 'admin'. The effect of having this is that even with the change I described above, permissions of cms nodes cannot be changed by users that are not in role called 'admin'.

Why does the security console need to have separate access rights? Aren't the access rights for the CMS admin console enough?



In core-cms/src/main/org/jboss/portal/core/cms/ui/admin/CMSAdminPortlet.java:

   private boolean isSecurityConsoleAccessible(PortletRequest portletRequest)
   {
      try
      {
         boolean isAccessible = false;

         if (portletRequest.getUserPrincipal() != null)
         {
            User user = this.userModule.findUserByUserName(portletRequest.getUserPrincipal().getName());
            Set roles = this.membershipModule.getRoles(user);
            if (roles != null)
            {
               for (Iterator itr = roles.iterator(); itr.hasNext();)
               {
                  Role role = (Role)itr.next();
                  if (role.getName().equalsIgnoreCase("admin"))
                  {
                     isAccessible = true;
                     break;
                  }
               }
            }
         }

         return isAccessible;
      }
      catch (Exception e)
      {
         return false;
      }
   }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 05:45:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 05:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17984461.1192009503474.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_12381366 ] 
            
Tobias Roth commented on JBPORTAL-1733:
---------------------------------------

I just created JBPORTAL-1740. Sorry, didn't see this one.

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 05:47:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 05:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1740) cms admin
 portlet checks for hardcoded role named 'admin'
In-Reply-To: <26476529.1192009265578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33063901.1192009623838.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1740?page=comments#action_12381368 ] 
            
Tobias Roth commented on JBPORTAL-1740:
---------------------------------------

Sorry, this is a duplicate for JBPORTAL-1733. I have more info in here though.

> cms admin portlet checks for hardcoded role named 'admin'
> ---------------------------------------------------------
>
>                 Key: JBPORTAL-1740
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1740
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>
> See also http://jira.jboss.com/jira/browse/JBPORTAL-1646
> I found another hardcoded use of 'admin'. The effect of having this is that even with the change I described above, permissions of cms nodes cannot be changed by users that are not in role called 'admin'.
> Why does the security console need to have separate access rights? Aren't the access rights for the CMS admin console enough?
> In core-cms/src/main/org/jboss/portal/core/cms/ui/admin/CMSAdminPortlet.java:
>    private boolean isSecurityConsoleAccessible(PortletRequest portletRequest)
>    {
>       try
>       {
>          boolean isAccessible = false;
>          if (portletRequest.getUserPrincipal() != null)
>          {
>             User user = this.userModule.findUserByUserName(portletRequest.getUserPrincipal().getName());
>             Set roles = this.membershipModule.getRoles(user);
>             if (roles != null)
>             {
>                for (Iterator itr = roles.iterator(); itr.hasNext();)
>                {
>                   Role role = (Role)itr.next();
>                   if (role.getName().equalsIgnoreCase("admin"))
>                   {
>                      isAccessible = true;
>                      break;
>                   }
>                }
>             }
>          }
>          return isAccessible;
>       }
>       catch (Exception e)
>       {
>          return false;
>       }
>    }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:00:03 2007
From: jira-events at lists.jboss.org (Alexandre Gattiker (JIRA))
Date: Wed, 10 Oct 2007 06:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
Message-ID: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
------------------------------------------------------------------

                 Key: JBRULES-1264
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Alexandre Gattiker
         Assigned To: Mark Proctor


Removing one of the three rules magically solves the problem.


java.lang.NullPointerException
	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
	at com.sample.DroolsTest.main(DroolsTest.java:21)




package com.sample;

import java.io.InputStreamReader;
import java.io.Reader;

import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;

public class DroolsTest
{

    public static final void main(String[] args)
    {
        try
        {
            RuleBase ruleBase = readRule();
            WorkingMemory workingMemory = ruleBase.newStatefulSession();
            workingMemory.insert(new Attribute());
            workingMemory.insert(new Message());
            workingMemory.fireAllRules();
        }
        catch (Throwable t)
        {
            t.printStackTrace();
        }
    }

    private static RuleBase readRule() throws Exception
    {
        Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
        PackageBuilder builder = new PackageBuilder();
        builder.addPackageFromDrl(source);
        Package pkg = builder.getPackage();
        RuleBase ruleBase = RuleBaseFactory.newRuleBase();
        ruleBase.addPackage(pkg);
        return ruleBase;
    }

    public static class Message
    {
        //empty
    }

    public static class Attribute
    {

        public Integer getValue()
        {
            return null;
        }

    }

}


package com.sample
 
import com.sample.DroolsTest.Message;
import com.sample.DroolsTest.Attribute;
 
rule "rule_1"
	
	when
		Message()
		Attribute(value == 1)
	then
		System.err.println("case 1");
end

rule "rule_2"
	
	when
		Message()
		Attribute(value == 2)
	then
		System.err.println("case 2");
end


rule "rule_3"
	
	when
		Message()
		$a:Attribute(value == 3)
	then
		System.err.println("case 3");
end


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:53:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Wed, 10 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1741) PortalURL
 security not honoured
Message-ID: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>

PortalURL security not honoured
-------------------------------

                 Key: JBPORTAL-1741
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core
    Affects Versions: 2.6.2 Final, 2.6.1 Final, 2.6 Final, 2.6.3 Final
            Reporter: Julien Viet
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final
         Attachments: PortalURLSecurity.zip

PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:53:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Wed, 10 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18667168.1192013583422.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Julien Viet updated JBPORTAL-1741:
----------------------------------

    Attachment: PortalURLSecurity.zip

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:55:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 06:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27991976.1192013703290.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Thomas Heute reassigned JBPORTAL-1741:
--------------------------------------

    Assignee: Thomas Heute  (was: Julien Viet)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 06:57:19 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Wed, 10 Oct 2007 06:57:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7278496.1192013839923.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Julien Viet updated JBPORTAL-1741:
----------------------------------

    Priority: Critical  (was: Major)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Thomas Heute
>            Priority: Critical
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:05:13 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 10 Oct 2007 07:05:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4714) Upgrade
 JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)
In-Reply-To: <17799303.1189663991032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22772019.1192014313382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4714?page=all ]

Dimitris Andreadis updated JBAS-4714:
-------------------------------------

    Summary: Upgrade JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)  (was: Upgrade JBossRemoting to 2.2.2.SP1 (from 2.2.0.GA))

> Upgrade JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)
> --------------------------------------------------
>
>                 Key: JBAS-4714
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4714
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The upgrade from Remoting 2.2.0.GA to 2.2.2.GA is occasioned largely by a set of features and fixes for JBossMessaging 1.4. 
> The further upgrade to 2.2.2.SP1 consists of fixes for JBREM-653 and JBREM-750.  The fix for JBREM-750 was supposed to go into 2.2.2.GA but was overlooked.  The fix for JBREM-653 is needed for ESB 4.2.1.
> These fixes have been applied to the remoting_2_2_0_GA branch from which 2.2.2.GA was released.  As soon as the related unit tests pass on cruisecontrol, the branch will be tagged remoting_2_2_2_SP1.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:07:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 07:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1646) portal-cms
 depends on existence of user 'admin'
In-Reply-To: <23503800.1187790682411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32935949.1192014423344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1646?page=all ]

Thomas Heute updated JBPORTAL-1646:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> portal-cms depends on existence of user 'admin'
> -----------------------------------------------
>
>                 Key: JBPORTAL-1646
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1646
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> cms/src/main/org/jboss/portal/cms/impl/jcr/JCRCMS.java has the user 'admin' hardcoded:
>    /** Loads content from sar and adds it to the repo. */
>    public void createContent() throws Exception
>    {
>       log.info("Creating default CMS content.");
>       
>       // Get the content
>       URL root = Thread.currentThread().getContextClassLoader().getResource(defaultContentLocation);
>       
>       //make the user executing these to create the default content, an 'Admin' user
>       //without this, the fine grained security won't allow the creation
>       UserModule userModule = getUserModule();
>       if(userModule != null)
>       {
> 	      org.hibernate.Session session = org.jboss.portal.cms.hibernate.state.Tools.getOpenSession();
> 	      org.hibernate.Transaction tx = session.beginTransaction();
> 	      User user = userModule.findUserByUserName("admin"); // HERE
> 	      if(user!=null)
> 	      {
> 	    	  JCRCMS.getUserInfo().set(user);
> 	      }
> 	      tx.rollback();
> 	      org.jboss.portal.cms.hibernate.state.Tools.closeSession(session);
>       }	
> If it doesn't exist (for example because LDAP is being used), portal-cms cannopt be deployed, and several database tables are not created. If 'admin' is changed to an existing user, everything works fine.
> There is another reference to 'admin' in cms/src/main/org/jboss/portal/cms/impl/jcr/command/ACLEnforcer.java, but leaving this as it is doesn't seem to have any negative effect.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:11:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1646) portal-cms
 depends on existence of user 'admin'
In-Reply-To: <23503800.1187790682411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4513258.1192014663344.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1646?page=comments#action_12381377 ] 
            
Tobias Roth commented on JBPORTAL-1646:
---------------------------------------

This is not the same as 1733 and 1740. This issue is unique, while 1733 and 1740 are the same.

> portal-cms depends on existence of user 'admin'
> -----------------------------------------------
>
>                 Key: JBPORTAL-1646
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1646
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> cms/src/main/org/jboss/portal/cms/impl/jcr/JCRCMS.java has the user 'admin' hardcoded:
>    /** Loads content from sar and adds it to the repo. */
>    public void createContent() throws Exception
>    {
>       log.info("Creating default CMS content.");
>       
>       // Get the content
>       URL root = Thread.currentThread().getContextClassLoader().getResource(defaultContentLocation);
>       
>       //make the user executing these to create the default content, an 'Admin' user
>       //without this, the fine grained security won't allow the creation
>       UserModule userModule = getUserModule();
>       if(userModule != null)
>       {
> 	      org.hibernate.Session session = org.jboss.portal.cms.hibernate.state.Tools.getOpenSession();
> 	      org.hibernate.Transaction tx = session.beginTransaction();
> 	      User user = userModule.findUserByUserName("admin"); // HERE
> 	      if(user!=null)
> 	      {
> 	    	  JCRCMS.getUserInfo().set(user);
> 	      }
> 	      tx.rollback();
> 	      org.jboss.portal.cms.hibernate.state.Tools.closeSession(session);
>       }	
> If it doesn't exist (for example because LDAP is being used), portal-cms cannopt be deployed, and several database tables are not created. If 'admin' is changed to an existing user, everything works fine.
> There is another reference to 'admin' in cms/src/main/org/jboss/portal/cms/impl/jcr/command/ACLEnforcer.java, but leaving this as it is doesn't seem to have any negative effect.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:11:03 2007
From: jira-events at lists.jboss.org (Tobias Roth (JIRA))
Date: Wed, 10 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role
 hardcoded somewhere
In-Reply-To: <5733160.1191340623365.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <569225.1192014663539.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_12381378 ] 
            
Tobias Roth commented on JBPORTAL-1733:
---------------------------------------

This is not the same as 1647. This issue is the same as 1740.

> CMS admin role hardcoded somewhere
> ----------------------------------
>
>                 Key: JBPORTAL-1733
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: Any
>            Reporter: Luc Boudreau
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
>  - Modify platform to use another admin role name
>  - Create user with new admin role and old Admin role
>  - Change security on root node of CMS and make the new role the manager
>  - Change the user's roles by removing the old Admin role
>  - Try to manage the root node : Access Denided

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:31:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 07:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1454) Redo the CMS
 Action Menu for the CMS Admin tool
In-Reply-To: <5514709.1179756952366.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18161337.1192015863558.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1454?page=all ]

Thomas Heute resolved JBPORTAL-1454.
------------------------------------

    Resolution: Out of Date

> Redo the CMS Action Menu for the CMS Admin tool
> -----------------------------------------------
>
>                 Key: JBPORTAL-1454
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1454
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.CR2
>            Reporter: Sohil Shah
>         Assigned To: Sohil Shah
>             Fix For: 2.8 Final
>
>
> The select Action drop down has a small triangle to the left of it, along with all of the items in the drop down. These should be removed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 07:35:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 07:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1646) portal-cms
 depends on existence of user 'admin'
In-Reply-To: <23503800.1187790682411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8092840.1192016103302.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1646?page=comments#action_12381381 ] 
            
Thomas Heute commented on JBPORTAL-1646:
----------------------------------------

Oups sorrry clicked too fast

> portal-cms depends on existence of user 'admin'
> -----------------------------------------------
>
>                 Key: JBPORTAL-1646
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1646
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.1 Final
>            Reporter: Tobias Roth
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> cms/src/main/org/jboss/portal/cms/impl/jcr/JCRCMS.java has the user 'admin' hardcoded:
>    /** Loads content from sar and adds it to the repo. */
>    public void createContent() throws Exception
>    {
>       log.info("Creating default CMS content.");
>       
>       // Get the content
>       URL root = Thread.currentThread().getContextClassLoader().getResource(defaultContentLocation);
>       
>       //make the user executing these to create the default content, an 'Admin' user
>       //without this, the fine grained security won't allow the creation
>       UserModule userModule = getUserModule();
>       if(userModule != null)
>       {
> 	      org.hibernate.Session session = org.jboss.portal.cms.hibernate.state.Tools.getOpenSession();
> 	      org.hibernate.Transaction tx = session.beginTransaction();
> 	      User user = userModule.findUserByUserName("admin"); // HERE
> 	      if(user!=null)
> 	      {
> 	    	  JCRCMS.getUserInfo().set(user);
> 	      }
> 	      tx.rollback();
> 	      org.jboss.portal.cms.hibernate.state.Tools.closeSession(session);
>       }	
> If it doesn't exist (for example because LDAP is being used), portal-cms cannopt be deployed, and several database tables are not created. If 'admin' is changed to an existing user, everything works fine.
> There is another reference to 'admin' in cms/src/main/org/jboss/portal/cms/impl/jcr/command/ACLEnforcer.java, but leaving this as it is doesn't seem to have any negative effect.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:23:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 08:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1265) literal/formula
 could be clearer in guided editor RHS
Message-ID: <29918365.1192018983205.JavaMail.jira@cloud.prod.atl2.jboss.com>

literal/formula could be clearer in guided editor RHS
-----------------------------------------------------

                 Key: JBRULES-1265
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1265
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:31:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1265) literal/formula
 could be clearer in guided editor RHS
In-Reply-To: <29918365.1192018983205.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19853589.1192019463466.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1265?page=all ]

Michael Neale closed JBRULES-1265.
----------------------------------

    Resolution: Done

> literal/formula could be clearer in guided editor RHS
> -----------------------------------------------------
>
>                 Key: JBRULES-1265
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1265
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:33:18 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 08:33:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2964703.1192019598156.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381390 ] 
            
Mark Proctor commented on JBRULES-1260:
---------------------------------------

Are you using Eclipse3.2?

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:33:18 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 08:33:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18574449.1192019598577.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381391 ] 
            
Mark Proctor commented on JBRULES-1260:
---------------------------------------

The  plugin  does  not work with Eclipse3.3.

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 08:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 08:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1263) Mark
 xml-apis/xercesImpl as
 optional dependencies in drools-compiler pom.xml
In-Reply-To: <31321311.1191997683967.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16018730.1192019703929.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1263?page=all ]

Mark Proctor closed JBRULES-1263.
---------------------------------

    Resolution: Out of Date

I'm not changing this  now for the  4.0.x series, but  I've dropped  it already  for 4.1.0.

> Mark xml-apis/xercesImpl as optional dependencies in drools-compiler pom.xml
> ----------------------------------------------------------------------------
>
>                 Key: JBRULES-1263
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1263
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Tuomas Kiviaho
>         Assigned To: Mark Proctor
>
> As commented in JBRULES-992 jdk provides xml-apis already so the declaration could be marked as optional or dropped completely. Marking of xercesImpl as optional requires compile time dependency check. Dropping it completely requires also verification that it isn't used anywhere at runtime.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 09:05:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 10 Oct 2007 09:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4807) Cannot redeploy
 webapp after deploy failure
Message-ID: <27444204.1192021503535.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot redeploy webapp after deploy failure
-------------------------------------------

                 Key: JBAS-4807
                 URL: http://jira.jboss.com/jira/browse/JBAS-4807
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Deployment services
            Reporter: Thomas Diesler
         Assigned To: Dimitris Andreadis
             Fix For:  JBossAS-5.0.0.Beta3


If a webapp cannot be deployed due to some deployment problem, this webapp is not taken down properly.
A subsequent deployment of the webapp fails

14:55:03,570 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war state=PostClassLoader mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war
        at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175)
        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
        at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)

Caused by: org.jboss.ws.WSException: Cannot find port in wsdl: {http://ws.com/}ProviderPort
        at org.jboss.ws.metadata.builder.MetaDataBuilder.replaceAddressLocation(MetaDataBuilder.java:338)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSProviderMetaDataBuilder.buildProviderMetaData(JAXWSProviderMetaDataBuilder.java:147)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:55)
        at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
        at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
        at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
        at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)

14:55:03,744 WARN  [MainDeployer] undeploy 'file:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war' : package not deployed
14:55:03,770 WARN  [MainDeployer] undeploy 'file:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war' : package not deployed
14:55:10,884 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/trunk/output/tests/libs/jaxws-jbws1807.war is already installed.






-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 09:32:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 10 Oct 2007 09:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7908950.1192023123258.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Thomas Heute resolved JBPORTAL-1741.
------------------------------------

    Resolution: Done
      Assignee: Julien Viet  (was: Thomas Heute)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final, 2.6.3 Final
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>            Priority: Critical
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 09:38:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 09:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
Message-ID: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix tutorial for 2.1.0 series
-----------------------------

                 Key: JBCACHE-1195
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.GA


As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.

Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Wed Oct 10 10:35:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 10 Oct 2007 10:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1061) Look into
 StatefulUnitTestCase, determine purpose
In-Reply-To: <7131874.1191939425385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11920156.1192026903392.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1061?page=comments#action_12381427 ] 
            
Brian Stansberry commented on EJBTHREE-1061:
--------------------------------------------

This is the test in the org.jboss.ejb3.test.cache.unit package.  There are SFSBs tests in org.jboss.ejb3.test.stateful and org.jboss.ejb3.test.clusteredsession that may cover the same stuff.

> Look into StatefulUnitTestCase, determine purpose
> -------------------------------------------------
>
>                 Key: EJBTHREE-1061
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1061
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Ensure the 7 tests in StatefulUnitTestCase are valid, testing for their intentions, and report any inconsistancies to Brian.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 10:43:04 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 10:43:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1266) Composite facts
 types (OR, AND) not rendering correctly
Message-ID: <7101908.1192027384751.JavaMail.jira@cloud.prod.atl2.jboss.com>

Composite facts types (OR, AND) not rendering correctly
-------------------------------------------------------

                 Key: JBRULES-1266
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1266
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.0.3, 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 10:51:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 10 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1266) Composite facts
 types (OR, AND) not rendering correctly
In-Reply-To: <7101908.1192027384751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21968329.1192027863430.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1266?page=all ]

Michael Neale closed JBRULES-1266.
----------------------------------

    Resolution: Done

> Composite facts types (OR, AND) not rendering correctly
> -------------------------------------------------------
>
>                 Key: JBRULES-1266
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1266
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:12:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 11:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-999) Bridge
 startup should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <264541.1192029123459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=all ]

Tim Fox reopened JBMESSAGING-999:
---------------------------------

      Assignee: Tim Fox  (was: Sergey Koshcheyev)
             

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:12:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 11:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-999) Bridge startup
 should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10977953.1192029123596.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=all ]

Tim Fox updated JBMESSAGING-999:
--------------------------------

        Fix Version/s: 1.4.0.SP1
                           (was: 1.4.0.CR1)
    Affects Version/s: 1.4.0.GA

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:13:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 10 Oct 2007 11:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-999) Bridge
 startup should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14295712.1192029184233.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=comments#action_12381446 ] 
            
Tim Fox commented on JBMESSAGING-999:
-------------------------------------

I've re-opened this since it seems the task wasn't completed properly.

Although retry logic was added on the Bridge class itself.

It would still fail since the destination lookups are made from the BridgeService class before the Bridge is instantiated.

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:19:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 10 Oct 2007 11:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4808) MBean Service to bind
 DistributedTimeCachePolicy to JNDI under java:
Message-ID: <5576125.1192029543311.JavaMail.jira@cloud.prod.atl2.jboss.com>

MBean Service to bind DistributedTimeCachePolicy to JNDI under java:
--------------------------------------------------------------------

                 Key: JBAS-4808
                 URL: http://jira.jboss.com/jira/browse/JBAS-4808
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Security
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Anil Saldhana
         Assigned To: Stefan Guilhen
             Fix For: JBossAS-4.2.3.GA


We have many requests for clustering of the authentication cache in the JBoss security managers.

We need a MBean service that can be configured (on demand by user)  which will bind the DistributedTimedCachePolicy in JNDI under java: context

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:27:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 11:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10859935.1192030023370.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=comments#action_12381448 ] 
            
Mark Proctor commented on JBRULES-1264:
---------------------------------------

ok I've confirmed this and its a valid bug :(
The isNull checks that where placed in a while ago are on the evaluators, but not on the indexing code - this code is only breaks with the index stuff.

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:39:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 10 Oct 2007 11:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-111) unmarshalling Map with
 XmlJavaTypeAdapter
Message-ID: <25538122.1192030743263.JavaMail.jira@cloud.prod.atl2.jboss.com>

unmarshalling Map with XmlJavaTypeAdapter
-----------------------------------------

                 Key: JBXB-111
                 URL: http://jira.jboss.com/jira/browse/JBXB-111
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Bug
    Affects Versions: JBossXB-2.0.0.CR4
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-2.0.0.CR5


The use-case was taken from http://java.sun.com/javaee/5/docs/api/javax/xml/bind/annotation/adapters/XmlAdapter.html but simplified in the test case

package org.jboss.test.xb.builder.object.element.javatypeadapter.test;
public class JavaTypeAdapterUnitTestCase extends AbstractBuilderTest


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:39:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 10 Oct 2007 11:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-111) unmarshalling Map with
 XmlJavaTypeAdapter
In-Reply-To: <25538122.1192030743263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3050046.1192030743371.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-111?page=all ]

Alexey Loubyansky closed JBXB-111.
----------------------------------

    Resolution: Done

Fixed.

> unmarshalling Map with XmlJavaTypeAdapter
> -----------------------------------------
>
>                 Key: JBXB-111
>                 URL: http://jira.jboss.com/jira/browse/JBXB-111
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> The use-case was taken from http://java.sun.com/javaee/5/docs/api/javax/xml/bind/annotation/adapters/XmlAdapter.html but simplified in the test case
> package org.jboss.test.xb.builder.object.element.javatypeadapter.test;
> public class JavaTypeAdapterUnitTestCase extends AbstractBuilderTest

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:42:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1182) JMX wrappers log
 WARN messages on calling getter for deprecated attributes
In-Reply-To: <18370997.1189447451670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25550239.1192030923386.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1182?page=all ]

Manik Surtani reopened JBCACHE-1182:
------------------------------------

             

> JMX wrappers log WARN messages on calling getter for deprecated attributes
> --------------------------------------------------------------------------
>
>                 Key: JBCACHE-1182
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1182
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA
>
>
> Logged after viewing a cache mbean in AS's jmx-console:
> 12:55:33,437 WARN  [CacheJmxWrapper] MBean attribute 'CacheLoaderConfiguration'
> is deprecated; use 'CacheLoaderConfig'
> 12:55:34,046 WARN  [CacheJmxWrapper] MBean attribute 'UseInterceptorMbeans' is d
> eprecated; use 'ExposeManagementStatistics'
> These should only be logged for the setter; the setter is what implies conscious usage of the outdated API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:42:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1182) JMX wrappers log
 WARN messages on calling getter for deprecated attributes
In-Reply-To: <18370997.1189447451670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29023216.1192030923580.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1182?page=all ]

Manik Surtani resolved JBCACHE-1182.
------------------------------------

    Resolution: Done

> JMX wrappers log WARN messages on calling getter for deprecated attributes
> --------------------------------------------------------------------------
>
>                 Key: JBCACHE-1182
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1182
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA
>
>
> Logged after viewing a cache mbean in AS's jmx-console:
> 12:55:33,437 WARN  [CacheJmxWrapper] MBean attribute 'CacheLoaderConfiguration'
> is deprecated; use 'CacheLoaderConfig'
> 12:55:34,046 WARN  [CacheJmxWrapper] MBean attribute 'UseInterceptorMbeans' is d
> eprecated; use 'ExposeManagementStatistics'
> These should only be logged for the setter; the setter is what implies conscious usage of the outdated API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1099) JDBCCacheLoader
 does not deal with Schema names?
In-Reply-To: <26867781.1181298011551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10082268.1192031062098.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1099?page=all ]

Manik Surtani reopened JBCACHE-1099:
------------------------------------

             

> JDBCCacheLoader does not deal with Schema names?
> ------------------------------------------------
>
>                 Key: JBCACHE-1099
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1099
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR2
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA
>
>
> Should be able to take in a schema name property and prepend this to table names when generating SQL.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1766228.1192031062230.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani reopened JBCACHE-1167:
------------------------------------

             

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4, 2.0.0.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP5, 2.1.0.GA
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1172)
 CacheLoaderInterceptor
 doesn't load data for Node.getKeys() or Node.getData()
In-Reply-To: <12017577.1188097518214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24501869.1192031062358.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1172?page=all ]

Manik Surtani reopened JBCACHE-1172:
------------------------------------

             

> CacheLoaderInterceptor doesn't load data for Node.getKeys() or Node.getData()
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1172
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1172
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> CacheLoaderInterceptor.mustLoad always returns false if there is no data key associated with the MethodCall.  Effect is calls for CacheImpl._getKeys  and _getData don't trigger a load from the cache loader.
> Added tests testKeyKeys() and testGetData() to CacheLoaderTestsBase to show the issue.
> Solution is to add a boolean 'allKeys' variable to CacheLoaderInterceptor.invoke.  Set it to true if the MethodCall is _getKeys or _getData.  Pass the value through to mustLoad, and if true load the data if Node.isDataLoaded returns false.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:22 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1175)
	Option.forceCall(A)sync
In-Reply-To: <31286648.1188585138477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17847357.1192031069668.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=all ]

Manik Surtani reopened JBCACHE-1175:
------------------------------------

             

> Option.forceCall(A)sync
> -----------------------
>
>                 Key: JBCACHE-1175
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Add an option to allow an individual call to go async/sync when the cache overall is configured for the opposite.
> This would only be relevant to calls not running in a tx; transactional replication would use the standard semantic configured for the cache.
> Use case for this is Hibernate timestamp region replication, which needs to go async, while all other Hibernate 2nd level cache traffic goes sync.  A good region-based cache impl would solve the problem as well, but that will surely take quite a while to implement a while while doing it via an Option looks quite trivial.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:29 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:29 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1178) Option to set
	lock timeout
In-Reply-To: <14176892.1189113131136.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31319067.1192031069816.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1178?page=all ]

Manik Surtani reopened JBCACHE-1178:
------------------------------------

             

> Option to set lock timeout
> --------------------------
>
>                 Key: JBCACHE-1178
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1178
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Allow override of the standard lock timeout on a per-invocation basis.
> For background on the specific use case that needs this, see http://lists.jboss.org/pipermail/hibernate-dev/2007-September/002669.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:29 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:29 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1180)
 CacheImpl.toString() prints cache details
In-Reply-To: <29419991.1189446491112.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22693300.1192031069946.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1180?page=all ]

Manik Surtani reopened JBCACHE-1180:
------------------------------------

             

> CacheImpl.toString() prints cache details
> -----------------------------------------
>
>                 Key: JBCACHE-1180
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1180
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Calls CacheImpl.toString(true), thus printing the entire tree.
> In 1.x the equivalent impl was to call toString(false).
> This shows up in the JMX console, which calls toString() on attribute values.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:44:30 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:44:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1181) CacheJmxWrappers
 exposes details as JMX attributes, not operations
In-Reply-To: <24706943.1189446862714.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31932402.1192031070078.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1181?page=all ]

Manik Surtani reopened JBCACHE-1181:
------------------------------------

             

> CacheJmxWrappers exposes details as JMX attributes, not operations
> ------------------------------------------------------------------
>
>                 Key: JBCACHE-1181
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1181
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> getConfigurationAsString();
> getConfigurationAsHtmlString();
> getCacheDetails();
> getCacheDetailsAsHtml();
> getLockInfo();
> getLockInfoAsHtml();
> All are too verbose for exposure as MBean attributes in the JMX console.  They need to be converted into operations so users will have to specifically invoke them.
> A better API would be:
> printConfigurationAsString();
> printConfigurationAsHtmlString();
> printCacheDetails();
> printCacheDetailsAsHtml();
> printLockInfo();
> printLockInfoAsHtml();

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1172)
 CacheLoaderInterceptor
 doesn't load data for Node.getKeys() or Node.getData()
In-Reply-To: <12017577.1188097518214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12999032.1192031283593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1172?page=all ]

Manik Surtani resolved JBCACHE-1172.
------------------------------------

    Resolution: Done

> CacheLoaderInterceptor doesn't load data for Node.getKeys() or Node.getData()
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1172
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1172
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> CacheLoaderInterceptor.mustLoad always returns false if there is no data key associated with the MethodCall.  Effect is calls for CacheImpl._getKeys  and _getData don't trigger a load from the cache loader.
> Added tests testKeyKeys() and testGetData() to CacheLoaderTestsBase to show the issue.
> Solution is to add a boolean 'allKeys' variable to CacheLoaderInterceptor.invoke.  Set it to true if the MethodCall is _getKeys or _getData.  Pass the value through to mustLoad, and if true load the data if Node.isDataLoaded returns false.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1175)
	Option.forceCall(A)sync
In-Reply-To: <31286648.1188585138477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10397571.1192031283702.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=all ]

Manik Surtani resolved JBCACHE-1175.
------------------------------------

    Resolution: Done

> Option.forceCall(A)sync
> -----------------------
>
>                 Key: JBCACHE-1175
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Add an option to allow an individual call to go async/sync when the cache overall is configured for the opposite.
> This would only be relevant to calls not running in a tx; transactional replication would use the standard semantic configured for the cache.
> Use case for this is Hibernate timestamp region replication, which needs to go async, while all other Hibernate 2nd level cache traffic goes sync.  A good region-based cache impl would solve the problem as well, but that will surely take quite a while to implement a while while doing it via an Option looks quite trivial.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1178) Option to set
	lock timeout
In-Reply-To: <14176892.1189113131136.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5857463.1192031283829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1178?page=all ]

Manik Surtani resolved JBCACHE-1178.
------------------------------------

    Resolution: Done

> Option to set lock timeout
> --------------------------
>
>                 Key: JBCACHE-1178
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1178
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Allow override of the standard lock timeout on a per-invocation basis.
> For background on the specific use case that needs this, see http://lists.jboss.org/pipermail/hibernate-dev/2007-September/002669.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1180)
 CacheImpl.toString() prints cache details
In-Reply-To: <29419991.1189446491112.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25717944.1192031283956.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1180?page=all ]

Manik Surtani resolved JBCACHE-1180.
------------------------------------

    Resolution: Done

> CacheImpl.toString() prints cache details
> -----------------------------------------
>
>                 Key: JBCACHE-1180
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1180
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> Calls CacheImpl.toString(true), thus printing the entire tree.
> In 1.x the equivalent impl was to call toString(false).
> This shows up in the JMX console, which calls toString() on attribute values.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:48:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1181) CacheJmxWrappers
 exposes details as JMX attributes, not operations
In-Reply-To: <24706943.1189446862714.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19846020.1192031284097.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1181?page=all ]

Manik Surtani resolved JBCACHE-1181.
------------------------------------

    Resolution: Done

> CacheJmxWrappers exposes details as JMX attributes, not operations
> ------------------------------------------------------------------
>
>                 Key: JBCACHE-1181
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1181
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA
>
>
> getConfigurationAsString();
> getConfigurationAsHtmlString();
> getCacheDetails();
> getCacheDetailsAsHtml();
> getLockInfo();
> getLockInfoAsHtml();
> All are too verbose for exposure as MBean attributes in the JMX console.  They need to be converted into operations so users will have to specifically invoke them.
> A better API would be:
> printConfigurationAsString();
> printConfigurationAsHtmlString();
> printCacheDetails();
> printCacheDetailsAsHtml();
> printLockInfo();
> printLockInfoAsHtml();

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:50:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1099) JDBCCacheLoader
 does not deal with Schema names?
In-Reply-To: <26867781.1181298011551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16170795.1192031403343.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1099?page=all ]

Manik Surtani resolved JBCACHE-1099.
------------------------------------

    Resolution: Done

> JDBCCacheLoader does not deal with Schema names?
> ------------------------------------------------
>
>                 Key: JBCACHE-1099
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1099
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR2
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA
>
>
> Should be able to take in a schema name property and prepend this to table names when generating SQL.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:50:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11781404.1192031403472.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani resolved JBCACHE-1167.
------------------------------------

    Resolution: Done

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4, 2.0.0.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1186)
 ClusteredCacheLoader to wait
 for first positive result rather than all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13928273.1192031644540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani updated JBCACHE-1186:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> ClusteredCacheLoader to wait for first positive result rather than all results
> ------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1155) Invalidation with
 optimistic versioning could cause cache to write stale data
In-Reply-To: <16391432.1185540287029.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17625630.1192031644447.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1155?page=all ]

Manik Surtani updated JBCACHE-1155:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Invalidation with optimistic versioning could cause cache to write stale data
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1155
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1155
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> The root of the problem is that invalidation evicts remote nodes which may mean that remote nodes are removed completely, losing all historic versioning data
> 1) Svr 1 generates state for node (data version 1)
> 2) Svr 2 generates newer state for same node (data version 2)
> 3) Svr 2 commits (data version 2), invalidates state on cache 1
> 4) Svr 1 commits, and this is allowed to proceed since it seems cache 1 created this data new, and it does not exist in cache 1.
> 5) Svr 1 will attempt to invalidate this remotely, but this will fail - but it will still be applied locally.
> 6) Inconsistency!!!
> Solution: Invalidation not to remove nodes, but evict nodes as though they had children (remove data maps and set dataInitialised to false), and (if optimistic) attach the version of the invalidation to the node.
> Eviction to have, in addition to maxTTL, a minTTL as well so that nodes spend at least a certain amount of time in the cache even if scheduled for eviction since even if we have the above eviction may come along and remove the node altogether.
> MinTTL to be configured to be greater than the max length of transactions.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-910)
 TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
In-Reply-To: <7891202.1166570293319.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13108693.1192031644834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-910?page=all ]

Manik Surtani updated JBCACHE-910:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> TreeCache.createSubtreeRootNode(Fqn subtree) ugliness
> -----------------------------------------------------
>
>                 Key: JBCACHE-910
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-910
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.ALPHA2
>            Reporter: Elias Ross
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> This method is called by the region manager.
> There's a bunch of Voodoo taking place here, legacy bits mixed with some newer stuff.
> One thing that strikes me as wrong already is this code:
> child = factory.createDataNode(type, name,
>                        subtree.getFqnChild(i + 1),
>                        parent, lock_table, coordinator, null, this.rootSpi);
> For some reason, it is passing the lock_table into the Node as the data to initialize the node with.
> Somehow I think the right way to fix this would be to do a Cache.addChild(Fqn) call in RegionManager and remove this method.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-549) Override GET_ALL
 and timeout for synchronous requests
Message-ID: <24057695.1192031645279.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-549?page=all ]

Manik Surtani updated JBCACHE-549:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Override GET_ALL and timeout for synchronous requests
> -----------------------------------------------------
>
>                 Key: JBCACHE-549
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-549
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4beta, 1.3.0.GA, 1.2.4, 1.2.4SP1, 1.2.4SP2
>            Reporter: Bela Ban
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Currently, when executing a *synchronous* method call across a cluster, the caller has to wait until all recipients send the reply, so the default mode is always GroupRequest.GET_ALL. However, we should provide more options (possibly in an Option), e.g.
> - GET_ALL
> - GET_FIRST
> - GET_N (where N < number of recipients)
> - GET_MAJORITY
> We may also want to be able to set the timeout for the call in an Options parameter, and combine this with the mode.
> So Options (used e.g. by put(), remove() etc) should have additional parameters, and *use* them in the relevant interceptors

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1144) Update build
 system to use Maven2 rather than Ant
In-Reply-To: <7905246.1184844227204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5986443.1192031645352.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1144?page=all ]

Manik Surtani updated JBCACHE-1144:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Update build system to use Maven2 rather than Ant
> -------------------------------------------------
>
>                 Key: JBCACHE-1144
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1144
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1180)
 CacheImpl.toString() prints cache details
In-Reply-To: <29419991.1189446491112.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17456119.1192031645471.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1180?page=all ]

Manik Surtani updated JBCACHE-1180:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> CacheImpl.toString() prints cache details
> -----------------------------------------
>
>                 Key: JBCACHE-1180
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1180
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Calls CacheImpl.toString(true), thus printing the entire tree.
> In 1.x the equivalent impl was to call toString(false).
> This shows up in the JMX console, which calls toString() on attribute values.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-957) Allow per-node
 configuration of LockParentForChildInsertRemove
In-Reply-To: <27480287.1170109978549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20273398.1192031645654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-957?page=all ]

Manik Surtani updated JBCACHE-957:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Allow per-node configuration of LockParentForChildInsertRemove
> --------------------------------------------------------------
>
>                 Key: JBCACHE-957
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-957
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>         Attachments: lock.diff
>
>
> Use the new LockParentForChildInsertRemove as a global default that sets a per-node behavior.  Expose an API in Node (not NodeSPI) that allows the application to change the behavior for an individual node.
> Use case: session replication, which stores data in a structure like this:
> /SESSION/webapp/session1/.../...
> /SESSION/webapp/session2/.../...
> The session managment layer wants the greater correctness that comes with enforcing LockParentForChildInsertRemove="true" with the sessionX node and below.  But requiring a WL on /SESSION/webapp before any session could be added or removed will greatly disrupt session creation and expiration.  This feature allows the best of both worlds, by allowing the application to set LockParentForChildInsertRemove="false" on /SESSION and /SESSION/webapp.
> This is a simple alternative to lock striping in the node's children map.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1127) Switch to
	jboss-javaee.jar
In-Reply-To: <27724535.1184097873268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3479932.1192031645792.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1127?page=all ]

Manik Surtani updated JBCACHE-1127:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Switch to jboss-javaee.jar
> --------------------------
>
>                 Key: JBCACHE-1127
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1127
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Carlo de Wolf has pulled the JEE APIs out of the AS codebase and into a separate project that produces a jboss-javaee.jar.  Right now it's only produced a snapshot, but once it produces a GA release JBC should switch to it from jboss-j2ee.jar.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1146) Parameterise
 tests for various permutations
In-Reply-To: <6430365.1184844227374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11016179.1192031645948.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1146?page=all ]

Manik Surtani updated JBCACHE-1146:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Parameterise tests for various permutations
> -------------------------------------------
>
>                 Key: JBCACHE-1146
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1146
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1182) JMX wrappers log
 WARN messages on calling getter for deprecated attributes
In-Reply-To: <18370997.1189447451670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20231992.1192031646062.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1182?page=all ]

Manik Surtani updated JBCACHE-1182:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> JMX wrappers log WARN messages on calling getter for deprecated attributes
> --------------------------------------------------------------------------
>
>                 Key: JBCACHE-1182
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1182
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Logged after viewing a cache mbean in AS's jmx-console:
> 12:55:33,437 WARN  [CacheJmxWrapper] MBean attribute 'CacheLoaderConfiguration'
> is deprecated; use 'CacheLoaderConfig'
> 12:55:34,046 WARN  [CacheJmxWrapper] MBean attribute 'UseInterceptorMbeans' is d
> eprecated; use 'ExposeManagementStatistics'
> These should only be logged for the setter; the setter is what implies conscious usage of the outdated API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1193) Tests should not
 call Transaction.commit/rollback()
In-Reply-To: <5880125.1191386163241.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15566822.1192031646190.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1193?page=all ]

Manik Surtani updated JBCACHE-1193:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Tests should not call Transaction.commit/rollback()
> ---------------------------------------------------
>
>                 Key: JBCACHE-1193
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1193
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Jason T. Greene
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> The JTA spec says that the thread association of a transaction can only be controlled by TransactionManager. The reason is that a Transaction can be bound to multple threads. In order to be compliant, and work with JBoss JTA, we need to ensure that all operations go through TransactionManager

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3105002.1192031646299.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani updated JBCACHE-1167:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1
                       (was: 1.4.1.SP5)

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5, 2.1.0.BETA1
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1171) Make constructor
 Fqn(List<E> names, boolean safe) public
In-Reply-To: <4725833.1187979928897.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31603394.1192031646422.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1171?page=all ]

Manik Surtani updated JBCACHE-1171:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Make constructor Fqn(List<E> names, boolean safe) public
> --------------------------------------------------------
>
>                 Key: JBCACHE-1171
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1171
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.BETA1, 2.1.0.GA
>
>
> This constructor saves the cost of making a defensive copy of the passed in List.  I've got some code that necessarily creates an ArrayList to pass to the Fqn c'tor, but there's no need to copy it; I hold no ref to the List.  Being able to use this c'tor would be a minor optimization.  I don't see any reason not to expose it as public; the javadoc for the constructor is clear about the proper usage.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1181) CacheJmxWrappers
 exposes details as JMX attributes, not operations
In-Reply-To: <24706943.1189446862714.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19007762.1192031646546.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1181?page=all ]

Manik Surtani updated JBCACHE-1181:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> CacheJmxWrappers exposes details as JMX attributes, not operations
> ------------------------------------------------------------------
>
>                 Key: JBCACHE-1181
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1181
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> getConfigurationAsString();
> getConfigurationAsHtmlString();
> getCacheDetails();
> getCacheDetailsAsHtml();
> getLockInfo();
> getLockInfoAsHtml();
> All are too verbose for exposure as MBean attributes in the JMX console.  They need to be converted into operations so users will have to specifically invoke them.
> A better API would be:
> printConfigurationAsString();
> printConfigurationAsHtmlString();
> printCacheDetails();
> printCacheDetailsAsHtml();
> printLockInfo();
> printLockInfoAsHtml();

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1178) Option to set
	lock timeout
In-Reply-To: <14176892.1189113131136.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23719913.1192031646680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1178?page=all ]

Manik Surtani updated JBCACHE-1178:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Option to set lock timeout
> --------------------------
>
>                 Key: JBCACHE-1178
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1178
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Allow override of the standard lock timeout on a per-invocation basis.
> For background on the specific use case that needs this, see http://lists.jboss.org/pipermail/hibernate-dev/2007-September/002669.html

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1175)
	Option.forceCall(A)sync
In-Reply-To: <31286648.1188585138477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28859184.1192031646800.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1175?page=all ]

Manik Surtani updated JBCACHE-1175:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Option.forceCall(A)sync
> -----------------------
>
>                 Key: JBCACHE-1175
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1175
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Add an option to allow an individual call to go async/sync when the cache overall is configured for the opposite.
> This would only be relevant to calls not running in a tx; transactional replication would use the standard semantic configured for the cache.
> Use case for this is Hibernate timestamp region replication, which needs to go async, while all other Hibernate 2nd level cache traffic goes sync.  A good region-based cache impl would solve the problem as well, but that will surely take quite a while to implement a while while doing it via an Option looks quite trivial.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1179) Blocking access
 to cache based
 on CacheStatus broken around channel connect/disconnect
In-Reply-To: <22553328.1189435151214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31035120.1192031647237.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1179?page=all ]

Manik Surtani updated JBCACHE-1179:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Blocking access to cache based on CacheStatus broken around channel connect/disconnect
> --------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1179
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1179
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> CacheImpl.invokeMethod will throw an ISE if CacheStatus != STARTED.  Problem is the channel is connected during CacheStatus.STARTING and CacheStatus.STOPPING. As long as the channel is connected you get exceptions during replication for as shown in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118013.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1142) Update JBoss
 Cache source code infrastructure
In-Reply-To: <31605360.1184844107046.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20649964.1192031647330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1142?page=all ]

Manik Surtani updated JBCACHE-1142:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Update JBoss Cache source code infrastructure
> ---------------------------------------------
>
>                 Key: JBCACHE-1142
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1142
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1145) Update test suite
 to use TestNG
In-Reply-To: <32594581.1184844227288.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26851459.1192031647474.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1145?page=all ]

Manik Surtani updated JBCACHE-1145:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Update test suite to use TestNG
> -------------------------------
>
>                 Key: JBCACHE-1145
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1145
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1099) JDBCCacheLoader
 does not deal with Schema names?
In-Reply-To: <26867781.1181298011551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32115359.1192031647600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1099?page=all ]

Manik Surtani updated JBCACHE-1099:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> JDBCCacheLoader does not deal with Schema names?
> ------------------------------------------------
>
>                 Key: JBCACHE-1099
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1099
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR2
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> Should be able to take in a schema name property and prepend this to table names when generating SQL.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1189) Implement JGroups
 Connect + State Transfer in JBC
In-Reply-To: <18329595.1190729863300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6043652.1192031647713.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1189?page=all ]

Manik Surtani updated JBCACHE-1189:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Implement JGroups Connect + State Transfer in JBC
> -------------------------------------------------
>
>                 Key: JBCACHE-1189
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1189
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1172)
 CacheLoaderInterceptor doesn't
 load data for Node.getKeys() or Node.getData()
In-Reply-To: <12017577.1188097518214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19020267.1192031647834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1172?page=all ]

Manik Surtani updated JBCACHE-1172:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> CacheLoaderInterceptor doesn't load data for Node.getKeys() or Node.getData()
> -----------------------------------------------------------------------------
>
>                 Key: JBCACHE-1172
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1172
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> CacheLoaderInterceptor.mustLoad always returns false if there is no data key associated with the MethodCall.  Effect is calls for CacheImpl._getKeys  and _getData don't trigger a load from the cache loader.
> Added tests testKeyKeys() and testGetData() to CacheLoaderTestsBase to show the issue.
> Solution is to add a boolean 'allKeys' variable to CacheLoaderInterceptor.invoke.  Set it to true if the MethodCall is _getKeys or _getData.  Pass the value through to mustLoad, and if true load the data if Node.isDataLoaded returns false.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-407) Write locks not
 acquired on newly created empty nodes
Message-ID: <1171809.1192031647974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-407?page=all ]

Manik Surtani updated JBCACHE-407:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Write locks not acquired on newly created empty nodes
> -----------------------------------------------------
>
>                 Key: JBCACHE-407
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-407
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.GA, 1.4.0.GA, 1.3.0.GA, 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> When an empty node is created during a put (e.g node "/a" created as a result of a cache.put("/a/1", "key", "value"); call), only a read lock is acquired on the empty node. If the node is created as part of a transaction, the following failure can occur:
> 2 threads, empty cache, READ_COMMITTED
> 1) T1 starts a tx
> 2) T1 invokes cache.put("/a/1", "key", "value1");
> 3) T2 invokes cache.put("/a/2", "key", "value2");
> 4) T1's transaction rolls back
> 5) T2 invokes cache.get("/a/2", "key");  Should get "value2", will get null because the tx rollback will remove node /a and thus /a/2 as well.
> This IMO breaks READ_COMMITTED semantics, as T2 is able to "read" /a (in the sense of seeing it exists and thus can have children appended to it) before the tx that created /a is committed.
> New unit test IsolationLevelReadCommittedTest.testNodeCreationRollback() demonstrates the issue.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1143) Migrate
 repository from CVS to SVN
In-Reply-To: <5716848.1184844227121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26322561.1192031648072.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1143?page=all ]

Manik Surtani updated JBCACHE-1143:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Migrate repository from CVS to SVN
> ----------------------------------
>
>                 Key: JBCACHE-1143
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1143
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1147) Document changes
In-Reply-To: <11638383.1184844347023.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21918357.1192031648147.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1147?page=all ]

Manik Surtani updated JBCACHE-1147:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Document changes
> ----------------
>
>                 Key: JBCACHE-1147
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1147
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1173)
 o.j.c.u.ThreadGate does not implement timeouts properly
In-Reply-To: <17723921.1188172829784.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5679970.1192031648283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1173?page=all ]

Manik Surtani updated JBCACHE-1173:
-----------------------------------

    Fix Version/s: 2.1.0.BETA1

> o.j.c.u.ThreadGate does not implement timeouts properly
> -------------------------------------------------------
>
>                 Key: JBCACHE-1173
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1173
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Jason T. Greene
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>
> The primary side-effect of this problem is that the state transfer will block forever waiting for an unblock event.
> This should be rewritten to use j.u.c Condition instead of object.wait()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-751)
 ignoreModifications cache
 loader flag to be extended to all cache loaders, not just ones configured
 in a chaining cache loader
In-Reply-To: <26415084.1156852159852.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22429299.1192031648373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-751?page=all ]

Manik Surtani updated JBCACHE-751:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> ignoreModifications cache loader flag to be extended to all cache loaders, not just ones configured in a chaining cache loader
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-751
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-751
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 1.4.0.GA, 1.3.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 11:54:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 11:54:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1167) Heuristic outcome
 (STATUS_UNKNOWN) of transaction not handled properly
In-Reply-To: <9760798.1187716218788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6117827.1192031648505.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1167?page=all ]

Manik Surtani updated JBCACHE-1167:
-----------------------------------

    Fix Version/s: 1.4.1.SP5

> Heuristic outcome (STATUS_UNKNOWN) of transaction not handled properly
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1167
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1167
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>            Reporter: Galder Zamarreno
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP5, 2.1.0.BETA1
>
>
> Where an XA transaction has a heuristic outcome, the status reported to 
> the afterCompletion synchronization is STATUS_UNKNOWN (5), since 
> JTA does not handle heuristics. In this case, the cache Synchronization 
> fails to rollback the cache tx. This leaves the app server in a bad (i.e. locked) 
> state even though the XA transaction has been resolved. 
> At first glance it looks like the afterCompletion synchronization should treat a 
> STATUS_UNKNOWN as a cause for rollback as well as logging the error as 
> they currently do. Unfortunately the fix may be more complex than that, since 
> the db may have committed rather than rolled back, meaning the cache would 
> be out of sync with the db if you rolled it back. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:40:14 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Wed, 10 Oct 2007 12:40:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4809) JCA deployer and
 metadata
 incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
Message-ID: <29252975.1192034414855.JavaMail.jira@cloud.prod.atl2.jboss.com>

JCA deployer and metadata incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
---------------------------------------------------------------------------------------------------

                 Key: JBAS-4809
                 URL: http://jira.jboss.com/jira/browse/JBAS-4809
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JCA service
            Reporter: Weston Price
         Assigned To: Weston Price
             Fix For:  JBossAS-5.0.0.Beta3


The ManagedConnectionEmptyContentAdapter did not correctly unmarshall XA based deployments. As a result, non datasource XA deployments (most notably JmsXA) are being incorrectly identified with local tx support and causing failures.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:55:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-315) Break locks for
	state transfer
Message-ID: <26741109.1192035306341.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-315?page=all ]

Manik Surtani updated JBCACHE-315:
----------------------------------

    Fix Version/s: 2.1.0.CR1

> Break locks for state transfer
> ------------------------------
>
>                 Key: JBCACHE-315
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-315
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> State transfer needs to acquire a lock on the root to make sure all existing TXs have been completed. However, when a TX takes more time than the lock acquisition timeout, state transfer will fail.
> Therefore, we need to forcefully acquire the locks for the state transfer by force-releasing the existing locks, and rolling back all TXs that held those locks.
> This will ensure that state transfer always succeeds, at the expense of some rolled back TXs.
> We need to investigate how this works with optimistic locking

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:55:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26678854.1192035306500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=all ]

Manik Surtani updated JBCACHE-1192:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication, Eviction
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 1.4.1.SP6, 2.1.0.CR1
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:55:06 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 12:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13564537.1192035306661.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=comments#action_12381479 ] 
            
Mark Proctor commented on JBRULES-1264:
---------------------------------------

To summarise this is a bug on CompositeObjectSink - which is only used when you have 3+ == constraints on the same field, the 3 value can be overriden by the threshold configuration value. The indexing for CompositeObjectSink is not able to handle null values. The work around for this at the moment is to set alphaNodeHashingThreshold to 0.

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:16 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1156) Configuration
	profiles
In-Reply-To: <12193835.1185540767196.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7925630.1192035436281.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1156?page=all ]

Manik Surtani updated JBCACHE-1156:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Configuration profiles
> ----------------------
>
>                 Key: JBCACHE-1156
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1156
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Requested by both AS clustering and Hibernate.
> The ability to use a specialised ConfigurationFactory that gives you a pre-configured cache for specific purposes.  E.g., CacheFactory.getAsyncReplicatedCache("myJGroupsMuxStackName")
> To be done as a subclass of DefaultCacheFactory (ProfileCacheFactory?)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:16 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5916860.1192035436438.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=all ]

Manik Surtani updated JBCACHE-1009:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:16 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 12:57:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17949382.1192035436617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Workaround Description: 
Set alphaNodeHashingThreshold to 0.


> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:18 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1153) Introduce a
 concept of structural nodes
In-Reply-To: <6252571.1185539387065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30777113.1192035438828.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1153?page=all ]

Manik Surtani updated JBCACHE-1153:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Introduce a concept of structural nodes
> ---------------------------------------
>
>                 Key: JBCACHE-1153
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1153
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Structural nodes should not be taken into consideration when processing regions for eviction.
> Typically are nodes that do not contain data (and are not intended to contain data), but are used to build tree structure.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:18 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1170) Partial state
 transfer fails when multiple regions present
In-Reply-To: <5358429.1187970318264.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28623580.1192035438965.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1170?page=all ]

Manik Surtani updated JBCACHE-1170:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Partial state transfer fails when multiple regions present
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1170
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.  
> Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase.  Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call.  Using region /JSESSION/localhost/http-field
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
> The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped", or perhaps nothing at all.
> Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal.  Two problems:
> 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
> 2) Need to ensure that the right Fqn gets written.  In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything.  If not, just cleaning up the ThreadLocal should work.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:57:19 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:57:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1154) Introduce ability
 to mark
 nodes as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11449903.1192035439131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Manik Surtani updated JBCACHE-1154:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-704) Externalise the TM
 used in the test suite so the TM can be injected when running tests.
In-Reply-To: <32285530.1153238351263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16436126.1192035543330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-704?page=all ]

Manik Surtani updated JBCACHE-704:
----------------------------------

    Fix Version/s: 2.1.0.CR1
         Assignee: Jason T. Greene  (was: Manik Surtani)

> Externalise the TM used in the test suite so the TM can be injected when running tests.
> ---------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-704
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-704
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Allows for QA to certify JBC on other TMs like JBossTS and JBossTM.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
In-Reply-To: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22245245.1192035543397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1195?page=all ]

Manik Surtani updated JBCACHE-1195:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Fix tutorial for 2.1.0 series
> -----------------------------
>
>                 Key: JBCACHE-1195
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.
> Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1176) Bad performance
 when deleting a large tree from JDBCCacheLoader
In-Reply-To: <22599873.1188997871354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20652388.1192035543620.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1176?page=all ]

Manik Surtani updated JBCACHE-1176:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Bad performance when deleting a large tree from JDBCCacheLoader 
> ----------------------------------------------------------------
>
>                 Key: JBCACHE-1176
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1176
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR1
>            Reporter: gmeroz
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> When using JDBCCacheLaoder and trying to delete the hole tree:
> using: cache.getCache().removeNode(Fqn.ROOT)
> it takes a long time which may cause transaction timeouts when running on application server.
> it seems that each node is deleted seperately instead of using one sql command.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 12:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 10 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-295) Add unit tests for
 ReplicationQueue
Message-ID: <15063994.1192035543759.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-295?page=all ]

Manik Surtani updated JBCACHE-295:
----------------------------------

    Fix Version/s: 2.1.0.CR1

> Add unit tests for ReplicationQueue
> -----------------------------------
>
>                 Key: JBCACHE-295
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-295
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:01:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 13:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1837352.1192035663494.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Workaround Description: 
Set alphaNodeHashingThreshold to really large number like 99999.


  was:
Set alphaNodeHashingThreshold to 0.



> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:03:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 10 Oct 2007 13:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1196) Option
 cacheModeLocal value gets changed during PESSIMISTIC calls
Message-ID: <18616605.1192035783594.JavaMail.jira@cloud.prod.atl2.jboss.com>

Option cacheModeLocal value gets changed during PESSIMISTIC calls
-----------------------------------------------------------------

                 Key: JBCACHE-1196
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1196
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Replication
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: 2.1.0.CR1


In org.jboss.cache.options.ForceCacheModeTest I unthinkingly used the same instance of an Option for two invocations. Option.cacheModeLocal meant to be true.  Found that with PESSIMISTIC locking enabled, cacheModeLocal would be set to false when the first request returned.  This led to intermittent failures in the tests, as the initial state of the system was not as expected.

Need to determine why the Option value is being changed.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:05:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 13:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27095792.1192035903316.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=comments#action_12381484 ] 
            
Mark Proctor commented on JBRULES-1264:
---------------------------------------

sorry 0 does not disable, so you have to set the threashold to a value greater than ever will be met, like 99999.

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 13:33:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Wed, 10 Oct 2007 13:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-478) ClassCastException on
 AnnotatedParameterAdviceInfo
Message-ID: <24439266.1192037583244.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException on AnnotatedParameterAdviceInfo
--------------------------------------------------

                 Key: JBAOP-478
                 URL: http://jira.jboss.com/jira/browse/JBAOP-478
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Flavia Rainone
         Assigned To: Flavia Rainone


This is what happens when line 464 of AnnotatedAdviceInfo is executed with a method that returns a parameterized type:
java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl
        at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$SingleParameterType.internalValidate(AnnotatedParameterAdviceInfo.java:464)
        at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$ParameterAnnotationType.validate(AnnotatedParameterAdviceInfo.java:374)
        at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo.matches(AnnotatedParameterAdviceInfo.java:124)
        at org.jboss.aop.advice.annotation.AdviceMethodFactory.bestValidAdvice(AdviceMethodFactory.java:412)
        at org.jboss.aop.advice.annotation.AdviceMethodFactory.findAdviceMethod(AdviceMethodFactory.java:291)
        at org.jboss.aop.instrument.JoinPointGenerator$AdviceSetups.<init>(JoinPointGenerator.java:1532)
        at org.jboss.aop.instrument.JoinPointGenerator.initialiseAdviceInfosAndAddFields(JoinPointGenerator.java:550)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:399)
        at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
        at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1630)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1626)
        at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
        at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1017)
        at org.jboss.test.aop.annotatedAdviceParams.ReturnInvalidPOJO$ReturnInvalidPOJOAdvisor.methodGenericsAfter54841465230530634828(ReturnInvalidPOJO$Retu
rnInvalidPOJOAdvisor.java)

This task includes a check on the code to see if the error is repeated in other code lines.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:24:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 10 Oct 2007 14:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1267) Allow predicates
 to be nested inside a field constraint
Message-ID: <3975385.1192040643293.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow predicates to be nested inside a field constraint
-------------------------------------------------------

                 Key: JBRULES-1267
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1267
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.1.0


Allow predicates to be nested inside a field constraint

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:26:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 10 Oct 2007 14:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1267) Allow predicates
 to be nested inside a field constraint
In-Reply-To: <3975385.1192040643293.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32736151.1192040763305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1267?page=all ]

Edson Tirelli closed JBRULES-1267.
----------------------------------

    Resolution: Done

Predicates now can be used as restrictions.

> Allow predicates to be nested inside a field constraint
> -------------------------------------------------------
>
>                 Key: JBRULES-1267
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1267
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.1.0
>
>
> Allow predicates to be nested inside a field constraint

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:26:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 10 Oct 2007 14:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1064) review and
 update assigned JIRA tasks
Message-ID: <18446539.1192040763458.JavaMail.jira@cloud.prod.atl2.jboss.com>

review and update assigned JIRA tasks
-------------------------------------

                 Key: EJBTHREE-1064
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1064
             Project: EJB 3.0
          Issue Type: Task
            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

        


From jira-events at lists.jboss.org  Wed Oct 10 14:54:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 10 Oct 2007 14:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1065) Integrate EJB3
 Tutorials Tests with build-test.xml
Message-ID: <30526178.1192042443286.JavaMail.jira@cloud.prod.atl2.jboss.com>

Integrate EJB3 Tutorials Tests with build-test.xml
--------------------------------------------------

                 Key: EJBTHREE-1065
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1065
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger


Will require obtaining the relevant Ant tasks from the tutorials build, merging into ejb3 build-test.xml.  JVM Argument will need to be passed into the target to specify JBOSS_HOME and TUTORIALS_HOME.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 15:05:03 2007
From: jira-events at lists.jboss.org (Kurt Stam (JIRA))
Date: Wed, 10 Oct 2007 15:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4810) mail-ra.rar make SSL
	configurable
Message-ID: <18464142.1192043103930.JavaMail.jira@cloud.prod.atl2.jboss.com>

mail-ra.rar make SSL configurable
---------------------------------

                 Key: JBAS-4810
                 URL: http://jira.jboss.com/jira/browse/JBAS-4810
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: JCA service
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Kurt Stam
         Assigned To: Weston Price
         Attachments: mail-ra-patch.txt

We are using it in JBossESB now, but in my (test) case I did not want SSL with my IMAP
connection, so I'm suggesting to make this setting configurable in the 

connector/src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java

-      sessionProps.setProperty("mail.imap.starttls.enable", "true");
+      sessionProps.setProperty("mail.imap.starttls.enable", starttls + "");

I have attached the patch.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 15:05:04 2007
From: jira-events at lists.jboss.org (Kurt Stam (JIRA))
Date: Wed, 10 Oct 2007 15:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4810) mail-ra.rar make SSL
	configurable
In-Reply-To: <18464142.1192043103930.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25188831.1192043104321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4810?page=all ]

Kurt Stam updated JBAS-4810:
----------------------------

    Attachment: mail-ra-patch.txt

> mail-ra.rar make SSL configurable
> ---------------------------------
>
>                 Key: JBAS-4810
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4810
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Kurt Stam
>         Assigned To: Weston Price
>         Attachments: mail-ra-patch.txt
>
>
> We are using it in JBossESB now, but in my (test) case I did not want SSL with my IMAP
> connection, so I'm suggesting to make this setting configurable in the 
> connector/src/main/org/jboss/resource/adapter/mail/inflow/MailFolder.java
> -      sessionProps.setProperty("mail.imap.starttls.enable", "true");
> +      sessionProps.setProperty("mail.imap.starttls.enable", starttls + "");
> I have attached the patch.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 16:22:04 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?C=C3=A9lio_=28JIRA=29?=)
Date: Wed, 10 Oct 2007 16:22:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1049) wrong
 insert/delete order when updating record-set
In-Reply-To: <3396984.1189729150976.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16874992.1192047724393.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1049?page=comments#action_12381527 ] 
            
C?lio commented on EJBTHREE-1049:
---------------------------------

I'm having the same problem.

> wrong insert/delete order when updating record-set
> --------------------------------------------------
>
>                 Key: EJBTHREE-1049
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1049
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>         Environment: jboss-4.2.1.GA , Fedora 6 
>            Reporter: Imran Pariyani
>
> Overview: I have a record with a OneToMany association. From this associated record-set a record is removed and added again, both records identified with the same key. When doing a merge, I get a Unique constraint violation, because EJB first tries to insert the new record. It should first delete the old record, and after this insert the new record, avoiding the unique constraint violation.
> Detailed description: I have the following entities: Location and LocationI18n. 
>  Location has onetomany mapping with locationi18n as follows 
> @OneToMany(cascade = CascadeType.ALL, mappedBy = "location", fetch = FetchType.EAGER)
> private List<LocationI18n> translations;
> And the mapping in the locationi18n is :
> @ManyToOne(cascade = {CascadeType.MERGE, CascadeType.PERSIST },fetch = FetchType.LAZY, optional = false)
> @JoinColumn(name = "loc_id", referencedColumnName = "id", nullable = false, columnDefinition = "loc_id INT NOT NULL")
>     private Location location;
> In the locationI18n table i have a unique key UNIQUE KEY (language, loc_id), 
> So now if i get a location and inside the location i have the collection of locationi18n .. if from that collection i remove one object with language lets say 'EN' and insert a new locationi18n object with the same language 'EN' then it first inserts the new record and then delets the records which has been removed from the collection
> Below is the stack trace:
> 2007-09-07 02:17:24,847 DEBUG [org.hibernate.SQL] insert into location_i18n (loc_id, language, date_created, date_updated, province, city, worldregion, region, subregion, quarter) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.IntegerType] binding '1' to parameter: 1
> 2007-09-07 02:17:24,848 DEBUG [org.hibernate.type.EnumType] Binding 'EN' to parameter: 2
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.TimestampType] binding '2007-09-07 02:17:24' to parameter: 3
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.TimestampType] binding '2007-09-07 02:17:24' to parameter: 4
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.StringType] binding null to parameter: 5
> 2007-09-07 02:17:24,848 TRACE [org.hibernate.type.StringType] binding null to parameter: 6
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding null to parameter: 7
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding 'afsdfa' to parameter: 8
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding null to parameter: 9
> 2007-09-07 02:17:24,849 TRACE [org.hibernate.type.StringType] binding null to parameter: 10
> 2007-09-07 02:17:24,873 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1062, SQLState: 23000
> 2007-09-07 02:17:24,874 ERROR [org.hibernate.util.JDBCExceptionReporter] Duplicate entry 'EN-1' for key 2
> 2007-09-07 02:17:24,874 ERROR [STDERR] javax.persistence.EntityExistsException: org.hibernate.exception.ConstraintViolationException: could not insert: [com.triple.LocationI18n]
> 2007-09-07 02:17:24,874 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:604)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:236)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at org.jboss.ejb3.entity.TransactionScopedEntityManager.merge(TransactionScopedEntityManager.java:188)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at com.triple.LocationBean.updateLocation(LocationBean.java:83)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2007-09-07 02:17:24,874 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 2007-09-07 02:17:24,875 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
> Test case of the same is present at 
> http://opensource.atlassian.com/projects/hibernate/secure/attachment/13468/test-pro.tar.gz

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 10 16:45:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 16:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3515440.1192049103315.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Attachment: JBRULES-1264.patch

this patch is applied to trunk and needs to be applied to 4.0.x and 4.1.x

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>         Attachments: JBRULES-1264.patch
>
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 17:20:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 10 Oct 2007 17:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-677) Compression
 marshalling fails intermittently.
In-Reply-To: <29287238.1169255872708.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24377757.1192051203286.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-677?page=comments#action_12381543 ] 
            
Ron Sigal commented on JBREM-677:
---------------------------------

Another forum reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119309

> Compression marshalling fails intermittently.
> ---------------------------------------------
>
>                 Key: JBREM-677
>                 URL: http://jira.jboss.com/jira/browse/JBREM-677
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> When used with EJB's, CompressingUnMarshaller intermittently throws java.io.IOException: Not in GZIP format.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 21:25:03 2007
From: jira-events at lists.jboss.org (Joshua Jackson (JIRA))
Date: Wed, 10 Oct 2007 21:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23270601.1192065903613.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381567 ] 
            
Joshua Jackson commented on JBRULES-1260:
-----------------------------------------

Yes exactly. We're using eclipse 3.3 europa
But if we insert the The Eclipse JDT Core jar into the drools plugin folder it will work

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 21:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 21:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21512205.1192066503597.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=comments#action_12381568 ] 
            
Mark Proctor commented on JBRULES-1260:
---------------------------------------

If we added the jar it would then be redundant for the Eclipse 3.2 and besides more than that is broken. 4.0.x will not be adding support for Eclipse 3.3. If want to use Eclipse 3.3 you can work of trunk snapshots which have already been upgraded for jdk1.5 and Eclipse 3.3. However bear in mind that trunk is our R&D area.
https://hudson.jboss.org/hudson/job/drools/lastSuccessfulBuild/artifact/trunk/target/



> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 21:37:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 10 Oct 2007 21:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1260) Include eclipse
 JDT library in drools-eclipse IDE plugin
In-Reply-To: <22852813.1191892695038.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18072917.1192066623271.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1260?page=all ]

Mark Proctor closed JBRULES-1260.
---------------------------------

    Resolution: Rejected

> Include eclipse JDT library in drools-eclipse IDE plugin
> --------------------------------------------------------
>
>                 Key: JBRULES-1260
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1260
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>    Affects Versions: 4.0.1
>            Reporter: Joshua Jackson
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> Include the core-3.2.3.v_686_R32x.jar inside the drools-eclipse IDE plugin otherwise rules can not be run from eclipse and throw this exception:
> org.drools.RuntimeDroolsException: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java'
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:134)
> 	at org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:110)
> 	at org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:83)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:120)
> 	at org.drools.compiler.PackageBuilder.<init>(PackageBuilder.java:86)
> 	at com.sample.DroolsTest.readRule(DroolsTest.java:50)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:98)
> 	at org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:56)
> 	at org.drools.compiler.PackageBuilderConfiguration.buildDialectRegistry(PackageBuilderConfiguration.java:130)
> 	... 6 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 10 23:59:03 2007
From: jira-events at lists.jboss.org (Travis Brown (JIRA))
Date: Wed, 10 Oct 2007 23:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
Message-ID: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failure to deserialize BytesMessage contents
--------------------------------------------

                 Key: JBMESSAGING-1101
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
            Reporter: Travis Brown
         Assigned To: Tim Fox


BytesMessage consumers often receive the following error:

Client side:
2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
java.io.EOFException
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)

Server side:
2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
java.lang.RuntimeException: Unknown type: 76
        at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
        at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
        at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
        at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
        at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
        at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
        at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
        at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.remoting.Client.invokeOneway(Client.java:598)
        at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
        at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
        at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
        at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
        at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
        at org.jgroups.JChannel.up(JChannel.java:1102)
        at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
        at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FC.up(FC.java:422)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
        at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FD.up(FD.java:300)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.Discovery.up(Discovery.java:225)
        at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
        at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
        at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
        at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
        at org.jgroups.protocols.TP.access$400(TP.java:45)
        at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
        at java.lang.Thread.run(Thread.java:595)


In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)

I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.


This fix resolves the issue in our environment:

diff -r org/jboss/jms/message/JBossBytesMessage.java
592c592
<       return (byte[])getPayload();
---
>       return (byte[])getBytesMessagePayload();

diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
281a282,303
> 	public synchronized Object getBytesMessagePayload()
> 	{
> 		if (payload != null)
> 		{
> 			return payload;
> 		}
> 		else if (payloadAsByteArray != null)
> 		{
> 			payload = payloadAsByteArray;
> 			payloadAsByteArray = null;
>   	  return payload;
> 		}
> 		else
> 		{
> 			return null;
> 		}
> 	}
> 




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 00:47:15 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 00:47:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-811) Privileged Block
 to create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17867615.1192078035029.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-811?page=comments#action_12381575 ] 
            
Ron Sigal commented on JBREM-811:
---------------------------------

Fix applied to branch remoting_2_x for release 2.4.0.Beta1.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1935471.1192079583564.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381579 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Fix applied to branch remoting_2_x for release 2.2.2.SP2.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:18:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-818) Release 2.2.2.GA_CP01
Message-ID: <12204903.1192079883249.JavaMail.jira@cloud.prod.atl2.jboss.com>

Release 2.2.2.GA_CP01
---------------------

                 Key: JBREM-818
                 URL: http://jira.jboss.com/jira/browse/JBREM-818
             Project: JBoss Remoting
          Issue Type: Release
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA_CP01
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.2.2.GA_CP01




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:27:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-811) Privileged Block
 to create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15113156.1192080423481.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-811?page=comments#action_12381580 ] 
            
Ron Sigal commented on JBREM-811:
---------------------------------

Fix applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:27:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12283490.1192080423675.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal updated JBREM-811:
----------------------------

    Assignee: Ron Sigal  (was: Trustin Lee)

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 01:27:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 01:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-811) Privileged Block to
 create Class Loader
In-Reply-To: <7405752.1190907101848.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18526438.1192080423877.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-811?page=all ]

Ron Sigal closed JBREM-811.
---------------------------

    Resolution: Done

Fix has now been applied to all relevant branches.

> Privileged Block to create Class Loader
> ---------------------------------------
>
>                 Key: JBREM-811
>                 URL: http://jira.jboss.com/jira/browse/JBREM-811
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: security
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA
>            Reporter: Anil Saldhana
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
>
>         Attachments: diff.patch
>
>
> Please add a Privileged Block to create the class loader.
> ===================================
> Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader)
> 	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264)
> 	at java.security.AccessController.checkPermission(AccessController.java:427)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
> 	at java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:594)
> 	at java.lang.ClassLoader.<init>(ClassLoader.java:201)
> 	at org.jboss.remoting.loading.ClassByteClassLoader.<init>(ClassByteClassLoader.java:62)
> 	at org.jboss.remoting.AbstractInvoker.<init>(AbstractInvoker.java:76)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.<init>(LocalClientInvoker.java:71)
> 	at org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:304)
> 	at org.jboss.remoting.Client.connect(Client.java:459)
> ====================================

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11905630.1192084743382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal updated JBREM-687:
----------------------------

    Fix Version/s:     (was: 2.2.2.GA_CP01)

Removed from fix version 2.2.2.GA_CP01:

When I asked about the related issue JBAS-4704 "The port for the InvokerLayer (ejb3-deployer) listens only to one interface (address)", got the following responses:

>From Dimitris: I don't personally know of a support case around this issue.

>From Carlo: The issue pop-ed in directly from Jira. I can't find any related support cases or forum posts.

Therefore, will not include fix in 2.2.2.GA_CP01 unless the problem arises in a support case.

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:39:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-687) allow binding to
	0.0.0.0
In-Reply-To: <9703586.1169657213353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1805202.1192084743563.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-687?page=all ]

Ron Sigal closed JBREM-687.
---------------------------

    Resolution: Done

Fix has been applied to all appropriate branches.

> allow binding to 0.0.0.0
> ------------------------
>
>                 Key: JBREM-687
>                 URL: http://jira.jboss.com/jira/browse/JBREM-687
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP2, 2.4.0.Beta1 (Pinto)
>
>
> Need to be able to really bind to 0.0.0.0.  Currently, remoting will swap out 0.0.0.0 with local host name or address.  Although this is about only way to be able to provide an invoker locator url that can be used by anyone else externally, means that only one network interface can ever be used.  For things such as JNDI, may want to use all interfaces and need to add back in ability to do 0.0.0.0 binding.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:44:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-814) Logger in
 HTTPClientInvoker should be static (CLONE of JBREM-750)
In-Reply-To: <13784125.1191454383444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24631782.1192085043251.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-814?page=all ]

Ron Sigal closed JBREM-814.
---------------------------

    Resolution: Done

Fix has been applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> Logger in HTTPClientInvoker should be static (CLONE of JBREM-750)
> -----------------------------------------------------------------
>
>                 Key: JBREM-814
>                 URL: http://jira.jboss.com/jira/browse/JBREM-814
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> When org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory() (which is called from the RemoteClientInvoker() constructor) tries to log an error, it throws a NullPointerException because the log variable has not been initialized.
> The log variable should be static.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:50:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-815) allow user to set
 content-type for http responses (CLONE of JBREM-653)
In-Reply-To: <24031755.1191457923333.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8587967.1192085403312.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-815?page=all ]

Ron Sigal closed JBREM-815.
---------------------------

    Resolution: Done

Fix applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> allow user to set content-type for http responses (CLONE of JBREM-653)
> ----------------------------------------------------------------------
>
>                 Key: JBREM-815
>                 URL: http://jira.jboss.com/jira/browse/JBREM-815
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>
> Currently the CoyoteInvoker.versionedWrite() method will set the content type of the http response by using WebUtil.getContentType(responseObject) to identify the content type based on the response object type being sent back to client.
> Should allow this to be overriden by the user in the same way the response code/message can be (using the response map).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:52:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30205180.1192085523344.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381593 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

There is a unit test, org.jboss.test.remoting.transport.servlet.ServletInvokerExceptionTestClient, which must be run manually; i.e., a servlet container must be started first.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:52:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-813)
 ServletServerInvoker should
 return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19707803.1192085523460.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-813?page=comments#action_12381594 ] 
            
Ron Sigal commented on JBREM-813:
---------------------------------

Fix applied to branch remoting_2_2_2_GA_CP for release 2.2.2.GA_CP01.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.SP2, 2.2.2.GA_CP01
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 02:54:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 11 Oct 2007 02:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-813) ServletServerInvoker
 should return an exception instead of just an error message
In-Reply-To: <13791675.1191371343785.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28156533.1192085643238.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-813?page=all ]

Ron Sigal closed JBREM-813.
---------------------------

    Resolution: Done

Fix has been applied to all appropriate branches.

> ServletServerInvoker should return an exception instead of just an error message
> --------------------------------------------------------------------------------
>
>                 Key: JBREM-813
>                 URL: http://jira.jboss.com/jira/browse/JBREM-813
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
>
>
> The behavior of org.jboss.remoting.transport.servlet.ServletServerInvoker differs from the other server invokers in that it returns an error message instead of an entire serialized exception.  An easy fix is described in the forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96861 .  
> Note that for backwards compatibility, this new behavior should be configurable but not the default behavior.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:10:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:10:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1268)
 Activation.remove() is removing the WRONG activation
Message-ID: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>

Activation.remove() is removing the WRONG activation
----------------------------------------------------

                 Key: JBRULES-1268
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Reteoo
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Mark Proctor
             Fix For: 4.1.0


Check out FIXME_testActivationCancellation in MiscTest.java.

It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.

The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().

This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 



-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:10:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:10:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1268)
 Activation.remove() is removing the WRONG activation
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14400900.1192086614664.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Michael Neale updated JBRULES-1268:
-----------------------------------

    Priority: Critical  (was: Major)

> Activation.remove() is removing the WRONG activation
> ----------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:17:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10033724.1192087023378.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Michael Neale updated JBRULES-1268:
-----------------------------------

    Summary: Activation.remove() is removing the WRONG activation when used in events  (was: Activation.remove() is removing the WRONG activation)

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:47:05 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 03:47:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1269) Import DRL to
 update existing assets
Message-ID: <27053219.1192088825786.JavaMail.jira@cloud.prod.atl2.jboss.com>

Import DRL to update existing assets
------------------------------------

                 Key: JBRULES-1269
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1269
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:54:18 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 11 Oct 2007 03:54:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
Message-ID: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>

Integrate the JBossWS core testsuite in the release QA
------------------------------------------------------

                 Key: JBAS-4811
                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For: JBossAS-4.2.2.GA


Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.

The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 03:56:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 11 Oct 2007 03:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1741) PortalURL
 security not honoured
In-Reply-To: <21771501.1192013583296.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31721949.1192089363242.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1741?page=all ]

Thomas Heute updated JBPORTAL-1741:
-----------------------------------

    Affects Version/s:     (was: 2.6.3 Final)

> PortalURL security not honoured
> -------------------------------
>
>                 Key: JBPORTAL-1741
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1741
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>            Priority: Critical
>             Fix For: 2.6.3 Final
>
>         Attachments: PortalURLSecurity.zip
>
>
> PortalURL security is not honoured, here is a patch for it. I am not commiting directly to SVN since I need that someone validates the patch and also create a portlet sample that will be a use case so it can be validated through this portlet.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:01:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 04:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1269) Import DRL to
 update existing assets
In-Reply-To: <27053219.1192088825786.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7992943.1192089663273.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1269?page=all ]

Michael Neale closed JBRULES-1269.
----------------------------------

    Resolution: Done

> Import DRL to update existing assets
> ------------------------------------
>
>                 Key: JBRULES-1269
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1269
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:06:03 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Thu, 11 Oct 2007 04:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1069) Include common-io
 and common-fileupload in the ear configuration
In-Reply-To: <22824913.1191835149906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10202963.1192089963507.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1069?page=comments#action_12381610 ] 
            
Tom Baeyens commented on JBPM-1069:
-----------------------------------

could you explain this a bit more ?  why are these libraries needed ?

> Include common-io and common-fileupload in the ear configuration
> ----------------------------------------------------------------
>
>                 Key: JBPM-1069
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1069
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>            Reporter: Fady Matar
>         Assigned To: Tom Baeyens
>            Priority: Trivial
>             Fix For: jBPM 3.3
>
>
> Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file)
> The ear files can be appended to the JBoss AS configuration or can be packaged within the ear

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:16:41 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Thu, 11 Oct 2007 04:16:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1069) Include common-io
 and common-fileupload in the ear configuration
In-Reply-To: <22824913.1191835149906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21105425.1192090601488.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1069?page=comments#action_12381613 ] 
            
Fady Matar commented on JBPM-1069:
----------------------------------

Those libraries are needed to handle the file upload mechanism. In previous releases of JBoss they were included with the Tomcat libraries, apparently they're being used in the deployment target. Whenever I deploy the application the exception stack trace indicates that they're missing. They could be bundled either in the application or added to the classpath libraries of JBoss (The workaround I have used)

> Include common-io and common-fileupload in the ear configuration
> ----------------------------------------------------------------
>
>                 Key: JBPM-1069
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1069
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>            Reporter: Fady Matar
>         Assigned To: Tom Baeyens
>            Priority: Trivial
>             Fix For: jBPM 3.3
>
>
> Include the common-io.jar or the common-fileupload in the ear configuration or the JBoss server configuration whenever building the enterprise configuration (running the deploy target from the jbpm.enterprise.xml ant file)
> The ear files can be appended to the JBoss AS configuration or can be packaged within the ear

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 04:33:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 11 Oct 2007 04:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21293095.1192091583924.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Andrew Rubinger resolved EJBTHREE-785.
--------------------------------------

    Resolution: Done

Fixes to unit tests confirmed resolved

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 05:31:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 11 Oct 2007 05:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11005646.1192095063668.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]

Carlo de Wolf reassigned JBAS-4805:
-----------------------------------

    Assignee: William DeCoste  (was: Carlo de Wolf)

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 06:07:04 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Thu, 11 Oct 2007 06:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
Message-ID: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>

Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
------------------------------------------------------------------------------

                 Key: JBAS-4812
                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.0.GA
            Reporter: Dominik Pospisil
         Assigned To: Brian Stansberry
         Attachments: ejb3-buddy.tgz

Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 06:07:06 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Thu, 11 Oct 2007 06:07:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16803037.1192097226826.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4812?page=all ]

Dominik Pospisil updated JBAS-4812:
-----------------------------------

    Attachment: ejb3-buddy.tgz

Test logs.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 08:52:22 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 11 Oct 2007 08:52:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1196) Option
 cacheModeLocal value gets changed during PESSIMISTIC calls
In-Reply-To: <18616605.1192035783594.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2366316.1192107142477.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1196?page=all ]

Brian Stansberry closed JBCACHE-1196.
-------------------------------------

    Fix Version/s:     (was: 2.1.0.CR1)
       Resolution: Won't Fix

A caller should not attempt to reuse an instance of Option. Once you pass it to the cache, it belongs to the cache.

> Option cacheModeLocal value gets changed during PESSIMISTIC calls
> -----------------------------------------------------------------
>
>                 Key: JBCACHE-1196
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1196
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>
> In org.jboss.cache.options.ForceCacheModeTest I unthinkingly used the same instance of an Option for two invocations. Option.cacheModeLocal meant to be true.  Found that with PESSIMISTIC locking enabled, cacheModeLocal would be set to false when the first request returned.  This led to intermittent failures in the tests, as the initial state of the system was not as expected.
> Need to determine why the Option value is being changed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:00:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Thu, 11 Oct 2007 09:00:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
Message-ID: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>

Business interfaces defined in the descriptor are ignored
---------------------------------------------------------

                 Key: EJBTHREE-1066
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Carlo de Wolf




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:09:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 11 Oct 2007 09:09:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4609) Original
 SevletResponse or
 wrapped original ServletResponse not passed to RequestDispatcher in
 violation of SRV.8.2 and SRV.14.2.5.1
In-Reply-To: <14152110.1187166841533.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12704092.1192108144015.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4609?page=all ]

Thomas Heute resolved JBAS-4609.
--------------------------------

    Resolution: Done

This is not a JBoss AS bug.

jboss-web got more strict regarding to the servlet spec, and does what it says.

If you want to have something a bit more loose, start JBoss AS with:
-Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=false

And it won't check for this, so you can use frameworks that are not strictly following the spec.

> Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4609
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4609
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: RHeL
>            Reporter: stefan lotties
>
> Sometimes in the log the following stacktrace appears while someone is surfing in an application:
> 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
> b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
> javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
> ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
>         at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
> a:1018)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
>         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
>         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
> r.java:237)
>         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
> java:300)
>         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
>         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>         at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
> ava:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
> 469)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
> java:316)
>         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
> 44)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
> 156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
> va:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595) 
> I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:48:21 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 09:48:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16229816.1192110501420.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381679 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

This can easily be reproduced by having a Resource injected that 
it's only deployed in one of the nodes, for example, an HA Singleton 
MBean like JBoss MQ in a clustered environment.  

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 09:52:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Thu, 11 Oct 2007 09:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-422) Retro-woven
 Class.getTypeParameters() method returns zero-length array
Message-ID: <25067970.1192110723740.JavaMail.jira@cloud.prod.atl2.jboss.com>

Retro-woven Class.getTypeParameters() method returns zero-length array
----------------------------------------------------------------------

                 Key: JBBUILD-422
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-422
             Project: JBoss Build System
          Issue Type: Bug
          Components: JBossRetro
    Affects Versions: JBossRetro-1.1.2.GA
            Reporter: Flavia Rainone


The method Class.getTypeParameters returns a zero length array when called on java.util.List.class.

Probably the same occurs with all other Java API classes that have been parameterized as of jdk1.5.

Not sure whether the problem occurs with a parameterized class that has been retro-woven, though (maybe the bug happens only with non-retrowoven classes)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 10:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 11 Oct 2007 10:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4609) Original
 SevletResponse or
 wrapped original ServletResponse not passed to RequestDispatcher in
 violation of SRV.8.2 and SRV.14.2.5.1
In-Reply-To: <14152110.1187166841533.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22759730.1192111263285.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4609?page=all ]

Dimitris Andreadis reopened JBAS-4609:
--------------------------------------

             

> Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4609
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4609
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: RHeL
>            Reporter: stefan lotties
>
> Sometimes in the log the following stacktrace appears while someone is surfing in an application:
> 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
> b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
> javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
> ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
>         at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
> a:1018)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
>         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
>         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
> r.java:237)
>         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
> java:300)
>         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
>         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>         at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
> ava:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
> 469)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
> java:316)
>         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
> 44)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
> 156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
> va:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595) 
> I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 10:03:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 11 Oct 2007 10:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4609) Original
 SevletResponse or wrapped
 original ServletResponse not passed to RequestDispatcher in violation of
 SRV.8.2 and SRV.14.2.5.1
In-Reply-To: <14152110.1187166841533.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24010254.1192111383255.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4609?page=all ]

Dimitris Andreadis closed JBAS-4609.
------------------------------------

    Resolution: Rejected

Thomas, when you close issues like this, please use a different resolution (like rejected, etc.)

> Original SevletResponse or wrapped original ServletResponse not passed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4609
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4609
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: RHeL
>            Reporter: stefan lotties
>
> Sometimes in the log the following stacktrace appears while someone is surfing in an application:
> 2007-08-09 12:10:01,834 [http-0.0.0.0-8080-1] ERROR org.apache.catalina.core.ContainerBase.[jboss.we
> b].[localhost].[/webadmin].[action] - Servlet.service() for servlet action threw exception
> javax.servlet.ServletException: Original SevletResponse or wrapped original ServletResponse not pass
> ed to RequestDispatcher in violation of SRV.8.2 and SRV.14.2.5.1
>         at org.apache.catalina.core.ApplicationDispatcher.checkSameObjects(ApplicationDispatcher.jav
> a:1018)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:329)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
>         at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:261)
>         at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcesso
> r.java:237)
>         at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.
> java:300)
>         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
>         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
>         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
>         at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:271)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
> ava:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:
> 469)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:403)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
>         at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.
> java:316)
>         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
> 44)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:491)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:
> 156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
> va:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595) 
> I debugged as far as I could and noticed that the http-request returns the host the jboss runs on when calling HttpServletRequest.getRemoteHost() and has "HEAD" as method. It can't be reproduced since it seems to be kinda random (doing the same action twice or more often does not end in this exception). Also the requested-URIs are different. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 10:06:05 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?C=EF=BF=A9dric_Chantepie_=28JIRA=29?=)
Date: Thu, 11 Oct 2007 10:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4813) EAR with WAR
 classloading isolation & commons-httpclient
Message-ID: <29000557.1192111565670.JavaMail.jira@cloud.prod.atl2.jboss.com>

EAR with WAR classloading isolation & commons-httpclient
--------------------------------------------------------

                 Key: JBAS-4813
                 URL: http://jira.jboss.com/jira/browse/JBAS-4813
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: ClassLoading, Web (Tomcat) service
    Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1
         Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
jrockit-R26.4.0-jdk1.5.0_06
            Reporter: C?dric Chantepie
         Assigned To: Scott M Stark
            Priority: Blocker


We have an EAR including 4 modules :
- an ejb .jar,
- persistence .har
- 2 webapps.

3 modules -- the ejb .jar and the 2 webapps,  depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.

== META-INF/jboss-app.xml ==
<!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
         "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">

<jboss-app>
  <loader-repository>my.package:loader=My.ear
    <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
  </loader-repository>
  <jmx-name>my.package:module=My.ear</jmx-name>
  <module>
    <har>MyPersistence.har</har>
  </module>
</jboss-app>

Then I've added Class-Path attribute in ejb .jar manifest.

== ejb.jar | META-INF/MANIFEST.MF ==

Manifest-Version: 1.0
Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
 ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
 ucene-analyzers-2.0.0.jar

(Line breaks there are as in MANIFEST.MF when I extract it from the jar.)

I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.

== webapp1.war | META-INF/MANIFEST.MF ==

Manifest-Version: 1.0
Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
 b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
 ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
 .jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
 ailer.jar lib/commons-httpclient-3.1.jar

== webapp2.war | META-INF/MANIFEST.MF ==

Manifest-Version: 1.0
Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
 b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
 2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
 jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
 APSHOT.jar lib/commons-httpclient-3.1.jar

And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".

== webapp1.war | WEB-INF/MANIFEST.MF ==

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE jboss-web
  PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
  "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">

<jboss-web>
  <context-root>/BO</context-root>
  <virtual-host>www.my-vhost.com</virtual-host>

  <class-loading java2ClassLoadingCompliance="false">
    <loader-repository>my.package:loader=My.ear
        <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
    </loader-repository>
  </class-loading>
</jboss-web>

== webapp2.war | WEB-INF/MANIFEST.MF ==

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE jboss-web
  PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
  "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">

<jboss-web>
  <context-root>/</context-root>
  <virtual-host>www.my-vhost.com</virtual-host>

  <class-loading java2ClassLoadingCompliance="false">
    <loader-repository>my.package:loader=My.ear
        <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
    </loader-repository>
  </class-loading>
</jboss-web>

Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.

The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one. 

If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.

I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.

2 of these test server have the same linux version (kernel), excepted SMP support.

Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.

So please if you can give some useful information.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 11 10:40:06 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 10:40:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4813) EAR with WAR
 classloading isolation & commons-httpclient
In-Reply-To: <29000557.1192111565670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8350158.1192113606802.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4813?page=all ]

Adrian Brock updated JBAS-4813:
-------------------------------

    Component/s:     (was: ClassLoading)
       Assignee: Remy Maucherat  (was: Scott M Stark)
       Priority: Major  (was: Blocker)

You'll get a faster response if you attach an example deployment reproducing the problem.

NOTE: The jboss-web.xml classloading configuration is largely ignored in 4.0.5
(since it uses the Tomcat classloader) unless you changed the jboss-web service config 
to use the jboss classloader.

Assigned to Remy since if there is an issue it is likely within the Tomcat classloader not JBoss
(e.g. Tomcat automatically ignores a lot of apache commons classes in the war?)

> EAR with WAR classloading isolation & commons-httpclient
> --------------------------------------------------------
>
>                 Key: JBAS-4813
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4813
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.5.GA
>         Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
> jrockit-R26.4.0-jdk1.5.0_06
>            Reporter: C?dric Chantepie
>         Assigned To: Remy Maucherat
>
> We have an EAR including 4 modules :
> - an ejb .jar,
> - persistence .har
> - 2 webapps.
> 3 modules -- the ejb .jar and the 2 webapps,  depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.
> == META-INF/jboss-app.xml ==
> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
>          "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
> <jboss-app>
>   <loader-repository>my.package:loader=My.ear
>     <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>   </loader-repository>
>   <jmx-name>my.package:module=My.ear</jmx-name>
>   <module>
>     <har>MyPersistence.har</har>
>   </module>
> </jboss-app>
> Then I've added Class-Path attribute in ejb .jar manifest.
> == ejb.jar | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
>  ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
>  ucene-analyzers-2.0.0.jar
> (Line breaks there are as in MANIFEST.MF when I extract it from the jar.)
> I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.
> == webapp1.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
>  ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
>  .jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
>  ailer.jar lib/commons-httpclient-3.1.jar
> == webapp2.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
>  2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
>  jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
>  APSHOT.jar lib/commons-httpclient-3.1.jar
> And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".
> == webapp1.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/BO</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> == webapp2.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.
> The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one. 
> If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.
> I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.
> 2 of these test server have the same linux version (kernel), excepted SMP support.
> Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.
> So please if you can give some useful information.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 11 10:50:13 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?C=EF=BF=A9dric_Chantepie_=28JIRA=29?=)
Date: Thu, 11 Oct 2007 10:50:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4813) EAR with WAR
 classloading isolation & commons-httpclient
In-Reply-To: <29000557.1192111565670.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15794159.1192114213696.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4813?page=comments#action_12381705 ] 
            
C?dric Chantepie commented on JBAS-4813:
----------------------------------------

I know that jboss-web are ignored, I have let them because maven generate them. 

As I've said the configuration for classloading is in jboss-app.xml, I think this is ok ?

> EAR with WAR classloading isolation & commons-httpclient
> --------------------------------------------------------
>
>                 Key: JBAS-4813
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4813
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.5.GA
>         Environment: Linux 2.6.11-1.1369_FC4smp (Fedora Core 4) 2005 i686 i686 i386 GNU/Linux
> jrockit-R26.4.0-jdk1.5.0_06
>            Reporter: C?dric Chantepie
>         Assigned To: Remy Maucherat
>
> We have an EAR including 4 modules :
> - an ejb .jar,
> - persistence .har
> - 2 webapps.
> 3 modules -- the ejb .jar and the 2 webapps,  depends on commons-httpclient 3.1, different from jboss version which 2.x, so I've first maid the EAR isolated by adding the jboss-app.xml with instruction given in JBoss wiki about EAR classloading.
> == META-INF/jboss-app.xml ==
> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
>          "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd">
> <jboss-app>
>   <loader-repository>my.package:loader=My.ear
>     <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>   </loader-repository>
>   <jmx-name>my.package:module=My.ear</jmx-name>
>   <module>
>     <har>MyPersistence.har</har>
>   </module>
> </jboss-app>
> Then I've added Class-Path attribute in ejb .jar manifest.
> == ejb.jar | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/commons-httpclient-3.1.jar lib/commons-codec-1.2.jar l
>  ib/lucene-core-2.0.0.jar lib/commons-lang-2.3.jar lib/j2cdk.jar lib/l
>  ucene-analyzers-2.0.0.jar
> (Line breaks there are as in MANIFEST.MF when I extract it from the jar.)
> I've also manifest files in WAR for the 2 webapps, but I'm not sure jboss/jbossweb(tomcat) take care of it.
> == webapp1.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/c
>  ommons-fileupload-1.0.jar lib/j2cdk-taglib.jar lib/j2cdk.jar lib/jgen
>  .jar lib/jstl.jar lib/standard.jar lib/struts-1.2.9.jar lib/taglibs-m
>  ailer.jar lib/commons-httpclient-3.1.jar
> == webapp2.war | META-INF/MANIFEST.MF ==
> Manifest-Version: 1.0
> Class-Path: lib/a-web-lib.jar lib/commons-beanutils-1.7.0.jar li
>  b/commons-beanutils-core-1.7.0.jar lib/commons-digester-1.6.jar lib/j
>  2cdk-taglib.jar lib/j2cdk.jar lib/jgen.jar lib/jstl.jar lib/standard.
>  jar lib/struts-1.2.9.jar lib/taglibs-mailer.jar lib/htmlparser-1.0-SN
>  APSHOT.jar lib/commons-httpclient-3.1.jar
> And I've also jboss-web.xml files in these two WAR, even if there are included when deployed inside EAR (which is the top deployment in this case), with the same load repository specified "my.package:loader=My.ear".
> == webapp1.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/BO</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> == webapp2.war | WEB-INF/MANIFEST.MF ==
> <?xml version='1.0' encoding='UTF-8'?>
> <!DOCTYPE jboss-web
>   PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
>   "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
> <jboss-web>
>   <context-root>/</context-root>
>   <virtual-host>www.my-vhost.com</virtual-host>
>   <class-loading java2ClassLoadingCompliance="false">
>     <loader-repository>my.package:loader=My.ear
>         <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
>     </loader-repository>
>   </class-loading>
> </jboss-web>
> Ok, that the situation. All work well on several developpement servers (tested on 3 linux hosts and 1 os x), it can be deployed without any error on prodution server (which environement is indicated in this issue), but I get an exception when I test it.
> The exceptions occurs when I call a JSP, not precompiled and so compiled on-the-fly by jbossweb (as on developpement servers where it works fine). Then I get a NoSuchMethodException about getParams() on org.apache.commons.httpclient.HttpConnectionManager. In fact this method doesn't exist in commons-httpclient 2.x included in JBoss, that why I include it as lib in EAR, and isolate this one. 
> If I replace the commons-httpclient in jboss/server/default/lib by mine it works fine.
> I've tested on 3 other server with the same JBoss, same JVM and same EAR, it works on the others. I'm sure JBoss/JVM/EAR are absolutely the same as on the production server because in fact I've make a tar file of all this on the server before transfering it on the 3 others.
> 2 of these test server have the same linux version (kernel), excepted SMP support.
> Here is where I'm. In fact now I really don't know what could cause this difference, and prevent EAR from working on production jboss server. Could it be related to the SMP (2 cpu) ? Does in this case jbossweb compile with a different classloader for the second cpu ? Maybe silly but I haven't real idea.
> So please if you can give some useful information.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 11 12:12:05 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Thu, 11 Oct 2007 12:12:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <13496434.1192119125187.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil updated JBMESSAGING-381:
------------------------------------

    Attachment: patch-JBMESSAGING-381.txt

tentative patch.

corresponding test case is:
export TARGET_CLASS=org.jboss.test.messaging.jms.PersistenceTest
export TARGET_TEST=testQueueWithDisabledPersistence

test case is:
* deploy a queue with disabled persistence
* send a few messages with DeliveryMode.PERSISTENT
* restart the server
* redeploy the same queue
* check that the queue is empty

(the opposing test is PersistenceTest.testQueuePersistence() which checks
that the messages are still in the queue after restart)

- Persistent is true by default for destinations.
- It can be set only before the destination is started (at deployment time)
- a "not persistent" destination corresponds to a MessagingQueue w/o a 
  PersistenceManager and flagged as non recoverable

I did not check passing null as a PersistenceManager in ChannelSupport is acceptable... it may generate unexpected NPE...

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:30:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 12:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25087275.1192120203552.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12381769 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

This issue has a secondary side effect where SessionContext.lookup() calls within 
the bean that had the Resource injected also throws a javax.naming.CommunicationException.

InitialContextFactory.getHAContext():

Hashtable env = ctx.getEnvironment(); // this is the Container's getEnc();
...
env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());

This call changes the EJB container's Context.PROVIDER_URL, so SessionContext.lookup 
calls after this are gonna try to go localhost first. If they fail, they'll try do a new InitIalContext() 
which will probably succeed (it did in my tests)

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:32:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4517) Remove the old
 JMSContainerInvoker and ServerSessionPool
In-Reply-To: <17973789.1183572230984.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13486272.1192120323241.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4517?page=all ]

Adrian Brock updated JBAS-4517:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120986

This has been mostly done, with some minor tidyup issues on the attached forum thread.

> Remove the old JMSContainerInvoker and ServerSessionPool
> --------------------------------------------------------
>
>                 Key: JBAS-4517
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4517
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The old EJB2.0 JMSContainerInvoker and supporting classes needs removing from the server module.
> With one exception (start/stopDelivery) all the features (+many others) are now supported in the jca inbound jms rar.
> This will remove a dependency on the XIDFactory from the old transaction project which shouldn't even be there.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:34:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4518) EJB3 should not have
 a dependency on the XID factory
In-Reply-To: <18371485.1183572351190.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21805479.1192120443384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4518?page=all ]

Adrian Brock closed JBAS-4518.
------------------------------

    Resolution: Done
      Assignee: Adrian Brock  (was: Carlo de Wolf)

This legacy class has been removed along with referenecs in the configuration.

> EJB3 should not have a dependency on the XID factory
> ----------------------------------------------------
>
>                 Key: JBAS-4518
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4518
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossAS-5.0.0.GA
>
>
> The EJB3 dependency on the XIDFactory should not be there.
> EJB3 should be using the JCA inbound resource adapter.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:07 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4518) EJB3 should not
 have a dependency on the XID factory
In-Reply-To: <18371485.1183572351190.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22451009.1192120567912.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4518?page=all ]

Adrian Brock reopened JBAS-4518:
--------------------------------

             

> EJB3 should not have a dependency on the XID factory
> ----------------------------------------------------
>
>                 Key: JBAS-4518
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4518
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The EJB3 dependency on the XIDFactory should not be there.
> EJB3 should be using the JCA inbound resource adapter.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:08 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4518) EJB3 should not have
 a dependency on the XID factory
In-Reply-To: <18371485.1183572351190.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3514502.1192120568074.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4518?page=all ]

Adrian Brock closed JBAS-4518.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> EJB3 should not have a dependency on the XID factory
> ----------------------------------------------------
>
>                 Key: JBAS-4518
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4518
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The EJB3 dependency on the XIDFactory should not be there.
> EJB3 should be using the JCA inbound resource adapter.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:08 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4519) The IIOP dependency
 on the old transaction needs removing
In-Reply-To: <2125312.1183572351674.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8261403.1192120568556.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4519?page=all ]

Adrian Brock reopened JBAS-4519:
--------------------------------

             

> The IIOP dependency on the old transaction needs removing
> ---------------------------------------------------------
>
>                 Key: JBAS-4519
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4519
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Adrian Brock
>         Assigned To: Francisco Reverbel
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:08 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4519) The IIOP dependency
 on the old transaction needs removing
In-Reply-To: <2125312.1183572351674.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7349141.1192120568784.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4519?page=all ]

Adrian Brock closed JBAS-4519.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> The IIOP dependency on the old transaction needs removing
> ---------------------------------------------------------
>
>                 Key: JBAS-4519
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4519
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: IIOP service
>            Reporter: Adrian Brock
>         Assigned To: Francisco Reverbel
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The IIOP project's dependency on the old transaction manager needs moving into a seperate optional project.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:09 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4520) Remove testsuite
 dependency on old transaction manager
In-Reply-To: <10023540.1183572471230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10231135.1192120569156.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4520?page=all ]

Adrian Brock reopened JBAS-4520:
--------------------------------

             

> Remove testsuite dependency on old transaction manager
> ------------------------------------------------------
>
>                 Key: JBAS-4520
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4520
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The parts of the testsuite that depend upon the old transaction manager need removing.
> They should either be replaced with JBossTM as an in-memory transaction manager (this could be done
> by changing the TransactionManagerLocator in the jboss-integration project)
> or the tests need moving to run inside the appserver.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:09 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4520) Remove testsuite
 dependency on old transaction manager
In-Reply-To: <10023540.1183572471230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7670394.1192120569380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4520?page=all ]

Adrian Brock closed JBAS-4520.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> Remove testsuite dependency on old transaction manager
> ------------------------------------------------------
>
>                 Key: JBAS-4520
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4520
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The parts of the testsuite that depend upon the old transaction manager need removing.
> They should either be replaced with JBossTM as an in-memory transaction manager (this could be done
> by changing the TransactionManagerLocator in the jboss-integration project)
> or the tests need moving to run inside the appserver.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:36:09 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4517) Remove the old
 JMSContainerInvoker and ServerSessionPool
In-Reply-To: <17973789.1183572230984.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2698131.1192120569628.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4517?page=all ]

Adrian Brock closed JBAS-4517.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

> Remove the old JMSContainerInvoker and ServerSessionPool
> --------------------------------------------------------
>
>                 Key: JBAS-4517
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4517
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The old EJB2.0 JMSContainerInvoker and supporting classes needs removing from the server module.
> With one exception (start/stopDelivery) all the features (+many others) are now supported in the jca inbound jms rar.
> This will remove a dependency on the XIDFactory from the old transaction project which shouldn't even be there.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:38:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 11 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4516) The transaction
 project needs moving out jboss-head since it is obsolete
In-Reply-To: <27290032.1183572051138.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20354746.1192120683637.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4516?page=all ]

Adrian Brock closed JBAS-4516.
------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
                       (was: JBossAS-5.0.0.GA)
       Resolution: Done

The old transaction manager is now gone from head.

> The transaction project needs moving out jboss-head since it is obsolete
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4516
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4516
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The transaction project in jboss-head is obsolete now that it uses JBossTM.
> The subtasks of this task describe what needs doing to complete that.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:40:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Thu, 11 Oct 2007 12:40:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as that is being removed
 from JBAS code
Message-ID: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
---------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1102
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: 1.4.0.GA
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 12:53:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Thu, 11 Oct 2007 12:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as
 that is being removed from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19145027.1192121583415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Clebert Suconic closed JBMESSAGING-1102.
----------------------------------------

    Resolution: Done

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:04:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Thu, 11 Oct 2007 13:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-478) ClassCastException on
 AnnotatedParameterAdviceInfo
In-Reply-To: <24439266.1192037583244.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23618154.1192122243295.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-478?page=all ]

Flavia Rainone closed JBAOP-478.
--------------------------------

    Resolution: Done

> ClassCastException on AnnotatedParameterAdviceInfo
> --------------------------------------------------
>
>                 Key: JBAOP-478
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-478
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>
> This is what happens when line 464 of AnnotatedAdviceInfo is executed with a method that returns a parameterized type:
> java.lang.ClassCastException: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl
>         at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$SingleParameterType.internalValidate(AnnotatedParameterAdviceInfo.java:464)
>         at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo$ParameterAnnotationType.validate(AnnotatedParameterAdviceInfo.java:374)
>         at org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo.matches(AnnotatedParameterAdviceInfo.java:124)
>         at org.jboss.aop.advice.annotation.AdviceMethodFactory.bestValidAdvice(AdviceMethodFactory.java:412)
>         at org.jboss.aop.advice.annotation.AdviceMethodFactory.findAdviceMethod(AdviceMethodFactory.java:291)
>         at org.jboss.aop.instrument.JoinPointGenerator$AdviceSetups.<init>(JoinPointGenerator.java:1532)
>         at org.jboss.aop.instrument.JoinPointGenerator.initialiseAdviceInfosAndAddFields(JoinPointGenerator.java:550)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:399)
>         at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
>         at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1630)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1626)
>         at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
>         at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1017)
>         at org.jboss.test.aop.annotatedAdviceParams.ReturnInvalidPOJO$ReturnInvalidPOJOAdvisor.methodGenericsAfter54841465230530634828(ReturnInvalidPOJO$Retu
> rnInvalidPOJOAdvisor.java)
> This task includes a check on the code to see if the error is repeated in other code lines.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:22:03 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 11 Oct 2007 13:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4814) Refactor the
 conf/jboss-service.xml services
Message-ID: <10029170.1192123323246.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor the conf/jboss-service.xml services
--------------------------------------------

                 Key: JBAS-4814
                 URL: http://jira.jboss.com/jira/browse/JBAS-4814
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Scott M Stark
         Assigned To: Scott M Stark
             Fix For: JBossAS-5.0.0.CR1


The legacy/conf/jboss-service.xml needs to be stripped down, possibly removed as there are too many non-core services in this currently.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:50:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 13:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4815)
 UnifiedInvokerProxyHA - Client
 instance check and assignment should be atomic
Message-ID: <15370726.1192125004025.JavaMail.jira@cloud.prod.atl2.jboss.com>

UnifiedInvokerProxyHA - Client instance check and assignment should be atomic
-----------------------------------------------------------------------------

                 Key: JBAS-4815
                 URL: http://jira.jboss.com/jira/browse/JBAS-4815
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering, Remoting
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Galder Zamarreno
         Assigned To: Galder Zamarreno


I have realised that UnifiedInvokerProxy/UnifiedInvokerProxyHA maintain a instance reference to 
the InvokerLocator/Client instances to a specific invocation is using. That is, when a new target is 
chosen, the unified proxy updates its Client and corresponding InvokerLocator instances (if they've 
changed), and uses the Cient instance variable to make the call. As far as I can see there's no 
synchronisation in the usage/assignment of Client or InvokerLocator. Proxies are meant to be thread 
safe which means that multiple client app threads could be using the same proxy without any problems. 
I can see all this going wrong the moment someone uses client proxies this way in a clustered 
environment with round robin load balance policy. We've got no guarantee that round robin will work 
correctly in these situations.

Several solutions have been discussed in 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 13:52:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 11 Oct 2007 13:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4816) FirstAvailable -
 access and update of electedTarget is not atomic
Message-ID: <9108020.1192125123233.JavaMail.jira@cloud.prod.atl2.jboss.com>

FirstAvailable - access and update of electedTarget is not atomic
-----------------------------------------------------------------

                 Key: JBAS-4816
                 URL: http://jira.jboss.com/jira/browse/JBAS-4816
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
            Reporter: Galder Zamarreno
         Assigned To: Galder Zamarreno
            Priority: Trivial


Looking at FirstAvailable load balance policy, electedTarget access/update is not synchronised, 
however, the chances of having some issues are very small. First, the proxy needs to be shared 
by various threads before the electedTarget has been set, but as electedTarget already elected 
randomly, the secondary effects of this lack of safety are none.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 16:44:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 11 Oct 2007 16:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-83) Maven sub-module
 jbosssx in the project
Message-ID: <28929119.1192135443570.JavaMail.jira@cloud.prod.atl2.jboss.com>

Maven sub-module jbosssx in the project
---------------------------------------

                 Key: SECURITY-83
                 URL: http://jira.jboss.com/jira/browse/SECURITY-83
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Repository
    Affects Versions: 2.0.1-BETA2
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-GA


projects/security/security-jboss-sx/trunk

needs to have two submodules
jbosssx
jbosssx-client

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 16:46:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Thu, 11 Oct 2007 16:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
Message-ID: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>

CtField.getConstantValue() for just added fileds
------------------------------------------------

                 Key: JASSIST-37
                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
             Project: Javassist
          Issue Type: Bug
         Environment: Java 5, javassist 3.4.ga
            Reporter: Vlad Skarzhevskyy
         Assigned To: Shigeru Chiba


I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = fields.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .





-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:07:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 11 Oct 2007 17:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-83) Maven sub-module
 jbosssx in the project
In-Reply-To: <28929119.1192135443570.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18928408.1192136823412.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-83?page=all ]

Anil Saldhana closed SECURITY-83.
---------------------------------

    Resolution: Done

> Maven sub-module jbosssx in the project
> ---------------------------------------
>
>                 Key: SECURITY-83
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-83
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Repository
>    Affects Versions: 2.0.1-BETA2
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-GA
>
>
> projects/security/security-jboss-sx/trunk
> needs to have two submodules
> jbosssx
> jbosssx-client

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:42:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 17:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4817)
 PreFillPoolingUnitTestCase isssues
Message-ID: <20249927.1192138923234.JavaMail.jira@cloud.prod.atl2.jboss.com>

PreFillPoolingUnitTestCase isssues
----------------------------------

                 Key: JBAS-4817
                 URL: http://jira.jboss.com/jira/browse/JBAS-4817
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JCA service
    Affects Versions: JBossAS-5.0.0.Beta2, JBossAS-5.0.0.Beta1
            Reporter: Weston Price
         Assigned To: Weston Price
             Fix For:  JBossAS-5.0.0.Beta3


There are two types of failures in the PreFillPoolingUnitTestCase. The first has to do with the new JAXB based deployment in AS5. JAXB appears to have an issue with the following type of XML booleans

<prefill>True</prefill>

JAXB incorrectly marshalls this to false while values such as

<prefill>tRue</prefill>

work. 

The other issue appears to be in timing and relation to the PoolFiller thread. 



-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:44:13 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Thu, 11 Oct 2007 17:44:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12327618.1192139053793.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Edson Tirelli reassigned JBRULES-1268:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 17:48:04 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Thu, 11 Oct 2007 17:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16150055.1192139284953.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=comments#action_12381830 ] 
            
Edson Tirelli commented on JBRULES-1268:
----------------------------------------

There are 2 problems. The first problem is easy to fix: an Activation that is not queued anymore, should never call dequeue on itself again. This is fixed by nulling out the queue reference in the dequeue method:

    public void dequeue() {
        if ( this.queue != null ) {
            // will only be null if the AgendaGroup is locked when the activation add was attempted
            this.queue.dequeue( this.index );
            this.queue = null;
        }
        this.activated = false;
    }

The second problem is more subtle: is it a valid use case to try to cancel (dequeue) an activation from inside a listener? I don't think we should allow this, since listeners are supposed to be read-only and not influence the rule engine execution.

Ideas?




> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 18:33:03 2007
From: jira-events at lists.jboss.org (Philippe Ombredanne (JIRA))
Date: Thu, 11 Oct 2007 18:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1270) Tool friendly
 MVEL features for MVEl 2.0
Message-ID: <5095612.1192141983349.JavaMail.jira@cloud.prod.atl2.jboss.com>

Tool friendly MVEL features for MVEl 2.0
----------------------------------------

                 Key: JBRULES-1270
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1270
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
            Reporter: Philippe Ombredanne
         Assigned To: Mark Proctor
             Fix For: FUTURE


Here are a couple request for MVEl 2.0:
- keeping something like an ast (may be with a  compile flag) that is close to the actual expression text
- producing compiled expression even of there were some errors (ie keep on trucking) (optional flag for that too)
- being able to extend the ast with completion information (ie attach completion stuffs directly as a decoration of node in the parse tree

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 19:09:03 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 11 Oct 2007 19:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4424)
 WebAuthentication:Generate a SSOID
In-Reply-To: <20618100.1179337252975.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3576019.1192144143964.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4424?page=comments#action_12381884 ] 
            
Stefan Guilhen commented on JBAS-4424:
--------------------------------------

I'm implementing the SSO functionality pretty much like the AuthenticatorBase, by delegating the SSO operations to the SingleSignOn valve. However, the methods that we must invoke (register, update, associate) are protected in the SingleSignOn class. I've started a discussion on the forums (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094309#4094309), and my first idea is to relax the SingleSignOn method's access to public in JBossWeb.

> WebAuthentication:Generate a SSOID
> ----------------------------------
>
>                 Key: JBAS-4424
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4424
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Security
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication
> The feature needs to implement the sso stuff if it is desired by the user.  At the least, ssoid needs to be generated and set on the session.
> The ssoid generation logic exists in AuthenticatorBase.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 19:53:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 19:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1268)
 Activation.remove() is
 removing the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5467112.1192146783345.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=comments#action_12381888 ] 
            
Michael Neale commented on JBRULES-1268:
----------------------------------------

yes that is a good point. The problem is that the event listener exposes the activation item in its API, thus the remove() is there. 

AgendaFilter is really what this is for. 

I would be happy with this to throw a UnsupportedOperationException - with clear error message saying how you can't change the activation inside a event listener (and use a filter instead).

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 20:33:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 11 Oct 2007 20:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1268)
 Activation.remove() is removing
 the WRONG activation when used in events
In-Reply-To: <5124304.1192086614482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15171768.1192149183322.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1268?page=all ]

Mark Proctor closed JBRULES-1268.
---------------------------------

    Resolution: Done

I've set this to null the queue, so if called twice this method does nothing. I'm less worried about this as it should never be called by a user. If someone wants to update javadocs, go for it. We could update the event object not to expose the Activation, that is a possability. So it just has getRule, getFactHandle methods.

> Activation.remove() is removing the WRONG activation when used in events
> ------------------------------------------------------------------------
>
>                 Key: JBRULES-1268
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1268
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.1.0
>
>
> Check out FIXME_testActivationCancellation in MiscTest.java.
> It shows how a call to activation.remove() for a given rule (in an event) actually removed the wrong rule.
> The reason for this is that fireNextItem in DefaultAgenda uses BinaryHeapQueueAgendaGroup.getNext().
> This poorly named "getNext()" actually calls dequeue on the queue, so when the event is called, the activation has ALREADY been dequeued. 
> Not sure of best solution, other then a queue "peek()" and then dequeue() to be called after then event is fired (if it wasn't called already). 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:15:04 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4720) Ensure
 security-domain is picked up by JCA Deployer
In-Reply-To: <25591894.1189710491347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12789027.1192158904386.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4720?page=all ]

Weston Price resolved JBAS-4720.
--------------------------------

    Resolution: Done

The new deployment model correctly handles security domain deployments.

> Ensure security-domain is picked up by JCA Deployer
> ---------------------------------------------------
>
>                 Key: JBAS-4720
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4720
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: Anil Saldhana
>         Assigned To: Weston Price
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Ensure that the security-domain settings are read into the metadata to be used by ConnectionManager.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:17:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4671)
 DsDataSourceTemplate needs to be completed
In-Reply-To: <29814872.1188958164434.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7707397.1192159023564.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4671?page=all ]

Weston Price reassigned JBAS-4671:
----------------------------------

    Assignee: Weston Price

> DsDataSourceTemplate needs to be completed
> ------------------------------------------
>
>                 Key: JBAS-4671
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4671
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service, Management services
>            Reporter: Scott M Stark
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The org.jboss.resource.deployers.management,DsDataSourceTemplate template implementation needs to be completed to allow the addition of datasources.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:17:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4671) DsDataSourceTemplate
 needs to be completed
In-Reply-To: <29814872.1188958164434.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26872096.1192159023888.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4671?page=all ]

Weston Price updated JBAS-4671:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120873

> DsDataSourceTemplate needs to be completed
> ------------------------------------------
>
>                 Key: JBAS-4671
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4671
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JCA service, Management services
>            Reporter: Scott M Stark
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The org.jboss.resource.deployers.management,DsDataSourceTemplate template implementation needs to be completed to allow the addition of datasources.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:19:03 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Thu, 11 Oct 2007 23:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4059) JBoss5 RARDeployer
 deploys RAR's twice
In-Reply-To: <15351446.1170628159545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15189924.1192159143422.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4059?page=all ]

Weston Price resolved JBAS-4059.
--------------------------------

    Resolution: Out of Date

Old issue that has been addressed by latest deployer framework.

> JBoss5 RARDeployer deploys RAR's twice
> --------------------------------------
>
>                 Key: JBAS-4059
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4059
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Weston Price
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Because of the new deployment structure in JBoss5, the RAR deployer is now deploying RAR's twice. I assume this has to do with the RARDeployer using a deprecated API of the DeploymentUnit. 
> As a result, the JMX console records deployments such as:
> # name='jboss-ha-local-jdbc.rar#jboss-ha-local-jdbc.rar',service=RARDeployment
> # name='jboss-ha-local-jdbc.rar',service=RARDeployment
> This is causing issues with programmatic deployment, as well as the new metadata repository. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:47:58 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 23:47:58 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1271) Test Manager
Message-ID: <23074427.1192160878947.JavaMail.jira@cloud.prod.atl2.jboss.com>

Test Manager
------------

                 Key: JBRULES-1271
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1271
             Project: JBoss Drools
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: drools-brms
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:47:59 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 23:47:59 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1121) Operator field and
 the fact's variable field required in the "then" part of the rule
In-Reply-To: <26598244.1187937569373.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14621178.1192160879140.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1121?page=all ]

Michael Neale closed JBRULES-1121.
----------------------------------

    Fix Version/s: 4.1.0
                       (was: FUTURE)
       Resolution: Done

I have changed the behaviour of this a bit - should be clearer in future how to do this.

> Operator field and the fact's variable field required in the "then" part of the rule
> ------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1121
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1121
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE, drools-brms
>    Affects Versions:  4.0.0.GA
>         Environment: drools-jbrms stand alone and Eclipse drools-4.0.0 
>            Reporter: sreeni sabapathy
>         Assigned To: Michael Neale
>            Priority: Minor
>             Fix For: 4.1.0
>
>   Original Estimate: 10 minutes
>  Remaining Estimate: 10 minutes
>
> In the drools-jbrms standalone and even in the eclipse plugin version of "New guided drl file"
> the "then" part of the rule has the limitation of assigning the fixed value to the fact's variable.
> But in many condition the the value of the variable depends upon the value of another variable.
> I have taken  a simple example for explanation.
> For calcluating simple interest
> SI = P*T*R/100
> Now in the rule file if the 
> "when" condition as the check of " Calcluation type (simple ineterst or compound interest)"
> "then" part having SI, 
> At the present drool-jbrms definition the 
> "then" part has SI = text field.
> But my requirement is to look up the class variable "principle", "Time" and the "Rate" and then calculate, not just 
> assign some fixed values.
> In a simple sentence I would appreciate if the drools- jbrms has the options related to  "when" in the "then" part of the rule also.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 11 23:47:59 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 11 Oct 2007 23:47:59 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1271) Test Manager
In-Reply-To: <23074427.1192160878947.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28592259.1192160879411.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1271?page=all ]

Michael Neale updated JBRULES-1271:
-----------------------------------

      Component/s: drools-brms
    Fix Version/s: FUTURE
      Description: General JIRA for test manager features.

> Test Manager
> ------------
>
>                 Key: JBRULES-1271
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1271
>             Project: JBoss Drools
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: FUTURE
>
>
> General JIRA for test manager features.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:02:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
Message-ID: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
---------------------------------------------------------------

                 Key: JBAS-4818
                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:04:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15613208.1192161843236.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith updated JBAS-4818:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

Chapter 1 is Attached.

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:06:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
Message-ID: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - TRACKER
-----------------------------------------

                 Key: JBAS-4819
                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Directory Structure
Message-ID: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 2 -  Directory Structure
------------------------------------------------------------------

                 Key: JBAS-4820
                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt

Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Directory Structure
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28514986.1192162263453.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Michael Smith updated JBAS-4820:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-2.odt

Chapter 2 Attached

> TECH REVIEW: Installation Guide - Chapter 2 -  Directory Structure
> ------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:13:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  The Default Server Configuration File Set
Message-ID: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 3 -  The Default Server Configuration File Set
----------------------------------------------------------------------------------------

                 Key: JBAS-4821
                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


 Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:15:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4822) TECH REVIEW:
 Installation Guide -
 Chapter 4 -  The Default Server Configuration File Set
Message-ID: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 4 -  The Default Server Configuration File Set
----------------------------------------------------------------------------------------

                 Key: JBAS-4822
                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt

Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:15:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide -
 Chapter 4 -  The Default Server Configuration File Set
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30427653.1192162503415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-4.odt

Chapter 4 Attached

> TECH REVIEW: Installation Guide - Chapter 4 -  The Default Server Configuration File Set
> ----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:17:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Starting and Stopping JBoss
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19742778.1192162623352.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 4 -  Starting and Stopping JBoss  (was: TECH REVIEW: Installation Guide - Chapter 4 -  The Default Server Configuration File Set)

> TECH REVIEW: Installation Guide - Chapter 4 -  Starting and Stopping JBoss
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:17:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  The Default Server Configuration File Set
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21949056.1192162623501.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

Michael Smith updated JBAS-4821:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-3.odt

Chapter 3 Attached

> TECH REVIEW: Installation Guide - Chapter 3 -  The Default Server Configuration File Set
> ----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 00:28:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 00:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4823) TECH REVIEW: Getting
 Started Guide - TRACKER
Message-ID: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - TRACKER
--------------------------------------------

                 Key: JBAS-4823
                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:34 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4824) TECH REVIEW: Getting
 Started Guide - Appendix A. Further Information Sources
Message-ID: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
----------------------------------------------------------------------------

                 Key: JBAS-4824
                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:34 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - Getting Started
Message-ID: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started
----------------------------------------------------------------

                 Key: JBAS-4825
                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/



-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4826) TECH REVIEW: Getting
 Started Guide - Chapter 2. The JBoss Server - A Quick Tour
Message-ID: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour
-------------------------------------------------------------------------------

                 Key: JBAS-4826
                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
Message-ID: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
------------------------------------------------------------------------------

                 Key: JBAS-4827
                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. The Duke's Bank Application
Message-ID: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 4. The Duke's Bank Application
---------------------------------------------------------------------------

                 Key: JBAS-4828
                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. J2EE Web Services
Message-ID: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 5. J2EE Web Services
-----------------------------------------------------------------

                 Key: JBAS-4829
                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. JMS and Message-Driven Beans
Message-ID: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans
----------------------------------------------------------------------------

                 Key: JBAS-4830
                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4831) TECH REVIEW: Getting
 Started Guide - Chapter 7. Container-Managed Persistence
Message-ID: <2964949.1192165535786.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
-----------------------------------------------------------------------------

                 Key: JBAS-4831
                 URL: http://jira.jboss.com/jira/browse/JBAS-4831
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:35 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4832) TECH REVIEW: Getting
 Started Guide - Chapter 8. Using other Databases
Message-ID: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
---------------------------------------------------------------------

                 Key: JBAS-4832
                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:05:36 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:05:36 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4833) TECH REVIEW: Getting
 Started Guide - Chapter 9. Using Hibernate
Message-ID: <12730012.1192165536058.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
---------------------------------------------------------------

                 Key: JBAS-4833
                 URL: http://jira.jboss.com/jira/browse/JBAS-4833
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4824) TECH REVIEW: Getting
 Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27804898.1192165623713.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Michael Smith updated JBAS-4824:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Appendix.odt

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4833) TECH REVIEW: Getting
 Started Guide - Chapter 9. Using Hibernate
In-Reply-To: <12730012.1192165536058.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21464001.1192165623842.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4833?page=all ]

Michael Smith updated JBAS-4833:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-9.odt

> TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
> ---------------------------------------------------------------
>
>                 Key: JBAS-4833
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4833
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-9.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4832) TECH REVIEW: Getting
 Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12852496.1192165624029.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4832?page=all ]

Michael Smith updated JBAS-4832:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-8.odt

> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4831) TECH REVIEW: Getting
 Started Guide - Chapter 7. Container-Managed Persistence
In-Reply-To: <2964949.1192165535786.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6612848.1192165624146.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4831?page=all ]

Michael Smith updated JBAS-4831:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-7.odt

> TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4831
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4831
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-7.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. JMS and Message-Driven Beans
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11527511.1192165624264.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Michael Smith updated JBAS-4830:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-6.odt

> TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. J2EE Web Services
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20457507.1192165624406.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Michael Smith updated JBAS-4829:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-5.odt

> TECH REVIEW: Getting Started Guide - Chapter 5. J2EE Web Services
> -----------------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. The Duke's Bank Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28879582.1192165624565.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Michael Smith updated JBAS-4828:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-4.odt

> TECH REVIEW: Getting Started Guide - Chapter 4. The Duke's Bank Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8294341.1192165624714.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Michael Smith updated JBAS-4827:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-3.odt

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started Guide - Chapter 2. The JBoss Server - A Quick Tour
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5040531.1192165624834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Michael Smith updated JBAS-4826:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-2.odt

> TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:07:04 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 01:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - Getting Started
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30196809.1192165624973.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

Michael Smith updated JBAS-4825:
--------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-1.odt

> TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started
> ----------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:11:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
Message-ID: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Clustering Guide - TRACKER
---------------------------------------

                 Key: JBAS-4834
                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
Message-ID: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
--------------------------------------------------------

                 Key: JBAS-4835
                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
Message-ID: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
-----------------------------------------------------------------------

                 Key: JBAS-4836
                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
Message-ID: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
-----------------------------------------------------------------------

                 Key: JBAS-4837
                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
Message-ID: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
----------------------------------------------------------------------

                 Key: JBAS-4838
                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
Message-ID: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
------------------------------------------------------------

                 Key: JBAS-4839
                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:35:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
Message-ID: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
----------------------------------------------------------

                 Key: JBAS-4840
                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:37:18 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:37:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
Message-ID: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Chapter2 - JBossCache and JGroups Services
-------------------------------------------------------

                 Key: JBAS-4841
                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Documentation
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Assigned To: Norman Richards


Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:37:18 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:37:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23378177.1192167438605.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

samson kittoli updated JBAS-4838:
---------------------------------

          Component/s: Documentation
    Affects Version/s: JBossAS-4.2.2.GA
              Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:37:18 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:37:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31680594.1192167438749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

samson kittoli updated JBAS-4837:
---------------------------------

          Component/s: Documentation
    Affects Version/s: JBossAS-4.2.2.GA
              Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:39:24 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:39:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6724946.1192167564192.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

samson kittoli updated JBAS-4836:
---------------------------------

          Component/s: Documentation
    Affects Version/s: JBossAS-4.2.2.GA
              Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:39:24 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:39:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30564211.1192167564359.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

samson kittoli updated JBAS-4835:
---------------------------------

    Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:39:24 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:39:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24988166.1192167564539.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

samson kittoli updated JBAS-4839:
---------------------------------

    Affects: [Documentation (Ref Guide, User Guide, etc.)]

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:41:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27184631.1192167663319.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

samson kittoli updated JBAS-4835:
---------------------------------

    Attachment: JBAS-422 - Clustering -  Chapter1 - Introduction.odt

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:41:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20521541.1192167663467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

samson kittoli updated JBAS-4836:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30925513.1192167783423.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

samson kittoli updated JBAS-4837:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10974014.1192167783540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

samson kittoli updated JBAS-4838:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9016242.1192167783824.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

samson kittoli updated JBAS-4839:
---------------------------------

    Attachment: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8884290.1192167784057.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

samson kittoli updated JBAS-4840:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:43:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:43:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21640176.1192167784240.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

samson kittoli updated JBAS-4841:
---------------------------------

    Attachment: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 01:50:17 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 01:50:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24797602.1192168217974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

samson kittoli updated JBAS-4835:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:01:19 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 12 Oct 2007 02:01:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29152137.1192168879742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Rubinger resolved EJBTHREE-1062.
---------------------------------------

    Resolution: Done

Unit test passes, none further broken (some unit tests required alterations to their existing naming strategies as fixes for this issue created a naming conflict).

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:01:19 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:01:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24747654.1192168879989.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

samson kittoli updated JBAS-4839:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:03:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14038244.1192168983437.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

samson kittoli updated JBAS-4840:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:03:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25108525.1192168983630.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

samson kittoli updated JBAS-4841:
---------------------------------

    Component/s: Clustering Guide
                     (was: Documentation)

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Norman Richards
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:05:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4842) TECH REVIEW: Server
 Configuration Guide - TRACKER
Message-ID: <22836378.1192169103482.JavaMail.jira@cloud.prod.atl2.jboss.com>

 TECH REVIEW: Server Configuration Guide - TRACKER
--------------------------------------------------

                 Key: JBAS-4842
                 URL: http://jira.jboss.com/jira/browse/JBAS-4842
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 02:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1197) Incorporate
 Spanish XML into Cache docs repo and build
Message-ID: <10175107.1192169223335.JavaMail.jira@cloud.prod.atl2.jboss.com>

Incorporate Spanish XML into Cache docs repo and build
------------------------------------------------------

                 Key: JBCACHE-1197
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1197
             Project: JBoss Cache
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Michael Smith
         Assigned To: Manik Surtani


Need to put the spanish XML file where it belongs

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
Message-ID: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
---------------------------------------------------------------------------------------------

                 Key: JBAS-4843
                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
Message-ID: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
-------------------------------------------------------------------------------

                 Key: JBAS-4844
                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4845) TECH REVIEW: Server
 Configuration
 Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
Message-ID: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
---------------------------------------------------------------------------------------------------------

                 Key: JBAS-4845
                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Messaging on JBoss
Message-ID: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Server Configuration Guide - Chapter6 - Messaging on JBoss
------------------------------------------------------------------------

                 Key: JBAS-4846
                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Transactions on JBoss
Message-ID: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Server Configuration Guide - Chapter5 - Transactions on JBoss
---------------------------------------------------------------------------

                 Key: JBAS-4847
                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Connectors on JBoss
Message-ID: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter4 - Connectors on JBoss
------------------------------------------------------------------------

                 Key: JBAS-4848
                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - Naming on JBoss
Message-ID: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Server Configuration Guide - Chapter3 - Naming on JBoss
---------------------------------------------------------------------

                 Key: JBAS-4849
                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
Message-ID: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
---------------------------------------------------------------

                 Key: JBAS-4850
                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:25:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:25:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
Message-ID: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
-----------------------------------------------------------------------------------------------

                 Key: JBAS-4851
                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5266748.1192170423487.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

samson kittoli updated JBAS-4851:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7674676.1192170423604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

samson kittoli updated JBAS-4850:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - Naming on JBoss
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28106266.1192170423718.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

samson kittoli updated JBAS-4849:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter3 - Naming on JBoss
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Connectors on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22761692.1192170423837.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli updated JBAS-4848:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter4 - Connectors on JBoss
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Transactions on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15672135.1192170423964.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

samson kittoli updated JBAS-4847:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Messaging on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3048313.1192170424104.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

samson kittoli updated JBAS-4846:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Messaging on JBoss
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration
 Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4857463.1192170424220.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

samson kittoli updated JBAS-4845:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt

> TECH REVIEW: Server Configuration Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:27:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:27:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9512597.1192170424355.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

samson kittoli updated JBAS-4844:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:29:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 12 Oct 2007 02:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20888218.1192170543216.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

samson kittoli updated JBAS-4843:
---------------------------------

    Attachment: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:31:05 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Fri, 12 Oct 2007 02:31:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1627) Evaluate and
 implement missing JSR-88 functionality
Message-ID: <17756514.1192170665958.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1627?page=all ]

Max Andersen closed JBAS-1627.
------------------------------

    Resolution: Rejected

> Evaluate and implement missing JSR-88 functionality
> ---------------------------------------------------
>
>                 Key: JBAS-1627
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1627
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>    Affects Versions: JBossAS-4.0.1 Final
>         Environment: deployment module
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:31:06 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Fri, 12 Oct 2007 02:31:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-1627) Evaluate and
 implement missing JSR-88 functionality
Message-ID: <20455638.1192170666270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1627?page=all ]

Max Andersen reopened JBAS-1627:
--------------------------------

             
wrong bug ;)

> Evaluate and implement missing JSR-88 functionality
> ---------------------------------------------------
>
>                 Key: JBAS-1627
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1627
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>    Affects Versions: JBossAS-4.0.1 Final
>         Environment: deployment module
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 02:45:15 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 12 Oct 2007 02:45:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4822584.1192171515246.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=all ]

Andrew Rubinger reassigned EJBTHREE-1066:
-----------------------------------------

    Assignee: Andrew Rubinger

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:44:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Fri, 12 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3894053.1192175043343.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Rubinger reopened EJBTHREE-1062:
---------------------------------------

             
Should not require JNDI naming fixes.

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:44:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7250862.1192175043521.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12381960 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I verified that jbossws-2.0.1.SP2 core tests pass against Branch_4_2.

The difference between SP1 and SP2 is that SP2 does not ship with the (outdated) container integration jar jbossws-jboss42.jar, which is now part of the AS code base. i.e. jbossws-jboss42.jar is not part of jbossws.sar any more.

Do you want me to install that version. Other than that there is no change and hence there is no QA rerun required.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:46:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7793479.1192175163488.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Thomas Diesler reassigned JBAS-4811:
------------------------------------

    Assignee: Dimitris Andreadis

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:46:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27767301.1192175163646.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12381961 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

The latest test run is here

http://jbws.dyndns.org:8280/hudson/

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 03:54:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 03:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4852) EJB3 web service
 endpoints ignore metadata in jboss.xml
Message-ID: <16146379.1192175643414.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJB3 web service endpoints ignore metadata in jboss.xml
-------------------------------------------------------

                 Key: JBAS-4852
                 URL: http://jira.jboss.com/jira/browse/JBAS-4852
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Carlo de Wolf
             Fix For: JBossAS-4.2.2.GA


This is related to JBWS-1813

It needs to be decided whether jboss-4.2.2 can go out despite this issue.
Currently, users are forced to use annotations on the bean.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 04:00:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 12 Oct 2007 04:00:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7717327.1192176007545.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12381962 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

Sure, we should move to SP2.

How you propose to incorporate the WS tests in AS releases?

Wouldn't the easiest thing be to replicate your hudson configuration in the QA environment?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 04:10:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 12 Oct 2007 04:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1067) Refactor EJB 3
 onto the unified metadata
Message-ID: <16637681.1192176603400.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor EJB 3 onto the unified metadata
----------------------------------------

                 Key: EJBTHREE-1067
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1067
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Carlo de Wolf
         Assigned To: Carlo de Wolf
            Priority: Critical
             Fix For: AS 5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 04:38:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 12 Oct 2007 04:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1067) Refactor EJB 3
 onto the unified metadata
In-Reply-To: <16637681.1192176603400.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29277586.1192178283650.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1067?page=all ]

Carlo de Wolf updated EJBTHREE-1067:
------------------------------------

     Original Estimate: 1 week
    Remaining Estimate: 1 week

> Refactor EJB 3 onto the unified metadata
> ----------------------------------------
>
>                 Key: EJBTHREE-1067
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1067
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:02:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 12 Oct 2007 05:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27116.1192179723315.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=comments#action_12381964 ] 
            
Dimitris Andreadis commented on EJBTHREE-1062:
----------------------------------------------

I added a note about this problem in the 4.2.2.GA release notes.

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:16:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-171) Split the jPDL plugin
 in a Common/jPDL/BPEL plugin triad
Message-ID: <25610757.1192180563603.JavaMail.jira@cloud.prod.atl2.jboss.com>

Split the jPDL plugin in a Common/jPDL/BPEL plugin triad
--------------------------------------------------------

                 Key: GPD-171
                 URL: http://jira.jboss.com/jira/browse/GPD-171
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers


the common classes and extension points have to be included in the common plugin

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:18:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-172) Develop an extension
 example for a simple DSL in its own plugin
Message-ID: <16781370.1192180683620.JavaMail.jira@cloud.prod.atl2.jboss.com>

Develop an extension example for a simple DSL in its own plugin
---------------------------------------------------------------

                 Key: GPD-172
                 URL: http://jira.jboss.com/jira/browse/GPD-172
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:18:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:18:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-173) Develop a complete
 jPDL extension example
Message-ID: <19634315.1192180685849.JavaMail.jira@cloud.prod.atl2.jboss.com>

Develop a complete jPDL extension example
-----------------------------------------

                 Key: GPD-173
                 URL: http://jira.jboss.com/jira/browse/GPD-173
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:20:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 05:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-174) Develop a jPDL
	cheatsheet
Message-ID: <1560923.1192180803591.JavaMail.jira@cloud.prod.atl2.jboss.com>

Develop a jPDL cheatsheet
-------------------------

                 Key: GPD-174
                 URL: http://jira.jboss.com/jira/browse/GPD-174
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 05:40:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 05:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
Message-ID: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>

jbossxb-1.0.0.GA shows webservice regression
--------------------------------------------

                 Key: JBAS-4853
                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For: JBossAS-4.2.2.GA


This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11

org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString

junit.framework.ComparisonFailure: expected:<   > but was:<>
	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:00:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Moved: (GPD-175) jBPM Process Designer
 fails with class cast exception
Message-ID: <12168646.1192183203536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-175?page=all ]

Koen Aers moved JBIDE-523 to GPD-175:
-------------------------------------

          Project: JBoss jBPM GPD  (was: JBoss Tools)
              Key: GPD-175  (was: JBIDE-523)
      Component/s: jpdl
                       (was: jbpm)
    Fix Version/s: jBPM jPDL Designer 3.1.0.SP1
                       (was: 2.0.0.CR1)

> jBPM Process Designer fails with class cast exception
> -----------------------------------------------------
>
>                 Key: GPD-175
>                 URL: http://jira.jboss.com/jira/browse/GPD-175
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Fedora Core 6 with Sun's Java 1.5.0_12
> Lenovo ThinkPad T60
> 2GB RAM
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.0.SP1
>
>         Attachments: processdefinition.xml
>
>
> I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open:
> java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput
> 	at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source)
> 	at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
> 	at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
> 	at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> 	at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> 	at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
> 	at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
> 	at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
> 	at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
> 	at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> 	at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822)
> 	at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721)
> 	at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100)
> 	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
> 	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> 	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
> 	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
> 	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:10:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-175) jBPM Process Designer
 fails with class cast exception
Message-ID: <7561128.1192183803723.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-175?page=all ]

Koen Aers updated GPD-175:
--------------------------

    Attachment: processimage.jpg

I guess it is not relevant anymore. I have attached the diagram that I get when opening the file (after some node-dragging to make it look better)

> jBPM Process Designer fails with class cast exception
> -----------------------------------------------------
>
>                 Key: GPD-175
>                 URL: http://jira.jboss.com/jira/browse/GPD-175
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Fedora Core 6 with Sun's Java 1.5.0_12
> Lenovo ThinkPad T60
> 2GB RAM
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.0.SP1
>
>         Attachments: processdefinition.xml, processimage.jpg
>
>
> I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open:
> java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput
> 	at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source)
> 	at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
> 	at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
> 	at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> 	at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> 	at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
> 	at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
> 	at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
> 	at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
> 	at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> 	at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822)
> 	at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721)
> 	at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100)
> 	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
> 	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> 	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
> 	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
> 	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:12:12 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:12:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-175) jBPM Process Designer
 fails with class cast exception
Message-ID: <23678244.1192183932844.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-175?page=all ]

Koen Aers closed GPD-175.
-------------------------

    Resolution: Done

I am closing this issue. Micah, if you still experience problems feel free to reopen.

> jBPM Process Designer fails with class cast exception
> -----------------------------------------------------
>
>                 Key: GPD-175
>                 URL: http://jira.jboss.com/jira/browse/GPD-175
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Fedora Core 6 with Sun's Java 1.5.0_12
> Lenovo ThinkPad T60
> 2GB RAM
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.0.SP1
>
>         Attachments: processdefinition.xml, processimage.jpg
>
>
> I get the following error when I attempt to open the attached file (from the demo station) in Eclipse from File->Open:
> java.lang.ClassCastException: org.eclipse.ui.internal.editors.text.JavaFileEditorInput
> 	at org.jbpm.ui.editor.DesignerEditor.init(Unknown Source)
> 	at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:842)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
> 	at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:290)
> 	at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:140)
> 	at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> 	at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> 	at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:394)
> 	at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1144)
> 	at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1097)
> 	at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1311)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:455)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:102)
> 	at org.eclipse.ui.internal.PartStack.add(PartStack.java:441)
> 	at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:111)
> 	at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:60)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> 	at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> 	at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:822)
> 	at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:721)
> 	at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:682)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2593)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
> 	at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
> 	at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
> 	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
> 	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2477)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:132)
> 	at org.eclipse.ui.internal.editors.text.OpenExternalFileAction.run(OpenExternalFileAction.java:100)
> 	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
> 	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
> 	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
> 	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
> 	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3180)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2856)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:30:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-176) Add code completion
 inside attributes and values within the xml source
Message-ID: <32030443.1192185004070.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add code completion inside attributes and values within the xml source
----------------------------------------------------------------------

                 Key: GPD-176
                 URL: http://jira.jboss.com/jira/browse/GPD-176
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:32:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 12 Oct 2007 06:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-177) Add code completion in
 the text input fields on the properties view
Message-ID: <10554814.1192185123592.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add code completion in the text input fields on the properties view
-------------------------------------------------------------------

                 Key: GPD-177
                 URL: http://jira.jboss.com/jira/browse/GPD-177
             Project: JBoss jBPM GPD
          Issue Type: Task
            Reporter: Koen Aers
         Assigned To: Koen Aers




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 06:59:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 12 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25969415.1192186743304.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382034 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I installed jbossws-2.0.1.SP2

Yes, QA should integrate our hudson environment, which is part of the jbossws framework codebase.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:08:04 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Fri, 12 Oct 2007 07:08:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4455) LoadBalancePolicy
 that tries to pin all requests associated with a tx to one server
In-Reply-To: <14717863.1180632608477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17049743.1192187284260.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4455?page=comments#action_12382040 ] 
            
Galder Zamarreno commented on JBAS-4455:
----------------------------------------

[private]

Another potential customer interested in this feature:
https://na1.salesforce.com/50030000003i3bC

> LoadBalancePolicy that tries to pin all requests associated with a tx to one server
> -----------------------------------------------------------------------------------
>
>                 Key: JBAS-4455
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4455
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>
> The HA proxies don't allow failover once a tx has reached a server.  This can lead to this kind of situation:
> EJB A deployed on nodes 1 and 2.
> EJB B deployed on nodes 1 and 2.
> 1) Start tx, invoke on A.1.
> 2) Lookup B.
> 3) Invoke on B. LB policy picks B.2
> 4) Node 2 is dead for some reason so call fails.
> 5) Can't fail over because tx context won't allow a failover after a call has reached a server.
> But, B.1 is fine and is running on the only node the tx has invoked on. :(
> Approach to improving this.  This is based on JRMPInovkerProxyHA methods, but the idea is generic:
> In invocationHasReachedAServer, instead of storing null as the value, you store the target (key is the tx).
> In invoke, if there's a tx, you add that target (if there is one) to the invocation as transient metadata 
> The LB policy gets passed the invocation as an arg when it chooses a target (this is already in the API)
> LB policy checks for the metadata. If there, and that target is in its target list, return that target

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:14:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 07:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user only if child folders
 have write or manage permssion for anonymous (read is not enough)
Message-ID: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>

ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
--------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1742
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final
         Environment: JBoss 4.2.1
            Reporter: Mariusz Smykula
         Assigned To: Sohil Shah


I want to execute simple code from my portlet:

 Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
 mainFolder = (Folder) cmsService.execute(listCMD);
 LOG.info(mainFolder .getFolders().size()); 

This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?

This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!

  for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
        {
            Permission specificPermission = (Permission)itr.next();
            
            if( (specificPermission.getService().equals("cms")) && 
                (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
            )
            {
                for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
                {
                    Permission userPermission = (Permission)itr2.next();
                    if( (userPermission.getService().equals("cms")) && 
                        (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
                    )
                    {
                        String pathCriteria = userPermission.findCriteriaValue("path");
                        if(pathCriteria.equals(path))
                        {
                            //this means this user has read access to this path
                            toolAccess = true;
                        }
                    }
                }
            }
        }

This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:20:30 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 07:20:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user
 only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <635736.1192188030146.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=comments#action_12382047 ] 
            
Mariusz Smykula commented on JBPORTAL-1742:
-------------------------------------------

Ok, computeToolAccess have interesting comment, but why this method is included in ACLInterceptor? I want to access CMS resources from my custom portlet and list them.

 * This is used to filter out cms resources in the CMS Admin tool, so that the user
     * can see only the resources that he has write/manage access to

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 07:41:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 07:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1197) Incorporate
 Spanish XML into Cache docs repo and build
In-Reply-To: <10175107.1192169223335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13491238.1192189263574.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1197?page=comments#action_12382067 ] 
            
Manik Surtani commented on JBCACHE-1197:
----------------------------------------

And where does this belong?  Current English docs reside in subversion alongside the code.  Not sure if we want all translations here as well since translations may be out of sync or a couple of releases behind.  E.g., the code is at version 2.1.0.Beta1, (and so is the English documentation) but given that we cut a public release ever couple of months, there may not be time for translations to catch up.

What would you suggest here?

> Incorporate Spanish XML into Cache docs repo and build
> ------------------------------------------------------
>
>                 Key: JBCACHE-1197
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1197
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Smith
>         Assigned To: Manik Surtani
>
> Need to put the spanish XML file where it belongs

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:13:13 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 08:13:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user
 only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23876766.1192191193680.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=comments#action_12382098 ] 
            
Mariusz Smykula commented on JBPORTAL-1742:
-------------------------------------------

In class ACLInterceptor (line: 270) is this code necessary?

securityContext.removeAttribute("command");

without this line, the ACLEnforcer know than my anonymous user want read subfolders, and then show folders to him.

For full explanation:
* Logged user can see subfolders without write or manage permission (only read is needed). 
* Anonymous user cant see subfolders with read permission - subfolders must be write or manage for Anonymous.

I think this is bad behavior.

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:15:21 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 08:15:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1467) URL's of page's
 whose
 <page-name> attribute has ampersand used as an entity (&amp;) is not
 encoded correctly
In-Reply-To: <18766428.1180623548864.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24166039.1192191321945.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1467?page=all ]

Thomas Heute reassigned JBPORTAL-1467:
--------------------------------------

    Assignee: Thomas Heute  (was: Julien Viet)

> URL's of page's whose <page-name> attribute has ampersand used as an entity (&amp;) is not encoded correctly
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1467
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1467
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.4.1 Final
>         Environment: All
>            Reporter: deepashree krishnamurthy
>         Assigned To: Thomas Heute
>
> URL's of page's whose <page-name> attribute has ampersand used as an entity (&amp;) is not encoded correctly.
> Define a page in *-object.xml eith ampersand in page-name 
> ex: 
> <deployment>
>      <if-exists>overwrite</if-exists>
>      <parent-ref>default</parent-ref>
>      <properties/>
>      <page>
>           <page-name>Auto &amp; Navigator</page-name>
>            :
>     </page>
> :
> </deployment>
> The page is unaccessible on FireFox. Seems that it is not encoded 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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:26:38 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 08:26:38 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-999) Bridge startup
 should retry if remote destinations are not available
In-Reply-To: <29606772.1182423652053.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30538482.1192191998374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-999?page=all ]

Tim Fox closed JBMESSAGING-999.
-------------------------------

    Resolution: Done

> Bridge startup should retry if remote destinations are not available
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-999
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-999
>             Project: JBoss Messaging
>          Issue Type: Task
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Currently the bridge only retries connection creation after startup.
> If remote provider is not available at startup it will fail to start.
> We should change this by institutiing a retry at startup too.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:37:19 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 12 Oct 2007 08:37:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-18) Work with Marshall on
 defining JBoss AOP IDE requirements
Message-ID: <24473605.1192192639920.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-18?page=all ]

Kabir Khan closed JBAOP-18.
---------------------------

    Resolution: Out of Date

> Work with Marshall on defining JBoss AOP IDE requirements
> ---------------------------------------------------------
>
>                 Key: JBAOP-18
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-18
>             Project: JBoss AOP
>          Issue Type: Feature Request
>    Affects Versions: 2.1.0.GA
>            Reporter: Bill Burke
>         Assigned To: Kabir Khan
>             Fix For: 2.1.0.GA
>
>
> Work with Marshall on what we need to improve JBoss AOP IDE support.  For both performance of the IDE, usability, and features.  Work on the ROADMAP to define when these should go out

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:46:22 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 12 Oct 2007 08:46:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-479) Enable
 org.jboss.test.aop.proxy.ProxyTestCase(jdk14).testAnnotationsExistInProxy
Message-ID: <24646856.1192193182276.JavaMail.jira@cloud.prod.atl2.jboss.com>

Enable org.jboss.test.aop.proxy.ProxyTestCase(jdk14).testAnnotationsExistInProxy
--------------------------------------------------------------------------------

                 Key: JBAOP-479
                 URL: http://jira.jboss.com/jira/browse/JBAOP-479
             Project: JBoss AOP
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Kabir Khan
         Assigned To: Kabir Khan
             Fix For: 2.0.0.GA


   public void testAnnotationsExistInProxy() throws Exception
   {
      //THis test fails if we run with jboss retro
      try
      {
         Class.forName("org.jboss.lang.ClassRedirects");
         System.out.println("IGNORING TEST ON JDK 1.4");
         return;
      }
      catch(Exception ignoreWeAreRunningWithJDK5)
      {
      }  

This *might* be deferrable to a later release since it is a JDK 1.4 thing and AOP 2.0 is targeting AS 5 (JDK 5)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:48:19 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 12 Oct 2007 08:48:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1103) Move JBM
	examples
Message-ID: <6865711.1192193299985.JavaMail.jira@cloud.prod.atl2.jboss.com>

Move JBM examples
-----------------

                 Key: JBMESSAGING-1103
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1103
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: AS 5.0 Integration, EAP 4.3 Integration
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:50:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 08:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8808787.1192193403311.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=all ]

Thomas Heute updated JBPORTAL-1742:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:57:26 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 08:57:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1103) Move JBM
	examples
In-Reply-To: <6865711.1192193299985.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13133475.1192193846316.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1103?page=all ]

Tim Fox updated JBMESSAGING-1103:
---------------------------------

        Fix Version/s: AS 5.0 Integration
                       EAP 4.3 Integration
    Affects Version/s:     (was: AS 5.0 Integration)
                           (was: EAP 4.3 Integration)

> Move JBM examples
> -----------------
>
>                 Key: JBMESSAGING-1103
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1103
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 08:57:26 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 08:57:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2942498.1192193846827.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=all ]

Tim Fox updated JBMESSAGING-1101:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:07:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 12 Oct 2007 09:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1104) Set StrictTCK
 as false by default, and chage TCK to be true
Message-ID: <8986192.1192194423340.JavaMail.jira@cloud.prod.atl2.jboss.com>

Set StrictTCK as false by default, and chage TCK to be true
-----------------------------------------------------------

                 Key: JBMESSAGING-1104
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1104
             Project: JBoss Messaging
          Issue Type: Feature Request
            Reporter: Clebert Suconic
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:16:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 12 Oct 2007 09:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1105) Run
 integration tests against default config as well
Message-ID: <2691823.1192194963472.JavaMail.jira@cloud.prod.atl2.jboss.com>

Run integration tests against default config as well
----------------------------------------------------

                 Key: JBMESSAGING-1105
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1105
             Project: JBoss Messaging
          Issue Type: Feature Request
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For: AS 5.0 Integration




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:25:03 2007
From: jira-events at lists.jboss.org (Delbart Vincent (JIRA))
Date: Fri, 12 Oct 2007 09:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1272) DSL : String
 index out of range: -1
Message-ID: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL : String index out of range: -1
-----------------------------------

                 Key: JBRULES-1272
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Delbart Vincent
         Assigned To: Mark Proctor
            Priority: Critical


Hi,

I have a problem with my DSL and the 4.0.2 version :

this sentence doesn't work in 4.0.2 :

[condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )

log :
!ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
!MESSAGE String index out of range: -1
!STACK 0
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
        at java.lang.String.substring(String.java:1768)
        at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
        at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
        at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
        at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
        at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
        at org.eclipse.jface.window.Window.open(Window.java:796)
        at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
        at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
        at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
        at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
        at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:977)
        at org.eclipse.core.launcher.Main.main(Main.java:952)


If I put two blanks between {number} {object}, it's working.
[condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:25:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 09:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1743) Test the bridge
 request dispatching
Message-ID: <20293184.1192195503912.JavaMail.jira@cloud.prod.atl2.jboss.com>

Test the bridge request dispatching
-----------------------------------

                 Key: JBPORTAL-1743
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1743
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core
            Reporter: Thomas Heute
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 12 Oct 2007 09:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16683674.1192195863836.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis reassigned JBAS-4811:
----------------------------------------

    Assignee: Rajesh Rajasekaran  (was: Dimitris Andreadis)

Assign this to Rajesh, to suggest how we can proceed incorporating the WS suite in the regular QA environment, and make it part of the AS release process.

For the 4.2.2.GA release, I think we don't have to block on this task, as long as Thomas is satisfied with the results of his local hudson runs.



> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:33:04 2007
From: jira-events at lists.jboss.org (Rainer Langbehn (JIRA))
Date: Fri, 12 Oct 2007 09:33:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
Message-ID: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>

Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
----------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1273
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Rainer Langbehn
         Assigned To: Mark Proctor


I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:35:03 2007
From: jira-events at lists.jboss.org (Madhusudhan Konda (JIRA))
Date: Fri, 12 Oct 2007 09:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1106) Deleting A
	Single Message
Message-ID: <10635104.1192196103958.JavaMail.jira@cloud.prod.atl2.jboss.com>

Deleting A Single Message
-------------------------

                 Key: JBMESSAGING-1106
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1106
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
            Reporter: Madhusudhan Konda
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


JBM should have a new feature to remove a single message from the Destination, perhaps based on a message id? Currently, we can only remove *all* messages, but this feature would be helpful so one can pick and delete a message individually. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:57:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 09:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1186)
 ClusteredCacheLoader to wait
 for first positive result rather than all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31834600.1192197423645.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani reopened JBCACHE-1186:
------------------------------------

             

> ClusteredCacheLoader to wait for first positive result rather than all results
> ------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Fri Oct 12 09:57:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 09:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1186)
 ClusteredCacheLoader and
 DataGravitationInterceptor to wait for first positive result rather than
 all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23838699.1192197423727.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani updated JBCACHE-1186:
-----------------------------------

          Summary: ClusteredCacheLoader and DataGravitationInterceptor to wait for first positive result rather than all results  (was: ClusteredCacheLoader to wait for first positive result rather than all results)
    Fix Version/s: 2.1.0.CR1
                       (was: 2.1.0.BETA1)

> ClusteredCacheLoader and DataGravitationInterceptor to wait for first positive result rather than all results
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:07:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 12 Oct 2007 10:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7042969.1192198023922.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12382154 ] 
            
Mark Proctor commented on JBRULES-1273:
---------------------------------------

can you attach it to our JIRA for us to look at?

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Mark Proctor
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:13:03 2007
From: jira-events at lists.jboss.org (Joni Niemi (JIRA))
Date: Fri, 12 Oct 2007 10:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4854) Duplicate
 Content-Type charset attribute causes exception
Message-ID: <22500888.1192198383865.JavaMail.jira@cloud.prod.atl2.jboss.com>

Duplicate Content-Type charset attribute causes exception
---------------------------------------------------------

                 Key: JBAS-4854
                 URL: http://jira.jboss.com/jira/browse/JBAS-4854
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.1.GA
         Environment: Windows XP, JBOSS AS 4.2.1.GA
            Reporter: Joni Niemi
         Assigned To: Remy Maucherat


New maemo Mozilla browser has a "feature" which sends duplicate charset parameter in the POST Content-type header. This causes following exception:

java.io.UnsupportedEncodingException: UTF-8;charset=UTF-8
	at java.lang.StringCoding.decode(StringCoding.java:170)
	at java.lang.String.<init>(String.java:444)
	at java.lang.String.<init>(String.java:516)
	at org.apache.catalina.connector.Request.setCharacterEncoding(Request.java:1469)
	at org.apache.catalina.connector.RequestFacade.setCharacterEncoding(RequestFacade.java:307)
	at com.sun.faces.context.ExternalContextImpl.setRequestCharacterEncoding(ExternalContextImpl.java:167)
	at javax.faces.application.ViewHandler.initView(ViewHandler.java:259)
	at org.ajax4jsf.application.ViewHandlerWrapper.initView(ViewHandlerWrapper.java:138)
	at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:208)
	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at com.jamonapi.http.JAMonTomcatValve.invoke(JAMonTomcatValve.java:72)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
	at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419)
	at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:393)
	at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1513)
	at java.lang.Thread.run(Thread.java:619)

The erraneous* Content-Type header causing this is 
"Content-Type: application/x-www-form-urlencoded; charset=UTF-8;charset=UTF-8" 
("User-agent: Mozilla/5.0 (X11; U; Linux armv6l; en-GB; rv:1.9a6pre) Gecko/20070810
Firefox/3.0a1 Tablet browser 0.1.16 RX-34_2007SE_4.2007.38-2")

Windows version of Mozilla causes no problems:
"Content-Type: application/x-www-form-urlencoded; charset=UTF-8" 
(User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi; rv:1.8.1.7) Gecko/20070914
Firefox/2.0.0"

* I don't think RFC2616 strictly speakings prohibits duplicate attributes.

This seems to be Catalina issue, but I don't know which version JBOSS AS 4.2.1.GA is using, so I'm submitting this here.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:13:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 12 Oct 2007 10:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1106) Deleting A
	Single Message
In-Reply-To: <10635104.1192196103958.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15300623.1192198384446.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1106?page=all ]

Tim Fox updated JBMESSAGING-1106:
---------------------------------

    Fix Version/s: Unscheduled
                       (was: 1.4.0.SP1)
         Priority: Minor  (was: Major)

> Deleting A Single Message
> -------------------------
>
>                 Key: JBMESSAGING-1106
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1106
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Madhusudhan Konda
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> JBM should have a new feature to remove a single message from the Destination, perhaps based on a message id? Currently, we can only remove *all* messages, but this feature would be helpful so one can pick and delete a message individually. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:15:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 12 Oct 2007 10:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1742) ACLEnforcer -
 folder.getFolders() give results for Anonymus user
 only if child folders
 have write or manage permssion for anonymous (read is not enough)
In-Reply-To: <29022684.1192187643480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15857709.1192198503389.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1742?page=comments#action_12382157 ] 
            
Mariusz Smykula commented on JBPORTAL-1742:
-------------------------------------------

Removing line 270 is not good idea. 
Solution than work for my is:

change in ACLInterceptor (line 138) from
 hasAccess = this.computeToolAccess(loggedInUser, path);   
to
 hasAccess = this.computeAccess(loggedInUser, path,"read");

computeToolAccess is method dedicated for CMSAdminPortlet:

Comment from code

// * This is used to filter out cms resources in the CMS Admin tool, so that the user
// * can see only the resources that he has write/manage access to

computeAccess(loggedInUser, path,"read") make real checking for READ access to listed resouce.

> ACLEnforcer - folder.getFolders() give results for Anonymus user only if child folders have write or manage permssion for anonymous (read is not enough)
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1742
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1742
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>         Environment: JBoss 4.2.1
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>
> I want to execute simple code from my portlet:
>  Command listCMD = cmsService.getCommandFactory().createFolderGetListCommand("/");
>  mainFolder = (Folder) cmsService.execute(listCMD);
>  LOG.info(mainFolder .getFolders().size()); 
> This is ALWAYS empty folders list, if executed as Anonymous user. For real result I need to set role write or manage for Anonymus user to all subfolders. This is correct?
> This happens because in ACLEnforce there is checked for write or mange permssion, but read is enough!
>   for(Iterator itr=specificPermissions.iterator();itr.hasNext();)
>         {
>             Permission specificPermission = (Permission)itr.next();
>             
>             if( (specificPermission.getService().equals("cms")) && 
>                 (specificPermission.getAction().equals("write") || specificPermission.getAction().equals("manage"))
>             )
>             {
>                 for(Iterator itr2=userPermissions.iterator();itr2.hasNext();)
>                 {
>                     Permission userPermission = (Permission)itr2.next();
>                     if( (userPermission.getService().equals("cms")) && 
>                         (userPermission.getAction().equals("write") || userPermission.getAction().equals("manage"))
>                     )
>                     {
>                         String pathCriteria = userPermission.findCriteriaValue("path");
>                         if(pathCriteria.equals(path))
>                         {
>                             //this means this user has read access to this path
>                             toolAccess = true;
>                         }
>                     }
>                 }
>             }
>         }
> This is correct?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:19:05 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 12 Oct 2007 10:19:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1197) Incorporate
 Spanish XML into Cache docs repo and build
In-Reply-To: <10175107.1192169223335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11675575.1192198745219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1197?page=comments#action_12382159 ] 
            
Michael Smith commented on JBCACHE-1197:
----------------------------------------

Hi Manik,

Sorry, there mate, can you assign this task to me? We are in process of recursing all the hibernate content into PO format and have used a new layout that keeps the translation in sync for the 4 AS books. This jira issue is a placeholder for me to ensure it stays in sync with your english. As soon as the tech review is done for AS422 I'll move onto this.

http://jira.jboss.com/jira/browse/JBAS-4696

- Mike



> Incorporate Spanish XML into Cache docs repo and build
> ------------------------------------------------------
>
>                 Key: JBCACHE-1197
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1197
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Smith
>         Assigned To: Manik Surtani
>
> Need to put the spanish XML file where it belongs

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:19:07 2007
From: jira-events at lists.jboss.org (Hontv?ri J?zsef (JIRA))
Date: Fri, 12 Oct 2007 10:19:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (HIBERNATE-50) Embedded
 Objects get set to null if all its members are null
In-Reply-To: <14240556.1164709076284.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6045732.1192198747536.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/HIBERNATE-50?page=comments#action_12382160 ] 
            
Hontv?ri J?zsef commented on HIBERNATE-50:
------------------------------------------

HB-31 is closed and you cannot comment on a closed issue, even though that contains  a better description of the problem

> Embedded Objects get set to null if all its members are null
> ------------------------------------------------------------
>
>                 Key: HIBERNATE-50
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-50
>             Project: Hibernate
>          Issue Type: Bug
>         Environment: WinXP SP2, JBoss 4.0.4 GA as well as JBoss 4.0.5 GA, installation profile ejb3
>            Reporter: milan w?lke
>         Assigned To: Steve Ebersole
>
> When having an embedded object only containing members of non-simple-types (e.g. String) and fetching it with the entity manager the following happens:
> If all columns, the embedded objects values are based on, are null the embedded object itself is set to null even if a non-arg-constructor set it to a non-null value before. A valid workaround is to include a member of a simple-type (e.g. int) in the embedded object. Doing this not all the values can be set to null, which results in not setting the embedded object itself to null, too.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:04 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24268695.1192198864698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Norman Richards updated JBAS-4841:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:04 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31061054.1192198864822.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Norman Richards updated JBAS-4835:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:04 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32235807.1192198864962.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Norman Richards updated JBAS-4839:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:21:05 2007
From: jira-events at lists.jboss.org (Norman Richards (JIRA))
Date: Fri, 12 Oct 2007 10:21:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6994262.1192198865093.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Norman Richards updated JBAS-4840:
----------------------------------

    Assignee:     (was: Norman Richards)

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:25:08 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 10:25:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1186)
 ClusteredCacheLoader and
 DataGravitationInterceptor to wait for first positive result rather than
 all results
In-Reply-To: <27677021.1190136251026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2049649.1192199108484.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1186?page=all ]

Manik Surtani resolved JBCACHE-1186.
------------------------------------

    Resolution: Done

> ClusteredCacheLoader and DataGravitationInterceptor to wait for first positive result rather than all results
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1186
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1186
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 10:52:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 12 Oct 2007 10:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (SWAP-26) Add RI JSF portlet
	for AS 4.2
In-Reply-To: <24942180.1186503829752.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19132955.1192200723330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SWAP-26?page=all ]

Thomas Heute resolved SWAP-26.
------------------------------

    Resolution: Done
      Assignee: Thomas Heute  (was: Julien Viet)

> Add RI JSF portlet for AS 4.2
> -----------------------------
>
>                 Key: SWAP-26
>                 URL: http://jira.jboss.com/jira/browse/SWAP-26
>             Project: PortletSwap
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portlets
>            Reporter: Chris Laprun
>         Assigned To: Thomas Heute
>
> Add a JSF portlet example showing how to use JSF RI to create a portlet.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 11:16:04 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 12 Oct 2007 11:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <14575825.1192202164110.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil updated JBMESSAGING-381:
------------------------------------

    Attachment: patch-JBMESSAGING-381.txt

2nd version of the patch.

removed a nasty bug in the test which kept old references on ConnectionFactory (after server restart) making all over subsequent local tests fail...

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 11:16:04 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 12 Oct 2007 11:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <19196062.1192202164236.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil updated JBMESSAGING-381:
------------------------------------

    Attachment:     (was: patch-JBMESSAGING-381.txt)

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:35:06 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:35:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19162639.1192206906415.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Vlad Skarzhevskyy updated JASSIST-37:
-------------------------------------

    Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga  (was: Java 5, javassist 3.4.ga)
    Description: 
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = field.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .

BUT When javassist  loads again the generated classes field.getConstantValue(); still null!



  was:
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = fields.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .






> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:37:12 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:37:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30935870.1192207032823.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Vlad Skarzhevskyy updated JASSIST-37:
-------------------------------------

    Attachment: AChildClass-generated.class

This is the resulting class with fileds created  by:
klass.addField(field, initializer);

Original class source:
class AChildClass extends AClass {
	public static final boolean booleanField = true;
	
	public static final float floatField = (float)3.14;
	
	public static final double doubleField = 3.1415;
     ...
}

When decompiled using jad constants are visible but javassist don't see them.

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:43:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18345357.1192207383441.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Vlad Skarzhevskyy updated JASSIST-37:
-------------------------------------

    Workaround Description: 
The problem was field.setModifiers() was not called before klass.addField(field, initializer);
So initializer was not suppose to be created. Later filed was modified to static final. But this does not affect initializer
               Description: 
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = field.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .

BUT When javassist  loads again the generated classes field.getConstantValue(); still null!




  was:
I'm creating tool to verify Java API compatibility

I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.

Then target is to compare new lib version to API described in XML.

project site: http://pyx4me.com/snapshot/jour/signature.html

This is what causing the problem:

CtField field =  new CtField(CtClass.longType, "test", klass);
CtField.Initializer initializer = CtField.Initializer.constant(1);
klass.addField(field, initializer);

// Then later when
Object value = field.getConstantValue();
//value is always null and can't be used for comparison.

when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .

BUT When javassist  loads again the generated classes field.getConstantValue(); still null!




> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 12:55:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 12:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <142262.1192208104015.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JASSIST-37?page=comments#action_12382206 ] 
            
Vlad Skarzhevskyy commented on JASSIST-37:
------------------------------------------

Now the only problem I see that there are no Initializer factory for boolean and float.


> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 13:56:22 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Fri, 12 Oct 2007 13:56:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2508301.1192211782054.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12382223 ] 
            
William DeCoste commented on JBAS-4805:
---------------------------------------

I've got this fixed for Branch_4_2 and Trunk - what other branches should I be merging??

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 15:17:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Fri, 12 Oct 2007 15:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1272) DSL : String
 index out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2212092.1192216623922.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Mark Proctor updated JBRULES-1272:
----------------------------------

    Fix Version/s: 4.0.3
                   4.1.0
                   FUTURE

This fix needs to be back ported to be part of 4.0.3

>From kris:
"This does not seem to be related to the editor itself, it is the DSL
compiler which seems to be throwing an exception if you have a DSL
sentence where 2 params are only 1 character apart (doens't matter
whether it is a space or not), like "My DSL sentence with
{key1}_{key2}".  If the distance is at least 2 characters, then there
is no problem.  The problem still exists in trunk as well.

Looking at the svn history, it is probably related to the fix edson
this in DefaultDSLMappingEntry for JBRULES-1164 (commit 15069): Fixing
DSL files with embedded () on key."

> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Mark Proctor
>            Priority: Critical
>             Fix For: FUTURE, 4.0.3, 4.1.0
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 16:15:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Fri, 12 Oct 2007 16:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1107) Less noisy
 client-side failover
Message-ID: <13404207.1192220103325.JavaMail.jira@cloud.prod.atl2.jboss.com>

Less noisy client-side failover
-------------------------------

                 Key: JBMESSAGING-1107
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Ovidiu Feodorov
            Priority: Minor


When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.

If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.

Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. 

The logging information should be naturally still available, but at DEBUG level.





-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 17:24:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 12 Oct 2007 17:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1272) DSL : String
 index out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7327348.1192224243947.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Edson Tirelli reassigned JBRULES-1272:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.0.3, 4.1.0, FUTURE
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 17:51:03 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Fri, 12 Oct 2007 17:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1068) @Interceptors
 defined on
 @Service EJBs do not have @PostConstruct @PreDestroy interceptor methods
 invoked
Message-ID: <18924421.1192225863309.JavaMail.jira@cloud.prod.atl2.jboss.com>

@Interceptors defined on @Service EJBs do not have @PostConstruct @PreDestroy interceptor methods invoked
---------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1068
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1068
             Project: EJB 3.0
          Issue Type: Bug
          Components: EJB3 Extensions
    Affects Versions: AS 4.2.1.GA
            Reporter: Michael McKibben


I've defined an injection-style interceptor class that needs to be called before a @Service EJBs start() method is invoked on service startup. Using @PostConstruct doesn't not work (the container never calls my @PostConstruct annotated method). @AroundInvoke only works for methods defined on the @Local or @Remote business interface, not the @Management interface.

Shouldn't @PostConstruct and @PreDestroy be invoked on @Service EJBs? I need my interceptor to behave like the standard injection interceptors do.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:06:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 12 Oct 2007 18:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1272) DSL : String
 index out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1568216.1192226763328.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Edson Tirelli resolved JBRULES-1272.
------------------------------------

    Fix Version/s: 4.0.2_SOA_4.2
       Resolution: Done

Fixed. Thanks for reporting and providing test case.

> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.0.2_SOA_4.2, 4.0.3, 4.1.0, FUTURE
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:16:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1744) Documentation
	improvements
Message-ID: <14343449.1192227363463.JavaMail.jira@cloud.prod.atl2.jboss.com>

Documentation improvements
--------------------------

                 Key: JBPORTAL-1744
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1744
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Reference Guide
    Affects Versions: 2.6.2 Final, 2.8 Final
            Reporter: Chris Laprun
         Assigned To: Julien Viet
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:18:13 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:18:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1745) DTD
 documentation is out of date
Message-ID: <29827431.1192227493792.JavaMail.jira@cloud.prod.atl2.jboss.com>

DTD documentation is out of date
--------------------------------

                 Key: JBPORTAL-1745
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1745
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun


This applies to the actual documentation in the DTD but also to the DTD documentation in the reference guide.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:31:15 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:31:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1746) Explain concept
 of context better
Message-ID: <10930468.1192228275087.JavaMail.jira@cloud.prod.atl2.jboss.com>

Explain concept of context better
---------------------------------

                 Key: JBPORTAL-1746
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1746
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 18:35:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 18:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1746) Explain concept
 of context (for portal objects) better
In-Reply-To: <10930468.1192228275087.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26317133.1192228503190.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1746?page=all ]

Chris Laprun updated JBPORTAL-1746:
-----------------------------------

    Summary: Explain concept of context (for portal objects) better  (was: Explain concept of context better)

> Explain concept of context (for portal objects) better
> ------------------------------------------------------
>
>                 Key: JBPORTAL-1746
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1746
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:07:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1747) Merge user guide
 and reference guide
Message-ID: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>

Merge user guide and reference guide
------------------------------------

                 Key: JBPORTAL-1747
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:09:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26055254.1192230543167.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382272 ] 
            
Chris Laprun commented on JBPORTAL-1747:
----------------------------------------

There's not much point keeping them separate and user guide and quick start guide kind of overlap.

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:11:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1748) Remove
 duplicated information by linking to appropriate sections
Message-ID: <25314407.1192230663362.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove duplicated information by linking to appropriate sections
----------------------------------------------------------------

                 Key: JBPORTAL-1748
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1748
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:11:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1748) Remove
 duplicated information by linking to appropriate sections
In-Reply-To: <25314407.1192230663362.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5987920.1192230663444.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1748?page=comments#action_12382273 ] 
            
Chris Laprun commented on JBPORTAL-1748:
----------------------------------------

The same information is repeated at several spots with tiny variations. Just like in OOP, removing the duplicates would help with maintenance and improve the overall quality of the documentation.

> Remove duplicated information by linking to appropriate sections
> ----------------------------------------------------------------
>
>                 Key: JBPORTAL-1748
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1748
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:13:07 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 19:13:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1749) Consider
	creating an index
Message-ID: <13224455.1192230787616.JavaMail.jira@cloud.prod.atl2.jboss.com>

Consider creating an index
--------------------------

                 Key: JBPORTAL-1749
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1749
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 19:26:18 2007
From: jira-events at lists.jboss.org (Seth Wilcox (JIRA))
Date: Fri, 12 Oct 2007 19:26:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2681) Add real support for
 password-stacking (useFirstPass) in LDAPExtLoginModule
Message-ID: <5377477.1192231578331.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2681?page=all ]

Seth Wilcox updated JBAS-2681:
------------------------------

    Attachment: LDAPAuth.patch

Fixes unexpected behavior with LdapExtLoginModule when using the password-stacking

> Add real support for password-stacking (useFirstPass) in LDAPExtLoginModule
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-2681
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2681
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.3 SP1
>         Environment: All
>            Reporter: Didier Kreutter
>         Attachments: LDAPAuth.patch
>
>
> It would be nice, we could use the "useFirstPass" option of this login-module, like it can be done with the DatabaseServerLoginModule.
> With the construct of the LDAPExtLoginModule, it is not possible to use the LDAP-Directory to search for Roles without having to validate the Password, if this has been done by an precedent LoginModule (DB or SSO).
> I think the problem is in the fact, that the effective Role-Search is done in the overridden "validatePassword" function... witch will never been called when the "useFirstPass" option is set. Is it Possible to fulfill the roles in the getRoleSets() function?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 20:54:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 12 Oct 2007 20:54:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1192) Cannot
 gravitate data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24889437.1192236854596.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=comments#action_12382278 ] 
            
Manik Surtani commented on JBCACHE-1192:
----------------------------------------

Resolved in trunk/2.1.x.  Now to back port the fix ... 

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction, Replication
>    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6, 2.1.0.GA, 2.1.0.CR1
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 21:21:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 12 Oct 2007 21:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1274) NPE when using
 reserved word "action" as a bound variable
Message-ID: <16945042.1192238463411.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE when using reserved word "action" as a bound variable
---------------------------------------------------------

                 Key: JBRULES-1274
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1274
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Justin Wick
         Assigned To: Mark Proctor


The following code using the reserved word "action" causes an NPE:

rule
	when
		action : Object()
	then
		System.out.println("A RHS");
end

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 21:24:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 12 Oct 2007 21:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1274) NPE when using
 reserved word "action" as a bound variable, or omitting rule title
In-Reply-To: <16945042.1192238463411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31939049.1192238643270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1274?page=all ]

Justin Wick updated JBRULES-1274:
---------------------------------

        Summary: NPE when using reserved word "action" as a bound variable, or omitting rule title  (was: NPE when using reserved word "action" as a bound variable)
    Description: 
The following code using the reserved word "action" causes an NPE:

rule "Test"
	when
		action : Object()
	then
		System.out.println("A RHS");
end

or this code (omitting title):


rule 
	when
		Object()
	then
		System.out.println("A RHS");
end

  was:
The following code using the reserved word "action" causes an NPE:

rule
	when
		action : Object()
	then
		System.out.println("A RHS");
end


> NPE when using reserved word "action" as a bound variable, or omitting rule title
> ---------------------------------------------------------------------------------
>
>                 Key: JBRULES-1274
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1274
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>
> The following code using the reserved word "action" causes an NPE:
> rule "Test"
> 	when
> 		action : Object()
> 	then
> 		System.out.println("A RHS");
> end
> or this code (omitting title):
> rule 
> 	when
> 		Object()
> 	then
> 		System.out.println("A RHS");
> end

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 21:31:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Fri, 12 Oct 2007 21:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1750) Explain effect
 of different values for error handling properties
Message-ID: <25923070.1192239063167.JavaMail.jira@cloud.prod.atl2.jboss.com>

Explain effect of different values for error handling properties
----------------------------------------------------------------

                 Key: JBPORTAL-1750
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1750
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 22:50:06 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Fri, 12 Oct 2007 22:50:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (BPEL-272) allow xpath
 expression/query to create more than one occurrence of an element
In-Reply-To: <21460509.1185436907082.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22765873.1192243806337.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-272?page=all ]

Alejandro Guizar resolved BPEL-272.
-----------------------------------

    Resolution: Partially Completed

The "last plus one" predicate proposal is already implemented and works for the time being. I will mark this issue as partially completed and revisit the extension assign operation proposal in a future release.

> allow xpath expression/query to create more than one occurrence of an element
> -----------------------------------------------------------------------------
>
>                 Key: BPEL-272
>                 URL: http://jira.jboss.com/jira/browse/BPEL-272
>             Project: JBoss jBPM BPEL
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>            Priority: Critical
>             Fix For: jBPM BPEL 1.1 GA
>
>
> PROBLEM The current XPath sublanguage implementation automatically creates nodes missing from location paths during assignment. This facility has a number of conceptual limitations. One of them is the inability to append a child element to an existing element if the latter already has a child element with the same name. There is no XPath syntax to express that a new element is required!
> It is tempting to think of a numeric XPath predicate as an array index, leading to the next snippet:
> <copy>
>  <from><literal>haha</literal></from>
>  <to variable='laughter' xmlns:ex='http://jbpm.org/bpel/examples'>
>   <query>ex:laugh[last() + 1]</query>
>  </to>
> </copy>
> However, such an interpretation of a predicate is wrong. Consider the following extract from XPath 1.0 specification on predicates:
> "A PredicateExpr is evaluated by evaluating the Expr and converting the result to a boolean. If the result is a number, the result will be converted to true if the number is equal to the context position and will be converted to false otherwise."
> The description of the last() function reads:
> "The last function returns a number equal to the context size from the expression evaluation context."
> Noticed the problem? The context position is never greater than the context size. Therefore the predicate [last() + 1] does not represent the position "one past the context size" but the boolean value false. Unfortunately, no other predicate seems appropriate. 
> PROPOSAL Introduce a minor deviation from the XPath 1.0 specification. Interpret the result of a numeric predicate that equals the context size plus one as a  request to create a new occurrence of the node.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 22:55:18 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Fri, 12 Oct 2007 22:55:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (BPEL-218) introduce a central
 service catalog
In-Reply-To: <17113795.1166408025580.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16395028.1192244118659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-218?page=all ]

Alejandro Guizar resolved BPEL-218.
-----------------------------------

    Resolution: Done

Completed the central service catalog, along with a registration servlet for programmatic registration and a console page that allows manual registration.

> introduce a central service catalog
> -----------------------------------
>
>                 Key: BPEL-218
>                 URL: http://jira.jboss.com/jira/browse/BPEL-218
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> In scenarios where full deployment information is missing (e.g. deployment from the eclipse designer) there is no source of partner service descriptions. An earlier proposal mentioned the imported WSDL documents. However, it is not a good solution as most BPEL processes are defined "in the abstract", i.e. without port-specific information.
> A better alternative is to maintain a central service catalog available to all processes. Registration in the central catalog can be either programmatic (ant task) or manual (web console). There are two registration modes: containment and reference. In the first mode, the WSDL document is stored in the jBPM database. In the second, only the document URL is remembered; the actual content is retrieved on demand.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 12 23:22:03 2007
From: jira-events at lists.jboss.org (Vlad Skarzhevskyy (JIRA))
Date: Fri, 12 Oct 2007 23:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5156981.1192245723305.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JASSIST-37?page=comments#action_12382286 ] 
            
Vlad Skarzhevskyy commented on JASSIST-37:
------------------------------------------

Also there are no Initializer for byte 

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 08:24:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 13 Oct 2007 08:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1700028.1192278243790.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=all ]

Tim Fox updated JBMESSAGING-1101:
---------------------------------

          Component/s:     (was: Messaging Core)
    Affects Version/s:     (was: 1.4.0.GA)

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 08:26:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 13 Oct 2007 08:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14042151.1192278363345.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=comments#action_12382294 ] 
            
Tim Fox commented on JBMESSAGING-1101:
--------------------------------------

This is replicated in QueueTest::testBytesMessagePersistence

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 08:56:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sat, 13 Oct 2007 08:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1275) Multiple moves
 win a step (moves without direct tabu property relations)
Message-ID: <33061919.1192280163254.JavaMail.jira@cloud.prod.atl2.jboss.com>

Multiple moves win a step (moves without direct tabu property relations)
------------------------------------------------------------------------

                 Key: JBRULES-1275
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1275
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Solver
            Reporter: Geoffrey De Smet
         Assigned To: Geoffrey De Smet
            Priority: Optional


Currently only one move can win a step.
If moves are evaluated not on their score, but on "the difference in score", it probably won't be a bad idea to take a low number of improving moves that have not tabu property's in common and do a step of all of them instead of just one, especially in the beginning.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 16:21:20 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 16:21:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1108) Shutting down
 simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
Message-ID: <7844397.1192306880579.JavaMail.jira@cloud.prod.atl2.jboss.com>

Shutting down simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
----------------------------------------------------------------------------------

                 Key: JBMESSAGING-1108
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1108
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Ovidiu Feodorov
            Priority: Minor


This is just an initial finding. I don't have more details at this point. I will investigate if necessary.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 17:02:13 2007
From: jira-events at lists.jboss.org (Cypher Punk (JIRA))
Date: Sat, 13 Oct 2007 17:02:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-29) Unable to read
 in jarfile if
 application installed to location with spaces in directory name
In-Reply-To: <3806585.1184593564214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19621656.1192309333612.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-29?page=comments#action_12382309 ] 
            
Cypher Punk commented on JBCOMMON-29:
-------------------------------------

Dimitris,

It seems that your code change (JBCOMMON-19, Deal with spaces in local file URIs) introduced this error. See the test below.



import junit.framework.TestCase;

import java.io.File;

import java.net.URL;


public class UrlTest extends TestCase {
    public void test1() throws Exception {
        URL url = new URL("file", "", "/C:/Documents%20and%20Settings/Administrator");

        File file = new File(url.toURI());
        assertTrue(file.exists());
    }

    public void test2() throws Exception {
        URL url = new URL("file", "", "/C:/Documents%20and%20Settings/Administrator");

        File file = new File(url.getPath());
        assertTrue(file.exists());
    }
}


Please add tests!

> Unable to read in jarfile if application installed to location with spaces in directory name
> --------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-29
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-29
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core
>    Affects Versions: 2.0.4.GA
>         Environment: windows XP sun-jre, happens also in core-2.2.0.GA
>            Reporter: klaasjan elzinga
>         Assigned To: Dimitris Andreadis
>
> I get an exception if the application is installed to a directory containing a space. I I rename the directory to a name without a space, the application runs perfectly.
> Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [loadtool/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/TIS%20FIIBLoadTool-3.0.2.SN
> APSHOT/TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar
> Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/TIS%20FIIBLoadTool-3.0.2.SNAPSHOT/TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar
>         at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:635)
>         at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350)
>         at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126)
>         at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:218)
>         at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:251)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1201)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1171)
>         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:425)
>         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
>         at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
>         at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
> ...
>         at loadtool.Main.main(Main.java:40)
> Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: C:\TIS%20FIIBLoadTool-3.0.2.SNAPSHOT\TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar (The system cannot find th
> e path specified)
>         at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:74)
>         at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48)
>         at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:57)
>         at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:626)
>         ... 29 more
> Caused by: java.io.FileNotFoundException: C:\TIS%20FIIBLoadTool-3.0.2.SNAPSHOT\TISFIIBLoadTool-3.0.2.SNAPSHOT-jar-with-dependencies.jar (The system cannot find the path specified)
>         at java.util.zip.ZipFile.open(Native Method)
>         at java.util.zip.ZipFile.<init>(ZipFile.java:114)
>         at java.util.jar.JarFile.<init>(JarFile.java:133)
>         at java.util.jar.JarFile.<init>(JarFile.java:97)
>         at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:69)
>         ... 32 more

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 19:37:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 19:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1109) Client-side
 race condition while closing connection
Message-ID: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>

Client-side race condition while closing connection
---------------------------------------------------

                 Key: JBMESSAGING-1109
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Minor


I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())

@Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
org.jboss.jms.exception.MessagingJMSException: Failed to invoke
        at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
        at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
        at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
        at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
        at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
        at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
        at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
        at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
        at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
        at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.remoting.Client.invoke(Client.java:536)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
        ... 17 more


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 19:37:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 19:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3910103.1192318623503.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1109:
-----------------------------------------

    Summary: Client-side race condition while receiving concurrently  (was: Client-side race condition while closing connection)

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 19:47:08 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Sat, 13 Oct 2007 19:47:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (BPEL-280) redeploy web modules
 upon server restart
Message-ID: <6144861.1192319228417.JavaMail.jira@cloud.prod.atl2.jboss.com>

redeploy web modules upon server restart
----------------------------------------

                 Key: BPEL-280
                 URL: http://jira.jboss.com/jira/browse/BPEL-280
             Project: JBoss jBPM BPEL
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Engine
            Reporter: Alejandro Guizar
         Assigned To: Alejandro Guizar
             Fix For: jBPM BPEL 1.1 GA


PROBLEM With the automated deployment procedure in place, new processes and the associated web services can be deployed on the fly. There is an issue, however. Upon server restart, web modules deployed through the JBoss AS main deployer dissapear. Three approaches come quickly to mind to address this situation:

PROPOSAL 1. Place the modules directly in the deployment directory of the application server

* Pros. The engine needs not perform any task at startup. The server is responsible for reading and deploying the modules.

* Cons. Loss of portability. Servers other than JBoss AS use different deployment directories. Some may not even support the concept of a deployment directory.
Furthermore, what if the modules are deleted? Because the responsibility is trasferred to the server, there can be a disconnection between the process definitions in the jBPM database and the deployed web services.

PROPOSAL 2. Save the prefabricated deployment artifacts in the process definition. Rebuild the module at startup.

* Pros. No external location is required to place the modules. All information required to rebuild them is saved along the process definition. The disconnection between the process definitions and the deployed web services dissapear.
* Cons. The engine has to process each process definition at startup to rebuild the modules. This could result in a significant startup time.
Plus, database space consumption might become excessive.

PROPOSAL 3. Save the prefabricated module in a content repository. Leverage the repository facilities provided by jBPM.

* Pros. Same as 2. Plus, no large database storage requirements.
* Cons. The engine still has to process each process definition at startup. Plus, an external content repository introduces new dependencies and installation complexities to the product.

Among these proposals, #1 looks good because it neither imposes large database storage requirements nor a significant startup processing time. It is also the easiest to implement, at the expense of brittleness due to the reliance on the app server.

Any comments or new proposals welcome.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 21:22:08 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 21:22:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
Message-ID: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>

Client incorrectly initiates client-side fail over on high concurrency
----------------------------------------------------------------------

                 Key: JBMESSAGING-1110
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Facade
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox


Dump of a faulty test run:

ofeodorov at yamato$ mess -sessions 50 receive all
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
Consumer21 starting to consume ...
Consumer43 starting to consume ...
Consumer23 starting to consume ...
Consumer44 starting to consume ...
Consumer11 starting to consume ...
Consumer29 starting to consume ...
Consumer26 starting to consume ...
Consumer39 starting to consume ...
Consumer40 starting to consume ...
Consumer01 starting to consume ...
Consumer17 starting to consume ...
Consumer14 starting to consume ...
Consumer04 starting to consume ...
Consumer16 starting to consume ...
Consumer49 starting to consume ...
Consumer42 starting to consume ...
Consumer41 starting to consume ...
Consumer34 starting to consume ...
Consumer18 starting to consume ...
Consumer46 starting to consume ...
Consumer20 starting to consume ...
Consumer02 starting to consume ...
Consumer06 starting to consume ...
Consumer32 starting to consume ...
Consumer07 starting to consume ...
Consumer19 starting to consume ...
Consumer35 starting to consume ...
Consumer48 starting to consume ...
Consumer24 starting to consume ...
Consumer30 starting to consume ...
Consumer08 starting to consume ...
Consumer12 starting to consume ...
Consumer36 starting to consume ...
Consumer09 starting to consume ...
Consumer47 starting to consume ...
Consumer00 starting to consume ...
Consumer13 starting to consume ...
Consumer31 starting to consume ...
Consumer27 starting to consume ...
Consumer33 starting to consume ...
Consumer10 starting to consume ...
Consumer05 starting to consume ...
Consumer45 starting to consume ...
Consumer15 starting to consume ...
Consumer03 starting to consume ...
Consumer37 starting to consume ...
Consumer28 starting to consume ...
Consumer38 starting to consume ...
Consumer22 starting to consume ...
Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
@Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network



closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...




@Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection



-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 21:22:08 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 21:22:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14503602.1192324928699.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382312 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1110:
----------------------------------------------

Server-side logs:

2007-10-13 18:20:01,630 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[465863, bisocket://10.152.1.38:1428632584] control socket replaced by: Socket[addr=/10.152.1.38,port=37373,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[6793a317, bisocket://10.152.1.85:310396915] replacing control socket: Socket[addr=/10.152.1.85,port=50855,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[6793a317, bisocket://10.152.1.85:310396915] control socket replaced by: Socket[addr=/10.152.1.85,port=50859,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[465863, bisocket://10.152.1.38:1428632584] replacing control socket: Socket[addr=/10.152.1.38,port=37373,localport=3309]
2007-10-13 18:20:35,558 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[465863, bisocket://10.152.1.38:1428632584] control socket replaced by: Socket[addr=/10.152.1.38,port=37376,localport=3309]


> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 22:12:03 2007
From: jira-events at lists.jboss.org (David Navara (JIRA))
Date: Sat, 13 Oct 2007 22:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4361)
 java.util.logging.FileHandler.formatter cannot be changed to
 java.util.logging.SimpleFormatter
In-Reply-To: <24133361.1177358310492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28870258.1192327923582.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4361?page=comments#action_12382313 ] 
            
David Navara commented on JBAS-4361:
------------------------------------

I had a similar problem and to my suprise I realized there is a space char ' ' after the class name java.util.logging.SimpleFormatter which causes the problem. Try to remove the whitespace at the end of the line.

> java.util.logging.FileHandler.formatter cannot be changed to java.util.logging.SimpleFormatter
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4361
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4361
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.0.CR2
>         Environment: JDK is 1.5.0_11-b03
>            Reporter: Wolfgang Knauf
>         Assigned To: Scott M Stark
>            Priority: Minor
>
> I tried to create a plain text log output with this logging.properties file:
> handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler
> .level= INFO
> java.util.logging.FileHandler.pattern = c:/temp/logfile.log 
> java.util.logging.FileHandler.level = INFO
> java.util.logging.FileHandler.limit = 50000
> java.util.logging.FileHandler.count = 1
> java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter 
> java.util.logging.ConsoleHandler.level = INFO
> java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
> I startup the server with this commandline:
> run.bat -c default -Djava.util.logging.config.file=c:/temp/logging.properties
> The log file is placed in c:\temp\logfile.log and contains my output, but it is in XML, not in Simple format. Console output is in SimpleFormat as expected.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 22:18:03 2007
From: jira-events at lists.jboss.org (Len DiMaggio (JIRA))
Date: Sat, 13 Oct 2007 22:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1111) JBM 1.4.0 in
 ESB from svn
 revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore]
 *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE
 INSTALLATION DEFAULT
Message-ID: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1111
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Security
    Affects Versions: 1.4.0.GA
         Environment: RHEL5
Java 1.5

JBESB - At revision 15800

JBM 1.4.0.GA
            Reporter: Len DiMaggio
         Assigned To: Tim Fox
            Priority: Minor


This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java

14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **

I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172



-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 13 22:56:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sat, 13 Oct 2007 22:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29498715.1192330563492.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382315 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1110:
----------------------------------------------

Also, messages seem to be vanished from the database. 

I started with 50,000 10K persistent text messages stored in the queue "ovidiu" on the node with the ID 39 (looked up a clustered but not load-balanced connection factory from that node and got confirmation by calling getServerID()). The queue was deployed as "clustered"

State of the database after killing the client (which became unresponsive):

mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             49288 | 
+-------------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 35528; (this is MIN(MESSAGE_ID))
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      35528 |           NULL | C     | 39070061203453943 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 84912; (this is MAX(MESSAGE_ID))
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      84912 |           NULL | C     | 39070075545073791 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_POSTOFFICE; (irrelevant destination names edited for privacy reasons)
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | *** | queue.***              | NULL     |         27 | Y         | N         | 
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         29 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         30 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         31 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         32 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         36 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         34 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         35 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         33 | Y         | N         | 
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         23 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         25 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         26 | Y         | N         | 
| JMS post office |      38 | *** | queue.*** | NULL     |         24 | Y         | N         | 
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |         12 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |         15 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |         13 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |          3 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |          5 | Y         | N         | 
| JMS post office |      39 | *** | queue.*** | NULL     |          4 | Y         | N         | 
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
26 rows in set (0.00 sec)

Please note that the channel corresponding to the "ovidiu" queue on node 39 vanished, and it seems there's no "ovidiu" queue on 39.

The JMX console on node 39 became unresponsive as well (couldn't check whether the queue is visible via the JMX interface)
Any attempt to connect to node 39 (even just to create a Connection and then close it) was unsuccessful .

This is the client-side log on a connection attempt:

ofeodorov at yamato$ mess ping
@Timer-1 19:45:51,445 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51137],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:46:31,458 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51142],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:46:56,467 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51143],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:47:31,479 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51146],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:48:21,497 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51147],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:48:46,506 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51148],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:49:26,521 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51150],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:50:36,548 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51154],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:51:31,567 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51159],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:52:21,586 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51160],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:53:06,603 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51162],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:53:46,619 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51164],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection
@Timer-1 19:54:26,633 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 74b957ea: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=51177],5,main] (a4812d-p364ba-f7qyex29-1-f7qyfgeu-5: requesting new control connection






> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:11:12 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:11:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1112) Highly
 concurrent clients
 lock a JBM server node and apparently cause persistent messages to
 "dissapear"
Message-ID: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>

Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
--------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1112
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Critical


The log of the experiment. 

* Empty database

mysql> CONNECT ovidiu
Connection id:    5288
Current database: ovidiu

mysql> SHOW TABLES;
Empty set (0.00 sec)

mysql> 

* Both cluster nodes down.

* Start node 39 

2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms

mysql> SELECT * FROM JBM_MSG_REF;
Empty set (0.00 sec)

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
...
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
17 rows in set (0.00 sec)


* Start node 38

2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms

mysql> SELECT * FROM JBM_MSG_REF;
Empty set (0.00 sec)

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
...
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
34 rows in set (0.00 sec)

* Make sure I look up a clustered but non load-balanced connection factory from node 39

ofeodorov at yamato$ mess ping
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
node 39 alive
closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...


* Sending 50,000 10K persistent text messages to "ovidiu" on node 39.

ofeodorov at yamato$ mess -stat send -size 10240 50000
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
.....
sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far

50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec

closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...


* Database content after send:

mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             50000 | 
+-------------------+

mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MIN(MESSAGE_ID) |
+-----------------+
|               0 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MAX(MESSAGE_ID) |
+-----------------+
|           54192 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
...
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
...
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
...
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
...
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
34 rows in set (0.00 sec)

* Receiving on 50 concurrent threads, from node 39

ofeodorov at yamato$ mess -stat -sessions 50 receive all
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
Consumer43 starting to consume, 1 active consumers ...
Consumer06 starting to consume, 2 active consumers ...
Consumer38 starting to consume, 3 active consumers ...
Consumer13 starting to consume, 4 active consumers ...
Consumer37 starting to consume, 5 active consumers ...
Consumer10 starting to consume, 6 active consumers ...
Consumer11 starting to consume, 7 active consumers ...
Consumer25 starting to consume, 8 active consumers ...
Consumer12 starting to consume, 9 active consumers ...
Consumer04 starting to consume, 10 active consumers ...
Consumer48 starting to consume, 11 active consumers ...
Consumer32 starting to consume, 12 active consumers ...
Consumer40 starting to consume, 13 active consumers ...
Consumer39 starting to consume, 14 active consumers ...
Consumer05 starting to consume, 15 active consumers ...
Consumer09 starting to consume, 16 active consumers ...
Consumer03 starting to consume, 17 active consumers ...
Consumer41 starting to consume, 18 active consumers ...
Consumer19 starting to consume, 19 active consumers ...
Consumer07 starting to consume, 20 active consumers ...
Consumer22 starting to consume, 21 active consumers ...
Consumer36 starting to consume, 22 active consumers ...
Consumer01 starting to consume, 23 active consumers ...
Consumer46 starting to consume, 24 active consumers ...
Consumer16 starting to consume, 25 active consumers ...
Consumer18 starting to consume, 26 active consumers ...
Consumer23 starting to consume, 28 active consumers ...
Consumer33 starting to consume, 27 active consumers ...
Consumer02 starting to consume, 29 active consumers ...
Consumer00 starting to consume, 30 active consumers ...
Consumer17 starting to consume, 31 active consumers ...
Consumer15 starting to consume, 32 active consumers ...
Consumer47 starting to consume, 33 active consumers ...
Consumer31 starting to consume, 34 active consumers ...
Consumer27 starting to consume, 35 active consumers ...
Consumer49 starting to consume, 36 active consumers ...
Consumer44 starting to consume, 37 active consumers ...
Consumer26 starting to consume, 38 active consumers ...
Consumer24 starting to consume, 39 active consumers ...
Consumer42 starting to consume, 40 active consumers ...
Consumer28 starting to consume, 41 active consumers ...
Consumer20 starting to consume, 42 active consumers ...
Consumer29 starting to consume, 43 active consumers ...
Consumer35 starting to consume, 44 active consumers ...
Consumer45 starting to consume, 45 active consumers ...
Consumer30 starting to consume, 47 active consumers ...
Consumer08 starting to consume, 46 active consumers ...
received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far

Could not just close() connection, I had to kill the java process

SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             34091 | 
+-------------------+

50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)

* Tried to create a new connection to the server, the JNDI invocation hung.

* Killed both servers, restarted.

Database situation:

mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
+-------------------+
| COUNT(MESSAGE_ID) |
+-------------------+
|             34091 | 
+-------------------+

mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MIN(MESSAGE_ID) |
+-----------------+
|            8957 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
+-----------------+
| MAX(MESSAGE_ID) |
+-----------------+
|           54192 | 
+-----------------+

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
| CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
|          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
+------------+------------+----------------+-------+-------------------+----------+----------------+----------------+

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
| JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
...
| JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
...
| JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
...
| JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
| JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
...
| JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
...
| JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
34 rows in set (0.00 sec)


* Pinged 39

ofeodorov at yamato$ mess ping
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]
node 39 alive
closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

* Browsed the queue (I don't expect any, since channel 0 does not exist anymore)

ofeodorov at yamato$ mess browse
ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
Destination: JBossQueue[ovidiu]

NO messages in queue

closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:13:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29224280.1192335183381.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1110:
-----------------------------------------

    Priority: Critical  (was: Major)

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:41:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31557765.1192336863436.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382318 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries generated during the above experiment:

2007-10-13 21:38:41,806 WARN  [org.jboss.messaging.core.impl.JDBCSupport] SQLException caught, SQLState 40001 code:1213- assuming deadlock detected, try:1
com.mysql.jdbc.exceptions.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:941)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2934)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1616)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1708)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:3255)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1293)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1566)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1480)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1465)
        at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251)
        at org.jboss.messaging.core.impl.JDBCPersistenceManager$1RemoveReferenceRunner.doTransaction(JDBCPersistenceManager.java:1279)
        at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner.execute(JDBCSupport.java:385)
        at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner.executeWithRetry(JDBCSupport.java:407)
        at org.jboss.messaging.core.impl.JDBCPersistenceManager.removeReference(JDBCPersistenceManager.java:1310)
        at org.jboss.messaging.core.impl.ChannelSupport.acknowledgeInternal(ChannelSupport.java:694)
        at org.jboss.messaging.core.impl.ChannelSupport.acknowledge(ChannelSupport.java:153)
        at org.jboss.messaging.core.impl.SimpleDelivery.acknowledge(SimpleDelivery.java:99)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeDeliveryInternal(ServerSessionEndpoint.java:1767)
        at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeDelivery(ServerSessionEndpoint.java:355)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$acknowledgeDelivery$aop(SessionAdvised.java:113)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised$acknowledgeDelivery_N8255607227065177522.invokeNext(SessionAdvised$acknowledgeDelivery_N8255607227065177522.java)
        at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised$acknowledgeDelivery_N8255607227065177522.invokeNext(SessionAdvised$acknowledgeDelivery_N8255607227065177522.java)
        at org.jboss.jms.server.endpoint.advised.SessionAdvised.acknowledgeDelivery(SessionAdvised.java)
        at org.jboss.jms.wireformat.SessionAcknowledgeDeliveryRequest.serverInvoke(SessionAcknowledgeDeliveryRequest.java:78)
        at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
        at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
2007-10-13 21:38:41,811 WARN  [org.jboss.messaging.core.impl.JDBCSupport] Trying again after a pause
2007-10-13 21:38:42,831 WARN  [org.jboss.messaging.core.impl.JDBCSupport] Update worked after retry
2007-10-13 21:38:52,316 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:52,474 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:52,660 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:53,171 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:53,325 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:38:53,488 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive
2007-10-13 21:39:05,279 WARN  [org.jboss.jms.server.endpoint.ServerSessionEndpoint] Timed out waiting for response to arrive



> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:47:15 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:47:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9252225.1192337235815.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382319 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries generated during the above experiment: 

2007-10-13 21:43:38,274 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session d3-4ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,274 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session j3-cezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,275 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session g3-8ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,367 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session c3-2ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,442 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session r3-lezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,443 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session u3-pezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,443 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session b3-wdzf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,443 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session d3-4ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,444 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session j3-cezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,444 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session g3-8ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:43:38,444 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session c3-2ezf2r7f-1-w4qq1r7f-yi60n8-31184a


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:51:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22231649.1192337463751.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382320 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries seen during the above experiment:

2007-10-13 21:44:39,657 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session r3-lezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:44:39,889 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session u3-pezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:44:54,192 WARN  [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 460ad983: detected failure on control connection 
Thread[control: Socket[addr=/10.152.1.38,port=3028,localport=58599],5,jboss] (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j: requesting new control connection
2007-10-13 21:44:54,194 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] getting secondary locator2007-10-13 21:44:54,196 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] secondary locator: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:44:54,196 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] creating control connection: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:44:54,197 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] created control connection (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j): Socket[addr=/10.152.1.38,port=30
28,localport=58663]
2007-10-13 21:44:54,215 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51615,localport=3995]
2007-10-13 21:44:54,215 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51663,localport=3995]
2007-10-13 21:44:54,232 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38149,localport=3995]
2007-10-13 21:44:54,233 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38190,localport=3995]
2007-10-13 21:45:03,889 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session b3-wdzf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:45:03,910 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session d3-4ezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:45:03,916 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session j3-cezf2r7f-1-w4qq1r7f-yi60n8-31184a
2007-10-13 21:45:03,922 WARN  [org.jboss.messaging.core.impl.postoffice.MessagingPostOffice] Cannot find session g3-8ezf2r7f-1-w4qq1r7f-yi60n8-31184a


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 00:55:06 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32536852.1192337706109.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382321 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Various server log entries seen during the above experiment:

2007-10-13 21:47:43,373 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
2007-10-13 21:48:06,642 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] replacing control socket: Socket[addr=/10.152.1.85,port=51617,localport=3995]
2007-10-13 21:48:06,642 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] control socket replaced by: Socket[addr=/10.152.1.85,port=51668,localport=3995]
2007-10-13 21:48:06,643 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38190,localport=3995]
2007-10-13 21:48:06,643 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38197,localport=3995]
2007-10-13 21:48:06,644 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51663,localport=3995]
2007-10-13 21:48:06,644 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51669,localport=3995]2007-10-13 21:48:37,005 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38197,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38198,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51669,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51670,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] replacing control socket: Socket[addr=/10.152.1.85,port=51668,localport=3995]2007-10-13 21:48:37,006 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] control socket replaced by: Socket[addr=/10.152.1.85,port=51671,localport=3995]
2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again2007-10-13 21:49:23,067 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

       



From jira-events at lists.jboss.org  Sun Oct 14 00:55:06 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 00:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24723417.1192337706577.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382322 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

...............

2007-10-13 21:53:57,616 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:612)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
2007-10-13 21:53:57,614 WARN  [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 460ad983: detected failure on control connection Thread[control: Socket[addr=/10.152.1.38,port=3028,localport=58680],5,jboss] (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j: requesting new control connection
2007-10-13 21:53:57,617 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] getting secondary locator
2007-10-13 21:53:57,628 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] secondary locator: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:53:57,628 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] creating control connection: InvokerLocator [null://10.152.1.38:3028/null]
2007-10-13 21:54:12,195 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] replacing control socket: Socket[addr=/10.152.1.38,port=38211,localport=3995]
2007-10-13 21:54:12,195 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[7692ed85, bisocket://10.152.1.38:472639509] control socket replaced by: Socket[addr=/10.152.1.38,port=38213,localport=3995]
2007-10-13 21:54:12,195 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] created control connection (a48113-8n06iy-f7r1qq4w-1-f7r1vijz-j): Socket[addr=/10.152.1.38,port=3028,localport=58687]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] replacing control socket: Socket[addr=/10.152.1.85,port=51685,localport=3995]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[60a10faf, bisocket://10.152.1.85:1612831607] control socket replaced by: Socket[addr=/10.152.1.85,port=51699,localport=3995]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] replacing control socket: Socket[addr=/10.152.1.85,port=51687,localport=3995]
2007-10-13 21:54:31,957 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[73fbcfb7, bisocket://10.152.1.85:1613244790] control socket replaced by: Socket[addr=/10.152.1.85,port=51700,localport=3995]


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 04:11:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Sun, 14 Oct 2007 04:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1751)
 portlet-instances.xml
 security-constraints are not verified using request.isUserInRole()
Message-ID: <28407251.1192349463289.JavaMail.jira@cloud.prod.atl2.jboss.com>

portlet-instances.xml security-constraints are not verified using request.isUserInRole()
----------------------------------------------------------------------------------------

                 Key: JBPORTAL-1751
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Security
    Affects Versions: 2.6.2 Final, 2.6.1 Final
         Environment: Java JDK 1.4.2
            Reporter: Johannes Fiala
         Assigned To: Julien Viet


The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole().

Fact 1:
If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule))
<portlet>
...
<security-role-ref>
			<role-name>PortletUser</role-name>
			<role-link>User</role-link>
		</security-role-ref>
</portlet>

and then use it in the portlet-instances.xml:
<instance>
...
<security-constraint>
				<policy-permission>
					<role-name>PortletUser</role-name>
					<action-name>view</action-name>
				</policy-permission>
			</security-constraint>
</instance>
</deployment>

the portlet instance will not show up.
If you use the User-role instead, it works correctly.

However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected.

Fact 2:
Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal.
I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule.
If I check it using request.isUserInRole("User"), it shows up 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

        


From jira-events at lists.jboss.org  Sun Oct 14 04:37:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Sun, 14 Oct 2007 04:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1751)
 portlet-instances.xml
 security-constraints are not verified using request.isUserInRole()
In-Reply-To: <28407251.1192349463289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30786854.1192351023548.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1751?page=all ]

Johannes Fiala updated JBPORTAL-1751:
-------------------------------------

    Attachment: fwd-jbportal-securitycheck-1.0.0.0.war


Installation:
Deploy this WAR-file to the JBOSS_HOME/server/default/deploy directory.
(tested with JBP 2.6.1 and 2.6.2)

Two pages should be showing up:
- SimplePortletPage
- SecurePortletPage

How to verify the issue:
1. Login using the user "user".
The SimplePortletPage shows that the role "PortletUser" is present.
However, the user is not allowed to access SecurePortletPage, although the security-constraints there allow the role "PortletUser" to view it (NOT working as expected / specified in the Java Portlet Specification, page 76).

2. Login using the user "admin"
The admin-user is allowed to see the SecurePortletPage because he has the role "Admin" assigned (this is working as expected).

> portlet-instances.xml security-constraints are not verified using request.isUserInRole()
> ----------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1751
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final, 2.6.2 Final
>         Environment: Java JDK 1.4.2
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>         Attachments: fwd-jbportal-securitycheck-1.0.0.0.war
>
>
> The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole().
> Fact 1:
> If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule))
> <portlet>
> ...
> <security-role-ref>
> 			<role-name>PortletUser</role-name>
> 			<role-link>User</role-link>
> 		</security-role-ref>
> </portlet>
> and then use it in the portlet-instances.xml:
> <instance>
> ...
> <security-constraint>
> 				<policy-permission>
> 					<role-name>PortletUser</role-name>
> 					<action-name>view</action-name>
> 				</policy-permission>
> 			</security-constraint>
> </instance>
> </deployment>
> the portlet instance will not show up.
> If you use the User-role instead, it works correctly.
> However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected.
> Fact 2:
> Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal.
> I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule.
> If I check it using request.isUserInRole("User"), it shows up 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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:49:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1111) JBM 1.4.0
 in ESB from svn revision 15800 writes WARNING to server log: WARN
 [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE
 CHANGED FROM THE INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27182619.1192358943362.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=comments#action_12382327 ] 
            
Tim Fox commented on JBMESSAGING-1111:
--------------------------------------

Why is this a bug?

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1716268.1192359363753.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=comments#action_12382328 ] 
            
Tim Fox commented on JBMESSAGING-1109:
--------------------------------------

Can you post a test program that replicates the issue?

I think you must be doing something else other than just receiving (closing?)

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1111) JBM 1.4.0 in
 ESB from svn
 revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore]
 *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE
 INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1980580.1192359364598.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=all ]

Tim Fox updated JBMESSAGING-1111:
---------------------------------

    Fix Version/s: Unscheduled

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2534892.1192359364856.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Tim Fox updated JBMESSAGING-1109:
---------------------------------

    Fix Version/s: Unscheduled

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Highly
 concurrent clients
 lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4899216.1192359365270.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox updated JBMESSAGING-1112:
---------------------------------

    Fix Version/s: Unscheduled

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10653588.1192359365680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Tim Fox updated JBMESSAGING-1110:
---------------------------------

    Fix Version/s: Unscheduled

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1107) Less noisy
 client-side failover
In-Reply-To: <13404207.1192220103325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10481183.1192359365804.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1107?page=all ]

Tim Fox updated JBMESSAGING-1107:
---------------------------------

    Fix Version/s: Unscheduled

> Less noisy client-side failover
> -------------------------------
>
>                 Key: JBMESSAGING-1107
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.
> If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.
> Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. 
> The logging information should be naturally still available, but at DEBUG level.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:56:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:56:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1108) Shutting down
 simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
In-Reply-To: <7844397.1192306880579.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20558314.1192359365962.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1108?page=all ]

Tim Fox updated JBMESSAGING-1108:
---------------------------------

    Fix Version/s: Unscheduled

> Shutting down simultaneously both nodes of a 2 nodes JBM cluster hangs the cluster
> ----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1108
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1108
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is just an initial finding. I don't have more details at this point. I will investigate if necessary.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 06:58:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 06:58:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21835040.1192359494119.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382329 ] 
            
Tim Fox commented on JBMESSAGING-1110:
--------------------------------------

Please post a test program that replicates the issue.

BTW 50 consumers on a single queue doesn't seem a very likely use case - why would you want to do that? Probably not going to get very good throughput with that many.

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 07:05:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 07:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5769091.1192359903527.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382330 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

Would need to see your source code, to understand why you think messages are "disappearing"?

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:19:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1274) NPE when using
 reserved word "action" as a bound variable, or omitting rule title
In-Reply-To: <16945042.1192238463411.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2512181.1192364343543.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1274?page=all ]

Edson Tirelli reassigned JBRULES-1274:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> NPE when using reserved word "action" as a bound variable, or omitting rule title
> ---------------------------------------------------------------------------------
>
>                 Key: JBRULES-1274
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1274
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Justin Wick
>         Assigned To: Edson Tirelli
>
> The following code using the reserved word "action" causes an NPE:
> rule "Test"
> 	when
> 		action : Object()
> 	then
> 		System.out.println("A RHS");
> end
> or this code (omitting title):
> rule 
> 	when
> 		Object()
> 	then
> 		System.out.println("A RHS");
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:21:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1262) DSL Parser "eval"
In-Reply-To: <29036708.1191916263283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20657665.1192364463478.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1262?page=all ]

Edson Tirelli reassigned JBRULES-1262:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> DSL Parser "eval"
> -----------------
>
>                 Key: JBRULES-1262
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1262
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: M H
>         Assigned To: Edson Tirelli
>
> [when]of type Item=Item()
> [when]- Title equals "{value}"=eval(title.isEqual("{value}")
> [when]- Event equals "{value}"=eval(id.isEqual("{value}")
> [then]Log : "{message}"=System.out.println("{message}");
> the dslr File:
> expander Test.dsl
> rule "Your First Rule"
>      when
>             $p : of type Item
>                - Title equals "test"
>                - Event equals "test"
>      then
>            #actions
> end
> resolves to (could be seen in the drl viewer)
> rule "Your First Rule"
>        when
>                $p :Item( eval(title.isEqual("test", eval(id.isEqual("test") ) )
>        then
>                #actions
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:23:05 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:23:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27424885.1192364585693.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=comments#action_12382335 ] 
            
Edson Tirelli commented on JBRULES-1247:
----------------------------------------

We need more info. Can you please provide a rule that causes this error for you?

Thanks,
Edson

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:23:06 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Sun, 14 Oct 2007 08:23:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1243) Pattern matching
 does not allow spaces
In-Reply-To: <22164328.1191333554304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7322218.1192364586021.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1243?page=all ]

Edson Tirelli reassigned JBRULES-1243:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> Pattern matching does not allow spaces
> --------------------------------------
>
>                 Key: JBRULES-1243
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1243
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Edson Tirelli
>
> When I have a rule condition like this:
>   Something( test matches "abc def")
> I'll get an exception during compilation saying "RuleError: Unable to determine the used declarations".
> When I remove the space and replace it with \s it does compile well.
> Spaces should be possible in regular expressions.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:23:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 08:23:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18366406.1192364586368.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382336 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

BTW if you're using an ack mode of auto_ack  then this would be expected behaviour, since messages are acked before the call to receive() has returned.

auto_ack = "at most once" delivery when used with synchronous receive()

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 14 Oct 2007 08:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11879.1192365303409.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor updated JBRULES-1264:
----------------------------------

    Fix Version/s: 4.0.2_SOA_4.2
                   4.0.3
                   4.1.0

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2
>
>         Attachments: JBRULES-1264.patch
>
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:35:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sun, 14 Oct 2007 08:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1264) NPE at
 BaseObjectClassFieldExtractor.getLongValue with null fields
In-Reply-To: <1168775.1192010403353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15081008.1192365303652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1264?page=all ]

Mark Proctor closed JBRULES-1264.
---------------------------------

    Resolution: Done

> NPE at BaseObjectClassFieldExtractor.getLongValue with null fields
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1264
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1264
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Alexandre Gattiker
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2_SOA_4.2, 4.0.3, 4.1.0
>
>         Attachments: JBRULES-1264.patch
>
>
> Removing one of the three rules magically solves the problem.
> java.lang.NullPointerException
> 	at org.drools.base.extractors.BaseObjectClassFieldExtractor.getLongValue(BaseObjectClassFieldExtractor.java:106)
> 	at org.drools.base.ClassFieldExtractor.getLongValue(ClassFieldExtractor.java:203)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter$HashKey.setValue(CompositeObjectSinkAdapter.java:467)
> 	at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:292)
> 	at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:153)
> 	at org.drools.reteoo.Rete.assertObject(Rete.java:177)
> 	at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:201)
> 	at org.drools.reteoo.ReteooWorkingMemory.doInsert(ReteooWorkingMemory.java:71)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:886)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:858)
> 	at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:659)
> 	at com.sample.DroolsTest.main(DroolsTest.java:21)
> package com.sample;
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest
> {
>     public static final void main(String[] args)
>     {
>         try
>         {
>             RuleBase ruleBase = readRule();
>             WorkingMemory workingMemory = ruleBase.newStatefulSession();
>             workingMemory.insert(new Attribute());
>             workingMemory.insert(new Message());
>             workingMemory.fireAllRules();
>         }
>         catch (Throwable t)
>         {
>             t.printStackTrace();
>         }
>     }
>     private static RuleBase readRule() throws Exception
>     {
>         Reader source = new InputStreamReader(DroolsTest.class.getResourceAsStream("/Sample.drl"));
>         PackageBuilder builder = new PackageBuilder();
>         builder.addPackageFromDrl(source);
>         Package pkg = builder.getPackage();
>         RuleBase ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         return ruleBase;
>     }
>     public static class Message
>     {
>         //empty
>     }
>     public static class Attribute
>     {
>         public Integer getValue()
>         {
>             return null;
>         }
>     }
> }
> package com.sample
>  
> import com.sample.DroolsTest.Message;
> import com.sample.DroolsTest.Attribute;
>  
> rule "rule_1"
> 	
> 	when
> 		Message()
> 		Attribute(value == 1)
> 	then
> 		System.err.println("case 1");
> end
> rule "rule_2"
> 	
> 	when
> 		Message()
> 		Attribute(value == 2)
> 	then
> 		System.err.println("case 2");
> end
> rule "rule_3"
> 	
> 	when
> 		Message()
> 		$a:Attribute(value == 3)
> 	then
> 		System.err.println("case 3");
> end

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 08:41:03 2007
From: jira-events at lists.jboss.org (Markus Wolf (JIRA))
Date: Sun, 14 Oct 2007 08:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1247) Bug during rule
	parsing
In-Reply-To: <32926802.1191497890611.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5331774.1192365663357.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1247?page=all ]

Markus Wolf updated JBRULES-1247:
---------------------------------

     Original Estimate: 0 minutes
    Remaining Estimate: 0 minutes

The '=' in the agenda-group option does caused this error. I know it is an invalid char at that position, but the error message is confusing and should state a syntax error.

rule "SomeName"
  agenda-group = "action"
  when
    SomeThing()
  then
    System.out.println("Test");
end

> Bug during rule parsing
> -----------------------
>
>                 Key: JBRULES-1247
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1247
>             Project: JBoss Drools
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Markus Wolf
>         Assigned To: Mark Proctor
>             Fix For: FUTURE
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team.
> 	at org.drools.compiler.DrlParser.compile(DrlParser.java:180)
> 	at org.drools.compiler.DrlParser.parse(DrlParser.java:61)
> 	at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 09:09:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Sun, 14 Oct 2007 09:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1038) Allow export of
 database to xml
In-Reply-To: <24585280.1158190113259.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1216887.1192367343282.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1038?page=all ]

Chris Laprun resolved JBPORTAL-1038.
------------------------------------

    Resolution: Duplicate Issue

> Allow export of database to xml
> -------------------------------
>
>                 Key: JBPORTAL-1038
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1038
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4 Final
>            Reporter: William DeCoste
>            Priority: Minor
>
> This feature was requested by Intuit.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 09:26:17 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Sun, 14 Oct 2007 09:26:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1752) Update SSO
 documentation to use AS 4.2 instead of 4.0.x
Message-ID: <25761598.1192368377472.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update SSO documentation to use AS 4.2 instead of 4.0.x
-------------------------------------------------------

                 Key: JBPORTAL-1752
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1752
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 13:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1079) JBM should
 call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7518044.1192381504205.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox reopened JBMESSAGING-1079:
----------------------------------

             

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 13:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1079) JBM should
 call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5108115.1192381504871.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox reassigned JBMESSAGING-1079:
------------------------------------

    Assignee: Tim Fox  (was: Clebert Suconic)

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:05:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sun, 14 Oct 2007 13:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1079) JBM should
 call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25156747.1192381505518.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox updated JBMESSAGING-1079:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: 1.4.0.GA)

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:26:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Sun, 14 Oct 2007 13:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19945973.1192382763445.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382347 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

You don't need to see any source code, you only need to read what I dumped above. Here, to make it easier:

mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
+------------+------------+
| CHANNEL_ID | MESSAGE_ID | ..........
+------------+------------+
|            0    | 8957       | ..........
+------------+------------+

mysql> SELECT * FROM JBM_POSTOFFICE;
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| POSTOFFICE_NAME | NODE_ID | QUEUE_NAME | COND | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
| JMS post office | 38 | ovidiu | queue.ovidiu | NULL | 20 | Y | N |
| JMS post office | 39 | ovidiu | queue.ovidiu | NULL | 40 | Y | N |
+-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+ 


> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 13:51:26 2007
From: jira-events at lists.jboss.org (Weston Price (JIRA))
Date: Sun, 14 Oct 2007 13:51:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4809) JCA deployer and
 metadata
 incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
In-Reply-To: <29252975.1192034414855.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4964342.1192384286301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4809?page=all ]

Weston Price resolved JBAS-4809.
--------------------------------

    Resolution: Done

Modified metadata to correctly identify local transaction on both non datasource and datasource deployments in the metadata subtypes versus the parent.

> JCA deployer and metadata incorrectly identifies TxConnectionFactory in unmarshalling *-ds.xml file
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4809
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4809
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>            Reporter: Weston Price
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The ManagedConnectionEmptyContentAdapter did not correctly unmarshall XA based deployments. As a result, non datasource XA deployments (most notably JmsXA) are being incorrectly identified with local tx support and causing failures.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 14 17:48:03 2007
From: jira-events at lists.jboss.org (Willian Mitsuda (JIRA))
Date: Sun, 14 Oct 2007 17:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1276) Drools toolbar
 should not
 appear in all perspectives and should reuse the standard "new" dropdown
Message-ID: <18713344.1192398483316.JavaMail.jira@cloud.prod.atl2.jboss.com>

Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown
-------------------------------------------------------------------------------------------------

                 Key: JBRULES-1276
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1276
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
    Affects Versions: 4.0.2
            Reporter: Willian Mitsuda
         Assigned To: Mark Proctor


I just installed the drools plugin and noted that it automatically enables a drools toolbar in every perspective.

This is not a good UI policy because it looks like the plugin is trying to appear more important than the others. I have other plugins installed, and I don't like the drools button appearing by default in the C++ or the Profilling perspective, for example. It could be enabled by default just in the Drools perspective, since it exists, and the user could enable it on the others, if he desires.

Also, since your actions are all about resource creation, you could hook them into the standard "new" dropdown, instead of creating your own actionset. This should make your plugin to appear more integrated to Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 01:24:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 01:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23900507.1192425843587.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Rubinger resolved EJBTHREE-1062.
---------------------------------------

    Resolution: Done

JNDI Naming fixes in unrelated unit tests reverted; issue corrected to cover previously-failing cases in which @Remote is specified using XML metadata.

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 02:49:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 15 Oct 2007 02:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1277) BRDRLPersitence
 is not rendering OR's correctly
Message-ID: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRDRLPersitence is not rendering OR's correctly
-----------------------------------------------

                 Key: JBRULES-1277
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Edson Tirelli
             Fix For: 4.0.2_SOA_4.2


Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 02:51:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 15 Oct 2007 02:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1277) BRDRLPersitence
 is not rendering OR's correctly
In-Reply-To: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23150533.1192431063350.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1277?page=all ]

Michael Neale updated JBRULES-1277:
-----------------------------------

    Attachment: BRDRLPersistence.java

This is the corrected one.

> BRDRLPersitence is not rendering OR's correctly
> -----------------------------------------------
>
>                 Key: JBRULES-1277
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2
>
>         Attachments: BRDRLPersistence.java, BRDRLPersistence.old
>
>
> Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 02:51:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 15 Oct 2007 02:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1277) BRDRLPersitence
 is not rendering OR's correctly
In-Reply-To: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24442419.1192431063500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1277?page=all ]

Michael Neale updated JBRULES-1277:
-----------------------------------

    Attachment: BRDRLPersistence.old

And pre patch

> BRDRLPersitence is not rendering OR's correctly
> -----------------------------------------------
>
>                 Key: JBRULES-1277
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2
>
>         Attachments: BRDRLPersistence.java, BRDRLPersistence.old
>
>
> Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:00:05 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Mon, 15 Oct 2007 03:00:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (BPEL-280) redeploy web modules
 upon server restart
In-Reply-To: <6144861.1192319228417.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32639890.1192431605538.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-280?page=all ]

Alejandro Guizar resolved BPEL-280.
-----------------------------------

    Resolution: Done

SOLUTION Adopting proposal 1. The other proposals might be revisited in a future release.

> redeploy web modules upon server restart
> ----------------------------------------
>
>                 Key: BPEL-280
>                 URL: http://jira.jboss.com/jira/browse/BPEL-280
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> PROBLEM With the automated deployment procedure in place, new processes and the associated web services can be deployed on the fly. There is an issue, however. Upon server restart, web modules deployed through the JBoss AS main deployer dissapear. Three approaches come quickly to mind to address this situation:
> PROPOSAL 1. Place the modules directly in the deployment directory of the application server
> * Pros. The engine needs not perform any task at startup. The server is responsible for reading and deploying the modules.
> * Cons. Loss of portability. Servers other than JBoss AS use different deployment directories. Some may not even support the concept of a deployment directory.
> Furthermore, what if the modules are deleted? Because the responsibility is trasferred to the server, there can be a disconnection between the process definitions in the jBPM database and the deployed web services.
> PROPOSAL 2. Save the prefabricated deployment artifacts in the process definition. Rebuild the module at startup.
> * Pros. No external location is required to place the modules. All information required to rebuild them is saved along the process definition. The disconnection between the process definitions and the deployed web services dissapear.
> * Cons. The engine has to process each process definition at startup to rebuild the modules. This could result in a significant startup time.
> Plus, database space consumption might become excessive.
> PROPOSAL 3. Save the prefabricated module in a content repository. Leverage the repository facilities provided by jBPM.
> * Pros. Same as 2. Plus, no large database storage requirements.
> * Cons. The engine still has to process each process definition at startup. Plus, an external content repository introduces new dependencies and installation complexities to the product.
> Among these proposals, #1 looks good because it neither imposes large database storage requirements nor a significant startup processing time. It is also the easiest to implement, at the expense of brittleness due to the reliance on the app server.
> Any comments or new proposals welcome.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:29:03 2007
From: jira-events at lists.jboss.org (M H (JIRA))
Date: Mon, 15 Oct 2007 03:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1278) DSL Parser "eval"
Message-ID: <17218346.1192433343339.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL Parser "eval"
-----------------

                 Key: JBRULES-1278
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1278
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.1
            Reporter: M H
         Assigned To: Mark Proctor
            Priority: Blocker


rule "PatternTest"
       when
               $pli:Item( title matches "^Test\s*")
       then
                       #
end

this one compiles but on Runtime it ends in an Exception when title looks for example like this "BlaBla (Test)".

as workaround i thought about using the next part, but

rule "PatternTest"
       when
               $pli:Item( eval(title.matches("^Test\s*")) )
       then
                       #
end

it resolves into, also it shouldn't (because title.matches() is Java Code a shouldn't be parsed by the DSL Parser itself):

SyntaxfehlerRule Compilation error : [Rule name=OnlineStreaming Start,
agendaGroup=MAIN, salience=100, no-loop=true]
com/p7s1/swi/phoenix/n24/Rule_OnlineStreaming_Start_0.java (19:923) :
Invalid escape sequence (valid ones are \b \t \n \f \r \" \' \\ )

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:46:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1751)
 portlet-instances.xml
 security-constraints are not verified using request.isUserInRole()
In-Reply-To: <28407251.1192349463289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28601821.1192434363520.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1751?page=all ]

Thomas Heute updated JBPORTAL-1751:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> portlet-instances.xml security-constraints are not verified using request.isUserInRole()
> ----------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1751
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1751
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final, 2.6.2 Final
>         Environment: Java JDK 1.4.2
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: fwd-jbportal-securitycheck-1.0.0.0.war
>
>
> The implementation which verifies the security of portlet-instances.xml against the user roles currently doesn't seem to use request.isUserInRole().
> Fact 1:
> If you use a role-link in the portlet.xml (to have a role which is not originally created by the Jboss Portal Loginmodule (IdentityLoginModule))
> <portlet>
> ...
> <security-role-ref>
> 			<role-name>PortletUser</role-name>
> 			<role-link>User</role-link>
> 		</security-role-ref>
> </portlet>
> and then use it in the portlet-instances.xml:
> <instance>
> ...
> <security-constraint>
> 				<policy-permission>
> 					<role-name>PortletUser</role-name>
> 					<action-name>view</action-name>
> 				</policy-permission>
> 			</security-constraint>
> </instance>
> </deployment>
> the portlet instance will not show up.
> If you use the User-role instead, it works correctly.
> However, if I do a request.isUserInRole("PortletUser") in the portlet itself, it will always show up as expected.
> Fact 2:
> Additionally, it seems the portlet-instances.xml- security check also makes use of the org.jboss.portal.identity.auth.UserPrincipal.
> I wrote a custom loginmodule and added the "User"-role using my own Principal-class. Again, the portlet instance doesn't show up with my custom loginmodule.
> If I check it using request.isUserInRole("User"), it shows up 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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:46:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:46:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-531) Import/Export of
 Portal Page and Portlet Database Settings
Message-ID: <5714337.1192434364250.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=all ]

Thomas Heute updated JBPORTAL-531:
----------------------------------

    Affects Version/s: 2.6.2 Final

> Import/Export of Portal Page and Portlet Database Settings
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-531
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-531
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.2 Final, 2.6.2 Final
>            Reporter: James Williams
>
> There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance.
> For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:50:03 2007
From: jira-events at lists.jboss.org (Magnus Sandberg (JIRA))
Date: Mon, 15 Oct 2007 03:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1069) persistance.xml
 with <jar-file> looks for jar file in the wrong place
Message-ID: <20172525.1192434603555.JavaMail.jira@cloud.prod.atl2.jboss.com>

persistance.xml with <jar-file> looks for jar file in the wrong place
---------------------------------------------------------------------

                 Key: EJBTHREE-1069
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1069
             Project: EJB 3.0
          Issue Type: Bug
         Environment: JBoss AS 4.2.0.GA (Hibernate 3.3.1.GA)
            Reporter: Magnus Sandberg
             Fix For: AS 4.2.0 GA


When using <jar-file> references in persistance.xml the Ejb3Configuration does not look for the jar relative to the jar with the persistance.xml but relative to from where jboss is started.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:52:07 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:52:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-531) Import/Export
 of Portal Page and Portlet Database Settings
Message-ID: <32166593.1192434727717.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=comments#action_12382373 ] 
            
Thomas Heute commented on JBPORTAL-531:
---------------------------------------

THis is not something we can do with the current isntances deployment.

Each portlet-instances.xml must live within their war file (so that the class is loaded before the instance is created), this is not something that can be centralized in 2.6 branch,

> Import/Export of Portal Page and Portlet Database Settings
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-531
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-531
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.2 Final, 2.6.2 Final
>            Reporter: James Williams
>
> There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance.
> For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:54:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-531) Import/Export of
 Portal Page and Portlet Database Settings
Message-ID: <1194964.1192434843215.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-531?page=all ]

Thomas Heute updated JBPORTAL-531:
----------------------------------

    Fix Version/s: 2.8 Final

> Import/Export of Portal Page and Portlet Database Settings
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-531
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-531
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.2 Final, 2.6.2 Final
>            Reporter: James Williams
>             Fix For: 2.8 Final
>
>
> There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance.
> For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 03:56:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 03:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15747969.1192434963339.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382374 ] 
            
Thomas Heute commented on JBPORTAL-1747:
----------------------------------------

While i'm concern about the extra work needed in the user guide which doesn't bring much value i think, the 2 guides have different scopes:

User guide: "where to click" guide, basically it should mention all the existing features of the embedded portlets and how to access them. 

QuickStartGuide: Drives the user through common configuration ex:
lead the user from the jboss-portal zip file to a fully customized portal.

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 04:24:03 2007
From: jira-events at lists.jboss.org (Ingo Bruell (JIRA))
Date: Mon, 15 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25091765.1192436643598.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12382375 ] 
            
Ingo Bruell commented on JBAS-4704:
-----------------------------------

How could i get JBoss Remoting 2.2.2 SP2 ?

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 04:49:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 04:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1111) JBM 1.4.0
 in ESB from svn revision 15800 writes WARNING to server log: WARN
 [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE
 CHANGED FROM THE INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4152510.1192438143312.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=comments#action_12382376 ] 
            
Tim Fox commented on JBMESSAGING-1111:
--------------------------------------

Nothings stops the server running, they just get the warning since there's a potential security risk until they specify a password.

It's a bit like installing Oracle and not changing the default password (if there is one - I can't remember?) - you get the idea.

We could take a "head in the sand" approach and not log a warning but I don't think this is a good idea - is this what you are suggesting?

BTW the text was changed some days ago.

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 04:49:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 04:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1111) JBM 1.4.0 in
 ESB from svn
 revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore]
 *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE
 INSTALLATION DEFAULT
In-Reply-To: <13815209.1192328283335.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14987178.1192438143493.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1111?page=all ]

Tim Fox closed JBMESSAGING-1111.
--------------------------------

    Resolution: Rejected

> JBM 1.4.0 in ESB from svn revision 15800 writes WARNING to server log: WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1111
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1111
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Security
>    Affects Versions: 1.4.0.GA
>         Environment: RHEL5
> Java 1.5
> JBESB - At revision 15800
> JBM 1.4.0.GA
>            Reporter: Len DiMaggio
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> This is coming from: jboss-messaging-1.4.0.GA-src/src/main/org/jboss/jms/server/ServerPeer.java
> 14:49:33,472 WARN [SecurityMetadataStore] *** THE DEFAULT SUCKER USER PASSWORD HAS NOT BE CHANGED FROM THE INSTALLATION DEFAULT - THIS IS A SECURITY RISK - PLEASE CHANGE THIS!! **
> I noticed this with ESB - from svn revision 15800 on oct 12 - http://jira.jboss.com/jira/browse/JBESB-1172

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:19:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 05:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4704) The port for the
 InvokerLayer (ejb3-deployer) listens only to one interface (address)
In-Reply-To: <5421281.1189597511503.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1532568.1192439943549.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4704?page=comments#action_12382381 ] 
            
Dimitris Andreadis commented on JBAS-4704:
------------------------------------------

http://repository.jboss.com/jboss/remoting/2.2.2.SP2/lib/

> The port for  the InvokerLayer (ejb3-deployer) listens only to one interface (address)
> --------------------------------------------------------------------------------------
>
>                 Key: JBAS-4704
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4704
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: linux ubuntu feisty, jdk6
>            Reporter: Ingo Bruell
>         Assigned To: Ron Sigal
>
> The port (3873) of the invokerLayer (ejb3-deployer) only binds to one interface even if i use explicit the address 0.0.0.0. JBoss is started with the argument '-b 0.0.0.0' and i tried to change the address in the mbean configuration but i had no success.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:24:07 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 15 Oct 2007 05:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3413050.1192440247912.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4805?page=comments#action_12382383 ] 
            
Galder Zamarreno commented on JBAS-4805:
----------------------------------------

Potentially the 4.2 CP branch, but depends on Patch Triage Team
approving it. See JBPAPP-356.

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:48:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:48:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-155) secure the gpd
	deployment servlet
In-Reply-To: <684538.1181894171603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9491212.1192441685338.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-155?page=all ]

Koen Aers updated GPD-155:
--------------------------

    Component/s: jpdl

A number of tasks have to be done:
- upload of the archive should be done using username/password combo
- servlet in engine should be secured 

> secure the gpd deployment servlet
> ---------------------------------
>
>                 Key: GPD-155
>                 URL: http://jira.jboss.com/jira/browse/GPD-155
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>
> the gpd deployment servlet should be secured.  the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that.  then the users will be able to control the authorization through the web interface itself.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:50:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-155) secure the gpd
	deployment servlet
In-Reply-To: <684538.1181894171603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24968503.1192441803727.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-155?page=all ]

Koen Aers updated GPD-155:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> secure the gpd deployment servlet
> ---------------------------------
>
>                 Key: GPD-155
>                 URL: http://jira.jboss.com/jira/browse/GPD-155
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> the gpd deployment servlet should be secured.  the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that.  then the users will be able to control the authorization through the web interface itself.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:50:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-171) Split the jPDL plugin
 in a Common/jPDL/BPEL plugin triad
In-Reply-To: <25610757.1192180563603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6009047.1192441803816.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-171?page=all ]

Koen Aers updated GPD-171:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1

> Split the jPDL plugin in a Common/jPDL/BPEL plugin triad
> --------------------------------------------------------
>
>                 Key: GPD-171
>                 URL: http://jira.jboss.com/jira/browse/GPD-171
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>
> the common classes and extension points have to be included in the common plugin

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:52:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-172) Develop an extension
 example for a simple DSL in its own plugin
In-Reply-To: <16781370.1192180683620.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <36794.1192441923539.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-172?page=all ]

Koen Aers updated GPD-172:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha2

> Develop an extension example for a simple DSL in its own plugin
> ---------------------------------------------------------------
>
>                 Key: GPD-172
>                 URL: http://jira.jboss.com/jira/browse/GPD-172
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:56:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-172) Develop an extension
 example for a simple DSL in its own plugin
In-Reply-To: <16781370.1192180683620.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30413350.1192442163383.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-172?page=all ]

Koen Aers updated GPD-172:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1
                       (was: jBPM jPDL Designer 3.2.0.alpha2)

> Develop an extension example for a simple DSL in its own plugin
> ---------------------------------------------------------------
>
>                 Key: GPD-172
>                 URL: http://jira.jboss.com/jira/browse/GPD-172
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:56:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 15 Oct 2007 05:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5517686.1192442163567.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382390 ] 
            
Alexey Loubyansky commented on JBAS-4853:
-----------------------------------------

Due to 1.0.0.GA not being released in JIra, CR11 was released after the 1.0.0.GA.

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 05:56:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 05:56:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-173) Develop a complete
 jPDL extension example
In-Reply-To: <19634315.1192180685849.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12875029.1192442163651.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-173?page=all ]

Koen Aers updated GPD-173:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha2

> Develop a complete jPDL extension example
> -----------------------------------------
>
>                 Key: GPD-173
>                 URL: http://jira.jboss.com/jira/browse/GPD-173
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:01:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-174) Develop a jPDL
	cheatsheet
In-Reply-To: <1560923.1192180803591.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14644850.1192442463468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-174?page=all ]

Koen Aers updated GPD-174:
--------------------------

      Component/s: jpdl
    Fix Version/s: jBPM jPDL Designer 3.1.2

> Develop a jPDL cheatsheet
> -------------------------
>
>                 Key: GPD-174
>                 URL: http://jira.jboss.com/jira/browse/GPD-174
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-176) Add code completion
 inside attributes and values within the xml source
In-Reply-To: <32030443.1192185004070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13301781.1192442464772.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-176?page=all ]

Koen Aers updated GPD-176:
--------------------------

    Component/s: jpdl

> Add code completion inside attributes and values within the xml source
> ----------------------------------------------------------------------
>
>                 Key: GPD-176
>                 URL: http://jira.jboss.com/jira/browse/GPD-176
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-177) Add code completion in
 the text input fields on the properties view
In-Reply-To: <10554814.1192185123592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17672036.1192442464914.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-177?page=all ]

Koen Aers updated GPD-177:
--------------------------

    Component/s: jpdl

> Add code completion in the text input fields on the properties view
> -------------------------------------------------------------------
>
>                 Key: GPD-177
>                 URL: http://jira.jboss.com/jira/browse/GPD-177
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:03:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 15 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-112) Failed to create a
	new SAX parser
Message-ID: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failed to create a new SAX parser
---------------------------------

                 Key: JBXB-112
                 URL: http://jira.jboss.com/jira/browse/JBXB-112
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Bug
    Affects Versions: JBossXB-2.0.0.CR4
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-2.0.0.CR5


package org.jboss.xb.binding.parser.sax;
public class SaxJBossXBParser

   public SaxJBossXBParser()
      throws JBossXBException
   {
...
 parser = saxFactory.newSAXParser();
         log.debug("Created parser: "+parser
               + ", isNamespaceAware: "+parser.isNamespaceAware()
               + ", isValidating: "+parser.isValidating()
               + ", isXIncludeAware: "+parser.isXIncludeAware()
               );

This is the javadoc for isXIncludeAware:

boolean javax.xml.parsers.SAXParser.isXIncludeAware()

Get the XInclude processing mode for this parser.

See Also:
SAXParserFactory.setXIncludeAware(boolean)
Returns:
the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
Throws:
UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
Since:
1.5

Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:07:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-15) add a readme in the
 create-project wizard
In-Reply-To: <29451119.1168949572678.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15168091.1192442823404.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-15?page=all ]

Koen Aers updated GPD-15:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.2

> add a readme in the create-project wizard
> -----------------------------------------
>
>                 Key: GPD-15
>                 URL: http://jira.jboss.com/jira/browse/GPD-15
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.2
>
>
> all features that help beginner get started are vital imho. therefor, i think the forum user points out a good opportunity for us: we could create a readme.txt in the root of the generated project. that readme is opened when the wizard creates the project and it explains the contents of the project and what do to next.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-25) Saving
 processdefinition should add
 problem markers and entries in problem view if any problems occur
In-Reply-To: <32549222.1168955452884.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23768689.1192443063533.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-25?page=all ]

Koen Aers updated GPD-25:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Saving processdefinition should add problem markers and entries in problem view if any problems occur
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GPD-25
>                 URL: http://jira.jboss.com/jira/browse/GPD-25
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-19) Endpoint Editing
In-Reply-To: <23652487.1168954132731.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2114039.1192443063615.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-19?page=all ]

Koen Aers updated GPD-19:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Endpoint Editing
> ----------------
>
>                 Key: GPD-19
>                 URL: http://jira.jboss.com/jira/browse/GPD-19
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Move endpoints of connections to wherever location on the edge of a node. Involves implementing a particular form of anchor point.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:11:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 15 Oct 2007 06:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4421433.1192443063739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

The isXIncludeAware() call is now in the try-catch block.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-18) Reordering graph
 elements in outline view
In-Reply-To: <4677367.1168954014581.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23984546.1192443183298.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-18?page=all ]

Koen Aers updated GPD-18:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Reordering graph elements in outline view
> -----------------------------------------
>
>                 Key: GPD-18
>                 URL: http://jira.jboss.com/jira/browse/GPD-18
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Reordering elements is possible by directly editing the xml. It should be possible to obtain the same effect by dragging and dropping elements in the outline view.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-17) jpdl designer user
 guide and documentation
In-Reply-To: <8987007.1168951973156.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15004350.1192443183443.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-17?page=all ]

Koen Aers updated GPD-17:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.2
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> jpdl designer user guide and documentation
> ------------------------------------------
>
>                 Key: GPD-17
>                 URL: http://jira.jboss.com/jira/browse/GPD-17
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.2
>
>
> A new user guide using screenshots of the new product should be written.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:17:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-36) Choose to have
 classpath container or expanded libraries
In-Reply-To: <16017528.1168963695187.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4802901.1192443423381.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-36?page=all ]

Koen Aers updated GPD-36:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Choose to have classpath container or expanded libraries
> --------------------------------------------------------
>
>                 Key: GPD-36
>                 URL: http://jira.jboss.com/jira/browse/GPD-36
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> It would be good to be able to choose between expanded libraries or a classpath container when creating a process project with the new... wizard. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:21:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-37) include snap to grid
In-Reply-To: <30030403.1168963978540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30727317.1192443663366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-37?page=all ]

Koen Aers updated GPD-37:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> include snap to grid
> --------------------
>
>                 Key: GPD-37
>                 URL: http://jira.jboss.com/jira/browse/GPD-37
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> While designing processes, it would be a lot easier if there is some kind of 'snap to grid'. You can then have easier manual allignment etc. Besides that, the images look better
> - transitions should snap to the grid to
> - transitions should be perpendicular at least if there are more than three points in the line 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:21:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-40) A slash character in
 Task Node name
 causes crash. Graphical Process Designer allows the slash to be entered
 anyway.
In-Reply-To: <30389570.1168965113514.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7733519.1192443663504.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-40?page=all ]

Koen Aers updated GPD-40:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> A slash character in Task Node name causes crash. Graphical Process Designer allows the slash to be entered anyway.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: GPD-40
>                 URL: http://jira.jboss.com/jira/browse/GPD-40
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> The Graphical Process Designer allows the user to enter a Task Node name that includes a slash, such as "Accounting/Finance". The slash causes a crash later on when the process is run, and it isn't obvious what the source of the problem is. Suggestion: somehow prevent the user from entering a name that includes a slash. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:21:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-34) Review the extension
 points and mechanism.
In-Reply-To: <4787168.1168962293366.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16583713.1192443663594.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-34?page=all ]

Koen Aers updated GPD-34:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1

> Review the extension points and mechanism.
> ------------------------------------------
>
>                 Key: GPD-34
>                 URL: http://jira.jboss.com/jira/browse/GPD-34
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:23:14 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:23:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-50) review the packaging
	mechanism
In-Reply-To: <12577296.1169589052820.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5901285.1192443794238.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-50?page=all ]

Koen Aers updated GPD-50:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> review the packaging mechanism
> ------------------------------
>
>                 Key: GPD-50
>                 URL: http://jira.jboss.com/jira/browse/GPD-50
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Leverage the eclipse packager mechanism to include the necessary features in the distributable and make the site installation mechanism work again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:25:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-33) remember the previous
 form generation data fields
In-Reply-To: <11469034.1168960792592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15663339.1192443903273.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-33?page=all ]

Koen Aers updated GPD-33:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> remember the previous form generation data fields
> -------------------------------------------------
>
>                 Key: GPD-33
>                 URL: http://jira.jboss.com/jira/browse/GPD-33
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> In the form generation, we currently start from the data entered in the task controller (if any)
> Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again.
> The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields).
> I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:28:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 06:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22340509.1192444083484.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382394 ] 
            
Dimitris Andreadis commented on JBAS-4853:
------------------------------------------

Alexey, can you prepare quickly a 1.0.0.SP1 ?

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:33:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-51) Integration of web
	console in GPD
In-Reply-To: <363597.1169633217418.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20640854.1192444383513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-51?page=all ]

Koen Aers updated GPD-51:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.4

> Integration of web console in GPD
> ---------------------------------
>
>                 Key: GPD-51
>                 URL: http://jira.jboss.com/jira/browse/GPD-51
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>
> Provide a number of links (throug hyperlinks or menu buttons) that open a browser on the configured url pointing at a jBPM server installation. These options should be disabled if no server installation is configured.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:35:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-74) Add a server adaptor to
 enable starting and stopping the 'jbpm server'.
In-Reply-To: <15710853.1178575432195.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4223589.1192444503411.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-74?page=all ]

Koen Aers updated GPD-74:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.4

> Add a server adaptor to enable starting and stopping the 'jbpm server'.
> -----------------------------------------------------------------------
>
>                 Key: GPD-74
>                 URL: http://jira.jboss.com/jira/browse/GPD-74
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:35:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:35:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-3) implement a generation
 mechanism for the new task forms
Message-ID: <30599002.1192444504979.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-3?page=all ]

Koen Aers updated GPD-3:
------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> implement a generation mechanism for the new task forms
> -------------------------------------------------------
>
>                 Key: GPD-3
>                 URL: http://jira.jboss.com/jira/browse/GPD-3
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:35:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:35:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-73) Review deployment
In-Reply-To: <19314408.1178573812166.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <326529.1192444505137.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-73?page=all ]

Koen Aers updated GPD-73:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> Review deployment
> -----------------
>
>                 Key: GPD-73
>                 URL: http://jira.jboss.com/jira/browse/GPD-73
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> - better status messages
> - saving the settings

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:37:10 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:37:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-9) save deployment options
In-Reply-To: <27696282.1163433282004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24059310.1192444630457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-9?page=all ]

Koen Aers updated GPD-9:
------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> save deployment options
> -----------------------
>
>                 Key: GPD-9
>                 URL: http://jira.jboss.com/jira/browse/GPD-9
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.0.11
>            Reporter: Brice Ruth
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> The current jBPM Process Designer plugin for Eclipse does not save deployment settings for a process definition. It would be useful to set remote deploy settings as a workspace preference (host/port/path). Then, what files are to be deployed (gpd.xml, processdefinition.xml, processimage.xml, src files, etc.) should be saved per process, and stored as part of the project/process files (whichever, just not in .metadata, so it can be committed to CVS and shared by a team).
> JBoss Support Case: 00012512

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:37:15 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:37:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-29) referencing an unknown
 class gives exception at deployment
In-Reply-To: <9620863.1168957132750.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32690023.1192444635574.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-29?page=all ]

Koen Aers updated GPD-29:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.1
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> referencing an unknown class gives exception at deployment
> ----------------------------------------------------------
>
>                 Key: GPD-29
>                 URL: http://jira.jboss.com/jira/browse/GPD-29
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> preferrably, this should be a warning in the problems view. in case the class is not found to be included in the .par, it just shouldn't be included. maybe a warning would be good;

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:37:15 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:37:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-10) can't find resource
In-Reply-To: <27226412.1163761961694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32811145.1192444635745.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-10?page=all ]

Koen Aers updated GPD-10:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> can't find resource
> -------------------
>
>                 Key: GPD-10
>                 URL: http://jira.jboss.com/jira/browse/GPD-10
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> i don't know why, but when trying to deploy the example process websale after modifying the form.create.xhtml, i got this exception that disabled depoyment of the process.
> java.lang.NullPointerException
> at org.jbpm.ui.util.ProcessDeployer.addClassOrResource(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.addClassesAndResources(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.createParBytes(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.access$1(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer$1.run(Unknown Source)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479)
> at org.jbpm.ui.util.ProcessDeployer.showProgressMonitorDialog(Unknown Source)
> at org.jbpm.ui.util.ProcessDeployer.deploy(Unknown Source)
> at org.jbpm.ui.editor.form.deployment.DeploymentForm$1.widgetSelected(Unknown Source)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:39:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-63) Inner classes are not
	deployed.
In-Reply-To: <21438537.1171956228437.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27014094.1192444743726.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-63?page=all ]

Koen Aers updated GPD-63:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.1
    Affects Version/s:     (was: jBPM JPDL Designer 3.0.13)

> Inner classes are not deployed.
> -------------------------------
>
>                 Key: GPD-63
>                 URL: http://jira.jboss.com/jira/browse/GPD-63
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Matej Knopp
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: patch.txt
>
>
> When process is being deployed, the inner classes are ignored. So when I have class Foo with inner class Bar, the Foo.class file gets deployed, but the Foo$Bar.class is not. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:41:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-23) deployment with
 problems still gives "process was deployed successfull"
In-Reply-To: <632757.1168954978751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20917529.1192444863356.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-23?page=all ]

Koen Aers updated GPD-23:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.4
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> deployment with problems still gives "process was deployed successfull"
> -----------------------------------------------------------------------
>
>                 Key: GPD-23
>                 URL: http://jira.jboss.com/jira/browse/GPD-23
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>
> Add more meaningful result notifications upon deploying process archives.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:41:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-32) Class chooser limited
 to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)
In-Reply-To: <25271593.1168960312566.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25603748.1192444863614.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-32?page=all ]

Koen Aers updated GPD-32:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.1
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0 alpha1)

> Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)
> -------------------------------------------------------------------------------
>
>                 Key: GPD-32
>                 URL: http://jira.jboss.com/jira/browse/GPD-32
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> When trying to lookup the class implementing an action handler, the class chooser dialog fails to see classes other than those in jBPM-3.1.1.
> This applies to task assignments as well.
> To re-create, create an action handler in a different eclipse project, place that project on the classpath of the process project, and invoke the class chooser for an action in a process definition. Typing the short name of the class does not cause the list of candidates to appear. Nor does typing the fully qualified name. Typing in "ActionHandler" causes candidates from the jBPM-3.1.1 jar file to appear.
> Classpath is proven to be complete, because pasting the fully qualified class name into the handler class field causes the designer to display the configuration fields that are available. This is also the workaround.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:43:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-112) Super state node name
 is not displayed
In-Reply-To: <8165273.1184094980612.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27378920.1192444983565.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-112?page=all ]

Koen Aers updated GPD-112:
--------------------------

        Fix Version/s: jBPM jPDL Designer 3.2.0.GA
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0.alpha2)
                           (was: jBPM JPDL Designer 3.1.0.alpha3)
                           (was: jBPM JPDL Designer 3.1.0.beta1)
                           (was: jBPM JPDL Designer 3.1.0.alpha4)

> Super state node name is not displayed
> --------------------------------------
>
>                 Key: GPD-112
>                 URL: http://jira.jboss.com/jira/browse/GPD-112
>             Project: JBoss jBPM GPD
>          Issue Type: Sub-task
>          Components: jpdl
>         Environment: all
>            Reporter: vladimir mezhibovsky
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Having a name of the super state shown on the process diagram would really help. Currently it is only visible in the outline window which make it hard to understand the process by just looking on the diagram. You have to click on the rectangle that represent super state to see the name.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:45:32 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 06:45:32 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
Message-ID: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>

jboss-web with 4.0 dtd does not deploy
--------------------------------------

                 Key: JBAS-4855
                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky
             Fix For:  JBossAS-5.0.0.Beta3


[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
        at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
        at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
        ... 66 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:45:32 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 06:45:32 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25496281.1192445132626.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4855?page=comments#action_12382399 ] 
            
Thomas Diesler commented on JBAS-4855:
--------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <security-domain>java:/jaas/JBossWS</security-domain>
</jboss-web>

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:49:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24682854.1192445343614.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4853?page=all ]

Dimitris Andreadis reassigned JBAS-4853:
----------------------------------------

    Assignee: Alexey Loubyansky

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:49:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-26) Offer the GPD as a
 standalone package
In-Reply-To: <6979309.1168955692736.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9084296.1192445343690.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-26?page=all ]

Koen Aers updated GPD-26:
-------------------------

    Fix Version/s: jBPM jPDL Designer 4.0.x

> Offer the GPD as a standalone package
> -------------------------------------
>
>                 Key: GPD-26
>                 URL: http://jira.jboss.com/jira/browse/GPD-26
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 4.0.x
>
>
> This can be done in a number of ways:
> - Most easy way is to use the perspective mechanism to distinguish between a 'developer' and a 'analist' perspective
> - Another way is to deliver the designer as an Eclipse RCP application

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:51:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-75) Add undo/redo ability
 for every possible action
In-Reply-To: <7347368.1178575552167.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4139600.1192445463416.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-75?page=all ]

Koen Aers updated GPD-75:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Add undo/redo ability for every possible action
> -----------------------------------------------
>
>                 Key: GPD-75
>                 URL: http://jira.jboss.com/jira/browse/GPD-75
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:51:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-38) Comment in graphical
 editor (UML annotations)
In-Reply-To: <20069791.1168964512751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1319738.1192445463489.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-38?page=all ]

Koen Aers updated GPD-38:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Comment in graphical editor (UML annotations)
> ---------------------------------------------
>
>                 Key: GPD-38
>                 URL: http://jira.jboss.com/jira/browse/GPD-38
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> It should be possible to annotate the graphical elements in the graphical editor with comments.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:53:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-39) Adapt property sheet
 according to context in xml tab
In-Reply-To: <31483791.1168964513032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20362965.1192445583393.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-39?page=all ]

Koen Aers updated GPD-39:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Adapt property sheet according to context in xml tab
> ----------------------------------------------------
>
>                 Key: GPD-39
>                 URL: http://jira.jboss.com/jira/browse/GPD-39
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Currently the property sheet does not reflect the context when editing the process definition in the xml source tab.
> Solution : define a selection listener that activates the model object corresponding to the cursor location in the xml source tab.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:53:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:53:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-54) Label and name support
 for graph elements
In-Reply-To: <17703731.1170780140362.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17515961.1192445584125.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-54?page=all ]

Koen Aers updated GPD-54:
-------------------------

        Fix Version/s: jBPM jPDL Designer 3.2.0.GA
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0.alpha2)

> Label and name support for graph elements
> -----------------------------------------
>
>                 Key: GPD-54
>                 URL: http://jira.jboss.com/jira/browse/GPD-54
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:57:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-31) Make sure all tasks in
 a process definition have a unique name
In-Reply-To: <27583187.1168958633498.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6725644.1192445823399.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-31?page=all ]

Koen Aers updated GPD-31:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> Make sure all tasks in a process definition have a unique name
> --------------------------------------------------------------
>
>                 Key: GPD-31
>                 URL: http://jira.jboss.com/jira/browse/GPD-31
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> When retrieving all tasks from a process definition like so:
>         processDefinition.getTaskMgmtDefinition().getTasks() 
> it returns a MAP of tasks, keyed by task name. This is a problem if two tasks anywhere in the same process definition have the same name.
> By default, the GPD creates all tasks as "task1" when it is the first task on a task node. If none of these were renamed, you would only get a single task when trying to get all of them for the process definition.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:57:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-20) refactor naming strategy
In-Reply-To: <32621900.1168954252939.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5171569.1192445823644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-20?page=all ]

Koen Aers updated GPD-20:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.2

> refactor naming strategy
> ------------------------
>
>                 Key: GPD-20
>                 URL: http://jira.jboss.com/jira/browse/GPD-20
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.2
>
>
> 1) generate default node names when nodes are created: {node1, node2, ...}. use this naming strategy for each node type.
> 2) do not generate a node name for the start-state. users should be able to give the start-state a name, though.
> 3) use the following naming strategy for end states: {end, end2, end3, end4, ...}
> 4) do not generate names for transitions. the problem reporting should generate warnings if a node-type requires named nodes. the correlation between the graphical information and the processdefinition.xml will be done based on the position (index), rather then on the name.
> 5) disallow slashes in names in a process definition (nodes, transitions, process definition, actions, ...) Because slashes will be used as a separator in hierarchical names. We should also investigate if it would be useful to specify a strict set of chars that can be used like e.g. 0-9,a-z,A-Z,space,dot

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:57:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-75) Add undo/redo ability
 for every possible action
In-Reply-To: <7347368.1178575552167.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28163367.1192445823917.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-75?page=all ]

Koen Aers updated GPD-75:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.2
                       (was: jBPM jPDL Designer 3.2.0.GA)

> Add undo/redo ability for every possible action
> -----------------------------------------------
>
>                 Key: GPD-75
>                 URL: http://jira.jboss.com/jira/browse/GPD-75
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:11 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:59:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-136) Widget is disposed in
 Task Controller Variables Table
In-Reply-To: <24052817.1186484989796.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14139989.1192445951706.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-136?page=all ]

Koen Aers updated GPD-136:
--------------------------

        Fix Version/s: jBPM jPDL Designer 3.1.3
    Affects Version/s:     (was: jBPM JPDL Designer 3.1.0.beta2)

> Widget is disposed in Task Controller Variables Table
> -----------------------------------------------------
>
>                 Key: GPD-136
>                 URL: http://jira.jboss.com/jira/browse/GPD-136
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: Eclipse 3.2.2 on Windows 2000
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> Select a Task Node. Go to Properties View.
> Select Tasks:<task>:Controller (default).
> Add two variables, remove the second.
> Error Log view contains the following SWT Exception:
> org.eclipse.swt.SWTException: Widget is disposed
> 	at org.eclipse.swt.SWT.error(SWT.java:3374)
> 	at org.eclipse.swt.SWT.error(SWT.java:3297)
> 	at org.eclipse.swt.SWT.error(SWT.java:3268)
> 	at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
> 	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330)
> 	at org.eclipse.swt.widgets.Control.setVisible(Control.java:2642)
> 	at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.applyName(VariableTableItemWrapper.java:164)
> 	at org.jbpm.gd.jpdl.util.VariableTableItemWrapper.cancelEditing(VariableTableItemWrapper.java:150)
> 	at org.jbpm.gd.jpdl.util.VariableTableCellClickedResolver.mouseDown(VariableTableCellClickedResolver.java:25)
> 	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
> 	at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
> 	at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> 	at org.eclipse.core.launcher.Main.run(Main.java:977)
> 	at org.eclipse.core.launcher.Main.main(Main.java:952)
> After that, table input is not working anymore ("Mapped Name" column not editable anymore, for example).

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17152056.1192445952519.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox reopened JBMESSAGING-1047:
----------------------------------

             

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:13 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-100) review the delegation
 configuration form
In-Reply-To: <9679061.1182417596922.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <871568.1192445953489.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-100?page=all ]

Koen Aers updated GPD-100:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> review the delegation configuration form
> ----------------------------------------
>
>                 Key: GPD-100
>                 URL: http://jira.jboss.com/jira/browse/GPD-100
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> - have a look at the visibility of the text and table in the configuration form
> - try to fix the resize problem

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20659946.1192445953655.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox updated JBMESSAGING-1047:
---------------------------------

    Priority: Minor  (was: Major)

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:13 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1047)
 ServerPeer.listMessageCountersAsHTML sorted by Name
In-Reply-To: <3125471.1186741681302.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28464493.1192445953983.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1047?page=all ]

Tim Fox closed JBMESSAGING-1047.
--------------------------------

    Resolution: Done

> ServerPeer.listMessageCountersAsHTML sorted by Name
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1047
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1047
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Aslak
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: jmessage_1047.patch
>
>
> Added name sort to the MessageCounter list. 
> Gives a better overview when having lots of Queue/Topic/Subscriptions on the server.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:14 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 06:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-109) review task form
	generation dialog
In-Reply-To: <22119502.1182883917540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <985571.1192445954424.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-109?page=all ]

Koen Aers updated GPD-109:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> review task form generation dialog
> ----------------------------------
>
>                 Key: GPD-109
>                 URL: http://jira.jboss.com/jira/browse/GPD-109
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> implement focuslost behaviour

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 06:59:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 06:59:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2987761.1192445954564.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Tim Fox reopened JBMESSAGING-1095:
----------------------------------

             

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16288547.1192446063912.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Tim Fox updated JBMESSAGING-1095:
---------------------------------

    Priority: Minor  (was: Major)

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1095) ServerPeer
 won't survive a stop/start of the service
In-Reply-To: <28746258.1191362703325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20773895.1192446064067.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1095?page=all ]

Tim Fox closed JBMESSAGING-1095.
--------------------------------

    Resolution: Done

> ServerPeer won't survive a stop/start of the service
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1095
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1095
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>
> Few NullPointerExceptions would happen..
> This won't affect any production system... 
> It would affect the JBossAS testsuite only... so this is not a critical production bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-133) with two transitions
 from a node, both need to be labelled, or jbpm-console exceptions
In-Reply-To: <11120214.1186477706404.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12237209.1192446064397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-133?page=all ]

Koen Aers updated GPD-133:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> with two transitions from a node, both need to be labelled, or jbpm-console exceptions
> --------------------------------------------------------------------------------------
>
>                 Key: GPD-133
>                 URL: http://jira.jboss.com/jira/browse/GPD-133
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: osx, macbook pro, eclipse 3.3.0, tomcat 5.0.28
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: broken_process.xml, broken_process_exception.txt, fixed_process.xml
>
>
> when there are two transitions from a node, both need to be labelled (given a name), I am not sure if there is a validate xml option within the plugin, it would help if there was, if both are not given a name, the jbpm-console exceptions across multiple 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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1091) Selector
 parser should
 use string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17234713.1192446064562.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox reopened JBMESSAGING-1091:
----------------------------------

             

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-141)
 IType.getCompilationUnit() can be
 null if handler class is in jar, leads to event loop exception
In-Reply-To: <31471639.1186745521420.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7841179.1192446064695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-141?page=all ]

Koen Aers updated GPD-141:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> IType.getCompilationUnit() can be null if handler class is in jar, leads to event loop exception
> ------------------------------------------------------------------------------------------------
>
>                 Key: GPD-141
>                 URL: http://jira.jboss.com/jira/browse/GPD-141
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: Eclipse 3.2 on Windows 2000
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> Following part of my processdefinition.xml:
> 		<event type="node-leave">
> 			<action class="x.y.z.MyClass" name="An Action">
> 				<arg>
> 					anArg
> 				</arg>
> 			</action>
> 		</event>
> MyClass is in a jar which is added to the classpath of the Process Project. Saving throws an event loop exception in Error Log View with the following stack.
> Caused by: org.eclipse.jface.util.Assert$AssertionFailedException: null argument;
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:150)
> at org.eclipse.jface.util.Assert.isNotNull(Assert.java:126)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:577)
> at org.eclipse.jface.viewers.CheckboxTreeViewer.setCheckedElements(CheckboxTreeViewer.java:431)
> at org.jbpm.gd.jpdl.deployment.IncludeInDeploymentTreeViewer.setCheckedElements(IncludeInDeploymentTreeViewer.java:61)
> at org.jbpm.gd.jpdl.deployment.DeploymentForm$17.run(DeploymentForm.java:635)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
> The problem is, that DeploymentForm.getElementsToCheckFor() does not respect that MyClass returns null for getCompilationUnit(). As a consequence, setCheckedElements is called with null in the Object[].

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26118761.1192446065958.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox closed JBMESSAGING-1091.
--------------------------------

    Resolution: Done

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1091) Selector
 parser should use
 string literals for DeliveryMode in selector expressions
In-Reply-To: <25789770.1191328023341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31339101.1192446065798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1091?page=all ]

Tim Fox updated JBMESSAGING-1091:
---------------------------------

    Priority: Minor  (was: Major)

> Selector parser should use string literals for DeliveryMode in selector expressions
> -----------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1091
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1091
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> In the current selector parser, DeliveryMode in a selector expression is expected as the integer value, but should be "PERSISTENT" or "NON_PERSISTENT" string literals.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:06 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-143) Load the icon of a
 paletteContribution entry from the plugin directory where it is defined
In-Reply-To: <28132773.1186761253835.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29101365.1192446066085.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-143?page=all ]

Koen Aers updated GPD-143:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.alpha1

> Load the icon of a paletteContribution entry from the plugin directory where it is defined
> ------------------------------------------------------------------------------------------
>
>                 Key: GPD-143
>                 URL: http://jira.jboss.com/jira/browse/GPD-143
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>
> In PaletteRoot class, the icon of a palette entry is always loaded from org.jbpm.gd.jpdl plugin, even if the paletteContribution entry is defined in a dependent plugin.
> The information, where the palette entry element (entryElement in PaletteRoot.addControls) is defined, can be found in entryElement.getContributor().getName().
> So also the corresponding image can be loaded from the correct bundle.
> [ Sorry to only give a verbal description of the implementation. I would sign a corporate contributor's agreement, but I have problems with the procedure, e.g.
> - do we need a corporate jboss account for my boss to sign
> - if we sign with the "corporate" account, with which account I need to contribute then
> etc.
> So I would need some assistance here. Then you would get a real diff also.
> ]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1102) JBM should
 use
 TransactionManagerLocator instead of the MBean API as that is being removed
 from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26225400.1192446066216.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Tim Fox reopened JBMESSAGING-1102:
----------------------------------

             

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:01:06 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:01:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-35) enhancement drawing
	transitions
In-Reply-To: <9729958.1168962532978.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24562680.1192446066373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-35?page=all ]

Koen Aers updated GPD-35:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> enhancement drawing transitions
> -------------------------------
>
>                 Key: GPD-35
>                 URL: http://jira.jboss.com/jira/browse/GPD-35
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> When the mousepointer is in the outer area of a node/state/task/.... but within it's boundaries, it should be possible to draw a transition. This is makes using the gpd a lot faster (not switching in the toolbar)
> Maybe it should only be in the 'middle areas' of top, bottom, left and right and not the corners

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:03:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-149) Creating tasks by
 editing XML source will prevent the XML file from being re-opened
In-Reply-To: <5015540.1187215741100.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26636521.1192446183414.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-149?page=all ]

Koen Aers updated GPD-149:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Creating tasks by editing XML source will prevent the XML file from being re-opened
> -----------------------------------------------------------------------------------
>
>                 Key: GPD-149
>                 URL: http://jira.jboss.com/jira/browse/GPD-149
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: Eclipse 3.3, Designer 3.1.0 CR
>            Reporter: Jeff Wang
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> When you create new tasks by editing the source, it will break the process definition and not allow you to re-open it in Eclipse.
> Steps to recreate:
> 1) Create a new process definition
> 2) Create a task node using the GUI
> 3) Switch to the source tab
> 4) Copy the task xml tag
> 5) Rename the task name to something unique
> 6) Close the file
> 7) Re-open using the JBPM editor

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:03:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-156)
 GenericElementXmlAdapter doesnt add child nodes
In-Reply-To: <9558754.1188946691290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2161733.1192446183635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-156?page=all ]

Koen Aers updated GPD-156:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> GenericElementXmlAdapter doesnt add child nodes
> -----------------------------------------------
>
>                 Key: GPD-156
>                 URL: http://jira.jboss.com/jira/browse/GPD-156
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Imran Naqvi
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> If you have a template such as:
> <?xml version="1.0"?> 
> <process-definition name="Movie" version="11"> 
> <start-state name="Start"> 
> <transition to="Get MPEG Properties" /> 
> </start-state> 
> <node name="Get MPEG Properties"> 
> <action class="SomeActionHandler"><send>010901</send> 
> <keys> 
> <entry> 
>                                             <key>VarName</key> 
>                                             <value>1122</value> 
>                                 </entry> 
> </keys> 
> <receive> 
> <element>030101</element> 
> <element>030102</element> 
> </receive> 
> </action> 
> <transition to="End"/> </node> 
> <end-state name="End" /> 
> The nested Generic Elements arent added by the adapter. The reason for this is that the GenericElementXmlAdapter.doModelAdd() doesnt do anything. We need to add the following code to this method:
>                                            String type = child.getElementType();
> 		SemanticElement jpdlElement;
> 		jpdlElement = getSemanticElementFactory().createById("org.jbpm.gd.jpdl.genericElement");
> 		child.initialize(jpdlElement);
> 		GenericElement genericElement= (GenericElement )getSemanticElement();
> 		genericElement.addGenericElement((GenericElement)jpdlElement);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:03:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-98) GPD creates invalid
 gpd.xml when nodes contain special characters on Windows
In-Reply-To: <10767958.1182332992363.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32336959.1192446184341.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-98?page=all ]

Koen Aers updated GPD-98:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> GPD creates invalid gpd.xml when nodes contain special characters on Windows 
> -----------------------------------------------------------------------------
>
>                 Key: GPD-98
>                 URL: http://jira.jboss.com/jira/browse/GPD-98
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.0.13, jBPM JPDL Designer 3.1.0.alpha4
>         Environment: Windows XP, Eclipse 3.2.1
>            Reporter: Martin Putz
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: processdefintion.xml
>
>
> A process with a node containing a special character, such as <start-state name="D?but">, leads to an invalid gpd.xml. This is reproducible with the attached sample processdefinition.xml on a Windows machine.

-- 
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

       



From jira-events at lists.jboss.org  Mon Oct 15 07:03:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-162) Deploying a process
 does not pull in necessary Java classes
In-Reply-To: <31205902.1189443251838.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33118550.1192446184462.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-162?page=all ]

Koen Aers updated GPD-162:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Deploying a process does not pull in necessary Java classes
> -----------------------------------------------------------
>
>                 Key: GPD-162
>                 URL: http://jira.jboss.com/jira/browse/GPD-162
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> GPD 3.1.0.CR1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: websale.par
>
>
> When I try to deploy a process from the GPD, the class files referenced in the definition do not come across properly.
> 1) Modified an existing process (as per GPD 161).
> 2) Save the process. (.par will be attached)
> 3) Use the Deployment tab to deploy the updated process.
> 4) Execute the process and you get the following error:
> In the web page:
> Error completing task: An exception of type "org.jbpm.graph.def.DelegationException" was thrown.
> On the console:
> 12:48:35,403 ERROR [Delegation] couldn't instantiate delegation class 'org.jbpm.websale.DeciderHandler'
> java.lang.NullPointerException
>         at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105)
>         at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:48)
>         at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:163)
>         at org.jbpm.instantiation.Delegation$$FastClassByCGLIB$$6bae1598.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.instantiation.Delegation$$EnhancerByCGLIB$$a8c02805.instantiate(<generated>)
>         at org.jbpm.graph.node.Decision.execute(Decision.java:87)
>         at org.jbpm.graph.def.Node.enter(Node.java:318)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.enter(<generated>)
>         at org.jbpm.graph.def.Transition.take(Transition.java:151)
>         at org.jbpm.graph.def.Node.leave(Node.java:393)
>         at org.jbpm.graph.node.StartState.leave(StartState.java:70)
>         at org.jbpm.graph.def.Node$$FastClassByCGLIB$$d187eeda.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$2abd72ab.leave(<generated>)
>         at org.jbpm.graph.exe.Token.signal(Token.java:194)
>         at org.jbpm.graph.exe.Token.signal(Token.java:139)
>         at org.jbpm.graph.exe.Token$$FastClassByCGLIB$$74df1c6e.invoke(<generated>)
>         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
>         at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:163)
>         at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$5a16e027.signal(<generated>)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:476)
>         at org.jbpm.taskmgmt.exe.TaskInstance.end(TaskInstance.java:390)
>         at org.jbpm.jsf.core.action.CompleteTaskActionListener.handleAction(CompleteTaskActionListener.java:47)
>         at org.jbpm.jsf.core.impl.JbpmActionListenerWrapper.processAction(JbpmActionListenerWrapper.java:82)
>         at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
>         at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:758)
>         at javax.faces.component.UICommand.broadcast(UICommand.java:368)
>         at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.broadcast(UITaskFormButtonBase.java:56)
>         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
>         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
>         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
>         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
>         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
>         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
>         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
>         at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
>         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
>         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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-170) misspelling: Assignmnet
In-Reply-To: <814774.1190993382986.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20559218.1192446303471.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-170?page=all ]

Koen Aers updated GPD-170:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> misspelling: Assignmnet
> -----------------------
>
>                 Key: GPD-170
>                 URL: http://jira.jboss.com/jira/browse/GPD-170
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Chris Whalen
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> "Assignment" misspelled on task and swimlane configuration tabs.
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/TaskConfigurationComposite.java   and
> jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/jpdl/properties/SwimlaneConfigurationComposite.java

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28954024.1192446304291.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

Koen Aers updated GPD-169:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-168) feature not recognized
In-Reply-To: <16678191.1189763591402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1388539.1192446304460.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-168?page=all ]

Koen Aers updated GPD-168:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> feature not recognized
> ----------------------
>
>                 Key: GPD-168
>                 URL: http://jira.jboss.com/jira/browse/GPD-168
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Java 1.5, Eclipse Europa, JBoss Tools 2.0 beta3, Seam 2.0 beta1
>            Reporter: Joachim Neubert
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: ein.txt
>
>
> After deleting the CR feature and plugin directories and installing the GA as described in readme.html, the org.jbpm.gd.jpdl.feature is not recognized by Eclipse.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:05:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-161) Overwriting a node in
 the source yields an out-of-sync diagram
In-Reply-To: <28293293.1189441931051.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33037812.1192446305079.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-161?page=all ]

Koen Aers updated GPD-161:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Overwriting a node in the source yields an out-of-sync diagram
> --------------------------------------------------------------
>
>                 Key: GPD-161
>                 URL: http://jira.jboss.com/jira/browse/GPD-161
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: RHEL 5
> 3.1.0cr1
>            Reporter: Micah Modell
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: cheat.txt, processdefinition.xml, websale.par
>
>
> I edited the source xml by pasting in the Decision Node from the cheat.txt (attached) over the "Evaluate web order" found in the example websale process.  When I switched back to visual mode, I found an unattached Decision Node with no name and the "Evaluate web order" remained as before.
> I'll attach the before and after JPDL as well as the substitution text after I open this bug.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:07:21 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:07:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-65) Would it possible to
 take parameters
 from an abstract super class of the Delegation class in the GPD?
In-Reply-To: <9401534.1174487808759.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18214342.1192446441714.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-65?page=all ]

Koen Aers updated GPD-65:
-------------------------

    Fix Version/s: jBPM jPDL Designer 4.0.x

> Would it possible to take parameters from an abstract super class of the Delegation class in the GPD?
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GPD-65
>                 URL: http://jira.jboss.com/jira/browse/GPD-65
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>         Environment: Eclipse (Windows XP)
>            Reporter: Nicolas Arnaud
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 4.0.x
>
>
> I have a problem with my AssignHandler class 
> I want to have a generic abstract class wich implements AssignHandler Other class extend this class 
> I put the parameters in my abstract class, but with the GPD, when I use Delegation to associate the sub-class to a Task, I can't get the parameters. 
> Would it possible to take parameters from the abstract super class of the Delegation class?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:07:21 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:07:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1089) Upgrade to
	JGroups 2.5
In-Reply-To: <1009337.1191323463272.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27963615.1192446441838.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1089?page=all ]

Tim Fox updated JBMESSAGING-1089:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                       (was: 1.4.0.SP1)

> Upgrade to JGroups 2.5
> ----------------------
>
>                 Key: JBMESSAGING-1089
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1089
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> Update to JGroups 2.5 to take advantage of better throughput.
> We need to ensure the post office code is sufficiently thread safe.
> We may need to do another release for 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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16745314.1192446543650.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=all ]

Tim Fox updated JBMESSAGING-1084:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                       (was: 1.4.0.SP1)

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 07:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as that is being removed
 from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26483543.1192446543872.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Tim Fox updated JBMESSAGING-1102:
---------------------------------

    Fix Version/s:     (was: 1.4.0.SP1)

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-176) Add code completion
 inside attributes and values within the xml source
In-Reply-To: <32030443.1192185004070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13990763.1192446663279.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-176?page=all ]

Koen Aers updated GPD-176:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Add code completion inside attributes and values within the xml source
> ----------------------------------------------------------------------
>
>                 Key: GPD-176
>                 URL: http://jira.jboss.com/jira/browse/GPD-176
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-177) Add code completion in
 the text input fields on the properties view
In-Reply-To: <10554814.1192185123592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20721062.1192446663380.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-177?page=all ]

Koen Aers updated GPD-177:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Add code completion in the text input fields on the properties view
> -------------------------------------------------------------------
>
>                 Key: GPD-177
>                 URL: http://jira.jboss.com/jira/browse/GPD-177
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-16) moving nodes around
	corrupts process
In-Reply-To: <24369874.1168951377529.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30450926.1192446663468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-16?page=all ]

Koen Aers updated GPD-16:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> moving nodes around corrupts process
> ------------------------------------
>
>                 Key: GPD-16
>                 URL: http://jira.jboss.com/jira/browse/GPD-16
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> in the XML i moves some nodes around. that lead to a corrupted graphical view. i tried to delete the whole gpd.xml content (and then the whole) file in the hope that the graphical content would be restored, but instead i lost the content of the processdefinition.xml and had to start all over again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:11:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-27) Make transitions
 identifiable by position
In-Reply-To: <26589236.1168956532704.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29815328.1192446663541.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-27?page=all ]

Koen Aers updated GPD-27:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Make transitions identifiable by position
> -----------------------------------------
>
>                 Key: GPD-27
>                 URL: http://jira.jboss.com/jira/browse/GPD-27
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Try and implement a strategy where transitions are identified by their position in the list of transitions rather than by a name. This should be done to eliminate the need for a transition name. When this is done the bendpoints in the gpd.xml file can be associated with their transition based on the position.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-67) GPD support for editing
 non-files (any IEditorInput, not just FileEditorInput)
In-Reply-To: <17125585.1175836378572.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24664447.1192446783593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-67?page=all ]

Koen Aers updated GPD-67:
-------------------------

    Fix Version/s: jBPM jPDL Designer 4.0.x

> GPD support for editing non-files (any IEditorInput, not just FileEditorInput)
> ------------------------------------------------------------------------------
>
>                 Key: GPD-67
>                 URL: http://jira.jboss.com/jira/browse/GPD-67
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: John Ruud
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 4.0.x
>
>
> We need to edit process defs that are stored in a DB, as opposed to the processdefinition.xml, gpd.xml files stored in the workspace. There are currently many dependencies to FileEditorInput/File throughout GPD (as is the case for a lot of other Eclipse editors BTW).
> It would be very helpful if it would be feasible to separate out the code that deals with a particular type of IEditorInput from the rest of the editor, possibly into a separete delegate class. For FileEditorInput the delegate would deal with reading, writing, and syncronizing the view (resource listeners), plus whatever else I may have forgotten. We could then replace the default "file" delegate with our own that knows how to deal our DB (by subclassing of the editor would be fine). 
> Probably not the #1 GPD issue for many other users, but hopefully something you would keep in mind...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-123) Ability to zoom
In-Reply-To: <18835035.1185455627463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2891026.1192446783734.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-123?page=all ]

Koen Aers updated GPD-123:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Ability to zoom
> ---------------
>
>                 Key: GPD-123
>                 URL: http://jira.jboss.com/jira/browse/GPD-123
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta1
>            Reporter: Matthew Sandoz
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> It would be nice especially for large flows to be able to zoom in and out of the process designer view.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-134) form file names
 generated from the task dialogue are unstable
In-Reply-To: <9189503.1186477849412.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12997119.1192446784375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-134?page=all ]

Koen Aers updated GPD-134:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> form file names generated from the task dialogue are unstable
> -------------------------------------------------------------
>
>                 Key: GPD-134
>                 URL: http://jira.jboss.com/jira/browse/GPD-134
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta1
>         Environment: osx macbook pro, eclipse 3.3.0
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> the form names generated from the task dialogue are sensitive to content...
> 'fbm-rejects.xhtml' is ok, and is stored in the DB fine when deployed,
> 'fbm-rejects-psr.xhtml' is not stored in the DB when deployed and therefore the form does not display within the jbpm-console
> the DB schema says the name field is varchar(255), which suggests that perhaps the second hyphen in the name is causing a problem somewhere

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:13:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-146) improve feedback when
 creating self referencing transitions
In-Reply-To: <14993915.1187097560953.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20590013.1192446784592.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-146?page=all ]

Koen Aers updated GPD-146:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> improve feedback when creating self referencing transitions
> -----------------------------------------------------------
>
>                 Key: GPD-146
>                 URL: http://jira.jboss.com/jira/browse/GPD-146
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> At the moment creating self referencing transitions is done by clicking twice on the source/target node. In the future some feedback (a dummy transition) should make this proces more obvious

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-138) error dialogue appears
 on task panel of properties for task node
In-Reply-To: <21642934.1186578244471.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32881218.1192446903556.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-138?page=all ]

Koen Aers updated GPD-138:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> error dialogue appears on task panel of properties for task node
> ----------------------------------------------------------------
>
>                 Key: GPD-138
>                 URL: http://jira.jboss.com/jira/browse/GPD-138
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta1
>         Environment: os x macbok pro, eclipse 3.3.0
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: stacktrace.txt
>
>
> Hi,
> when working with the designer in eclipse, if I put a new task node on the screen, immediately enter a value against the name on the 'general' panel under properties, then click on the tasks panel under properties, I get an error dialogue with the following details :
> Reason:
> 0
> 'An error has occurred. See error log for more details.
> 0
> On the other hand, if after entering a name, I click on the description input field, but do not enter anything, then click on the task panel under properties, there is no error.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-150) In-place label edit
 box offset in scrolled editor
In-Reply-To: <33534539.1187343121259.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14208971.1192446904561.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-150?page=all ]

Koen Aers updated GPD-150:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> In-place label edit box offset in scrolled editor
> -------------------------------------------------
>
>                 Key: GPD-150
>                 URL: http://jira.jboss.com/jira/browse/GPD-150
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: Eclipse 3.3, Windows XP SP2, JDK 6
>            Reporter: David Good
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: screenshot-1.jpg
>
>
> When editing a diagram larger than the editor window, clicking on a node label causes the edit box to appear in an offset position if the scroll bars are not in the origin. (see attachment)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-151) entries in mail node
 subject and
 body elements disappear depending on click order before save
In-Reply-To: <17748603.1187967378477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3730940.1192446904695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-151?page=all ]

Koen Aers updated GPD-151:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> entries in mail node subject and body elements disappear depending on click order before save
> ---------------------------------------------------------------------------------------------
>
>                 Key: GPD-151
>                 URL: http://jira.jboss.com/jira/browse/GPD-151
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>         Environment: os x, eclipse 3.3.0, 
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> when I enter text in a mail node 'subject' input box, if I just click straight on the save button in eclipse, I lose the text entered...
> the same is true of the 'body' input box on the mail node
> to get this process to work I need to enter my text in the 'subject' input box, then click on the body input box, then click on the save button on the toolbar, this ensures my entry is in fact saved

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-158) Have the
 formsgenerator put a required attribute on jsf components
In-Reply-To: <14285454.1188998591044.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9699851.1192446904828.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-158?page=all ]

Koen Aers updated GPD-158:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.3

> Have the formsgenerator put a required attribute on jsf components
> ------------------------------------------------------------------
>
>                 Key: GPD-158
>                 URL: http://jira.jboss.com/jira/browse/GPD-158
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: James Baxter
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.3
>
>
> Tasks can have variables specified as 'required'. This is not built into the taskform, the forms are missing the following attribute from the h:input tag:
> [code]
> required="true"
> [/code]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:04 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-167) Diagram should not
 scroll after adding nodes from palette
In-Reply-To: <26566612.1189755791340.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16757867.1192446904967.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-167?page=all ]

Koen Aers updated GPD-167:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> Diagram should not scroll after adding nodes from palette
> ---------------------------------------------------------
>
>                 Key: GPD-167
>                 URL: http://jira.jboss.com/jira/browse/GPD-167
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>            Reporter: John Ruud
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> After adding nodes from the palette to diagrams where the scroll-bars are not in the top left corner position, the diagram will automatically scroll (to the top-left position). This is not desirable IMO, as it makes it easy to loose track of just-added nodes for large diagrams.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:15:05 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:15:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-154) process image rendered
 incorrectly for large process definition
In-Reply-To: <2916967.1186754521287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4668547.1192446905267.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-154?page=all ]

Koen Aers updated GPD-154:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> process image rendered incorrectly for large process definition
> ---------------------------------------------------------------
>
>                 Key: GPD-154
>                 URL: http://jira.jboss.com/jira/browse/GPD-154
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>         Environment: mac osx,  tomcat 5.0.28
>            Reporter: Ross McDonald
>         Assigned To: Tom Baeyens
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> Hi,
> then I create a large process, and extend to the left beyond the original boundary, by placing and element in the designer and dragging, so scrollbars appear, the image when rendered in the console is offset incorrectly while on any given node,
> cheers
> Ross

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:17:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-14) Lay out Algorithm
In-Reply-To: <763449.1168949213846.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18908090.1192447023638.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-14?page=all ]

Koen Aers updated GPD-14:
-------------------------

    Fix Version/s: jBPM jPDL Designer 3.2.0.GA

> Lay out Algorithm
> -----------------
>
>                 Key: GPD-14
>                 URL: http://jira.jboss.com/jira/browse/GPD-14
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>            Priority: Minor
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> Integrate a layout algorithm that is used when users add nodes to the xml directly to lay out the newly created components in an orderly fashion on the graphical canvas.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:17:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 07:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-140) when working with
 large process
 definitions, screen jumps to top whenever new nodes added in designer
In-Reply-To: <12103377.1186742271676.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9821009.1192447023785.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-140?page=all ]

Koen Aers updated GPD-140:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.1

> when working with large process definitions, screen jumps to top whenever new nodes added in designer
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GPD-140
>                 URL: http://jira.jboss.com/jira/browse/GPD-140
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.beta2
>         Environment: osx macbook pro, eclipse 3.3.0, designer plugin 3.1.0 beta 1, beta 2, CR1
>            Reporter: Ross McDonald
>         Assigned To: Koen Aers
>            Priority: Trivial
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> Hi,
> when working with large process diagrams, if I am scrolled down to the bottom of the view, and add a new node, when the screen is updated it jumps back up to the top, so I need to scroll down again.
> Obviously when adding many nodes, this costs time, its just a trivial thing.
> Cheers
> Ross

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:38:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 15 Oct 2007 07:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBSER-97)
 RegularObjectPersister.readSlotWithFields to log number of fields being
 read
Message-ID: <32246194.1192448283370.JavaMail.jira@cloud.prod.atl2.jboss.com>

RegularObjectPersister.readSlotWithFields to log number of fields being read
----------------------------------------------------------------------------

                 Key: JBSER-97
                 URL: http://jira.jboss.com/jira/browse/JBSER-97
             Project: JBoss Serialization
          Issue Type: Task
    Affects Versions: 1.0.3 GA
            Reporter: Galder Zamarreno
         Assigned To: Clebert Suconic
            Priority: Minor


writeSlotWithFields logs the slot name and number of fields to be written.

for debugging pupouses, readSlotWithFields could do with logging the number of fields written too, i.e.

RegularObjectPersister.readSlotWithFields() to start like this:

     short numberOfFields = (short)fieldsKey.length;

      if (isDebug)
      {
         log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName() + " and " + numberOfFields + " fields");
      }

instead of:

       if (isDebug)
       {
          log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName());
       }

       //final int numberOfFields = input.readShort();
      short numberOfFields = (short)fieldsKey.length;

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:40:30 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 15 Oct 2007 07:40:30 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11366225.1192448430259.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382414 ] 
            
Chris Laprun commented on JBPORTAL-1747:
----------------------------------------

I think that there should only be one guide that shows the GUI way and the XML way (which is actually expected to progressively disappear) in the same place. It doesn't make much sense to separate that information: why should an admin look at 2 different places to learn everything there is to know about Portal? Chapters could be structured with an overview, then how to proceed in the GUI then a more detailed look (if required). This is kind of the approach I took with the WSRP chapter and I think it works quite well. Moreover, looking at the reference guide, there are already some coverage of the GUI so it's kind of confusing that not everything is in there.

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 07:49:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 07:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1747) Merge user
 guide and reference guide
In-Reply-To: <28268849.1192230423488.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24515743.1192448943498.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1747?page=comments#action_12382416 ] 
            
Thomas Heute commented on JBPORTAL-1747:
----------------------------------------

Ok, i misread...

I though you were talking about userGuide and Quickstartguide merging :(

Yes i agree we could merge those 2

> Merge user guide and reference guide
> ------------------------------------
>
>                 Key: JBPORTAL-1747
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1747
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Chris Laprun
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4856) Fix web service
 issues related to the new metadata model
Message-ID: <28485098.1192452063304.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix web service issues related to the new metadata model
--------------------------------------------------------

                 Key: JBAS-4856
                 URL: http://jira.jboss.com/jira/browse/JBAS-4856
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:49:16 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:49:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4857) NPE in
 ContainerConfigurationMetaDataWrapper
Message-ID: <29114130.1192452556750.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in ContainerConfigurationMetaDataWrapper
--------------------------------------------

                 Key: JBAS-4857
                 URL: http://jira.jboss.com/jira/browse/JBAS-4857
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark


[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test

getContainerConfigurations returns null

      configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
            defaults.getContainerConfigurations());


Caused by: java.lang.NullPointerException
        at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:57:15 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:57:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5486656.1192453035963.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4855?page=comments#action_12382447 ] 
            
Thomas Diesler commented on JBAS-4855:
--------------------------------------

You should be able to see this when you change the jboss-web.xml for the jmx-console


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 08:59:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 15 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <29506450.1192445132240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6610902.1192453143284.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4855?page=comments#action_12382449 ] 
            
Thomas Diesler commented on JBAS-4855:
--------------------------------------

14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:01:03 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 15 Oct 2007 09:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-472) Wrappers lack the
 generic type information
In-Reply-To: <5055386.1191269501072.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1261007.1192453263831.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-472?page=all ]

Flavia Rainone closed JBAOP-472.
--------------------------------

    Resolution: Done

Notice that this affects only @Arg and @Return-annotated parameters.

The wrappers are not of too much use when it comes to @Target types, and to @Caller types.

Regarding @Thrown, we can test it know due to the fact that currently the type of a @Thrown-annotated advice parameter is forced to be Throwable, which is not a parameterized type.

> Wrappers lack the generic type information
> ------------------------------------------
>
>                 Key: JBAOP-472
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-472
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> This issue has already been fixed by Kabir with method wrappers.
> This task consists of fixing the issue for all other joinpoint types.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 09:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1079) JBM should call
 BytesMessage.reset() before redelivery, or not redeliver the same message
 instance
In-Reply-To: <25829200.1190706077396.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14182746.1192453504583.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1079?page=all ]

Tim Fox closed JBMESSAGING-1079.
--------------------------------

    Resolution: Done

> JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1079
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1079
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0 CR3
>         Environment: $ java -version
> java version "1.5.0_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
> Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
> The unit tests have been run using the postgresql provider with PostgreSQL 8.1.4.
>            Reporter: Julian Scheid
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>         Attachments: RedeliveryResetTest.java
>
>
> Consider the following sequence of events:
> - a durable subscriber subscribes to a topic with client acknowledgment
> - a BytesMessage is sent to that topic
> - the durable subscriber receives the message and reads its contents completely using BytesMessage.readBytes(byte[])
> - the connection is closed without the subscriber acknowledging the message
> - the subscriber re-subscribes and re-receives the message
> - the subscriber re-reads the contents of the message using BytesMessage.readBytes(byte[])
> In this situation, the second call to readBytes will not return any data (it will return -1 to indicate EOF and no data will be copied to the byte array passed in), unless the message is explicitly reset() by the client first.
> This can be verified by the unit test that I am going to attach.
> The JMS 1.1 specification isn't entirely clear on whether the provider is required to reset a message in this situation.
> However, the spec says in section 3.10, "Changing the Value of a Received Message"
> "If the consumer modifies a received message, and the message is subsequently redelivered, the redelivered message must be the original, unmodified message [...]"
> Here, I would interpret changing the BytesMessage's internal stream pointer as a side-effect of reading its data to be a modification.
> Furthermore, the API docs for javax.jms.BytesMessage say
> "The same message object can be sent multiple times. When a message has been received, the provider has called reset so that the message body is in read-only mode for the client."
> (see http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/BytesMessage.html#reset() )
> This also sounds to me like a client could expect that the reset() method has been called when receiving it, regardless of whether it has been received before.
> Even if I am misreading the spec and it is not the provider's responsibility to reset the message in the interim, there are clients out there (e.g. StompConnect - see my corresponding ticket at http://jira.codehaus.org/browse/STOMP-5 ) that do expect this behavior, and so in the spirit of the Robustness Principle ("Be conservative in what you do; be liberal in what you accept from others") I would suggest to implement this behavior regardless.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:05:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 09:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1101) Failure to
 deserialize BytesMessage contents
In-Reply-To: <15212112.1192075143358.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21051765.1192453504876.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1101?page=all ]

Tim Fox closed JBMESSAGING-1101.
--------------------------------

    Resolution: Done

> Failure to deserialize BytesMessage contents
> --------------------------------------------
>
>                 Key: JBMESSAGING-1101
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1101
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-4.2.1.GA, jboss-remoting 2.2.2.SP1-brew, 7 node cluster
>            Reporter: Travis Brown
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> BytesMessage consumers often receive the following error:
> Client side:
> 2007-10-09 06:54:12,076 [WorkerThread#1[10.7.68.52:2209]] ERROR ServerThread  - Worker thread initialization failure
> java.io.EOFException
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:530)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> Server side:
> 2007-10-09 06:54:12,071 ERROR [org.jboss.jms.wireformat.JMSWireFormat] Failed to write packet
> java.lang.RuntimeException: Unknown type: 76
>         at org.jboss.messaging.util.StreamUtils.readObject(StreamUtils.java:159)
>         at org.jboss.messaging.core.impl.message.MessageSupport.readPayload(MessageSupport.java:435)
>         at org.jboss.messaging.core.impl.message.MessageSupport.getPayload(MessageSupport.java:264)
>         at org.jboss.jms.message.JBossBytesMessage.getPayloadAsByteArray(JBossBytesMessage.java:592)
>         at org.jboss.messaging.core.impl.message.MessageSupport.write(MessageSupport.java:369)
>         at org.jboss.jms.message.JBossMessage.write(JBossMessage.java:1048)
>         at org.jboss.jms.wireformat.ClientDelivery.write(ClientDelivery.java:91)
>         at org.jboss.jms.wireformat.JMSWireFormat.write(JMSWireFormat.java:237)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:983)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:559)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invokeOneway(Client.java:598)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:815)
>         at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:686)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1494)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.replicateDeliveryResponseReceived(ServerSessionEndpoint.java:1094)
>         at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.handleReplicateDeliveryAck(MessagingPostOffice.java:1274)
>         at org.jboss.messaging.core.impl.postoffice.ReplicateDeliveryAckMessage.execute(ReplicateDeliveryAckMessage.java:54)
>         at org.jboss.messaging.core.impl.postoffice.GroupMember$DataReceiver.receive(GroupMember.java:582)
>         at org.jgroups.JChannel.up(JChannel.java:1102)
>         at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:382)
>         at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:398)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FRAG2.up(FRAG2.java:197)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FC.up(FC.java:422)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.GMS.up(GMS.java:768)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.protocols.pbcast.GMS.receiveUpEvent(GMS.java:788)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:258)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:516)
>         at org.jgroups.protocols.UNICAST.up(UNICAST.java:242)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:569)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:170)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD.up(FD.java:300)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.MERGE2.up(MERGE2.java:162)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.Discovery.up(Discovery.java:225)
>         at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:470)
>         at org.jgroups.stack.Protocol.passUp(Protocol.java:520)
>         at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
>         at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
>         at org.jgroups.protocols.TP.access$400(TP.java:45)
>         at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
>         at java.lang.Thread.run(Thread.java:595)
> In MessageSupport.getPayload(MessageSupport.java:264), if payload == null, it attempts to deserialize the byte array, which in this case is the content of the BytesMessage. StreamUtils.readObject(StreamUtils.java:159) will report "Unknown type" followed by the value of the first byte of the BytesMessage payload. (This could be misinterpreted during deserialization if the first byte happens to match a constant.)
> I am not sure how to recreate the test case yet (payload is perhaps typically non-null), but it happens frequently in our environment, where the BytesMessage is 95% of the traffic.
> This fix resolves the issue in our environment:
> diff -r org/jboss/jms/message/JBossBytesMessage.java
> 592c592
> <       return (byte[])getPayload();
> ---
> >       return (byte[])getBytesMessagePayload();
> diff -r org/jboss/messaging/core/impl/message/MessageSupport.java
> 281a282,303
> > 	public synchronized Object getBytesMessagePayload()
> > 	{
> > 		if (payload != null)
> > 		{
> > 			return payload;
> > 		}
> > 		else if (payloadAsByteArray != null)
> > 		{
> > 			payload = payloadAsByteArray;
> > 			payloadAsByteArray = null;
> >   	  return payload;
> > 		}
> > 		else
> > 		{
> > 			return null;
> > 		}
> > 	}
> > 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:07:04 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Mon, 15 Oct 2007 09:07:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-415) Advice Matching
 algorithm is ignoring generics
In-Reply-To: <25286165.1181706071627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27068144.1192453624742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-415?page=all ]

Flavia Rainone closed JBAOP-415.
--------------------------------

    Resolution: Done

Generics information cannot currently be retrieved for @Target and @Caller.

To understand why, consider the following class:

public class MyClass<A>
{
    public void method()
    {}
}

When we intercept an execution of method, we have access to a target of type MyClass. To know the generics type of the target, we would need some method like Object.getType(), which we do not have.

The same explanation goes to @Caller on call pointcuts.

And for @Target on call joinpoints, we would also need some way to know the type of the object being called. Despite the difference that now we are in the context of the call, and not inside the method being executed, we cannot access the generics target type information for the same reasons as we cant in a method execution joinpoint.

> Advice Matching algorithm is ignoring generics
> ----------------------------------------------
>
>                 Key: JBAOP-415
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-415
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Advice Matching does not takes into account generic types; it is working with the old reflection API instead (Class instead of Type).
> To modifiy this, we need to update code in classes:
> - org.jboss.aop.advice.annotation.AdviceInfo
> - org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo
> - org.jboss.aop.advice.AdviceMethodProperties
> - joinpoint generators that pass the return, arguments and exception types to AdviceMethodProperties instances.
> This includes updating the assignability degree algorithm of org.jboss.aop.advice.annotation package.
> The methods for this task are partly written in org.jboss.test.aop.beforeafterArgs.ArgAspectGenerics.
> Tests for generic return types are also necessary, and need to be written.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:33:21 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 09:33:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-155) secure the gpd
	deployment servlet
In-Reply-To: <684538.1181894171603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20892072.1192455201333.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-155?page=all ]

Koen Aers updated GPD-155:
--------------------------

    Fix Version/s: jBPM jPDL Designer 3.1.4
                       (was: jBPM jPDL Designer 3.1.1)

> secure the gpd deployment servlet
> ---------------------------------
>
>                 Key: GPD-155
>                 URL: http://jira.jboss.com/jira/browse/GPD-155
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Tom Baeyens
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.4
>
>
> the gpd deployment servlet should be secured.  the gpd should add authentication information in the url like e.g. http://gpd:gpd:localhost/jbpm-console/upload or something like that.  then the users will be able to control the authorization through the web interface itself.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 09:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 15 Oct 2007 09:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24085504.1192456743389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=all ]

Manik Surtani resolved JBCACHE-1192.
------------------------------------

    Resolution: Done

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication, Eviction
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6, 2.1.0.CR1, 2.1.0.GA
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 10:07:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 15 Oct 2007 10:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1753) Align WSRP with
	WS 2.0
Message-ID: <3188765.1192457223550.JavaMail.jira@cloud.prod.atl2.jboss.com>

Align WSRP with WS 2.0
----------------------

                 Key: JBPORTAL-1753
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1753
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal WSRP
    Affects Versions: 2.6.2 Final
            Reporter: Thomas Heute
         Assigned To: Chris Laprun
             Fix For: 2.6.3 Final


At least portal-wsrp.jse must be renamed portal-wsrp.war.

There are also some WARN when you start WSRP on JBoss AS 4.2.2.GA

15:49:57,971 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_ServiceDescription_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null
15:49:58,920 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Markup_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null
15:49:59,827 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_PortletManagement_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null
15:50:01,753 WARN  [ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef

serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Registration_PortType
 portQName=null
 enableMTOM=false
 portComponentLink=null
 callProperties=[]
 stubProperties=[]
 configName=null
 configFile=null 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 10:28:15 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 15 Oct 2007 10:28:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-156)
 GenericElementXmlAdapter doesnt add child nodes
In-Reply-To: <9558754.1188946691290.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25320190.1192458495935.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-156?page=all ]

Koen Aers closed GPD-156.
-------------------------

    Resolution: Done

The fix was applied to HEAD. Thanks for the contribution and sorry for the delay. Feel free to reopen if there are still problems.

> GenericElementXmlAdapter doesnt add child nodes
> -----------------------------------------------
>
>                 Key: GPD-156
>                 URL: http://jira.jboss.com/jira/browse/GPD-156
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.CR
>            Reporter: Imran Naqvi
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> If you have a template such as:
> <?xml version="1.0"?> 
> <process-definition name="Movie" version="11"> 
> <start-state name="Start"> 
> <transition to="Get MPEG Properties" /> 
> </start-state> 
> <node name="Get MPEG Properties"> 
> <action class="SomeActionHandler"><send>010901</send> 
> <keys> 
> <entry> 
>                                             <key>VarName</key> 
>                                             <value>1122</value> 
>                                 </entry> 
> </keys> 
> <receive> 
> <element>030101</element> 
> <element>030102</element> 
> </receive> 
> </action> 
> <transition to="End"/> </node> 
> <end-state name="End" /> 
> The nested Generic Elements arent added by the adapter. The reason for this is that the GenericElementXmlAdapter.doModelAdd() doesnt do anything. We need to add the following code to this method:
>                                            String type = child.getElementType();
> 		SemanticElement jpdlElement;
> 		jpdlElement = getSemanticElementFactory().createById("org.jbpm.gd.jpdl.genericElement");
> 		child.initialize(jpdlElement);
> 		GenericElement genericElement= (GenericElement )getSemanticElement();
> 		genericElement.addGenericElement((GenericElement)jpdlElement);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:05:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 15 Oct 2007 11:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25920044.1192460703605.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382498 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1112:
----------------------------------------------

Summary of the case:
1. 50  (and then 20) concurrent consumers overload the node they're connected to, rendering it useless (including making the JMX console inaccessible)
2. Killing and then restarting the server makes messages disappear

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:05:04 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 15 Oct 2007 11:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20416391.1192460704116.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382500 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

Since this is a release task, and as i am testing the version of jbossws already installed in AS (in this case, 2.0.1.SP2), i think i can ignore the undeploy and deploy tasks before running the test suite?
As far as the testsuite src is concerned should i be using jbossws/native/trunk or jbossws/tags/jbossws-native-2.0.1.SP2 ?



> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:05:04 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Mon, 15 Oct 2007 11:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <11549323.1192460704766.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]

Jeff Mesnil updated JBMESSAGING-375:
------------------------------------

    Attachment: patch-JBMESSAGING-375.txt

updated Stian's patch for JBoss Messaging 1.4.0 (based on r3190):
- base class is RoundRobinDistributor
- "grouping" round robin algorithm is done in GroupingRoundRobinDistributor
- associated tests are in GroupingRoundRobinDistributorTest
- put test code common to RRDTest and GroupingRRDTest into
  SimpleReferenceableReceiver class
- added support to reset bound receiver by setting JMSXGroupSeq to 0

some caveats:
- GroupingRRD's algorithm is brittle and depends on a lot of internals from
RRD which should not be exposed
  -> maybe grouping should be handled directly by RRD?
- GroupingRRD is not used by MessagingQueue (still using RRD)

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:13:04 2007
From: jira-events at lists.jboss.org (Paul Jackson (JIRA))
Date: Mon, 15 Oct 2007 11:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1279) Memory leak in
	release 4.0.2
Message-ID: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory leak in release 4.0.2
----------------------------

                 Key: JBRULES-1279
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
         Environment: tested with windows jdk5 and jdk6
            Reporter: Paul Jackson
         Assigned To: Mark Proctor


I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:

DroolsTest.java

import java.io.InputStreamReader;
import java.io.Reader;

import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.StatefulSession;
import org.drools.compiler.PackageBuilder;
import org.drools.rule.Package;

public class DroolsTest {

	public void run() throws Exception {
		
		RuleBase ruleBase = createRuleBase();

		long counter = 0;
		while(true) {
			StatefulSession session = ruleBase.newStatefulSession(false);
			if(++counter % 100 == 0) {
				System.out.println(counter);
			}
			session.dispose();
		}
	}
	
	private RuleBase createRuleBase() throws Exception {
		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );

		PackageBuilder builder = new PackageBuilder();
		builder.addPackageFromDrl( source );
		if ( builder.hasErrors() ) {
		    System.out.println( builder.getErrors().toString() );
		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
		}
		Package pkg = builder.getPackage();
		
		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
		ruleBase.addPackage( pkg );

		return ruleBase;
	}
	
	public static void main(String[] args) throws Exception {
		new DroolsTest().run();
	}
}

HelloWorld.drl

#list any import classes here.



#declare any global variables here




rule "Your First Rule"
	
	when
		#conditions
	then 
		#actions
		
end

rule "Your Second Rule"
	#include attributes such as "salience" here...
	when
		#conditions
	then 
		#actions
		
end

When I run this with release 4.0.1 I have to manually break the program to get it to stop.

When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:25:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 11:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26077558.1192461903429.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382509 ] 
            
Dimitris Andreadis commented on JBAS-4853:
------------------------------------------

I upgraded Branch_4_2 to jbossxb 1.0.0.SP1. 

Hopefully that will solve the regression seen by Thomas.

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:25:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 15 Oct 2007 11:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33009617.1192461903654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4853?page=all ]

Dimitris Andreadis closed JBAS-4853.
------------------------------------

    Resolution: Done

Thomas, please re-open if the problem persists.

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 11:49:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 15 Oct 2007 11:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21755702.1192463343391.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120411  (was: http://www.jboss.com/index.html?module=bb&op=viewforum&f=153)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:07:47 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Mon, 15 Oct 2007 12:07:47 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20234407.1192464467533.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4766?page=comments#action_12382530 ] 
            
Dominik Pospisil commented on JBAS-4766:
----------------------------------------

Confirming that this is fixed in JBossCache trunk.

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: buddy-sync-20s.tgz, driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:18:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Mon, 15 Oct 2007 12:18:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4858) SecurityDeployer
 changes with metadata
Message-ID: <15605108.1192465087771.JavaMail.jira@cloud.prod.atl2.jboss.com>

SecurityDeployer changes with metadata
--------------------------------------

                 Key: JBAS-4858
                 URL: http://jira.jboss.com/jira/browse/JBAS-4858
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Security
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For:  JBossAS-5.0.0.Beta3


The Security Deployer needs to be changed as per the following rant from Adrian


=============================
To me this is the wrong approach anyway.

There shouldn't be any code that does

if (ejbdeployment)
  doThis();
else if (webdeployment)
  doThat();
else if (unknowntype) // OOPS (pun intended  ;-) 
  cantDoIt();

The webservice deployers should be working off some generic metadata that triggers them to operate.

Then each type of deployment can populate that metadata to say "I want a webservice endpoint for this".

This is a seperate deployer for each type we know how to map to a webservice it takes the ejb/web/other metadata and maps or bridges it to the webservice metadata.

It shouldn't just be restricted to ejbs and wars.

e.g. An MBean should be capable of being an endpoint if there is a deployer that creates the relevant metadata attachment from say a META-INF/jboss-webservice.xml in the sar.

The security deployers take the same brain dead (non object orientated) approach.
============================================================

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 15 Oct 2007 12:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8905339.1192465203491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=comments#action_12382537 ] 
            
Manik Surtani commented on JBCACHE-1009:
----------------------------------------

A bit tricky at the moment since regions aren't a top level construct.  Caches are preloaded at startup, and these preload Fqns are loaded regardless of whether it is in an active region or not.  Then, *after* the cache starts, regions are defined as active or inactive.

I guess this approach does make some sense when defaultInactive is true, and cache loader preloads *only* happens when regions are activated.

Still though, moving to 3.0.0 once we have regions as a top level construct since the shape of all this may yet change.

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 15 Oct 2007 12:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27729935.1192465203615.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=all ]

Manik Surtani updated JBCACHE-1009:
-----------------------------------

    Fix Version/s: 3.0.0
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:52:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 15 Oct 2007 12:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4766) HTTP session
 replication failover failures with async buddy replication
In-Reply-To: <18409345.1191224141455.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7121210.1192467123354.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4766?page=comments#action_12382552 ] 
            
Brian Stansberry commented on JBAS-4766:
----------------------------------------

Actually that's fixed in current head of JBoss Cache branch 1.4.X; JBC trunk produces the 2.x releases and isn't being tested in these tests.

> HTTP session replication failover failures with async buddy replication
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4766
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4766
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: 4 nodes, buddy async replication, 100 clients
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: buddy-sync-20s.tgz, driver.log, server-perf01.log.gz, server-perf02.log.gz, server-perf03.log.gz, server-perf04.log.gz, test.log
>
>
> Sending test-logs of failed tests. Failed clients: 72, 96. For details please see attached log files.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:54:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 15 Oct 2007 12:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-295) Add unit tests for
 ReplicationQueue
Message-ID: <19003617.1192467243481.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-295?page=all ]

Brian Stansberry updated JBCACHE-295:
-------------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)

> Add unit tests for ReplicationQueue
> -----------------------------------
>
>                 Key: JBCACHE-295
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-295
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.2.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:54:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 12:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16450045.1192467243768.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=all ]

Andrew Rubinger updated EJBTHREE-1066:
--------------------------------------

    Workaround Description: 
Instead of using 2 <business-remote> nodes, use one with comma-delimited values ie:

<business-remote>org.jboss.ejb3.test.ejbthree1066.Adder,org.jboss.ejb3.test.ejbthree1066.Subtractor</business-remote>
                Workaround: [Workaround Exists]

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 12:59:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 15 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29144613.1192467543395.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=comments#action_12382556 ] 
            
Brian Stansberry commented on JBCACHE-1009:
-------------------------------------------

Yeah, should have made that clearer; assumption is defaultInactive = true. TBH, having region-based marshalling enabled and inactiveOnStartup=false doesn't really make sense; only useful for a corner case where someone would instantiate a cache, register some classloaders, and *then* start the cache (and even that might not work properly).  For 3.0 we might be better off getting rid of inactiveOnStartup as a config option.

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 13:07:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Mon, 15 Oct 2007 13:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-469) Make sure @Aspect
 works in older versions of AS
In-Reply-To: <21626519.1190893361105.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25000476.1192468023577.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-469?page=all ]

Kabir Khan reassigned JBAOP-469:
--------------------------------

    Assignee: Kabir Khan  (was: Stale Pedersen)

> Make sure @Aspect works in older versions of AS
> -----------------------------------------------
>
>                 Key: JBAOP-469
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-469
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.beta2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repackaging of the annotations stuff http://jira.jboss.com/jira/browse/JBAOP-428 has caused some problems. Create a simple test in the testsuite for https://svn.jboss.org/repos/jbossas/branches/Branch_4_2/ using @Aspect + @Bind, instead of a jboss-aop.xml file.
> If any classes are missing, add jars taken from jboss-container.jar to the AS 4.x deployers for both jdk 1.4 and jdk 5. There are some examples for this already in https://svn.jboss.org/repos/jbossas/projects/aop/trunk/build/build-release.xml
> JBoss 5 uses the correct version of MC, so all the classes will be available there.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 13:09:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Mon, 15 Oct 2007 13:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-469) Make sure @Aspect
 works in older versions of AS
In-Reply-To: <21626519.1190893361105.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14916855.1192468143266.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-469?page=all ]

Kabir Khan closed JBAOP-469.
----------------------------

    Resolution: Done

This should be fine, we already are creating a jboss-container-annotation.jar, and the ScopedUnitTestCase uses annotations already

> Make sure @Aspect works in older versions of AS
> -----------------------------------------------
>
>                 Key: JBAOP-469
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-469
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.beta2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repackaging of the annotations stuff http://jira.jboss.com/jira/browse/JBAOP-428 has caused some problems. Create a simple test in the testsuite for https://svn.jboss.org/repos/jbossas/branches/Branch_4_2/ using @Aspect + @Bind, instead of a jboss-aop.xml file.
> If any classes are missing, add jars taken from jboss-container.jar to the AS 4.x deployers for both jdk 1.4 and jdk 5. There are some examples for this already in https://svn.jboss.org/repos/jbossas/projects/aop/trunk/build/build-release.xml
> JBoss 5 uses the correct version of MC, so all the classes will be available there.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 14:05:03 2007
From: jira-events at lists.jboss.org (Chris Lee (JIRA))
Date: Mon, 15 Oct 2007 14:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4859) No facility to
 change location of Tomcat 'work' directory (catalina home)
Message-ID: <638196.1192471503492.JavaMail.jira@cloud.prod.atl2.jboss.com>

No facility to change location of Tomcat 'work' directory (catalina home)
-------------------------------------------------------------------------

                 Key: JBAS-4859
                 URL: http://jira.jboss.com/jira/browse/JBAS-4859
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.1.GA
         Environment: n/a
            Reporter: Chris Lee
         Assigned To: Remy Maucherat


Presently the location for Tomcat's 'work' directory is hard-coded to jboss.server.home.dir; it would be nice to override this (as is done with jboss.server.data.dir, jboss.server.log.dir, and jboss.server.temp.dir) to move 'data' directories outside the server home.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:11:04 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 15 Oct 2007 15:11:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1754) RoleModule
 documentation has duplicate code in identity chapter
Message-ID: <8051413.1192475464311.JavaMail.jira@cloud.prod.atl2.jboss.com>

RoleModule documentation has duplicate code in identity chapter
---------------------------------------------------------------

                 Key: JBPORTAL-1754
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1754
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun
         Assigned To: Boleslaw Dawidowicz




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:17:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 15:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Highly
 concurrent
 clients lock a JBM server node and apparently cause persistent messages to
 "dissapear"
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26250721.1192475823517.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382587 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

Large number of consumers appear fine *as long* supportsFailover on the connection factory is false.

When it is set to true, throughput dramtically drops. This implies a problem with session replication between nodes. Will investigate further.

> Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear"
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:20:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 15 Oct 2007 15:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1113) Post office
 and message updates at failover need to be transactional
Message-ID: <32831290.1192476003623.JavaMail.jira@cloud.prod.atl2.jboss.com>

Post office and message updates at failover need to be transactional
--------------------------------------------------------------------

                 Key: JBMESSAGING-1113
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Ovidiu Feodorov


At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.

If the failing over server is itself killed during this process, then the system can enter an inconsistent state.

Need to make sure all database updates are performed in a single transaction.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:26:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 15:26:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9316960.1192476364546.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=comments#action_12382590 ] 
            
Andrew Rubinger commented on EJBTHREE-1066:
-------------------------------------------

EnterpriseBean.remote and EnterpriseBean.local are overwritten in org.jboss.ejb3.metamodel.EjbJarDDObjectFactory.isEjbParentName() when more than one invocation is made (multiple "business-remote" or "business-local" nodes).

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:40:03 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Mon, 15 Oct 2007 15:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24440057.1192477203620.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Damien Delautre reopened JBRULES-1252:
--------------------------------------

             
When I have two function imports, only the last one is dumped.

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:42:03 2007
From: jira-events at lists.jboss.org (Damien Delautre (JIRA))
Date: Mon, 15 Oct 2007 15:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <538412.1192477323895.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Damien Delautre updated JBRULES-1252:
-------------------------------------

    Attachment: DrlDumper.patch

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2
>
>         Attachments: DrlDumper.patch, DrlDumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 15:42:07 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 15 Oct 2007 15:42:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1755) Identity chapter
 has lots of typos
Message-ID: <8667873.1192477327630.JavaMail.jira@cloud.prod.atl2.jboss.com>

Identity chapter has lots of typos
----------------------------------

                 Key: JBPORTAL-1755
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1755
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 16:05:03 2007
From: jira-events at lists.jboss.org (Frank Langelage (JIRA))
Date: Mon, 15 Oct 2007 16:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4860) List of Timers
 contains all SLSB and MDB, not only those implementing TimedObject
Message-ID: <1925938.1192478703269.JavaMail.jira@cloud.prod.atl2.jboss.com>

List of Timers contains all SLSB and MDB, not only those implementing TimedObject
---------------------------------------------------------------------------------

                 Key: JBAS-4860
                 URL: http://jira.jboss.com/jira/browse/JBAS-4860
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
         Environment: JBoss-4.2.2.GA, built from the current sources.
Sun JDK 1.5.0_13 on Sun Solaris 10 SPARC.
            Reporter: Frank Langelage
            Priority: Minor


If I call the listTimers operation using the jmx-console I see all Stateless session Beans and all Message Driven Beans now, but only 5 of this 64 are really TimeObjects:
Output is for example:
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MbiWaehrFacade]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-planning.jar,name=MbiProbfSelect]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-costing.jar,name=PreliminaryCosting]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-common.jar,name=Version]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=Calendar]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-inventory.jar,name=StockManagement]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-sales.jar,name=SalesOrder]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-sales.jar,name=SalesItem]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService]
handle: [id=1190398872277,target=[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService],first=21-Sep-2007 20:23:00.000,periode=60000]
[id=1190398872277,target=[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService],remaining=47564,periode=60000,in_timeout]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MbiFistaFacade]
[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MessageRetrieval]

MailService implements TimeObject, but all others do not.
My Stateful Session Beans don't appear in the list, but all Stateless and MDBs do.


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 16:39:03 2007
From: jira-events at lists.jboss.org (Danilo Guerra (JIRA))
Date: Mon, 15 Oct 2007 16:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1070) dlqhandler fails
 on
 redelivery for messages missing  the JMS property "JMSXDeliveryCount"
Message-ID: <24854922.1192480743296.JavaMail.jira@cloud.prod.atl2.jboss.com>

dlqhandler fails on redelivery for messages missing  the JMS property "JMSXDeliveryCount"
-----------------------------------------------------------------------------------------

                 Key: EJBTHREE-1070
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1070
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.1.GA
            Reporter: Danilo Guerra


GenericDLQHandler fails when handling redelivery of messages missing the property "JMSXDeliveryCount" when using non JbossMQ providers.

excerpt from the class: org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler

   protected boolean handleDelivery(Message msg)
   {
   .....
         try
         {
            if (msg.propertyExists(PROPERTY_DELIVERY_COUNT))
               count = msg.getIntProperty(PROPERTY_DELIVERY_COUNT) - 1;
         }
         catch (JMSException ignored)
         {
            count = incrementResentCounter(id);
         }
...
}

This code fails because the property PROPERTY_DELIVERY_COUNT is checked and the exception is never thrown. As a result the resent counter is not incremented and the message will not be sent to the DLQ.


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 15 Oct 2007 17:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25263483.1192483983474.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 1.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 15 Oct 2007 17:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26579506.1192483983688.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 2.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:33:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Mon, 15 Oct 2007 17:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25219704.1192483983926.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 3.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 17:37:41 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 17:37:41 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1060)
 getInvokedBusinessInterface doesn't return correct interface
In-Reply-To: <22610729.1191919853782.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22996228.1192484261848.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1060?page=comments#action_12382619 ] 
            
Andrew Rubinger commented on EJBTHREE-1060:
-------------------------------------------

Root of problem is org.jboss.ejb3.session.SessionContainer.getInvokedBusinessInterface() matching Remote invocations by method signature to implemented interfaces, incorrectly assuming that if a business interface contains the method invoked, than this interface was in turn invoked.  This is not the case with inheritance or if many interfaces dictate the same method signature.

> getInvokedBusinessInterface doesn't return correct interface
> ------------------------------------------------------------
>
>                 Key: EJBTHREE-1060
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>
> When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface.
> @Stateless
> @Remote({Remote1.class, Remote2.class})
> interface Remote1 extends CommonRemote
> interface Remote2 extends CommonRemote

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:41:04 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 15 Oct 2007 18:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-819) Consider removing
 dependency on jboss-commons
Message-ID: <26278208.1192488064482.JavaMail.jira@cloud.prod.atl2.jboss.com>

Consider removing dependency on jboss-commons
---------------------------------------------

                 Key: JBREM-819
                 URL: http://jira.jboss.com/jira/browse/JBREM-819
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.GA
            Reporter: Ron Sigal
         Assigned To: Trustin Lee
             Fix For: 3.0.0.Alpha1 (Otter)


>From Greg Hinkle of the JBoss Operations Network group:  

"... not only are the including tons of crap in the garbage pale called commons, but they dictate tons of library dependencies and serialization versions. For a group like ours that has to be able to simultaneously connect to every version of jboss released in the last 3 years it is not a good situation. We end up having to create a separate class loader per connection.

"Now with remoting, we're actually using it as a core infrastructure piece. That means its in parent classloaders to these connection classloaders. As long as commons is in that required list we can't use remoting this way. We're going to have to do some serious classloader restructuring to be able to support our needs."


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:50:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 18:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-751) @Local and
 @Remote on one interface must not be allowed
In-Reply-To: <25136912.1161262361433.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13850398.1192488603396.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-751?page=all ]

Andrew Rubinger updated EJBTHREE-751:
-------------------------------------

    Description: 
EJB3 4.6.6 bullet 5.4
'The same business interface cannot be both a local and a remote business interface of the bean.'

Deployment must fail with a nice friendly message.

  was:
EJB3 4.6.7 bullet 5.4
'The same business interface cannot be both a local and a remote business interface of the bean.'

Deployment must fail with a nice friendly message.


Corrected EJB3 Specification reference in description

> @Local and @Remote on one interface must not be allowed
> -------------------------------------------------------
>
>                 Key: EJBTHREE-751
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-751
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.0 GA
>
>
> EJB3 4.6.6 bullet 5.4
> 'The same business interface cannot be both a local and a remote business interface of the bean.'
> Deployment must fail with a nice friendly message.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:52:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 18:52:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19448736.1192488724368.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=comments#action_12382631 ] 
            
Andrew Rubinger commented on EJBTHREE-1063:
-------------------------------------------

Test Cases now deploy, 17 total, 3 errors, 0 failures.

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil; possibly related to EJB3Registry

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 18:52:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 18:52:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24322401.1192488724642.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=all ]

Andrew Rubinger updated EJBTHREE-1063:
--------------------------------------

    Description: Requested by Anil  (was: Requested by Anil; possibly related to EJB3Registry)

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Requested by Anil

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 19:03:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 19:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1063) Ensure
 EJBSpecUnitTestCase Passes
In-Reply-To: <29448620.1191960363626.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19172621.1192489383382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1063?page=all ]

Andrew Rubinger updated EJBTHREE-1063:
--------------------------------------

    Assignee: Anil Saldhana  (was: Andrew Rubinger)

Sending back to Anil; deployment successful.

> Ensure EJBSpecUnitTestCase Passes
> ---------------------------------
>
>                 Key: EJBTHREE-1063
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: HEAD
>            Reporter: Andrew Rubinger
>         Assigned To: Anil Saldhana
>             Fix For: HEAD
>
>
> Requested by Anil

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 19:13:03 2007
From: jira-events at lists.jboss.org (Burr Sutter (JIRA))
Date: Mon, 15 Oct 2007 19:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-987) display non GMT+0
	time zones
In-Reply-To: <14779733.1181746286332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28705834.1192489983868.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-987?page=comments#action_12382634 ] 
            
Burr Sutter commented on JBPM-987:
----------------------------------

why is the GUI playing with timezone?  It should just display what ever is in the database for that process instance.  



> display non GMT+0 time zones
> ----------------------------
>
>                 Key: JBPM-987
>                 URL: http://jira.jboss.com/jira/browse/JBPM-987
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: Jean-Louis Rastapoc
>         Assigned To: David Lloyd
>
> The web-console currently uses the default JSF timezone conversion and displays GMT+0.
> Other time zones should be read from the client or be configurable.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 20:18:04 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 20:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1058) Cannot invoke
 EJBObject methods on EJBs without explicit Home Interface Defined
In-Reply-To: <18009866.1191572583287.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31445879.1192493884429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1058?page=all ]

Andrew Rubinger resolved EJBTHREE-1058.
---------------------------------------

    Resolution: Rejected

This construct is a violation of EJB3 Spec 4.6.6 Bullet 1:

"The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface."


> Cannot invoke EJBObject methods on EJBs without explicit Home Interface Defined
> -------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1058
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1058
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Assuming:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean
> ..when invoking:
> Object obj = getInitialContext().lookup(StatefulRemote.JNDI_NAME_REMOTE);
> EJBObject ejbObject = (EJBObject) obj;
> ejbObject.remove();
> ...the following exception is encountered:
> Could not resolve beanClass method from proxy call
> java.lang.RuntimeException: Could not resolve beanClass method from proxy call
> 	at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:330)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1634)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateful.StatefulRemoteProxy.invoke(StatefulRemoteProxy.java:135)
> 	at $Proxy2.remove(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 20:22:09 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 15 Oct 2007 20:22:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1071) Business
 Interface must not extend EJBObject or EJBLocalObject
Message-ID: <18467162.1192494129846.JavaMail.jira@cloud.prod.atl2.jboss.com>

Business Interface must not extend EJBObject or EJBLocalObject
--------------------------------------------------------------

                 Key: EJBTHREE-1071
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1071
             Project: EJB 3.0
          Issue Type: Bug
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


EJB3 Spec 4.6.6 Bullet 1:

"The following are the requirements for the session bean's business interface:
     * The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface."

...thus the following construct:

public interface StatefulRemote extends EJBObject{...}

...and:

@Stateful
@Remote(StatefulRemote.class)
@RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
public class StatefulRemoteBean 

...should fail with a deployment exception referencing the specification.


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 15 21:43:03 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Mon, 15 Oct 2007 21:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAOP-480) NPE in concurrent
 join point generation
Message-ID: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in concurrent join point generation
---------------------------------------

                 Key: JBAOP-480
                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
             Project: JBoss AOP
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.beta1
            Reporter: Jason T. Greene
             Fix For: 2.0.0.beta2


Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 

Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
	... 14 more
Caused by: java.lang.NullPointerException
	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
	... 33 more


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:13:03 2007
From: jira-events at lists.jboss.org (lepe (JIRA))
Date: Tue, 16 Oct 2007 03:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4861) CLONE -bin/run.sh
 should force IPv4 on Darwin systems
Message-ID: <7505315.1192518783592.JavaMail.jira@cloud.prod.atl2.jboss.com>

CLONE -bin/run.sh should force IPv4 on Darwin systems
-----------------------------------------------------

                 Key: JBAS-4861
                 URL: http://jira.jboss.com/jira/browse/JBAS-4861
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: System service
            Reporter: lepe
         Assigned To: Dimitris Andreadis
             Fix For: JBossAS-4.2.0.CR2,  JBossAS-5.0.0.Beta3


There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. 

Something like:

   if [ "`uname`" = "Linux" ]; then 
       JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" 
   fi 
fi 

So that Linux systems use ipv4 


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:13:03 2007
From: jira-events at lists.jboss.org (lepe (JIRA))
Date: Tue, 16 Oct 2007 03:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4862) Verify whether
 -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
Message-ID: <13570609.1192518783751.JavaMail.jira@cloud.prod.atl2.jboss.com>

Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
--------------------------------------------------------------------------------

                 Key: JBAS-4862
                 URL: http://jira.jboss.com/jira/browse/JBAS-4862
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: System service
            Reporter: lepe
         Assigned To: Dimitris Andreadis
             Fix For: JBossAS-5.0.1.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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:17:03 2007
From: jira-events at lists.jboss.org (lepe (JIRA))
Date: Tue, 16 Oct 2007 03:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4861) CLONE -bin/run.sh
 should force IPv4 on Darwin systems
In-Reply-To: <7505315.1192518783592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1217785.1192519023424.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4861?page=comments#action_12382654 ] 
            
lepe commented on JBAS-4861:
----------------------------

Sorry, bad idea of cloning the issue, thought I would have a chance an modify the description etc... :)

What I would like is to have the same stuff added for Darwin, that is to preferIPv4Stack.

regards,

/L

Redpill AB

> CLONE -bin/run.sh should force IPv4 on Darwin systems
> -----------------------------------------------------
>
>                 Key: JBAS-4861
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4861
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: System service
>            Reporter: lepe
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.0.CR2,  JBossAS-5.0.0.Beta3
>
>
> There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. 
> Something like:
>    if [ "`uname`" = "Linux" ]; then 
>        JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" 
>    fi 
> fi 
> So that Linux systems use ipv4 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:30:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 03:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13960270.1192519803453.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382656 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

Yes, do not call the deploy target.

Run 

ant tests

from  https://svn.jboss.org/repos/jbossws/stack/native/tags/jbossws-native-2.0.1.SP2


> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 03:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4861) CLONE -bin/run.sh
 should force IPv4 on Darwin systems
In-Reply-To: <7505315.1192518783592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29014143.1192520223412.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4861?page=all ]

Dimitris Andreadis updated JBAS-4861:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.2.0.CR2)
                       (was:  JBossAS-5.0.0.Beta3)

Please don't set the fix version.

> CLONE -bin/run.sh should force IPv4 on Darwin systems
> -----------------------------------------------------
>
>                 Key: JBAS-4861
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4861
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: System service
>            Reporter: lepe
>         Assigned To: Dimitris Andreadis
>
> There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. 
> Something like:
>    if [ "`uname`" = "Linux" ]; then 
>        JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" 
>    fi 
> fi 
> So that Linux systems use ipv4 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 03:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 03:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4862) Verify whether
 -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
In-Reply-To: <13570609.1192518783751.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25303140.1192520223698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4862?page=all ]

Dimitris Andreadis updated JBAS-4862:
-------------------------------------

    Fix Version/s:     (was: JBossAS-5.0.1.CR1)

> Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4862
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4862
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: System service
>            Reporter: lepe
>         Assigned To: Dimitris Andreadis
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:20:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 04:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4853) jbossxb-1.0.0.GA
 shows webservice regression
In-Reply-To: <3091539.1192182003658.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2196067.1192522803325.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4853?page=comments#action_12382668 ] 
            
Dimitris Andreadis commented on JBAS-4853:
------------------------------------------

The following are the issues that were included into the CR11/SP1

JBXB-97 org.w3c.dom.Element is being mapped incorrectly
JBXB-105 switch from oswego to java.util concurrent
JBXB-103 JBossXB ignores non-ignorable white space
JBXB-96 JAXB error when using different derived types in the same container/array type

> jbossxb-1.0.0.GA shows webservice regression
> --------------------------------------------
>
>                 Key: JBAS-4853
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4853
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossAS-4.2.2.GA
>
>
> This failure occurs with jbossxb-1.0.0.GA-brew. It does not occur with CR11
> org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase.testString
> junit.framework.ComparisonFailure: expected:<   > but was:<>
> 	at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:24:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6425861.1192523043711.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12382669 ] 
            
Dimitris Andreadis commented on JBAS-4754:
------------------------------------------

The TCK should be fully passing now. We did a jbossxb upgrade in JBAS-4853, so maybe we should retest? :-/



> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:24:04 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Tue, 16 Oct 2007 04:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1070) The jBPM test
 configuration has problem with database setup
Message-ID: <18592858.1192523044126.JavaMail.jira@cloud.prod.atl2.jboss.com>

The jBPM test configuration has problem with database setup
-----------------------------------------------------------

                 Key: JBPM-1070
                 URL: http://jira.jboss.com/jira/browse/JBPM-1070
             Project: JBoss jBPM
          Issue Type: Bug
    Affects Versions: jBPM jPDL 3.2.2
            Reporter: Jiri Pechanec
         Assigned To: Tom Baeyens


The jBPM test process expects hiberante.properties file to be placed in defined configuration directory. jBPM config file JBPM.3/jpdl/jar/src/test/config/jbpm.cfg.xml orders to use hibernate.properties file (<string name="resource.hibernate.properties" value="hibernate.properties" />).
But the JBPM.3/jpdl/jar/src/test/java/org/jbpm/db/AbstractDbTestCase.java uses config file less JBPM.3/jpdl/jar/src/test/java/org/jbpm/jbpm.test.cfg.xml and the line mentioned above is missing. Thus the configuration is read from standard hibernate.cfg.xml.

Solution
Either add the missing line to jbpm.test.cfg.xml or change AbstractDbTestCase.java to use central config file in config directory. The second one is preferred.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:37:08 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:37:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4863) NPE in
 ContainerConfigurationMetaDataWrapper
Message-ID: <22857669.1192523828772.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in ContainerConfigurationMetaDataWrapper
--------------------------------------------

                 Key: JBAS-4863
                 URL: http://jira.jboss.com/jira/browse/JBAS-4863
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark
             Fix For:  JBossAS-5.0.0.Beta3


[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test

getContainerConfigurations returns null

      configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
            defaults.getContainerConfigurations());


Caused by: java.lang.NullPointerException
        at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:37:08 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:37:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4857) NPE in
 ContainerConfigurationMetaDataWrapper
Message-ID: <17176280.1192523828962.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4857?page=all ]

Thomas Diesler deleted JBAS-4857:
---------------------------------


> NPE in ContainerConfigurationMetaDataWrapper
> --------------------------------------------
>
>                 Key: JBAS-4857
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4857
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> getContainerConfigurations returns null
>       configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
>             defaults.getContainerConfigurations());
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
>         at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
Message-ID: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>

jboss-web with 4.0 dtd does not deploy
--------------------------------------

                 Key: JBAS-4864
                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30735970.1192524063851.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382670 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

[tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
        at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
        at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
        ... 66 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30521598.1192524064063.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382671 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

 <?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <security-domain>java:/jaas/JBossWS</security-domain>
</jboss-web>

You should be able to see this when you change the jboss-web.xml for the jmx-console

14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26164928.1192524064335.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4864?page=all ]

Thomas Diesler updated JBAS-4864:
---------------------------------

    Comment: was deleted

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:41:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:41:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33129325.1192524064519.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382672 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <security-domain>java:/jaas/JBossWS</security-domain>
</jboss-web>

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24919213.1192524183445.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382673 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/

You should be able to see this when you change the jboss-web.xml for the jmx-console 

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
        at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
        at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
[ Show ? ]
Thomas Diesler [15/Oct/07 08:58 AM] 14:55:54,121 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-console.war/ Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

       



From jira-events at lists.jboss.org  Tue Oct 16 04:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12380199.1192524183786.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4864?page=all ]

Thomas Diesler updated JBAS-4864:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 04:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 16 Oct 2007 04:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4855) jboss-web with 4.0
 dtd does not deploy
Message-ID: <8727861.1192524183617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4855?page=all ]

Thomas Diesler deleted JBAS-4855:
---------------------------------


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4855
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4855
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
>         at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153)
>         at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71)
>         at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223)
>         ... 66 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 05:50:03 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Tue, 16 Oct 2007 05:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27404211.1192528203607.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12382679 ] 
            
Alexey Loubyansky commented on JBAS-4864:
-----------------------------------------

Strange, if I do that for jmx-console.war, it starts w/o an error. With or w/o Internet connection.

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:19:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 06:19:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1009) Support preload
 functionality as part of region activation
In-Reply-To: <30615959.1174011523634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10958405.1192529955085.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1009?page=comments#action_12382683 ] 
            
Manik Surtani commented on JBCACHE-1009:
----------------------------------------

Yes, well we really need to get into the detailed design of JBCACHE-64, including whether each region has it's own lifecycle, which in effect is your region activation.

> Support preload functionality as part of region activation
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1009
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region.  If one of the defined preload regions names a subregion of the region being activated, preload the subregion.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:21:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
In-Reply-To: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11944812.1192530063377.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1195?page=all ]

Manik Surtani reassigned JBCACHE-1195:
--------------------------------------

    Assignee: Mircea Markus  (was: Manik Surtani)

> Fix tutorial for 2.1.0 series
> -----------------------------
>
>                 Key: JBCACHE-1195
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.
> Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:21:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-486) Optimize
	activations
Message-ID: <30176370.1192530063651.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-486?page=all ]

Manik Surtani updated JBCACHE-486:
----------------------------------

    Fix Version/s: 2.1.0.CR1

> Optimize activations
> --------------------
>
>                 Key: JBCACHE-486
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-486
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.3.0.GA
>            Reporter: Jerry Gauthier
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> JBCACHE-420 notes that activation processing is performed excessively.  The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue.
> The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor.  Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated.  This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination.  This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader).
> It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance.  One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__
> to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when
> activated.  

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 06:27:13 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 16 Oct 2007 06:27:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBSER-98) Write slot with
 fields only if both readObject and writeObject are missing
Message-ID: <1789794.1192530433263.JavaMail.jira@cloud.prod.atl2.jboss.com>

Write slot with fields only if both readObject and writeObject are missing
--------------------------------------------------------------------------

                 Key: JBSER-98
                 URL: http://jira.jboss.com/jira/browse/JBSER-98
             Project: JBoss Serialization
          Issue Type: Feature Request
    Affects Versions: 1.0.3 GA
            Reporter: Galder Zamarreno
         Assigned To: Clebert Suconic


Over the last few weeks, I've been dealing with a funky support case which showed the following 
stacktrace:

...
Caused by: org.jboss.serial.exception.SerializationException: Excepted to be String
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1120)
at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:71)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
at org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
at org.jboss.serial.io.MarshalledObjectForLocalCalls.get(MarshalledObjectForLocalCalls.java:60)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
... 28 more
Caused by: java.lang.ClassCastException: org.jboss.serial.finalcontainers.IntegerContainer
at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1116)
... 42 more 

The cause of the issue was that the customer had a class where it had re-implemented 
readObject(java.io.ObjectInputStream stream) but had not re-implemented 
writeObject(java.io.ObjectOutputStream stream). This is obviously a programming error on their side,
but it took a while to detect such stupid mistake.

The problem within JBoss Serialization was that because this class didn't have a writeObject() 
reimplementation, it was a writing the class as a slot with fields, but when it came to reading it, it 
was reading the class as a slot with method because readObject had been reimplemented. The 
next time a slot with fields was read, the fields were mixed up.

To avoid these type of situations, I'd suggest that:
- JBS only writes as fields if *both* writeObject and readObject are missing. Right now, can't see a 
situation where you'd implement one and not the other, thoughts?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 07:59:03 2007
From: jira-events at lists.jboss.org (Olaf Fricke (JIRA))
Date: Tue, 16 Oct 2007 07:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1072) Ejb3TxPolicy
 does not rollback the transaction in case of an error
Message-ID: <20940487.1192535943615.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ejb3TxPolicy does not rollback the transaction in case of an error
------------------------------------------------------------------

                 Key: EJBTHREE-1072
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1072
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: HEAD
            Reporter: Olaf Fricke
            Priority: Blocker


The class Ejb3TxPolicy is used to rollback the transaction in the case of exceptions. According to the ejb 3.0 spec, the transaction is rolled back in case of ApplicationException with rollback() evaluating to true, in case of RuntimeExceptions or in case of EjbException. 

All other exception will not lead to a rollback on the current transaction.

Unfortunately, the same is true in case of errors. If, for example, an AssertionError (or a ClassDefNotFoundError etc.) occurs, the current transaction will be committed and not rolled back. This behaviour is wrong with respect to the ejb 3.0 spec (see for example table 14 on page 360 of ejbcore.pdf)

A possible solution would be to wrap the error into a new RuntimeException after handling ApplicationException (in both methods handleExceptionInOurTx and handleInCallerTx):

<code>
if (t instanceof Error)
      {
         t = new RuntimeException(t);
      }
if (!(t instanceof RuntimeException || t instanceof RemoteException))
      {
         throw t;
      }
</code>

The wrapping is necessary, because both the EJBException and the EJBTransactionRolledbackException can only handle exceptions, but not errors.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 08:32:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 08:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <27580949.1192537923568.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12382707 ] 
            
Tim Fox commented on JBMESSAGING-375:
-------------------------------------

Jeff-

Feel free to implement another way if you wish.

You don't have to use the patch.

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 08:52:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 08:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1154) Introduce ability
 to mark nodes
 as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <594535.1192539123417.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Mircea Markus closed JBCACHE-1154.
----------------------------------

    Resolution: Done

documentation also updated

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:19:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Tue, 16 Oct 2007 09:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28166456.1192540743305.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382720 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

The hudson job is configured here.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBossWS-2.0.1.SP2-testsuite-AS4.2.x/

There are 3 test failures due to java.lang.ClassNotFoundException: org.apache.ws.scout.registry.ConnectionFactoryImpl
Where is this class located?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:28:03 2007
From: jira-events at lists.jboss.org (Davide Baroncelli (JIRA))
Date: Tue, 16 Oct 2007 09:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCOMMON-38) Use URI instead of
 URL in FileProtocolArchiveBrowserFactory
Message-ID: <12430491.1192541283774.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use URI instead of URL in FileProtocolArchiveBrowserFactory
-----------------------------------------------------------

                 Key: JBCOMMON-38
                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-38
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Davide Baroncelli
         Assigned To: Dimitris Andreadis
            Priority: Critical
             Fix For: 2.2.2.GA


Current code in FileProtocolArchiveBrowserFactory has problems when the URL coming from above contains escaped characters. E.g.: In an app. I'm writing, the class receives an URL coming from a ClassLoader.getResources method: resources in directories containing square brackets arrive to the class in escaped URLs such as the following:

file:/C:/Stratosfera/pos_back/%5BCARCON%5Dstratosfera-verifica-cartoline-concorso/war/WEB-INF/classes/

this form fails in the current implementation because of line 40:

File f = new File(url.getPath());

this results in a non existing file. Replacing the line with the following solves the problem:

       File f;
       try {
           f = new File(url.toURI());
       }
       catch ( URISyntaxException e ) {
           throw new RuntimeException( e );
       }

this problems creates various compatibility problems in depending libraries (hibernate entitymanager for one).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:36:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 16 Oct 2007 09:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-856) Use Buddy
 Replication for clustered SFSBs
In-Reply-To: <24225310.1170195680226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13739062.1192541763623.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-856?page=comments#action_12382724 ] 
            
Brian Stansberry commented on EJBTHREE-856:
-------------------------------------------

This remains open for AS 4.2.2 due to JBCACHE-1194; will need JBC 1.4.1.SP6 to resolve.

> Use Buddy Replication for clustered SFSBs
> -----------------------------------------
>
>                 Key: EJBTHREE-856
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-856
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Optimize the replicated SFSB cache for use with Buddy Replication.  Basically means checking cache calls to ensure unwanted data gravitations do not occur. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 09:42:04 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 16 Oct 2007 09:42:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-987) display non GMT+0
	time zones
In-Reply-To: <14779733.1181746286332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5659386.1192542124516.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-987?page=comments#action_12382726 ] 
            
Ronald van Kuijk commented on JBPM-987:
---------------------------------------

The 'gui' is not, well not the jbpm developers at least... JSF is.... That is the reason the seam convertDateTime does this for you. It converts the date/time to the seam timezone, which is the current users' local timezone. Normally JSF displays date/time always according to Zulu time. 

> display non GMT+0 time zones
> ----------------------------
>
>                 Key: JBPM-987
>                 URL: http://jira.jboss.com/jira/browse/JBPM-987
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: Jean-Louis Rastapoc
>         Assigned To: David Lloyd
>
> The web-console currently uses the default JSF timezone conversion and displays GMT+0.
> Other time zones should be read from the client or be configurable.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:16:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 10:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-38) Use URI instead of
 URL in FileProtocolArchiveBrowserFactory
In-Reply-To: <12430491.1192541283774.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15346559.1192544163903.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-38?page=all ]

Dimitris Andreadis updated JBCOMMON-38:
---------------------------------------

    Fix Version/s:     (was: 2.2.2.GA)
         Priority: Major  (was: Critical)

Please, don't set the fix version and the criticality.

> Use URI instead of URL in FileProtocolArchiveBrowserFactory
> -----------------------------------------------------------
>
>                 Key: JBCOMMON-38
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-38
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Davide Baroncelli
>         Assigned To: Dimitris Andreadis
>
> Current code in FileProtocolArchiveBrowserFactory has problems when the URL coming from above contains escaped characters. E.g.: In an app. I'm writing, the class receives an URL coming from a ClassLoader.getResources method: resources in directories containing square brackets arrive to the class in escaped URLs such as the following:
> file:/C:/Stratosfera/pos_back/%5BCARCON%5Dstratosfera-verifica-cartoline-concorso/war/WEB-INF/classes/
> this form fails in the current implementation because of line 40:
> File f = new File(url.getPath());
> this results in a non existing file. Replacing the line with the following solves the problem:
>        File f;
>        try {
>            f = new File(url.toURI());
>        }
>        catch ( URISyntaxException e ) {
>            throw new RuntimeException( e );
>        }
> this problems creates various compatibility problems in depending libraries (hibernate entitymanager for one).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 10:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20369705.1192544283706.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Fix Version/s: 2.2.3.GA
                       (was: 2.2.2.GA)

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.0.6.GA, 2.2.3.GA, 1.2.2.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 16 Oct 2007 10:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-35) NestedThrowable
 Class when accessed concurrently by 2 Threads cause deadlock .
In-Reply-To: <7851949.1191329943789.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15290293.1192544283894.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-35?page=all ]

Dimitris Andreadis updated JBCOMMON-35:
---------------------------------------

    Fix Version/s: 2.2.3.GA
                       (was: 2.2.2.GA)

> NestedThrowable Class when accessed concurrently by 2 Threads cause deadlock .
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-35
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-35
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Vicky Kak
>             Fix For: 1.0.5.GA, 2.0.6.GA, 2.2.3.GA, 1.2.2.GA
>
>
> http://forum.java.sun.com/thread.jspa?threadID=752201

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCACHE-1128) Add a full
 component-info.xml to source tree
In-Reply-To: <5459575.1184107351575.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12501393.1192544284036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1128?page=all ]

Manik Surtani reassigned JBCACHE-1128:
--------------------------------------

    Assignee: Manik Surtani  (was: Brian Stansberry)

> Add a full component-info.xml to source tree
> --------------------------------------------
>
>                 Key: JBCACHE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1128) Add a full
 component-info.xml to source tree
In-Reply-To: <5459575.1184107351575.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29736576.1192544284219.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1128?page=all ]

Manik Surtani updated JBCACHE-1128:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Add a full component-info.xml to source tree
> --------------------------------------------
>
>                 Key: JBCACHE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCACHE-1129) Specify version
 dependencies in component-info.xml
In-Reply-To: <1176722.1184107471596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18545100.1192544284410.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1129?page=all ]

Manik Surtani reassigned JBCACHE-1129:
--------------------------------------

    Assignee: Manik Surtani  (was: Brian Stansberry)

> Specify version dependencies in component-info.xml
> --------------------------------------------------
>
>                 Key: JBCACHE-1129
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Seems they are listed in pom.xml; need equivalent entries in component-info.xml.
> This adds fun, since we need to ensure consistency with the AS versions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:18:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:18:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1129) Specify version
 dependencies in component-info.xml
In-Reply-To: <1176722.1184107471596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6423955.1192544284586.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1129?page=all ]

Manik Surtani updated JBCACHE-1129:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Specify version dependencies in component-info.xml
> --------------------------------------------------
>
>                 Key: JBCACHE-1129
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Seems they are listed in pom.xml; need equivalent entries in component-info.xml.
> This adds fun, since we need to ensure consistency with the AS versions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1170) Partial state
 transfer fails when multiple regions present
In-Reply-To: <5358429.1187970318264.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20614273.1192544403310.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1170?page=all ]

Manik Surtani resolved JBCACHE-1170.
------------------------------------

    Resolution: Done

> Partial state transfer fails when multiple regions present
> ----------------------------------------------------------
>
>                 Key: JBCACHE-1170
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.  
> Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase.  Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call.  Using region /JSESSION/localhost/http-field
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
> The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped", or perhaps nothing at all.
> Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal.  Two problems:
> 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
> 2) Need to ensure that the right Fqn gets written.  In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything.  If not, just cleaning up the ThreadLocal should work.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:20:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1170) Leakage of
 marshalling region
 stored in ThreadLocal causes partial state transfer to fail when multiple
 regions present
In-Reply-To: <5358429.1187970318264.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19187545.1192544403488.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1170?page=all ]

Manik Surtani updated JBCACHE-1170:
-----------------------------------

       Summary: Leakage of marshalling region stored in ThreadLocal causes partial state transfer to fail when multiple regions present  (was: Partial state transfer fails when multiple regions present)
    Complexity: Medium

> Leakage of marshalling region stored in ThreadLocal causes partial state transfer to fail when multiple regions present
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1170
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.  
> Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase.  Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call.  Using region /JSESSION/localhost/http-field
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
> 2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
> The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped", or perhaps nothing at all.
> Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal.  Two problems:
> 1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
> 2) Need to ensure that the right Fqn gets written.  In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything.  If not, just cleaning up the ThreadLocal should work.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:22:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 10:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1176) Bad performance
 when deleting a large tree from JDBCCacheLoader
In-Reply-To: <22599873.1188997871354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15734615.1192544523639.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1176?page=all ]

Mircea Markus resolved JBCACHE-1176.
------------------------------------

    Resolution: Done

Starting with 2.0 remove operations are executed to a single call to the DBMS. I've added logs (trace) that show the operations being executed whils removing the nodes from the database.

> Bad performance when deleting a large tree from JDBCCacheLoader 
> ----------------------------------------------------------------
>
>                 Key: JBCACHE-1176
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1176
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>    Affects Versions: 2.0.0.CR1
>            Reporter: gmeroz
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> When using JDBCCacheLaoder and trying to delete the hole tree:
> using: cache.getCache().removeNode(Fqn.ROOT)
> it takes a long time which may cause transaction timeouts when running on application server.
> it seems that each node is deleted seperately instead of using one sql command.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:32:48 2007
From: jira-events at lists.jboss.org (Prabhat Jha (JIRA))
Date: Tue, 16 Oct 2007 10:32:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1756) port jacc
 contention workaround that was made for Intuit to 2.6.2
Message-ID: <20582814.1192545168988.JavaMail.jira@cloud.prod.atl2.jboss.com>

port jacc contention workaround that was made for Intuit to 2.6.2
-----------------------------------------------------------------

                 Key: JBPORTAL-1756
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1756
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Security
    Affects Versions: 2.6.2 Final
            Reporter: Prabhat Jha
         Assigned To: Sohil Shah


As agreed during today's portal QA call, please port jacc fix that was done for Intuit to 2.6.2. We will test to make sure everything works as expected and then make it mainstream in 2.6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:34:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 10:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1154) Introduce
 ability to mark
 nodes as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17495372.1192545243698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Mircea Markus reopened JBCACHE-1154:
------------------------------------

             
status should be resolved, not closed

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:36:03 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 16 Oct 2007 10:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1154) Introduce
 ability to mark
 nodes as resident- i.e., they never get considered for eviction
In-Reply-To: <19979184.1185539627066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6244037.1192545363465.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1154?page=all ]

Mircea Markus resolved JBCACHE-1154.
------------------------------------

    Resolution: Done

resolved

> Introduce ability to mark nodes as resident- i.e., they never get considered for eviction
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1154
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Eviction
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:40:08 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 16 Oct 2007 10:40:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1066) Business
 interfaces defined in the descriptor are ignored
In-Reply-To: <1743168.1192107604906.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13229065.1192545609361.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1066?page=comments#action_12382747 ] 
            
Andrew Rubinger commented on EJBTHREE-1066:
-------------------------------------------

Progress temporarily suspended while refactoring in metamodel is performed.

> Business interfaces defined in the descriptor are ignored
> ---------------------------------------------------------
>
>                 Key: EJBTHREE-1066
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1066
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:50:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 16 Oct 2007 10:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1174) Add further
	passivation docs
In-Reply-To: <8204338.1188232763535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15554735.1192546203794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1174?page=all ]

Brian Stansberry closed JBCACHE-1174.
-------------------------------------

    Fix Version/s: 2.1.0.CR1
                       (was: 2.1.0.GA)
       Resolution: Done

> Add further passivation docs
> ----------------------------
>
>                 Key: JBCACHE-1174
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1174
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.CR1
>
>
> Add discussion a la http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077805#4077805. I've already done this in my local checkout but can't figure out how to get the maven jdocbook stuff to run so I can validate.  This task is just a reminder to finish up once a more urgent need drives me to figure this stuff out.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 10:58:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 10:58:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1121) Investigate the
 suitability of not copying child maps into workspace
In-Reply-To: <14759070.1183724948890.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24856985.1192546684177.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1121?page=all ]

Manik Surtani updated JBCACHE-1121:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Investigate the suitability of not copying child maps into workspace
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1121
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1121
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Optimistic Locking
>    Affects Versions: 1.4.1.GA, 1.4.0.GA, 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.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

        


From jira-events at lists.jboss.org  Tue Oct 16 11:36:54 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 11:36:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6966050.1192549014983.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=comments#action_12382789 ] 
            
Tim Fox commented on JBMESSAGING-1110:
--------------------------------------

This could be related to a jboss remoting issue where remoting incorrectly terminates a connection under load since it didn't receive a ping.

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: Unscheduled
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 11:55:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 11:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1129) Specify version
 dependencies in component-info.xml
In-Reply-To: <1176722.1184107471596.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17441905.1192550103413.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1129?page=all ]

Manik Surtani resolved JBCACHE-1129.
------------------------------------

    Resolution: Rejected

> Specify version dependencies in component-info.xml
> --------------------------------------------------
>
>                 Key: JBCACHE-1129
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Seems they are listed in pom.xml; need equivalent entries in component-info.xml.
> This adds fun, since we need to ensure consistency with the AS versions.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:01:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 16 Oct 2007 12:01:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1128) Automated
 integration testing to ensure compatibility of dependencies
In-Reply-To: <5459575.1184107351575.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <822587.1192550475150.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1128?page=all ]

Manik Surtani updated JBCACHE-1128:
-----------------------------------

               Summary: Automated integration testing to ensure compatibility of dependencies  (was: Add a full component-info.xml to source tree)
     Original Estimate: 1 week
    Remaining Estimate: 1 week
         Fix Version/s: 2.2.0.GA
                            (was: 2.1.0.GA)
                            (was: 2.1.0.CR1)
            Complexity: Medium

Deferring this to 2.2.0.

The purpose here is to ensure that the dependencies JBC ships with are compatible with versions shipped with JBoss AS.

E.g., (hypothetically speaking) JBC ships with JGroups 2.6.1 and JBoss AS 5 shipped with JGroups 2.6.0.  The JBC tests just run with 2.6.1 and before release we should certify it against libs shipped with AS 5.

Basically, an automated way to generate this page:

http://labs.jboss.org/jbosscache/compatibility/index.html

Should be as simple as an ant script, that pulls down:

1.  Srcs for JBC we hope to test
2.  Dependent libs from JBC's pom.xml
3.  Dependent libs from AS's component-info.xml that overlaps with libs from (2)
4.  Run test suite
5.  Repeat steps 1-4 for all versions of AS we need to test against
6.  Generate report based on output



> Automated integration testing to ensure compatibility of dependencies
> ---------------------------------------------------------------------
>
>                 Key: JBCACHE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.2.0.GA
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:15:04 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 16 Oct 2007 12:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-987) display non GMT+0
	time zones
In-Reply-To: <14779733.1181746286332.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <603890.1192551304219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-987?page=comments#action_12382800 ] 
            
Ronald van Kuijk commented on JBPM-987:
---------------------------------------

@Tom,

No it does not. The seam convertDateTime does this for you when displaying it. On the server side (e.g. when posting) it is still in Zulu time. There are multiple solutions:
1: Take the seam s:convertDateTime component and port that to a j4j one
2: just use f:convertDateTime and create one component that looks up the users timezone
3: just use convertDateTime and configure somewhere what the timezone would be.

Only the last needs documentation. 2 is plain jsf as is 1 (but a little less)

And after that, add this tag to each field that requires a date

> display non GMT+0 time zones
> ----------------------------
>
>                 Key: JBPM-987
>                 URL: http://jira.jboss.com/jira/browse/JBPM-987
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM jPDL 3.2,  jBPM jPDL 3.2.1
>            Reporter: Jean-Louis Rastapoc
>         Assigned To: David Lloyd
>
> The web-console currently uses the default JSF timezone conversion and displays GMT+0.
> Other time zones should be read from the client or be configurable.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:38:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 16 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19159656.1192552683936.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Edson Tirelli reassigned JBRULES-1279:
--------------------------------------

    Assignee: Edson Tirelli  (was: Mark Proctor)

> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 12:45:35 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 16 Oct 2007 12:45:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3351079.1192553136006.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Edson Tirelli updated JBRULES-1279:
-----------------------------------

    Fix Version/s: 4.0.2_SOA_4.2-CP1
                   4.0.3
                   4.1.0

> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:03:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Tue, 16 Oct 2007 13:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13115398.1192554183969.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Edson Tirelli resolved JBRULES-1279.
------------------------------------

    Resolution: Done

Thanks for reporting and providing test case.

This was indeed a serious regression introduced at revision #15532. It is now fixed and I added an integration test to make sure it will not happen again.

Please let us know if you face any other related problem.

> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:30:14 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1113) Post office
 and message updates at failover need to be transactional
In-Reply-To: <32831290.1192476003623.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4069029.1192555814461.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1113?page=all ]

Tim Fox updated JBMESSAGING-1113:
---------------------------------

    Fix Version/s: 1.4.0.SP1
      Description: 
At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.

If the failing over server is itself killed during this process, then the system can enter an inconsistent state.

Easy solution is to make sure the the postoffice db update is done *after* the merge.

  was:
At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.

If the failing over server is itself killed during this process, then the system can enter an inconsistent state.

Need to make sure all database updates are performed in a single transaction.

         Assignee: Tim Fox  (was: Ovidiu Feodorov)

> Post office and message updates at failover need to be transactional
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1113
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.
> If the failing over server is itself killed during this process, then the system can enter an inconsistent state.
> Easy solution is to make sure the the postoffice db update is done *after* the merge.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:34:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23022572.1192556043695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox updated JBMESSAGING-1112:
---------------------------------

          Summary: Consumption with highly concurrent clients lock a JBM server node.  (was: Highly concurrent clients lock a JBM server node and apparently cause persistent messages to "dissapear")
    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:34:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13590499.1192556043907.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=comments#action_12382835 ] 
            
Tim Fox commented on JBMESSAGING-1112:
--------------------------------------

I have fixed this in TRUNK by using a semaphore to prevent more than a max number of replication requests to occur concurrently to prevent overwhelming JGroups.

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:42:06 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:42:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1114) JBoss
 Remoting fails under load
Message-ID: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Remoting fails under load
-------------------------------

                 Key: JBMESSAGING-1114
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Tim Fox
         Assigned To: Tim Fox
            Priority: Critical
             Fix For: 1.4.0.SP1


JBoss Remoting fails with various different errors when under extreme load.

To replicate this, set up two clustered server nodes, using a MySQL database.

These can both be on the same machine, using ServiceBindingManager.

On a second machine run Ovidiu's messkit toolki, first to send some messages:

mess -stat send -size 10240 50000 

And then to receive them back using 50 concurrent consumers:

mess -stat -sessions 50 receive all

You will notice that JBoss Remoting fails with errors:

I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?

I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.

It also seems remoting is continually timing out and recreating connections - this could also be a source of error.

How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Tue Oct 16 13:46:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 13:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3611764.1192556763383.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox updated JBMESSAGING-1112:
---------------------------------

    Attachment: messkit.zip

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>         Attachments: messkit.zip
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 14:26:03 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Tue, 16 Oct 2007 14:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1073)
 SessionContext.getBusinessObject(...) throws IllegalStateException on
 @Service EJB
Message-ID: <27081964.1192559163555.JavaMail.jira@cloud.prod.atl2.jboss.com>

SessionContext.getBusinessObject(...) throws IllegalStateException on @Service EJB
----------------------------------------------------------------------------------

                 Key: EJBTHREE-1073
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1073
             Project: EJB 3.0
          Issue Type: Bug
          Components: EJB3 Extensions
    Affects Versions: AS 4.2.1.GA
            Reporter: Michael McKibben


Calling SessionContext.getBusinessObject(...) throws an IllegalStateException within a @Service EJB. This should behave like a Stateless/Stateful EJB no?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 15:16:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 16 Oct 2007 15:16:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1113) Post office
 and message updates at failover need to be transactional
In-Reply-To: <32831290.1192476003623.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15023360.1192562165500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1113?page=all ]

Tim Fox closed JBMESSAGING-1113.
--------------------------------

    Resolution: Done

> Post office and message updates at failover need to be transactional
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1113
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office.
> If the failing over server is itself killed during this process, then the system can enter an inconsistent state.
> Easy solution is to make sure the the postoffice db update is done *after* the merge.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 15:30:06 2007
From: jira-events at lists.jboss.org (Matthew Sandoz (JIRA))
Date: Tue, 16 Oct 2007 15:30:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-143) Load the icon of a
 paletteContribution entry from the plugin directory where it is defined
In-Reply-To: <28132773.1186761253835.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26630040.1192563006056.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-143?page=all ]

Matthew Sandoz updated GPD-143:
-------------------------------

    Attachment: PaletteRoot.java

I just ended up needing to do this as well - if you havent already fixed it this seems to work. I am also attaching this file to the issue

### Eclipse Workspace Patch 1.0
#P org.jbpm.gd.jpdl
Index: src/org/jbpm/gd/common/editor/PaletteRoot.java
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/designer/jpdl/org.jbpm.gd.jpdl/src/org/jbpm/gd/common/editor/PaletteRoot.java,v
retrieving revision 1.2
diff -u -r1.2 PaletteRoot.java
--- src/org/jbpm/gd/common/editor/PaletteRoot.java	7 Aug 2007 11:38:49 -0000	1.2
+++ src/org/jbpm/gd/common/editor/PaletteRoot.java	16 Oct 2007 19:25:06 -0000
@@ -21,6 +21,7 @@
  */
 package org.jbpm.gd.common.editor;
 
+import java.net.URL;
 import java.util.ArrayList;
 import java.util.HashMap;
 import java.util.List;
@@ -37,6 +38,7 @@
 import org.eclipse.gef.palette.ToolEntry;
 import org.eclipse.jface.resource.ImageDescriptor;
 import org.jbpm.gd.jpdl.Plugin;
+import org.osgi.framework.Bundle;
 
 
 public class PaletteRoot extends org.eclipse.gef.palette.PaletteRoot {
@@ -78,9 +80,9 @@
 					PaletteEntry entry;
 					CreationFactory factory = new CreationFactory(object, editor.getSemanticElementFactory(), editor.getNotationElementFactory());
 					if (isNode) {
-						entry = new CreationToolEntry(label, tooltip, factory, getIconDescriptor(icon), null);
+						entry = new CreationToolEntry(label, tooltip, factory, getIconDescriptor(entryElement), null);
 					} else {
-						entry = new ConnectionCreationToolEntry(label, tooltip, factory, getIconDescriptor(icon), null);
+						entry = new ConnectionCreationToolEntry(label, tooltip, factory, getIconDescriptor(entryElement), null);
 					}
 					entry.setId(entryName);
 					paletteGroup.add(entry);
@@ -90,8 +92,10 @@
 		}
 	}
 	
-	private ImageDescriptor getIconDescriptor(String icon) {
-		return ImageDescriptor.createFromURL(Plugin.getDefault().getBundle().getEntry("/" + icon));
+	private ImageDescriptor getIconDescriptor(IConfigurationElement element) {
+		Bundle bundle = Platform.getBundle(element.getDeclaringExtension().getNamespace());
+		URL location = bundle.getEntry("/" + element.getAttribute("icon"));
+		return ImageDescriptor.createFromURL(location);
 	}
 	
 	private void processPaletteContribution(IConfigurationElement configurationElement) {


> Load the icon of a paletteContribution entry from the plugin directory where it is defined
> ------------------------------------------------------------------------------------------
>
>                 Key: GPD-143
>                 URL: http://jira.jboss.com/jira/browse/GPD-143
>             Project: JBoss jBPM GPD
>          Issue Type: Feature Request
>          Components: jpdl
>            Reporter: Matthias Hanisch
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.alpha1
>
>         Attachments: PaletteRoot.java
>
>
> In PaletteRoot class, the icon of a palette entry is always loaded from org.jbpm.gd.jpdl plugin, even if the paletteContribution entry is defined in a dependent plugin.
> The information, where the palette entry element (entryElement in PaletteRoot.addControls) is defined, can be found in entryElement.getContributor().getName().
> So also the corresponding image can be loaded from the correct bundle.
> [ Sorry to only give a verbal description of the implementation. I would sign a corporate contributor's agreement, but I have problems with the procedure, e.g.
> - do we need a corporate jboss account for my boss to sign
> - if we sign with the "corporate" account, with which account I need to contribute then
> etc.
> So I would need some assistance here. Then you would get a real diff also.
> ]

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:42:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 16 Oct 2007 16:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2006933.1192567323610.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 103.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:42:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 16 Oct 2007 16:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25940469.1192567323911.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 104.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:42:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 16 Oct 2007 16:42:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-603) FLUSH: problems with
 TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4106651.1192567324101.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-603?page=all ]

Bela Ban updated JGRP-603:
--------------------------

    Attachment: 105.txt

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 16:52:03 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 16 Oct 2007 16:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-603) FLUSH: problems
 with TCP and concurrent startup/shutdowns
In-Reply-To: <17061465.1191400143350.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10968731.1192567923491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-603?page=comments#action_12382877 ] 
            
Vladimir Blagojevic commented on JGRP-603:
------------------------------------------

Bela described the scenario to reproduce this issue:

- View is V2 {A,B,C}
- Member C has address C:7602
- Member C is killed and *immediately* restarted (before A can exclude it)
- Member C has the *same* address: C:7602
- On JOIN, A will return the *existing view* V2 because it sees that C is still a member !

Does C's FLUSH.down() unblock in such a case ? I don't think so, it only unblocks on reception of the STOP-FLUSH message ! However, this message is never received because the coord (A) never even starts the flush in this case !

> FLUSH: problems with TCP and concurrent startup/shutdowns
> ---------------------------------------------------------
>
>                 Key: JGRP-603
>                 URL: http://jira.jboss.com/jira/browse/JGRP-603
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>         Attachments: 1.txt, 103.txt, 104.txt, 105.txt, 2.txt, 3.txt, jgtest.zip
>
>
> The attached ZIP file has code that reproduces this.
> Modify props.props (pf.cluster.transport.protocol=udp) to "tcp" and "tcp-nio" if you want to test the different stacks.
> To reproduce:
> - Start a number of instances (e.g. 5) concurrently. This almost never works, even under "udp". Joiners' JOIN requests time out and they have to retry (possibly because the coord is busy with the FLUSH protocol). They become singleton members and *never* merge !
> - This works fine without FLUSH
> - With "udp", it works almost always, with "tcp" it works 50% of the time, with "tcp-nio" is almost never works
> - Randomly kill and restart instances

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 17:37:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Tue, 16 Oct 2007 17:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1757) Update workflow
 chapter as it
 doesn't take into account the fact that the workflow service has been
 extracted... Should also document how to use the service in portlets.
Message-ID: <2067996.1192570623164.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update workflow chapter as it doesn't take into account the fact that the workflow service has been extracted... Should also document how to use the service in portlets.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1757
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1757
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Chris Laprun




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:50:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4865) Validate the JBM
	clustered config
Message-ID: <13693139.1192585803269.JavaMail.jira@cloud.prod.atl2.jboss.com>

Validate the JBM clustered config
---------------------------------

                 Key: JBAS-4865
                 URL: http://jira.jboss.com/jira/browse/JBAS-4865
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For:  JBossAS-5.0.0.Beta3


This is just a link to a JBM task : JBMESSAGING-1093

I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:50:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4865) Validate the JBM
	clustered config
In-Reply-To: <13693139.1192585803269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21820092.1192585803628.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4865?page=all ]

Clebert Suconic updated JBAS-4865:
----------------------------------

    Component/s: JB5-Messaging

> Validate the JBM clustered config
> ---------------------------------
>
>                 Key: JBAS-4865
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4865
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This is just a link to a JBM task : JBMESSAGING-1093
> I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:54:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4865) Validate the JBM
	clustered config
In-Reply-To: <13693139.1192585803269.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9738458.1192586043355.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4865?page=all ]

Clebert Suconic closed JBAS-4865.
---------------------------------

    Resolution: Done

> Validate the JBM clustered config
> ---------------------------------
>
>                 Key: JBAS-4865
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4865
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This is just a link to a JBM task : JBMESSAGING-1093
> I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:54:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1093) Verify/Update
 the "all" configuration on JBossHead
In-Reply-To: <16954470.1191336783673.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20653264.1192586043510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1093?page=all ]

Clebert Suconic closed JBMESSAGING-1093.
----------------------------------------

    Resolution: Done

> Verify/Update the "all" configuration on JBossHead
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1093
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 21:54:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 16 Oct 2007 21:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-726) Write/Ellect
 some
 Clustering tests to go into Integration Testsuite on ApplicationServer
In-Reply-To: <1288401.1168296267440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28549451.1192586043701.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-726?page=all ]

Clebert Suconic updated JBMESSAGING-726:
----------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121313

> Write/Ellect some Clustering tests to go into Integration Testsuite on ApplicationServer
> ----------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-726
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-726
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.2.0.Beta1
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: EAP 4.3 Integration, AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 16 23:30:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 16 Oct 2007 23:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1198)
 putForExternalRead not silent on remote node
Message-ID: <22737059.1192591803386.JavaMail.jira@cloud.prod.atl2.jboss.com>

putForExternalRead not silent on remote node
--------------------------------------------

                 Key: JBCACHE-1198
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1198
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani


Seeing WARN logging like this when using PFER with a replicating cache:

22:16:37,931  WARN pessimistic-shared:2839 - replication failure with method_call MethodName: _putForExternalRead; MethodIdInteger: 45; Args: (null, /test/com/foo/test/ENTITY/KEY, item, VALUE1) exception
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/test/com/foo/test/ENTITY/KEY, caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock=write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)
	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348)
	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299)
	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3958)
	at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2826)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330)
	at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77)
	at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624)
	at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533)
	at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365)
	at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:744)
	at org.jgroups.JChannel.up(JChannel.java:1137)
	at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:999)
	at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1023)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.cache.lock.TimeoutException: write lock for /test/com/foo/test/ENTITY/KEY could not be acquired after 0 ms. Locks: Read lock owners: []
Write lock owner: GlobalTransaction:<192.168.1.145:35562>:1
 (caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock info: write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0))
	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244)
	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
	... 33 more

Issue seems to be that the logic in CacheImpl.putForExternalRead that makes the call a no-op if the node exists and sets the failSilently option otherwise never gets executed on the remote node.  Instead the call gets handled by _replicate which just passes the MethodCall into the interceptor chain without setting any options.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 00:11:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 17 Oct 2007 00:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7559882.1192594263424.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Andrew Rubinger reassigned EJBTHREE-1057:
-----------------------------------------

    Assignee: Andrew Rubinger

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 4.2.2.GA
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 00:32:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 17 Oct 2007 00:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-820) Fix race in
 ServerInvokerCallbackHandler.handleCallback()
Message-ID: <17208857.1192595523247.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix race in ServerInvokerCallbackHandler.handleCallback()
---------------------------------------------------------

                 Key: JBREM-820
                 URL: http://jira.jboss.com/jira/browse/JBREM-820
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: callbacks
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.4.0.Beta1 (Pinto)


org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback() calls  callBackClient.setSessionId(sessionId) without synchronization.  It's doing that so that the callback is sent to the client with a sessionId that matches the appropriate InvokerCallbackHandler on the client side.  However, I think that if two separate threads made the same call at the same time, callbackClient's sessionId could get messed up.

The solution is to call callBackClient.setSessionId(sessionId) once in init() right after the Client has been created.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:03:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4866) TECHREVIEW:
 Installation Guide - Zip Installation
Message-ID: <2871061.1192600983255.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide - Zip Installation
-------------------------------------------------

                 Key: JBAS-4866
                 URL: http://jira.jboss.com/jira/browse/JBAS-4866
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:05:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4867) TECHREVIEW:
 Installation Guide - Graphical Installation
Message-ID: <10698891.1192601103903.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide - Graphical Installation
-------------------------------------------------------

                 Key: JBAS-4867
                 URL: http://jira.jboss.com/jira/browse/JBAS-4867
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:05:04 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4868) TECHREVIEW:
 Installation Guide - Chapter:'Test Your Installation'
Message-ID: <33490414.1192601104115.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide -  Chapter:'Test Your Installation'
------------------------------------------------------------------

                 Key: JBAS-4868
                 URL: http://jira.jboss.com/jira/browse/JBAS-4868
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:05:04 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4869) TECHREVIEW:
 Installation Guide - Chapter:'Getting Started'
Message-ID: <23725770.1192601104378.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECHREVIEW: Installation Guide -  Chapter:'Getting Started'
-----------------------------------------------------------

                 Key: JBAS-4869
                 URL: http://jira.jboss.com/jira/browse/JBAS-4869
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Vinu S Renish




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:07:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4866) TECHREVIEW:
 Installation Guide - Zip Installation
In-Reply-To: <2871061.1192600983255.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32206138.1192601223726.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4866?page=comments#action_12382906 ] 
            
Vinu S Renish commented on JBAS-4866:
-------------------------------------

Verify the following content in this chapter:
1. Zip download Filename - jboss-4.2.2.GA.zip
2. Zip file download location
3. Description

> TECHREVIEW: Installation Guide - Zip Installation
> -------------------------------------------------
>
>                 Key: JBAS-4866
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4866
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:11:18 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:11:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4867) TECHREVIEW:
 Installation Guide - Graphical Installation
In-Reply-To: <10698891.1192601103903.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8855243.1192601478637.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4867?page=comments#action_12382907 ] 
            
Vinu S Renish commented on JBAS-4867:
-------------------------------------

 Verify the following content in this chapter:
1. Do we have a GUI installer?
2. Installer Filename - jboss-4.2.2.GA.zip
3. Major Installation Steps
4. Shortcuts / XDG Menu applicable?


> TECHREVIEW: Installation Guide - Graphical Installation
> -------------------------------------------------------
>
>                 Key: JBAS-4867
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4867
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:13:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4868) TECHREVIEW:
 Installation Guide -  Chapter:'Test Your Installation'
In-Reply-To: <33490414.1192601104115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2914165.1192601583413.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4868?page=comments#action_12382908 ] 
            
Vinu S Renish commented on JBAS-4868:
-------------------------------------

Verify the following content in this chapter: 
1. Console output on server start up
2. Do we have a production profile? 
3. Image snapshot


> TECHREVIEW: Installation Guide -  Chapter:'Test Your Installation'
> ------------------------------------------------------------------
>
>                 Key: JBAS-4868
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4868
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 02:15:03 2007
From: jira-events at lists.jboss.org (Vinu S Renish (JIRA))
Date: Wed, 17 Oct 2007 02:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4869) TECHREVIEW:
 Installation Guide -  Chapter:'Getting Started'
In-Reply-To: <23725770.1192601104378.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21233685.1192601703648.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4869?page=comments#action_12382909 ] 
            
Vinu S Renish commented on JBAS-4869:
-------------------------------------

Is there a link we can point to for supported Operating System/Databases etc?

> TECHREVIEW: Installation Guide -  Chapter:'Getting Started'
> -----------------------------------------------------------
>
>                 Key: JBAS-4869
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4869
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Vinu S Renish
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:07:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 03:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1071) Possible problem in
 concurrent signalling from multiple threads
Message-ID: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>

Possible problem in concurrent signalling from multiple threads
---------------------------------------------------------------

                 Key: JBPM-1071
                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
MySQL 5.0.22
            Reporter: Jiri Pechanec
         Assigned To: Tom Baeyens
            Priority: Critical
         Attachments: expl.tar.gz

Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts the process instance that will go to the wait state on first node
3) Starts 20 threads that tries concurrently signal the same process instance
4) The second node writes a record to the database

The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Action 2
Action 2
Action 2
Action 2
Action 2 1
Action 2 1
Action 2 1
Action 2 1
Signalist 5
Signalist 6
Signalist 8
Signalist 12
Signalist 7
Signalist 13
Signalist 14
Signalist 15
Signalist 9
Signalist 16
Signalist 17
Signalist 18
Signalist 4
Success 7
Failure 13

Explanation of the outcome
4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
3 threads successfully executed the signal operation but no real action was performed
13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:07:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 03:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1071) Possible problem in
 concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10436493.1192604823943.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]

Jiri Pechanec updated JBPM-1071:
--------------------------------

    Attachment: expl.tar.gz

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:09:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 03:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1280) Automatically
 import types into a package config if no config exists
Message-ID: <11072875.1192604943226.JavaMail.jira@cloud.prod.atl2.jboss.com>

Automatically import types into a package config if no config exists
--------------------------------------------------------------------

                 Key: JBRULES-1280
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1280
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE


based on what it finds in the jar.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 03:17:17 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 17 Oct 2007 03:17:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21552592.1192605437644.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382912 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

You need to deploy the juddi-service.sar from the jbossws/thirdparty directory.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 04:16:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 04:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1072) Concurrent
 JobExecutors can process the same job in parallel
Message-ID: <8119670.1192608963680.JavaMail.jira@cloud.prod.atl2.jboss.com>

Concurrent JobExecutors can process the same job in parallel
------------------------------------------------------------

                 Key: JBPM-1072
                 URL: http://jira.jboss.com/jira/browse/JBPM-1072
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
MySQL 5.0.22
            Reporter: Jiri Pechanec
         Assigned To: Tom Baeyens
         Attachments: expl.tar.gz

Attached is a simple test case that
1) Deploys process definition with two nodes
2) Starts 20 executor threads
2) Starts the process instance that will asynchronously execute action on the second node
4) The second node writes a record to the database

The test case needs to be executed multiple times to see the incorrect behaviour.
This is an example of run output
Isol 8
Action 1
Success 0
Failure 0
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2 1
Action 2
Action 2
Action 2 1
Action 2 1
Action 2
Action 2 1

Explanation of the outcome
9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created)


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 04:16:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Wed, 17 Oct 2007 04:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1072) Concurrent
 JobExecutors can process the same job in parallel
In-Reply-To: <8119670.1192608963680.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18039029.1192608963858.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1072?page=all ]

Jiri Pechanec updated JBPM-1072:
--------------------------------

    Attachment: expl.tar.gz

Test case is TestMultiJobExecutor

> Concurrent JobExecutors can process the same job in parallel
> ------------------------------------------------------------
>
>                 Key: JBPM-1072
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1072
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts 20 executor threads
> 2) Starts the process instance that will asynchronously execute action on the second node
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Success 0
> Failure 0
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2 1
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2
> Action 2 1
> Explanation of the outcome
> 9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 05:18:19 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Wed, 17 Oct 2007 05:18:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <22446557.1192612699908.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]

Jeff Mesnil updated JBMESSAGING-375:
------------------------------------

    Attachment: patch-JBMESSAGING-375.txt

simpler patch: group ID binding is handled directly in RoundRobinDistributor

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 05:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 17 Oct 2007 05:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-467) Serialize container
 proxies out of vm
In-Reply-To: <21248201.1190887061041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29856113.1192613404389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-467?page=all ]

Kabir Khan reassigned JBAOP-467:
--------------------------------

    Assignee: Flavia Rainone  (was: Kabir Khan)

> Serialize container proxies out of vm
> -------------------------------------
>
>                 Key: JBAOP-467
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-467
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Flavia Rainone
>             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

        


From jira-events at lists.jboss.org  Wed Oct 17 05:30:06 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 17 Oct 2007 05:30:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3281188.1192613406528.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Kabir Khan reassigned JBAOP-480:
--------------------------------

    Assignee: Flavia Rainone

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 06:43:03 2007
From: jira-events at lists.jboss.org (Ian Priest (JIRA))
Date: Wed, 17 Oct 2007 06:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-178) ClassCastException
 using Process Designer 3.1.0SP1
Message-ID: <15484296.1192617783364.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException using Process Designer 3.1.0SP1
--------------------------------------------------

                 Key: GPD-178
                 URL: http://jira.jboss.com/jira/browse/GPD-178
             Project: JBoss jBPM GPD
          Issue Type: Bug
          Components: jpdl
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
         Environment: Windows XP, Java 1.6.0_02, Eclipse 3.3, suite_3.2.2 (which packages GPD 3.1.0SP1)
            Reporter: Ian Priest
         Assigned To: Koen Aers


Get a ClassCastException using the Process Designer to open the gpd.xml in the websales example provided with the 3.2.2 suite download.

The exception is (full stack trace to follow)

java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement

The problem seems to lie in class GenericElementXmlAdapter, which deals with the classes though the SemanticElement interface, which both classes do implement. The following class reproduces the runtime issue and demonstrates the faulty cast:

import org.jbpm.gd.common.model.GenericElement;
import org.jbpm.gd.common.model.SemanticElement;
import org.jbpm.gd.jpdl.model.ProcessDefinition;


public class Play {

	public static void main(String[] args) {
		
		ProcessDefinition pd = new ProcessDefinition();
		SemanticElement se = (SemanticElement)pd;
		GenericElement ge = (GenericElement)se;
	}
}

which gives a runtime error:

Exception in thread "main" java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
at Play.main(Play.java:15) 

See also the forum discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121355

Full stack trace:

!ENTRY org.eclipse.ui 4 0 2007-10-16 11:12:33.685
!MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
!STACK 0
java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2719)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169) 




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 07:10:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 17 Oct 2007 07:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <1253999.1192619403518.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12382954 ] 
            
Tim Fox commented on JBMESSAGING-375:
-------------------------------------

One thought here.

Would it be possible to have this functionality working across a cluster too?

I.e. all messages sent using a particular value of JMSXGroupid go to the same consumer on the cluster?

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 07:43:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 17 Oct 2007 07:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1198)
 putForExternalRead not silent on remote node
In-Reply-To: <22737059.1192591803386.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3382337.1192621383454.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1198?page=all ]

Manik Surtani updated JBCACHE-1198:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA

> putForExternalRead not silent on remote node
> --------------------------------------------
>
>                 Key: JBCACHE-1198
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1198
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Seeing WARN logging like this when using PFER with a replicating cache:
> 22:16:37,931  WARN pessimistic-shared:2839 - replication failure with method_call MethodName: _putForExternalRead; MethodIdInteger: 45; Args: (null, /test/com/foo/test/ENTITY/KEY, item, VALUE1) exception
> org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/test/com/foo/test/ENTITY/KEY, caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock=write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299)
> 	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
> 	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3958)
> 	at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2826)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330)
> 	at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77)
> 	at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624)
> 	at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533)
> 	at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365)
> 	at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:744)
> 	at org.jgroups.JChannel.up(JChannel.java:1137)
> 	at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:999)
> 	at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1023)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.cache.lock.TimeoutException: write lock for /test/com/foo/test/ENTITY/KEY could not be acquired after 0 ms. Locks: Read lock owners: []
> Write lock owner: GlobalTransaction:<192.168.1.145:35562>:1
>  (caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock info: write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0))
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
> 	... 33 more
> Issue seems to be that the logic in CacheImpl.putForExternalRead that makes the call a no-op if the node exists and sets the failSilently option otherwise never gets executed on the remote node.  Instead the call gets handled by _replicate which just passes the MethodCall into the interceptor chain without setting any options.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:09:06 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Wed, 17 Oct 2007 08:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-178) ClassCastException
 using Process Designer 3.1.0SP1
In-Reply-To: <15484296.1192617783364.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11992738.1192622946938.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-178?page=comments#action_12382964 ] 
            
Koen Aers commented on GPD-178:
-------------------------------

I cannot reproduce this issue. The gpd.xml is not supposed to open with the graphical process designer. Only the processdefinition.xml should do this. Does this happen with clean downloads and empty workspaces?

Regards,
Koen

> ClassCastException using Process Designer 3.1.0SP1
> --------------------------------------------------
>
>                 Key: GPD-178
>                 URL: http://jira.jboss.com/jira/browse/GPD-178
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>         Environment: Windows XP, Java 1.6.0_02, Eclipse 3.3, suite_3.2.2 (which packages GPD 3.1.0SP1)
>            Reporter: Ian Priest
>         Assigned To: Koen Aers
>
> Get a ClassCastException using the Process Designer to open the gpd.xml in the websales example provided with the 3.2.2 suite download.
> The exception is (full stack trace to follow)
> java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> The problem seems to lie in class GenericElementXmlAdapter, which deals with the classes though the SemanticElement interface, which both classes do implement. The following class reproduces the runtime issue and demonstrates the faulty cast:
> import org.jbpm.gd.common.model.GenericElement;
> import org.jbpm.gd.common.model.SemanticElement;
> import org.jbpm.gd.jpdl.model.ProcessDefinition;
> public class Play {
> 	public static void main(String[] args) {
> 		
> 		ProcessDefinition pd = new ProcessDefinition();
> 		SemanticElement se = (SemanticElement)pd;
> 		GenericElement ge = (GenericElement)se;
> 	}
> }
> which gives a runtime error:
> Exception in thread "main" java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> at Play.main(Play.java:15) 
> See also the forum discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121355
> Full stack trace:
> !ENTRY org.eclipse.ui 4 0 2007-10-16 11:12:33.685
> !MESSAGE Unable to create editor ID org.jbpm.gd.jpdl.editor: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> !STACK 0
> java.lang.ClassCastException: org.jbpm.gd.jpdl.model.ProcessDefinition cannot be cast to org.jbpm.gd.common.model.GenericElement
> at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
> at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
> at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
> at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
> at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299)
> at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179)
> at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
> at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400)
> at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
> at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
> at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604)
> at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
> at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
> at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
> at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
> at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
> at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
> at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
> at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774)
> at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673)
> at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2719)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
> at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
> at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
> at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
> at org.eclipse.ui.actions.OpenWithMenu$3.handleEvent(OpenWithMenu.java:226)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1169) 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:34:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Wed, 17 Oct 2007 08:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28310807.1192624443745.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4754?page=all ]

Rajesh Rajasekaran resolved JBAS-4754.
--------------------------------------

    Resolution: Done

Did a full run and tck1.4 is now at 100% for 4.2.2.GA

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:39:04 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 17 Oct 2007 08:39:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4805)
 InitialContextFactory.getHAContext() should not use hardcoded localhost for
 lookup
In-Reply-To: <30863935.1191921483315.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19768221.1192624744098.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4805?page=all ]

Galder Zamarreno updated JBAS-4805:
-----------------------------------

    Workaround Description: 
+ Workaround for injecting ConnectionFactory instances - Inject JmsXA instead of ConnectionFactory

   @Resource(mappedName="java:/JmsXA", type=javax.jms.ConnectionFactory.class) 
   private ConnectionFactory factory;

+ Workarounds for injecting Queue/Topic instances:

1.- Not to inject Queue and instead, assuming the queue name is "queue/A" use the
following code to initialise it the first time you use the Queue instance variable:

String bindAddress = System.getProperty("jboss.bind.address") == null ? "localhost" : System.getProperty("jboss.bind.address");
InitialContext ic = new InitialContext();
Queue queueA = (Queue)ic.lookup("jnp://" + bindAddress + ":1100/queue/A");

2.- For this second option, let's assume the queue name is "queue/B". In this case,
you can add META-INF/jboss.xml to your EJB jar deployment, which looks like this:

<?xml version="1.0"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
<jboss>
<enterprise-beans>
<session>
<ejb-name>InhaltPruefungVerwaltungBean</ejb-name>
<resource-ref>
<res-ref-name>queue/ref/B</res-ref-name>
<jndi-name>jnp://${jboss.bind.address:localhost}:1100/queue/B</jndi-name>
</resource-ref>
</session>
</enterprise-beans>
</jboss>

And inject the Queue in your EJB this way:

@Resource(mappedName="java:comp/env/queue/ref/B")
private Queue queueB;

  was:
A possible workaround (that the customer is trying out at the moment is):

in deploy/cluster-service.xml:

<mbean code="org.jboss.ha.jndi.HANamingService"
name="jboss:service=HAJNDI">
...
<!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
<attribute name="BindAddress">localhost</attribute> 


Updated with workarounds from support case.

> InitialContextFactory.getHAContext() should not use hardcoded localhost for lookup
> ----------------------------------------------------------------------------------
>
>                 Key: JBAS-4805
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4805
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2
>            Reporter: Galder Zamarreno
>         Assigned To: William DeCoste
>
> org.jboss.ejb3.InitialContextFactory.getHAContext() contains:
> env.put(Context.PROVIDER_URL, "localhost:" + getHaJndiPort());
> InitialContext haCtx = new InitialContext(env);
> The code should not have hardcoded localhost because as soon as someone binds JBoss 
> to something different, a localhost lookup will fail.
> This could should instead check HAJNDI service's BindAddress attribute and use that.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:41:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 08:41:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4754) Do a full CTS1.4
 run to check for regressions.
In-Reply-To: <30457303.1190796892507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18278504.1192624865934.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4754?page=comments#action_12382973 ] 
            
Dimitris Andreadis commented on JBAS-4754:
------------------------------------------

Excellent! I'll do a final pass over the release notes and tag after that.

> Do a full CTS1.4 run to check for regressions.
> ----------------------------------------------
>
>                 Key: JBAS-4754
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4754
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Rajesh Rajasekaran
>            Priority: Blocker
>             Fix For: JBossAS-4.2.2.GA
>
>
> Before releasing, we should perform a final CTS run.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 08:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4852) EJB3 web service
 endpoints ignore metadata in jboss.xml
In-Reply-To: <16146379.1192175643414.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6357857.1192625823738.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4852?page=all ]

Dimitris Andreadis updated JBAS-4852:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

To the next release.

> EJB3 web service endpoints ignore metadata in jboss.xml
> -------------------------------------------------------
>
>                 Key: JBAS-4852
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4852
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For: JBossAS-4.2.3.GA
>
>
> This is related to JBWS-1813
> It needs to be decided whether jboss-4.2.2 can go out despite this issue.
> Currently, users are forced to use annotations on the bean.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 08:59:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 08:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4696) Arrange community
 documents for 4.2.2.GA
In-Reply-To: <25461197.1189416611004.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23889102.1192625943859.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4696?page=all ]

Dimitris Andreadis updated JBAS-4696:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.2.2.GA)

I'm just unscheduling this issue, because it will continue after the release.

I'm about to tag the release today.

> Arrange community documents for 4.2.2.GA
> ----------------------------------------
>
>                 Key: JBAS-4696
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4696
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Michael Smith
>            Priority: Blocker
>
> We *must* produce community documents for AS.
> At the moment, the only 4.2.x documentation that exists is the EAP one.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 09:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9559732.1192626063672.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382978 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

I'm about to tag, so this needs closing, or if work is on-going move to the next release.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:19:06 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Wed, 17 Oct 2007 09:19:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10266724.1192627146489.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12382992 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

The juddi-service.sar is already deployed in the 'all' config. This is just some classpath issue and we can move on with the release.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:41:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Wed, 17 Oct 2007 09:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
Message-ID: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>

Redelivery flags not updated in case of JBossMQ node failure
------------------------------------------------------------

                 Key: JBAS-4870
                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JMS service
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Adrian Brock
         Assigned To: Adrian Brock
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA


When the JBossMQ node fails with messages currently being delivered to the clients,
the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).

The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
(which it won't do if it has crashed).

A potential fix, is to update the status early before delivering the message to the client,
see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 09:47:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 09:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16879252.1192628823672.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis updated JBAS-4811:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 10:01:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 17 Oct 2007 10:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4591) Create a generic way
 to createDestinations on MDB Container
In-Reply-To: <32782847.1186095349327.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8808884.1192629663303.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4591?page=all ]

Dimitris Andreadis updated JBAS-4591:
-------------------------------------

    Fix Version/s:     (was: JBossAS-4.4.0.CR1)

Unscheduling, as 4.4.0.CR1 version has been archived.

> Create a generic way to createDestinations on MDB Container
> -----------------------------------------------------------
>
>                 Key: JBAS-4591
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4591
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>
> We should provide a generic way to configure the MDB container to create destinations in other providers besidess JBossMQ.
> The Implementation I'm going to do will use a Property Name for the MBean responsible to create destinations and method names for the create methods.
> Also... we will support two signatures... one (createTopic(String Topicname) or createQueue(String queueName))
> or
> createTopic(String TopicName, String jndti) or createQueue(String queueName, String jndi)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:16:24 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 11:16:24 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1281) ExecutorService
 cannot be shared
Message-ID: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>

ExecutorService cannot be shared
--------------------------------

                 Key: JBRULES-1281
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2, 4.0.1
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0


Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:30:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 11:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1281) ExecutorService
 cannot be shared
In-Reply-To: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32779624.1192635003468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1281?page=all ]

Mark Proctor updated JBRULES-1281:
----------------------------------

    Attachment: UnshareExecutorService.patch

> ExecutorService cannot be shared
> --------------------------------
>
>                 Key: JBRULES-1281
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>         Attachments: UnshareExecutorService.patch
>
>
> Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:32:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 11:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1281) ExecutorService
 cannot be shared
In-Reply-To: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23642386.1192635123600.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1281?page=comments#action_12383049 ] 
            
Mark Proctor commented on JBRULES-1281:
---------------------------------------

commit to trunk:
commit -m "JBRULES-1281 ExecutorService cannot be shared
-Added cached reflection class resolve and object instantiator to ClassUtil.
-Made RuleBaseUpdateListenerFactory and ExecutorServiceFactory use ClassUtil.
-Now each new stateful or stateless session get's its own instance of ExecutorService." C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooRuleBase.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatefulSession.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatelessSession.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/RuleBaseConfiguration.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/ExecutorServiceFactory.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/RuleBaseUpdateListenerFactory.java C:/dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/util/ClassUtils.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/RuleBaseConfiguration.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooRuleBase.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatefulSession.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/reteoo/ReteooStatelessSession.java
    Adding         dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/ExecutorServiceFactory.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/spi/RuleBaseUpdateListenerFactory.java
    Sending        dev/jbossrules/4.1.0/drools-core/src/main/java/org/drools/util/ClassUtils.java
    Transmitting file data ...
    Committed revision 15887.


> ExecutorService cannot be shared
> --------------------------------
>
>                 Key: JBRULES-1281
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>         Attachments: UnshareExecutorService.patch
>
>
> Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:40:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 11:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1199) Update
 InvalidatorInterceptorTest to use Node.isValid()
Message-ID: <2782171.1192635603222.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update InvalidatorInterceptorTest to use Node.isValid()
-------------------------------------------------------

                 Key: JBCACHE-1199
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For: 2.1.0.GA


InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node.  See the forum link.  Need to replace with a call to isValid() whenever that is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:48:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 11:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-130) Problems with
	reincarnation
Message-ID: <23412040.1192636084470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-130?page=all ]

Bela Ban updated JGRP-130:
--------------------------

    Fix Version/s: 2.5.2

Needs to be backported to 2.5.2

> Problems with reincarnation
> ---------------------------
>
>                 Key: JGRP-130
>                 URL: http://jira.jboss.com/jira/browse/JGRP-130
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6, 2.5.2
>
>         Attachments: tcp.xml
>
>
> Problems with reincarnation
> ===========================
> Author: Bela Ban
> Version: $Id$
> The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
> bind_port is set (not set by default).
> Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a
> higher port, say 5002. This depends on how many other processes requested a port in between the start and restart
> of the member.
> JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically)
> *increasing* across a single machine. If this is not the case, then the following problems can occur:
> 1. Restart:
> When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded,
> then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table),
> retransmission requests sent to the new P will fail.
> 2. Shunning:
> Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of
> those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have
> processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time,
> when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so
> they could assume each other's identity !
> Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a
> new process and in case #2, the list is process-wide, but not machine-wide.
> Again, these problems occur *only* when the OS reuses previously assigned ports.
> SOLUTION:
> A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we
> don't reuse previous addresses
> B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host.
> Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity.
> The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:48:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 11:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JGRP-130) Problems with
	reincarnation
Message-ID: <3012786.1192636084921.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-130?page=all ]

Bela Ban reopened JGRP-130:
---------------------------

             

> Problems with reincarnation
> ---------------------------
>
>                 Key: JGRP-130
>                 URL: http://jira.jboss.com/jira/browse/JGRP-130
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6, 2.5.2
>
>         Attachments: tcp.xml
>
>
> Problems with reincarnation
> ===========================
> Author: Bela Ban
> Version: $Id$
> The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
> bind_port is set (not set by default).
> Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a
> higher port, say 5002. This depends on how many other processes requested a port in between the start and restart
> of the member.
> JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically)
> *increasing* across a single machine. If this is not the case, then the following problems can occur:
> 1. Restart:
> When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded,
> then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table),
> retransmission requests sent to the new P will fail.
> 2. Shunning:
> Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of
> those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have
> processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time,
> when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so
> they could assume each other's identity !
> Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a
> new process and in case #2, the list is process-wide, but not machine-wide.
> Again, these problems occur *only* when the OS reuses previously assigned ports.
> SOLUTION:
> A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we
> don't reuse previous addresses
> B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host.
> Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity.
> The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 11:57:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 17 Oct 2007 11:57:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1121) Investigate the
 suitability of not copying child maps into workspace
In-Reply-To: <14759070.1183724948890.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30242184.1192636624706.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1121?page=all ]

Manik Surtani resolved JBCACHE-1121.
------------------------------------

    Resolution: Done

> Investigate the suitability of not copying child maps into workspace
> --------------------------------------------------------------------
>
>                 Key: JBCACHE-1121
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1121
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Optimistic Locking
>    Affects Versions: 2.0.0.GA, 1.4.0.GA, 1.4.1.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:07:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Wed, 17 Oct 2007 12:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Moved: (GPD-179) pages.xml doesn't work
 with pageflow editor
Message-ID: <6550650.1192637223887.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-179?page=all ]

Koen Aers moved JBIDE-642 to GPD-179:
-------------------------------------

              Project: JBoss jBPM GPD  (was: JBoss Tools)
                  Key: GPD-179  (was: JBIDE-642)
          Component/s: jpdl
                           (was: jbpm)
        Fix Version/s: jBPM jPDL Designer 3.1.1
                           (was: 2.0.1)
    Affects Version/s:     (was: 2.0.0.Beta3)
                           (was: 2.0.0.CR1)

> pages.xml doesn't work with pageflow editor
> -------------------------------------------
>
>                 Key: GPD-179
>                 URL: http://jira.jboss.com/jira/browse/GPD-179
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Max Andersen
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu.
> and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get 
> java.lang.NullPointerException
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> 	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:09:04 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Wed, 17 Oct 2007 12:09:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-179) pages.xml doesn't
 work with pageflow editor
Message-ID: <14500344.1192637344264.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-179?page=comments#action_12383077 ] 
            
Max Andersen commented on GPD-179:
----------------------------------

koen - please don't *move* the bugs because then we can't see them as outstanding issues for JBossTools/RHDS. Link to it instead please.

> pages.xml doesn't work with pageflow editor
> -------------------------------------------
>
>                 Key: GPD-179
>                 URL: http://jira.jboss.com/jira/browse/GPD-179
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>            Reporter: Max Andersen
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> a pages.xml with a proper page flow syntax does not have the pageflow editor in the right click menu.
> and when using Open with... and choosing jBpm pageflow designer (not the correct name is it ?) I get 
> java.lang.NullPointerException
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addProcessDiagramDimension(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowContentProvider.addGraphicalInfo(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.initInput(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowGraphicalEditorPage.init(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.addGraphPage(Unknown Source)
> 	at org.jbpm.ui.pageflow.editor.PageFlowEditor.createPages(Unknown Source)
> 	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
> 	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
> 	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
> 	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
> 	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
> 	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:32:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 12:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1200) Node removal with
 invalidation leaves child data accessible
Message-ID: <4642624.1192638724532.JavaMail.jira@cloud.prod.atl2.jboss.com>

Node removal with invalidation leaves child data accessible
-----------------------------------------------------------

                 Key: JBCACHE-1200
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1200
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
            Priority: Critical
             Fix For: 2.1.0.CR1


With invalidation, when a node that has children is removed, on remote caches the data in the children is still visible; e..g

cache1.put(childFqn, key, value);
cache1.removeNode(parentFqn);
// This assertion fails
assertNull(cache2.get(childFqn, key));

InvalidationInterceptorTest.testPessimisticNodeRemoval() and testOptimisticNodeRemoval() have been modified to show this issue.

This is a significant problem for the Hibernate/JBC integration

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:34:04 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 12:34:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-130) Problems with
	reincarnation
Message-ID: <32278397.1192638844330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-130?page=all ]

Bela Ban resolved JGRP-130.
---------------------------

    Resolution: Done

backported to 2.5.2

> Problems with reincarnation
> ---------------------------
>
>                 Key: JGRP-130
>                 URL: http://jira.jboss.com/jira/browse/JGRP-130
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.2.9
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.5.2, 2.6
>
>         Attachments: tcp.xml
>
>
> Problems with reincarnation
> ===========================
> Author: Bela Ban
> Version: $Id$
> The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless
> bind_port is set (not set by default).
> Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a
> higher port, say 5002. This depends on how many other processes requested a port in between the start and restart
> of the member.
> JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically)
> *increasing* across a single machine. If this is not the case, then the following problems can occur:
> 1. Restart:
> When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded,
> then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table),
> retransmission requests sent to the new P will fail.
> 2. Shunning:
> Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of
> those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have
> processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time,
> when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so
> they could assume each other's identity !
> Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a
> new process and in case #2, the list is process-wide, but not machine-wide.
> Again, these problems occur *only* when the OS reuses previously assigned ports.
> SOLUTION:
> A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we
> don't reuse previous addresses
> B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host.
> Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity.
> The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:40:06 2007
From: jira-events at lists.jboss.org (Gunnar Grim (JIRA))
Date: Wed, 17 Oct 2007 12:40:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1074) Circular @EJB3
 references in session beans fail to deploy.
Message-ID: <7270653.1192639206697.JavaMail.jira@cloud.prod.atl2.jboss.com>

Circular @EJB3 references in session beans fail to deploy.
----------------------------------------------------------

                 Key: EJBTHREE-1074
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.1.GA
            Reporter: Gunnar Grim


The following circular references makes the application undeployable:

In ArchiveBrokerBean:

  @EJB 
  private SeriesBrokerLocal itsSeriesBroker;	

In SeriesBrokerBean

  @EJB 
  private ArchiveBrokerLocal itsArchiveBroker;	

Circular references like these work fine in Glassfish but JBoss shows the following error message:

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
  Depends On Me:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
  Depends On Me:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3

ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
  State: NOTYETINSTALLED
  I Depend On:
    jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
    persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU



-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 12:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11399830.1192639683658.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

    Attachment: Dumper.patch

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 12:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10920215.1192639683964.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor updated JBRULES-1252:
----------------------------------

        Fix Version/s: 4.0.2_SOA_4.2-CP1
                       4.0.3
                       4.1.0
                           (was: 4.0.2)
    Affects Version/s: 4.0.2

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 12:50:05 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 12:50:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1252) DrlDumper does
 not dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22371207.1192639805158.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=comments#action_12383112 ] 
            
Mark Proctor commented on JBRULES-1252:
---------------------------------------

commit -m "JBRULES-1252 DrlDumper does not dump functions
-Fixed function dumper issues
-added tests for various other globals, imports etc.
-updated to add quotes to other attributes like date-effective." C:/dev/jbossrules/4.1.0/drools-compiler/src/main/java/org/drools/lang/DrlDumper.java C:/dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTest.java C:/dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTestHelper.java C:/dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.drl C:/dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.xml
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/main/java/org/drools/lang/DrlDumper.java
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTest.java
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/java/org/drools/xml/DumperTestHelper.java
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.drl
    Sending        dev/jbossrules/4.1.0/drools-compiler/src/test/resources/org/drools/xml/test_RoundTrip.xml
    Transmitting file data ...
    Committed revision 15895.

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 13:28:14 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Wed, 17 Oct 2007 13:28:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-821) JBoss Remoting fails
	under load
Message-ID: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Remoting fails under load
-------------------------------

                 Key: JBREM-821
                 URL: http://jira.jboss.com/jira/browse/JBREM-821
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP1
            Reporter: Ovidiu Feodorov
         Assigned To: Trustin Lee
            Priority: Blocker


This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.

Phrasing belongs to Tim:

JBoss Remoting fails with various different errors when under extreme load.

To replicate this, set up two clustered server nodes, using a MySQL database.

These can both be on the same machine, using ServiceBindingManager.

On a second machine run Ovidiu's messkit toolki, first to send some messages:

mess -stat send -size 10240 50000

And then to receive them back using 50 concurrent consumers:

mess -stat -sessions 50 receive all

You will notice that JBoss Remoting fails with errors:

I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?

I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.

It also seems remoting is continually timing out and recreating connections - this could also be a source of error.

How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:15:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 17 Oct 2007 14:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBSER-97)
 RegularObjectPersister.readSlotWithFields to log number of fields being
 read
In-Reply-To: <32246194.1192448283370.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17856604.1192644903591.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBSER-97?page=all ]

Galder Zamarreno reassigned JBSER-97:
-------------------------------------

    Assignee: Galder Zamarreno  (was: Clebert Suconic)

> RegularObjectPersister.readSlotWithFields to log number of fields being read
> ----------------------------------------------------------------------------
>
>                 Key: JBSER-97
>                 URL: http://jira.jboss.com/jira/browse/JBSER-97
>             Project: JBoss Serialization
>          Issue Type: Task
>    Affects Versions: 1.0.3 GA
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>
> writeSlotWithFields logs the slot name and number of fields to be written.
> for debugging pupouses, readSlotWithFields could do with logging the number of fields written too, i.e.
> RegularObjectPersister.readSlotWithFields() to start like this:
>      short numberOfFields = (short)fieldsKey.length;
>       if (isDebug)
>       {
>          log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName() + " and " + numberOfFields + " fields");
>       }
> instead of:
>        if (isDebug)
>        {
>           log.debug("readSlotWithFields slot=" + slot.getSlotClass().getName());
>        }
>        //final int numberOfFields = input.readShort();
>       short numberOfFields = (short)fieldsKey.length;

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:22:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 17 Oct 2007 14:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBSER-98) Write slot with
 fields only if both readObject and writeObject are missing
In-Reply-To: <1789794.1192530433263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16139517.1192645323336.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBSER-98?page=all ]

Galder Zamarreno reassigned JBSER-98:
-------------------------------------

    Assignee: Galder Zamarreno  (was: Clebert Suconic)

> Write slot with fields only if both readObject and writeObject are missing
> --------------------------------------------------------------------------
>
>                 Key: JBSER-98
>                 URL: http://jira.jboss.com/jira/browse/JBSER-98
>             Project: JBoss Serialization
>          Issue Type: Feature Request
>    Affects Versions: 1.0.3 GA
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>
> Over the last few weeks, I've been dealing with a funky support case which showed the following 
> stacktrace:
> ...
> Caused by: org.jboss.serial.exception.SerializationException: Excepted to be String
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1120)
> at org.jboss.serial.classmetamodel.StreamingClass.readStream(StreamingClass.java:71)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:381)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
> at org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
> at org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
> at org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
> at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readObject(DataContainer.java:845)
> at org.jboss.serial.io.MarshalledObjectForLocalCalls.get(MarshalledObjectForLocalCalls.java:60)
> at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> ... 28 more
> Caused by: java.lang.ClassCastException: org.jboss.serial.finalcontainers.IntegerContainer
> at org.jboss.serial.objectmetamodel.DataContainer$DataContainerInput.readUTF(DataContainer.java:1116)
> ... 42 more 
> The cause of the issue was that the customer had a class where it had re-implemented 
> readObject(java.io.ObjectInputStream stream) but had not re-implemented 
> writeObject(java.io.ObjectOutputStream stream). This is obviously a programming error on their side,
> but it took a while to detect such stupid mistake.
> The problem within JBoss Serialization was that because this class didn't have a writeObject() 
> reimplementation, it was a writing the class as a slot with fields, but when it came to reading it, it 
> was reading the class as a slot with method because readObject had been reimplemented. The 
> next time a slot with fields was read, the fields were mixed up.
> To avoid these type of situations, I'd suggest that:
> - JBS only writes as fields if *both* writeObject and readObject are missing. Right now, can't see a 
> situation where you'd implement one and not the other, thoughts?

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:55:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 14:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
Message-ID: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>

OPTIMISTIC locking requires SyncCommitPhase to be true
------------------------------------------------------

                 Key: JBCACHE-1201
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Replication
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
             Fix For: 2.1.0.BETA1


When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:

tm.begin();
cache1.put(fqn, KEY, VALUE1);
tm.commit();
      
assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));

With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.

A simple sleep after the commit call will also make this test pass

My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.

The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.

Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 14:57:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 14:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17604160.1192647423382.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=comments#action_12383122 ] 
            
Brian Stansberry commented on JBCACHE-1201:
-------------------------------------------

This appears to not be an issue with INVALIDATION, although I'm not 100% certain of that.

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.BETA1
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:05:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1252) DrlDumper does not
 dump import functions
In-Reply-To: <8020220.1191594483274.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29337642.1192647904086.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1252?page=all ]

Mark Proctor closed JBRULES-1252.
---------------------------------

    Resolution: Done

> DrlDumper does not dump import functions
> ----------------------------------------
>
>                 Key: JBRULES-1252
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1252
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Damien Delautre
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: DrlDumper.patch, DrlDumper.patch, Dumper.patch
>
>
> When I dump a PackageDescr, the import function statements are ignored

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:05:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1281) ExecutorService
 cannot be shared
In-Reply-To: <32255069.1192634184321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3979950.1192647904251.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1281?page=all ]

Mark Proctor closed JBRULES-1281.
---------------------------------

    Resolution: Done

> ExecutorService cannot be shared
> --------------------------------
>
>                 Key: JBRULES-1281
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1281
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.1, 4.0.2
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>         Attachments: UnshareExecutorService.patch
>
>
> Currently the RuleBaseConfigration instantiations and the ExecutorService once, which means each WM session uses the same ExecutorService and overwrites the CommandExecutor - clearly a bug.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:07:08 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:07:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1277) BRDRLPersitence is
 not rendering OR's correctly
In-Reply-To: <4218717.1192430943289.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7569022.1192648028851.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1277?page=all ]

Mark Proctor closed JBRULES-1277.
---------------------------------

    Resolution: Done

> BRDRLPersitence is not rendering OR's correctly
> -----------------------------------------------
>
>                 Key: JBRULES-1277
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1277
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.2_SOA_4.2-CP1
>
>         Attachments: BRDRLPersistence.java, BRDRLPersistence.old
>
>
> Has been corrected in trunk, this is a patch for 4.0.3 and SOA branch (if its not too late for it).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:12:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1272) DSL : String index
 out of range: -1
In-Reply-To: <32255549.1192195503694.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24800588.1192648323327.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1272?page=all ]

Mark Proctor closed JBRULES-1272.
---------------------------------


> DSL : String index out of range: -1
> -----------------------------------
>
>                 Key: JBRULES-1272
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1272
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Delbart Vincent
>         Assigned To: Edson Tirelli
>            Priority: Critical
>             Fix For: 4.0.3, 4.1.0, FUTURE, 4.0.2_SOA_4.2-CP1
>
>
> Hi,
> I have a problem with my DSL and the 4.0.2 version :
> this sentence doesn't work in 4.0.2 :
> [condition][]there is at least {number} {object}=ArrayList( size >= {number}) from collect( {object}() )
> log :
> !ENTRY org.eclipse.ui 4 0 2007-10-11 14:29:29.052
> !MESSAGE String index out of range: -1
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>         at java.lang.String.substring(String.java:1768)
>         at org.drools.lang.dsl.DefaultDSLMappingEntry.setMappingKey(DefaultDSLMappingEntry.java:139)
>         at org.drools.eclipse.dsl.editor.MappingEditor.okPressed(Unknown Source)
>         at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:508)
>         at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
>         at org.eclipse.jface.window.Window.open(Window.java:796)
>         at org.drools.eclipse.dsl.editor.DSLEditor$8.widgetSelected(Unknown Source)
>         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
>         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> If I put two blanks between {number} {object}, it's working.
> [condition][]there is at least {number}  {object}=ArrayList( size >= {number}) from collect( {object}() )

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 15:12:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Wed, 17 Oct 2007 15:12:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1279) Memory leak in
	release 4.0.2
In-Reply-To: <25598440.1192461184348.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10973978.1192648324200.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1279?page=all ]

Mark Proctor closed JBRULES-1279.
---------------------------------


> Memory leak in release 4.0.2
> ----------------------------
>
>                 Key: JBRULES-1279
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1279
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: tested with windows jdk5 and jdk6
>            Reporter: Paul Jackson
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>
> I  have observed memory leaks in our application after upgrading to the latest 4.0.2 release. I have replicated the problem with the sample code below:
> DroolsTest.java
> import java.io.InputStreamReader;
> import java.io.Reader;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.StatefulSession;
> import org.drools.compiler.PackageBuilder;
> import org.drools.rule.Package;
> public class DroolsTest {
> 	public void run() throws Exception {
> 		
> 		RuleBase ruleBase = createRuleBase();
> 		long counter = 0;
> 		while(true) {
> 			StatefulSession session = ruleBase.newStatefulSession(false);
> 			if(++counter % 100 == 0) {
> 				System.out.println(counter);
> 			}
> 			session.dispose();
> 		}
> 	}
> 	
> 	private RuleBase createRuleBase() throws Exception {
> 		Reader source = new InputStreamReader( this.getClass().getResourceAsStream( "HelloWorld.drl" ) );
> 		PackageBuilder builder = new PackageBuilder();
> 		builder.addPackageFromDrl( source );
> 		if ( builder.hasErrors() ) {
> 		    System.out.println( builder.getErrors().toString() );
> 		    throw new RuntimeException( "Unable to compile \"HelloWorld.drl\".");
> 		}
> 		Package pkg = builder.getPackage();
> 		
> 		RuleBase ruleBase = RuleBaseFactory.newRuleBase();
> 		ruleBase.addPackage( pkg );
> 		return ruleBase;
> 	}
> 	
> 	public static void main(String[] args) throws Exception {
> 		new DroolsTest().run();
> 	}
> }
> HelloWorld.drl
> #list any import classes here.
> #declare any global variables here
> rule "Your First Rule"
> 	
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> rule "Your Second Rule"
> 	#include attributes such as "salience" here...
> 	when
> 		#conditions
> 	then 
> 		#actions
> 		
> end
> When I run this with release 4.0.1 I have to manually break the program to get it to stop.
> When I run with release 4.0.2 it reaches about 14000 iterations before crashing with an out of memory error.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 16:30:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 16:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-605) Dynamically adjust
 min_threads in thread pools
Message-ID: <14206383.1192653003274.JavaMail.jira@cloud.prod.atl2.jboss.com>

Dynamically adjust min_threads in thread pools
----------------------------------------------

                 Key: JGRP-605
                 URL: http://jira.jboss.com/jira/browse/JGRP-605
             Project: JGroups
          Issue Type: Feature Request
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.7


This should be a function of 
- number of nodes
- number of CPUs
, as described in JCIP

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 16:41:03 2007
From: jira-events at lists.jboss.org (Diego Belfer (JIRA))
Date: Wed, 17 Oct 2007 16:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4871) TransactionIsolation
 is not reset when Connection is returned to the pool
Message-ID: <33190829.1192653663634.JavaMail.jira@cloud.prod.atl2.jboss.com>

TransactionIsolation is not reset when Connection is returned to the pool
-------------------------------------------------------------------------

                 Key: JBAS-4871
                 URL: http://jira.jboss.com/jira/browse/JBAS-4871
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.0.5.GA
            Reporter: Diego Belfer


TransactionIsolation is not being reset when the JDBC connection is returned to the pool. Bug is indicated in the code. 
This was also reported in http://jira.jboss.com/jira/browse/JBAS-1123 and marked as closed but the bug is still there.

   public void cleanup() throws ResourceException
   {
      synchronized (handles)
      {
         for (Iterator i = handles.iterator(); i.hasNext(); )
         {
            WrappedConnection lc = (WrappedConnection)i.next();
            lc.setManagedConnection(null);
         }
         handles.clear();
      }
      //reset all the properties we know about to defaults.
      synchronized (stateLock)
      {
         jdbcAutoCommit = true;
         jdbcReadOnly = readOnly;
         if (jdbcTransactionIsolation != transactionIsolation)
         {
            try
            {
               con.setTransactionIsolation(jdbcTransactionIsolation); <-- BUG: It should be con.setTransactionIsolation(transactionIsolation);
               jdbcTransactionIsolation = transactionIsolation;
            }
            catch (SQLException e)
            {
               mcf.log.warn("Error resetting transaction isolation ", e);
            }
         }
      }
   }


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 16:52:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 16:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
Message-ID: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>

State transfer does not include optimistic node's DataVersion
-------------------------------------------------------------

                 Key: JBCACHE-1202
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani


Here's the object that's transferred; doesn't include the DataVersion

public class NodeData implements Externalizable
{
   private Fqn<?> fqn = null;
   private Map<?, ?> attrs = null;
}

A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 17:35:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 17 Oct 2007 17:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
Message-ID: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure Session Beans with Incomplete 2.1 View Fail Deployment
-------------------------------------------------------------

                 Key: EJBTHREE-1075
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 17:44:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 17 Oct 2007 17:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19933662.1192657443787.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Brian Stansberry updated JBCACHE-1201:
--------------------------------------

        Fix Version/s:     (was: 2.1.0.BETA1)
    Affects Version/s: 2.1.0.BETA1

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 17:57:03 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 17 Oct 2007 17:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-606) Use same properties
 for start_port/bind_port and end_port/port_range
Message-ID: <33207067.1192658223238.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use same properties for start_port/bind_port and end_port/port_range
--------------------------------------------------------------------

                 Key: JGRP-606
                 URL: http://jira.jboss.com/jira/browse/JGRP-606
             Project: JGroups
          Issue Type: Task
            Reporter: Bela Ban
         Assigned To: Bela Ban
            Priority: Minor
             Fix For: 2.7


In UDP, we use bind_port and port_range to define a range of valid ports.
In TCP, we use start_port and end_port

We should use
- bind_port (rather than start_port) to define the port to bind to
- end_port to define the range



-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 18:49:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Wed, 17 Oct 2007 18:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1758)
 PortletManagerBean$Comparator is not robust enough
Message-ID: <24053748.1192661343193.JavaMail.jira@cloud.prod.atl2.jboss.com>

PortletManagerBean$Comparator is not robust enough
--------------------------------------------------

                 Key: JBPORTAL-1758
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1758
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
    Affects Versions: 2.6.2 Final
            Reporter: Chris Laprun
         Assigned To: Chris Laprun
            Priority: Critical
             Fix For: 2.6.3 Final


In particular in a portlet doesn't have a display name then the comparator crashes.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 19:25:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Wed, 17 Oct 2007 19:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13974271.1192663503461.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383149 ] 
            
Ronald van Kuijk commented on JBPM-1071:
----------------------------------------

what exceptions were thrown? and what action was not performed? There has been lots of discussion on simultaneous access to node, actions and database. Can you please check  the JBPM-993 and JBPM-995 (and related) if that contains some more info?

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 20:08:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 20:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
Message-ID: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>

Problems uploading models etc. into the BRMS
--------------------------------------------

                 Key: JBRULES-1282
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.0.3, 4.1.0


There are 2 problems (this shows up mainly in WebKIT and safary browsers): 

1) the return content type for a successfull upload is text/plain when it should be test/html
2) if any form fields are not visible, they will not be submitted to the server. 


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 20:11:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 20:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3172314.1192666263518.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383152 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

Notify soa-p at redhat.com of change



> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 20:11:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 20:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25068376.1192666263671.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Michael Neale updated JBRULES-1282:
-----------------------------------

    Fix Version/s: 4.0.2_SOA_4.2-CP1
                   4.0.2_SOA.4.2-CP2

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:13:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 17 Oct 2007 21:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-822) Avoid deadlock when
 Connector
 shuts down while callback client invoker is in handleConnect()
Message-ID: <21914029.1192669983283.JavaMail.jira@cloud.prod.atl2.jboss.com>

Avoid deadlock when Connector shuts down while callback client invoker is in handleConnect()
--------------------------------------------------------------------------------------------

                 Key: JBREM-822
                 URL: http://jira.jboss.com/jira/browse/JBREM-822
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
             Fix For: 2.4.0.Beta1 (Pinto)


Clebert Suconic has experienced a deadlock while shutting down the Application Server.  

The thread dump shows that the AS has called Connector.stop(), which leads to a call to the synchronized method org.jboss.remoting.MicroRemoteClientInvoker.disconnect() on the callback org.jboss.remoting.transport.bisocket.BisocketClientInvoker.  However, all this happens at the same time that a callback handler is being installed, which leads to a call to the synchronized method MicroRemoteClientInvoker.connect() on *the same* callback BisocketClientInvoker.  The BisocketClientInvoker is in BisocketClientInvoker.handleConnect(), where it is waiting (with, in the case of JBossMessaging, a timeout of 0) to get a control socket.  As a result, MicroRemoteClientInvoker.disconnect() is blocked and cannot execute.

This situation needs careful study.  Do MicroRemoteClientInvoker.connect() and MicroRemoteClientInvoker.disconnect() need to be fully synchronized?



-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:15:03 2007
From: jira-events at lists.jboss.org (Jonathan Duty (JIRA))
Date: Wed, 17 Oct 2007 21:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24690310.1192670103331.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=comments#action_12383153 ] 
            
Jonathan Duty commented on EJBTHREE-1031:
-----------------------------------------

As a production user of both ejb3 and jboss 4.2.1 can someone explain this issue?  Should this bug mean that 4.2.1 shouldn't be used in production or we may create SLSB out of control???

Thanks,
~Jonathan


> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:15:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 17 Oct 2007 21:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-822) Avoid deadlock when
 Connector
 shuts down while callback client invoker is in handleConnect()
In-Reply-To: <21914029.1192669983283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13290170.1192670103486.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-822?page=all ]

Ron Sigal updated JBREM-822:
----------------------------

    Attachment: connect_disconnect_deadlock_thread_dump

Attached file with thread dump.

> Avoid deadlock when Connector shuts down while callback client invoker is in handleConnect()
> --------------------------------------------------------------------------------------------
>
>                 Key: JBREM-822
>                 URL: http://jira.jboss.com/jira/browse/JBREM-822
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: connect_disconnect_deadlock_thread_dump
>
>
> Clebert Suconic has experienced a deadlock while shutting down the Application Server.  
> The thread dump shows that the AS has called Connector.stop(), which leads to a call to the synchronized method org.jboss.remoting.MicroRemoteClientInvoker.disconnect() on the callback org.jboss.remoting.transport.bisocket.BisocketClientInvoker.  However, all this happens at the same time that a callback handler is being installed, which leads to a call to the synchronized method MicroRemoteClientInvoker.connect() on *the same* callback BisocketClientInvoker.  The BisocketClientInvoker is in BisocketClientInvoker.handleConnect(), where it is waiting (with, in the case of JBossMessaging, a timeout of 0) to get a control socket.  As a result, MicroRemoteClientInvoker.disconnect() is blocked and cannot execute.
> This situation needs careful study.  Do MicroRemoteClientInvoker.connect() and MicroRemoteClientInvoker.disconnect() need to be fully synchronized?

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 21:42:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 17 Oct 2007 21:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27682190.1192671723473.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=comments#action_12383156 ] 
            
William DeCoste commented on EJBTHREE-1031:
-------------------------------------------

Under some loads, SLSB instances are not always removed, so there is a potential memory leak in 4.2.1. 4.2.2 is coming out shortly and has this issue resolved.

> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 23:12:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 17 Oct 2007 23:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28690901.1192677123281.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383159 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

OMGWTFBBQ: there is also http://code.google.com/p/google-web-toolkit/issues/detail?id=1585

DAMN YOU! 3 bugs (one in my code, one safari quirk, and one on GWT) all conspire to make my week hell. I need a drink.

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 17 23:18:03 2007
From: jira-events at lists.jboss.org (Jonathan Duty (JIRA))
Date: Wed, 17 Oct 2007 23:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30669531.1192677483362.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=comments#action_12383160 ] 
            
Jonathan Duty commented on EJBTHREE-1031:
-----------------------------------------

Does this  typically with high or low loads?  We just want to know what to look for.

> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 00:19:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 18 Oct 2007 00:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22068422.1192681143234.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383161 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

http://www.webmasterworld.com/macintosh_webmaster/3300569.htm

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:21:14 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 02:21:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25268038.1192688474760.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383167 ] 
            
Jiri Pechanec commented on JBPM-1071:
-------------------------------------

Hi,
the exception throws is
org.jbpm.JbpmException: couldn't execute org.jbpm.command.SignalCommand at 715c2843
	at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73)
	at org.jpbm.exploratory.Signalist.run(Signalist.java:30)
Caused by: org.jbpm.JbpmException: couldn't signal token 'Token(/)' : node 'EndState(end-state1)' doesn't have a default transition
	at org.jbpm.graph.exe.Token.signal(Token.java:138)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157)
	at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$9af9b4e6.signal(<generated>)
	at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91)
	at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:71)
	... 1 more

Which means that other threads are isgnalling process when it is in the end state.
But this is not a problem I am trying to point out.
The problem is that the same node is executed 4 times from different threads and all changes made are successfully comitted.
IMHO the correct semantics is that only one thread executes each action (each node). The rest of threads will either throw something like concurrent access exception or will be used to signal in the next wait states.
According to content of the exception I can pretty accurately suppose that
4 threads executed Action 2, commited
3 threads executed transition to end state, probably committed
13 threads failed as there is no next transition
What I suppose is to have
1 thread executed Action 2, commited
3 thread executed Action 2, fail and rollback
1 thread executed transition to end state,  committed
2 threads executed transition to end state,  fail and rollback
13 threads failed as there is no next transition
or
1 thread executed Action 2, commited
1 thread executed transition to end state,  committed
18 threads failed as there is no next transition




> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:35:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 02:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4872) Invalid URI if the
 jboss.bind.address is IPv6
Message-ID: <37566.1192689303570.JavaMail.jira@cloud.prod.atl2.jboss.com>

Invalid URI if the jboss.bind.address is IPv6
---------------------------------------------

                 Key: JBAS-4872
                 URL: http://jira.jboss.com/jira/browse/JBAS-4872
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Remoting
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Takayoshi Kimura
         Assigned To: Ron Sigal


JBossRemoting uses jboss.bind.address in URI like the following:
socket://${jboss.bind.address}:4446/?datatype=invocation

However, if the jboss.bind.address is IPv6, it should be inside
of square brackets.

Invalid URI
socket://::1:4446/?datatype=invocation

Valid URI
socket://[::1]:4446/?datatype=invocation

To reproduce this issue:

Run JBoss instance by the following commend on IPv6 enabled system.
$ ./run.sh -c default -b ::1

Workaround:
Edit JBossRemoting URL not to use jboss.bind.address.

Note:
IPv6 address cannot be parsed with JBossRemoting 2.2.1.GA bundled in 4.2.1.GA. IPv6 parsing needs updated version of JBossRemoting.
http://jira.jboss.com/jira/browse/JBREM-645

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:45:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 02:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-823)
 ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value
 is IPv6
Message-ID: <9184117.1192689903468.JavaMail.jira@cloud.prod.atl2.jboss.com>

ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6
-----------------------------------------------------------------------------------

                 Key: JBREM-823
                 URL: http://jira.jboss.com/jira/browse/JBREM-823
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 3.0.0.Alpha1 (Otter)
            Reporter: Takayoshi Kimura
         Assigned To: Trustin Lee


IPv6 address contains ":" character, so it cannot be used in ObjectName.

2007-10-18 15:37:40,476 WARN  [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer.
javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
	at javax.management.ObjectName.construct(ObjectName.java:529)
	at javax.management.ObjectName.<init>(ObjectName.java:1304)
	at org.jboss.remoting.transport.Connector.init(Connector.java:402)
	at org.jboss.remoting.transport.Connector.create(Connector.java:760)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
	at $Proxy0.create(Unknown Source)
	at org.jboss.system.ServiceController.create(ServiceController.java:330)
	at org.jboss.system.ServiceController.create(ServiceController.java:273)
	at org.jboss.system.ServiceController.create(ServiceController.java:349)
	at org.jboss.system.ServiceController.create(ServiceController.java:273)
	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.create(Unknown Source)
	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy5.deploy(Unknown Source)
	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
	at org.jboss.Main.boot(Main.java:200)
	at org.jboss.Main$1.run(Main.java:508)
	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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:45:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 18 Oct 2007 02:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27825363.1192689903616.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=comments#action_12383168 ] 
            
Michael Neale commented on JBRULES-1282:
----------------------------------------

FOR THE SOA-P TEAM: OK, fix is in both trunk and 4.0.x.

The changes are from revision 15901 to 15906 on the 4.0.x branch. 

To get a cumulative patch (or svn merge):
svn diff -r 15901:15906 https://svn.labs.jboss.org/labs/jbossrules/branches/4.0.x/  > cumulative_patch.patch

etc.

-------
DETAILS OF FIX:
Was a problem effecting some browsers (notably webkit or khtml related ones) from 3 unrelated bugs all conspiring to make my life a living hell.
Meant it was not always possible to upload to the BRMS.
Now it should be fine on all (known) browsers.

This fix is not critical, without it, it will still work with Firefox (version 2) at least, and IE. 

-------

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 02:47:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 18 Oct 2007 02:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31663275.1192690023511.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Michael Neale updated JBRULES-1282:
-----------------------------------

    Attachment: cumulative_patch.patch

Here is a cumulative patch (its a bit big as the UI was changed).

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1, 4.0.2_SOA.4.2-CP2
>
>         Attachments: cumulative_patch.patch
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 03:01:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 03:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4872) Invalid URI if the
 jboss.bind.address is IPv6
In-Reply-To: <37566.1192689303570.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6508105.1192690863316.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4872?page=comments#action_12383170 ] 
            
Takayoshi Kimura commented on JBAS-4872:
----------------------------------------

Another workaround:

Use-b [::1] instead of -b ::1. Somehow it works.

$ ./run.sh -b \[::1\]

> Invalid URI if the jboss.bind.address is IPv6
> ---------------------------------------------
>
>                 Key: JBAS-4872
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4872
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Takayoshi Kimura
>         Assigned To: Ron Sigal
>
> JBossRemoting uses jboss.bind.address in URI like the following:
> socket://${jboss.bind.address}:4446/?datatype=invocation
> However, if the jboss.bind.address is IPv6, it should be inside
> of square brackets.
> Invalid URI
> socket://::1:4446/?datatype=invocation
> Valid URI
> socket://[::1]:4446/?datatype=invocation
> To reproduce this issue:
> Run JBoss instance by the following commend on IPv6 enabled system.
> $ ./run.sh -c default -b ::1
> Workaround:
> Edit JBossRemoting URL not to use jboss.bind.address.
> Note:
> IPv6 address cannot be parsed with JBossRemoting 2.2.1.GA bundled in 4.2.1.GA. IPv6 parsing needs updated version of JBossRemoting.
> http://jira.jboss.com/jira/browse/JBREM-645

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 03:06:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Thu, 18 Oct 2007 03:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-823)
 ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value
 is IPv6
In-Reply-To: <9184117.1192689903468.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17523669.1192691163409.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-823?page=all ]

Takayoshi Kimura updated JBREM-823:
-----------------------------------

    Attachment: JBREM-823.patch

Patch attached: Encode address during construct ObjectName.

> ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6
> -----------------------------------------------------------------------------------
>
>                 Key: JBREM-823
>                 URL: http://jira.jboss.com/jira/browse/JBREM-823
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.Alpha1 (Otter)
>            Reporter: Takayoshi Kimura
>         Assigned To: Trustin Lee
>         Attachments: JBREM-823.patch
>
>
> IPv6 address contains ":" character, so it cannot be used in ObjectName.
> 2007-10-18 15:37:40,476 WARN  [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer.
> javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
> 	at javax.management.ObjectName.construct(ObjectName.java:529)
> 	at javax.management.ObjectName.<init>(ObjectName.java:1304)
> 	at org.jboss.remoting.transport.Connector.init(Connector.java:402)
> 	at org.jboss.remoting.transport.Connector.create(Connector.java:760)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:349)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy4.create(Unknown Source)
> 	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy5.deploy(Unknown Source)
> 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
> 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
> 	at org.jboss.Main.boot(Main.java:200)
> 	at org.jboss.Main$1.run(Main.java:508)
> 	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

        


From jira-events at lists.jboss.org  Thu Oct 18 03:52:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 18 Oct 2007 03:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20994848.1192693923475.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383177 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

Well, we should see a successful testrun before we can release.
If you don't want to deploy the juddi-service.sar to default, you can also run the tests against all.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 04:53:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 18 Oct 2007 04:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1114) JBoss
 Remoting fails under load
In-Reply-To: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27627477.1192697583331.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=comments#action_12383187 ] 
            
Tim Fox commented on JBMESSAGING-1114:
--------------------------------------

I found out why this is happening (why the callback handler can't be found).   :

1. An invocation fails because remoting timed out waiting for a TCP connection to be returned to the pool. (Pool size to small).
2. In this case remoting throws a java.net.SocketException:

throw new SocketException("Can not obtain client socket connection from pool. " +
           "Have waited " + (System.currentTimeMillis() - start) +
           " milliseconds for available connection (" + usedPooled + "in use)");

3. JBM catches the exception and since it is a java.net.SocketException, assumes some fatal problem has happened with the connection, and falsely initiates failover to another node.

4. Before failing over JBM closes the failed connection.

5. This results in the JBR Callback Connector getting closed.

6. All this while callbacks are still arriving from the server, since that connection is actually still fine.

7. The connector closing process removes the callbackhandler from the callback ServerInvoker so any more callbacks arrive barf with not being able to find the handler.

So:

After increasing the client pool size I'm not getting these exceptions any more, but imho there are two issues here:

1) Why does remoting throw SocketException? - I would say this is inappropriate since the socket is fine - I would suggest some kind of org.jboss.remoting.RemotingException should be thrown?
This would allow JBM to catch it and not initiate failover in this case.
In the mean-time I will have to do some kind of text comparison:

if (exception.getMessage().startsWith("Can not obtain client....))
{
//don't do failover
}
else
{
//do failover
}
This will work for now but is ugly and brittle.

2) The connector close process is not clean. I would suggest the code should be changed so the server threads are shut down at the beginning of the connector close process.
I.e.
a) Wait for current invocations on that server invoker to complete - and don't allow any more.
b) Once all are complete shut it down.
(I believe we also have a deadlock on JBoss AS that Clebert discovered that was something due to connectors closing. I don't know if this is related?) 

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBMESSAGING-1114
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000 
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:06:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Thu, 18 Oct 2007 06:06:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17446147.1192701963467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani updated JBCACHE-1202:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA
       Complexity: High

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.3.0.GA, 1.4.0.GA, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3, 1.4.0.SP1, 1.4.1.GA, 1.3.0.SP4, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:08:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Thu, 18 Oct 2007 06:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22323022.1192702083562.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Manik Surtani updated JBCACHE-1201:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:10:03 2007
From: jira-events at lists.jboss.org (Tom Baeyens (JIRA))
Date: Thu, 18 Oct 2007 06:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1071) Possible problem in
 concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20471683.1192702203444.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]

Tom Baeyens updated JBPM-1071:
------------------------------

    Attachment: LockingTest.java

I attached a test LockingTest.  This test does basically the same as your test, but it fits in our overall test suite.

This test runs fine.  So I can't reproduce the problem.

The way that I check the optimistic locking is a bit different.  First, I spawn of x number of competing threads/transactions.  In each transaction, a comment is added that includes the name of the thread.

Later on, we check if exactly 1 thread managed to commit, while the other were rolled back.

What I think that you do different is that you don't use transactional resource to measure which transactions committed and which transactions rolled back.  A limitation of the current implementation is that you can't see if an optimistic failure rollback occured or not.

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz, LockingTest.java
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:16:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Thu, 18 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31612804.1192702563316.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani updated JBCACHE-1202:
-----------------------------------

    Priority: Critical  (was: Major)

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.3.0.GA, 1.4.0.GA, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3, 1.4.0.SP1, 1.4.1.GA, 1.3.0.SP4, 1.4.1.SP1, 1.4.1.SP2, 1.4.1.SP3, 1.4.1.SP4, 1.4.1.SP5, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:21:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 18 Oct 2007 06:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19041360.1192702863283.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12383202 ] 
            
Thomas Diesler commented on JBAS-4864:
--------------------------------------

Alex, this cant be true. 

I verified this the startup problem after a clean build on two different boxes. 
Heiko is seeing this as well.

Did you do: rm -rf thirdparty/*


[tdiesler at jbws trunk]$ svn info
Path: .
URL: https://svn.jboss.org/repos/jbossas/trunk
Repository Root: https://svn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 66231
Node Kind: directory
Schedule: normal
Last Changed Author: scott.stark at jboss.org
Last Changed Rev: 66229
Last Changed Date: 2007-10-18 07:51:39 +0200 (Thu, 18 Oct 2007)


> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:31:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1283) Unable to
	serialize rule base
Message-ID: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>

Unable to serialize rule base
-----------------------------

                 Key: JBRULES-1283
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Jiri Pechanec
         Assigned To: Mark Proctor
            Priority: Minor


When I am trying to serialize rulebase, I am getting the exception
Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at java.util.ArrayList.writeObject(ArrayList.java:569)
        at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
        at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
        at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
        at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
        at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
        at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:31:04 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:31:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1283) Unable to
	serialize rule base
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23534102.1192703464157.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=all ]

Jiri Pechanec updated JBRULES-1283:
-----------------------------------

    Component/s: Reteoo

> Unable to serialize rule base
> -----------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:31:04 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Thu, 18 Oct 2007 06:31:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11145231.1192703464437.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4864?page=comments#action_12383204 ] 
            
Alexey Loubyansky commented on JBAS-4864:
-----------------------------------------

After svn update I see it.

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:37:03 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3406905.1192703823280.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383206 ] 
            
Jiri Pechanec commented on JBPM-1071:
-------------------------------------

I will look at the code. But what pleas pay attantion to the fact that in my test I am also accessing to the database and all changes done in successful threads are committed.

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz, LockingTest.java
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:46:20 2007
From: jira-events at lists.jboss.org (Jiri Pechanec (JIRA))
Date: Thu, 18 Oct 2007 06:46:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1071) Possible problem
 in concurrent signalling from multiple threads
In-Reply-To: <16765129.1192604823496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15883845.1192704380200.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1071?page=comments#action_12383207 ] 
            
Jiri Pechanec commented on JBPM-1071:
-------------------------------------

I have run your test in my environment and this is the result (I have run it not as junit test but as a standalone application)
More updates [org.jbpm.graph.exe.Comment at 3be0e954, org.jbpm.graph.exe.Comment at 2af6a882]
So in that assertEquals there are two results, not just one.
Sometimes there is only one, sometimes there are three

> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
>                 Key: JBPM-1071
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1071
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Linux  2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
>            Reporter: Jiri Pechanec
>         Assigned To: Tom Baeyens
>            Priority: Critical
>         Attachments: expl.tar.gz, LockingTest.java
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an exception

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 06:59:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1300) Default a
 portlet window to maximized.
In-Reply-To: <24092633.1173097870945.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32799694.1192705143429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1300?page=all ]

Thomas Heute updated JBPORTAL-1300:
-----------------------------------

      Component/s: Portal Core
    Fix Version/s: 2.6.3 Final

> Default a portlet window to maximized.
> --------------------------------------
>
>                 Key: JBPORTAL-1300
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: David Roberts
>            Priority: Optional
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 07:01:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1619) Multiple
	maximized windows
In-Reply-To: <8587201.1185976549535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15562040.1192705263305.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1619?page=all ]

Thomas Heute updated JBPORTAL-1619:
-----------------------------------

    Fix Version/s: 2.6.3 Final
         Assignee: Thomas Heute  (was: Julien Viet)

> Multiple maximized windows
> --------------------------
>
>                 Key: JBPORTAL-1619
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature.
> If you follow the next steps:
> 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized
> 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window.
> you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window.
> If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it).
> Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 07:03:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 07:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1300) Default a
 portlet window to maximized.
In-Reply-To: <24092633.1173097870945.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3550156.1192705383362.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1300?page=all ]

Thomas Heute reassigned JBPORTAL-1300:
--------------------------------------

    Assignee: Thomas Heute

> Default a portlet window to maximized.
> --------------------------------------
>
>                 Key: JBPORTAL-1300
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: David Roberts
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:02:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:02:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4567) Install
	jbossws-2.0.1.SP1
In-Reply-To: <13626450.1184838707453.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25807349.1192712523370.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4567?page=all ]

Dimitris Andreadis reopened JBAS-4567:
--------------------------------------

             
Re-opening the task, as we are back to a snapshot version.

> Install jbossws-2.0.1.SP1
> -------------------------
>
>                 Key: JBAS-4567
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4567
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:04:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4689) Upgrade JBoss
 messaging to 1.4.0.GA
In-Reply-To: <16306175.1189160291086.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25713946.1192712643491.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4689?page=all ]

Dimitris Andreadis reopened JBAS-4689:
--------------------------------------

             
re-open, we are back to a snapshot version.

> Upgrade JBoss messaging to 1.4.0.GA
> -----------------------------------
>
>                 Key: JBAS-4689
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4689
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Messaging
>            Reporter: Dimitris Andreadis
>         Assigned To: Clebert Suconic
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> We are currently at 1.4.0.CR2

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:04:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 18 Oct 2007 09:04:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1283) Unable to
 serialize rule base ( NotSerializableException:
 org.drools.base.FireAllRulesRuleBaseUpdateListener)
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3516149.1192712644456.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=all ]

Mark Proctor updated JBRULES-1283:
----------------------------------

          Summary: Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)  (was: Unable to serialize rule base)
    Fix Version/s: 4.0.2_SOA_4.2-CP1
                   4.0.3
                   4.1.0

> Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:08:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 18 Oct 2007 09:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4567) Install jbossws-2.0.x
In-Reply-To: <13626450.1184838707453.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12980656.1192712883502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4567?page=all ]

Thomas Diesler updated JBAS-4567:
---------------------------------

    Summary: Install jbossws-2.0.x  (was: Install jbossws-2.0.1.SP1)

> Install jbossws-2.0.x
> ---------------------
>
>                 Key: JBAS-4567
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4567
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:12:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4714) Upgrade JBossRemoting
 to 2.2.2.SP2 (from 2.2.0.GA)
In-Reply-To: <17799303.1189663991032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14406232.1192713123347.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4714?page=all ]

Dimitris Andreadis closed JBAS-4714.
------------------------------------

    Resolution: Done

Closing it. We are running on remoting 2.2.2.SP2 since Oct/10th.

(Ron, unfortunately the SP2 release wasn't used for AS 4.2.2.GA)

> Upgrade JBossRemoting to 2.2.2.SP2 (from 2.2.0.GA)
> --------------------------------------------------
>
>                 Key: JBAS-4714
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4714
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> The upgrade from Remoting 2.2.0.GA to 2.2.2.GA is occasioned largely by a set of features and fixes for JBossMessaging 1.4. 
> The further upgrade to 2.2.2.SP1 consists of fixes for JBREM-653 and JBREM-750.  The fix for JBREM-750 was supposed to go into 2.2.2.GA but was overlooked.  The fix for JBREM-653 is needed for ESB 4.2.1.
> These fixes have been applied to the remoting_2_2_0_GA branch from which 2.2.2.GA was released.  As soon as the related unit tests pass on cruisecontrol, the branch will be tagged remoting_2_2_2_SP1.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:14:04 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 18 Oct 2007 09:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1283) Unable to
 serialize rule base ( NotSerializableException:
 org.drools.base.FireAllRulesRuleBaseUpdateListener)
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16683222.1192713244587.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=comments#action_12383238 ] 
            
Mark Proctor commented on JBRULES-1283:
---------------------------------------

I've fixed for trunk and 4.0.x. raise the jira in the SOAP mailing list.

> Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2_SOA_4.2-CP1, 4.0.3, 4.1.0
>
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:16:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Thu, 18 Oct 2007 09:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1282) Problems
 uploading models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9997667.1192713363818.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Mark Proctor updated JBRULES-1282:
----------------------------------

    Fix Version/s:     (was: 4.0.2_SOA.4.2-CP2)

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.3, 4.1.0, 4.0.2_SOA_4.2-CP1
>
>         Attachments: cumulative_patch.patch
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:16:04 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Thu, 18 Oct 2007 09:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4864) jboss-web with 4.0
 dtd does not deploy
In-Reply-To: <7580359.1192524063577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12797008.1192713364389.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4864?page=all ]

Alexey Loubyansky closed JBAS-4864.
-----------------------------------

    Resolution: Done

Fixed.

> jboss-web with 4.0 dtd does not deploy
> --------------------------------------
>
>                 Key: JBAS-4864
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4864
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:34:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 09:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30994347.1192714443317.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12383246 ] 
            
Dimitris Andreadis commented on JBAS-4688:
------------------------------------------

Pointing trunk to Beta2. I see the integration project currently at 5.0.0.Beta3.

Is an update to that necessary, as well?

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 09:40:11 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Thu, 18 Oct 2007 09:40:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17012592.1192714812233.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4688?page=comments#action_12383247 ] 
            
Jonathan Halliday commented on JBAS-4688:
-----------------------------------------

Yes. The change is in, it just needs releasing. My understanding from http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120481 was that Paul would handle the tagging for the release, but I may have misunderstood. 

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:05:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Thu, 18 Oct 2007 11:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-423) Fix microcontainer
 poms and metatdata in maven repository
Message-ID: <15025489.1192719903676.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix microcontainer poms and metatdata in maven repository
---------------------------------------------------------

                 Key: JBBUILD-423
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-423
             Project: JBoss Build System
          Issue Type: Task
          Components: Maven
            Reporter: Paul Gier
             Fix For: Maven Build - Maint 2007


The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:05:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Thu, 18 Oct 2007 11:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBBUILD-423) Fix
 microcontainer poms and metatdata in maven repository
In-Reply-To: <15025489.1192719903676.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26146717.1192719903834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-423?page=all ]

Paul Gier reassigned JBBUILD-423:
---------------------------------

    Assignee: Paul Gier

> Fix microcontainer poms and metatdata in maven repository
> ---------------------------------------------------------
>
>                 Key: JBBUILD-423
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-423
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 11:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4874) Track JBoss and
 thirdparty dependencies for JBossAS 4.2.3
Message-ID: <29949338.1192721463216.JavaMail.jira@cloud.prod.atl2.jboss.com>

Track JBoss and thirdparty dependencies for JBossAS 4.2.3
---------------------------------------------------------

                 Key: JBAS-4874
                 URL: http://jira.jboss.com/jira/browse/JBAS-4874
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Other
            Reporter: Dimitris Andreadis
             Fix For: JBossAS-4.2.3.GA


Use subtasks to track component updates in AS 4.2.3.GA

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 11:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4875) Upgrade jboss
 transactions to 4.2.3.SP7 (from 4.2.3.SP6)
Message-ID: <27966578.1192721823361.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6)
--------------------------------------------------------

                 Key: JBAS-4875
                 URL: http://jira.jboss.com/jira/browse/JBAS-4875
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: JB5-Transaction Manager
            Reporter: Dimitris Andreadis
         Assigned To: Mark Little
             Fix For: JBossAS-4.2.3.GA




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 11:37:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 18 Oct 2007 11:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4875) Upgrade jboss
 transactions to 4.2.3.SP7 (from 4.2.3.SP6)
In-Reply-To: <27966578.1192721823361.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24614390.1192721823524.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4875?page=all ]

Dimitris Andreadis reassigned JBAS-4875:
----------------------------------------

    Assignee: Dimitris Andreadis  (was: Mark Little)

> Upgrade jboss transactions to 4.2.3.SP7 (from 4.2.3.SP6)
> --------------------------------------------------------
>
>                 Key: JBAS-4875
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4875
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.3.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:13:04 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 18 Oct 2007 12:13:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4863) NPE in
 ContainerConfigurationMetaDataWrapper
In-Reply-To: <22857669.1192523828772.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17898972.1192723984747.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4863?page=all ]

Scott M Stark resolved JBAS-4863.
---------------------------------

    Resolution: Done

The ContainerConfigurationMetaDataWrapper has been resolved

> NPE in ContainerConfigurationMetaDataWrapper
> --------------------------------------------
>
>                 Key: JBAS-4863
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4863
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell trunk]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> getContainerConfigurations returns null
>       configurationsWrapper = new ContainerConfigurationsMetaDataWrapper(primary.getContainerConfigurations(),
>             defaults.getContainerConfigurations());
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.ejb.jboss.ContainerConfigurationsMetaDataWrapper.<init>(ContainerConfigurationsMetaDataWrapper.java:60)
>         at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:57)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)
>         at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:44)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:17:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 18 Oct 2007 12:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28525134.1192724223669.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4180?page=comments#action_12383290 ] 
            
Galder Zamarreno commented on JBAS-4180:
----------------------------------------

I have committed a simple UT for an HA Singleton with a Pojo bean injected 
without a JMX annotation that passes.

Still TODO: remove @JMX from HA singleton election policy tests and 
investigate why tests are failing.

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:23:03 2007
From: jira-events at lists.jboss.org (Jonathan Halliday (JIRA))
Date: Thu, 18 Oct 2007 12:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4759) Upgrade jboss
 transactions to 4.2.3.SP6 (from 4.2.3.SP5)
In-Reply-To: <1093019.1190995301217.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19406993.1192724583682.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4759?page=comments#action_12383291 ] 
            
Jonathan Halliday commented on JBAS-4759:
-----------------------------------------

Unfortunately the JBOSSTS_4_2_3_SP6 tag in JBossTS project svn does not correctly reflect the content of the JBossTS 4.2.3.SP6 binaries on repository.jboss.com and in JBossAS 4.2.2.GA.

The tag was incorrectly created from the wrong branch, whilst the binaries were built from the correct one.

The good news is that the AS 4.2.2.GA therefore has the necessary transactions bug fixes.

The bad news is that recreating the source requires using the JBOSSTS_4_2_3_SP6_FOR_AS tag of the JBossTS svn, not the JBOSSTS_4_2_3_SP6  tag.

The binaries of SP6 on repository.jboss.com are now accompanied by a warning to this effect.

> Upgrade jboss transactions to 4.2.3.SP6 (from 4.2.3.SP5)
> --------------------------------------------------------
>
>                 Key: JBAS-4759
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4759
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 12:46:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 18 Oct 2007 12:46:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1107) Less noisy
 client-side failover
In-Reply-To: <13404207.1192220103325.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3105332.1192725964801.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1107?page=comments#action_12383301 ] 
            
Tim Fox commented on JBMESSAGING-1107:
--------------------------------------

I agree.

Although AFAICT the only thing that logs at ERROR during failover is JBoss Remoting code.

We would need JBR to changes this and bring out a new release.

> Less noisy client-side failover
> -------------------------------
>
>                 Key: JBMESSAGING-1107
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1107
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> When a cluster node failure occurs, the client side reports a significant amount of ERROR logging. This is technically correct, those errors are actually occurring, but a clustered connection factory has in-place a fail-over mechanism whose job is to cope with those errors and hopefully make them disappear.
> If the fail-over succeeds, the user should not see any ERROR-level logging. At most, there should be a WARN along the lines of "node failure detected, the fail-over mechanism is dealing with it". The user should see ERRORs only if the fail-over itself fails.
> Tons of stack traces produce a significant level of discomfort even if the fail-over succeeds, leaving the user in doubt whether actually the process worked. 
> The logging information should be naturally still available, but at DEBUG level.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:19:21 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:19:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-821) JBoss Remoting fails
	under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21278235.1192731561260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-821?page=all ]

Ron Sigal updated JBREM-821:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:21:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8806969.1192731663308.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383307 ] 
            
Ron Sigal commented on JBREM-821:
---------------------------------

Copying Tim Fox's comment from JBMESSAGING-1114:

I found out why this is happening (why the callback handler can't be found). :

1. An invocation fails because remoting timed out waiting for a TCP connection to be returned to the pool. (Pool size to small).
2. In this case remoting throws a java.net.SocketException:

throw new SocketException("Can not obtain client socket connection from pool. " +
           "Have waited " + (System.currentTimeMillis() - start) +
           " milliseconds for available connection (" + usedPooled + "in use)");

3. JBM catches the exception and since it is a java.net.SocketException, assumes some fatal problem has happened with the connection, and falsely initiates failover to another node.

4. Before failing over JBM closes the failed connection.

5. This results in the JBR Callback Connector getting closed.

6. All this while callbacks are still arriving from the server, since that connection is actually still fine.

7. The connector closing process removes the callbackhandler from the callback ServerInvoker so any more callbacks arrive barf with not being able to find the handler.

So:

After increasing the client pool size I'm not getting these exceptions any more, but imho there are two issues here:

1) Why does remoting throw SocketException? - I would say this is inappropriate since the socket is fine - I would suggest some kind of org.jboss.remoting.RemotingException should be thrown?
This would allow JBM to catch it and not initiate failover in this case.
In the mean-time I will have to do some kind of text comparison:

if (exception.getMessage().startsWith("Can not obtain client....))
{
//don't do failover
}
else
{
//do failover
}
This will work for now but is ugly and brittle.

2) The connector close process is not clean. I would suggest the code should be changed so the server threads are shut down at the beginning of the connector close process.
I.e.
a) Wait for current invocations on that server invoker to complete - and don't allow any more.
b) Once all are complete shut it down.
(I believe we also have a deadlock on JBoss AS that Clebert discovered that was something due to connectors closing. I don't know if this is related?)

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:25:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16548689.1192731903304.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383309 ] 
            
Ron Sigal commented on JBREM-821:
---------------------------------

Regarding issue 2) from Tim's note:  org.jboss.remoting.transport.socket.SocketServerInvoker.cleanup() should wait for all worker threads to finish processing before returning to SocketServerInvoker.stop(), which then calls ServerInvoker.stop().  The problem is that ServerInvoker.stop() removes all callback handlers, which could happen while a worker thread is still processing.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:29:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:29:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20316417.1192732143758.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383311 ] 
            
Ron Sigal commented on JBREM-821:
---------------------------------

Regarding the deadlock that Clebert discovered (JBREM-822):  I don't think it's related.  The deadlock occurs on the server side while JBossAS is shutting down.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:35:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-821) JBoss Remoting fails
	under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4664955.1192732503499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-821?page=all ]

Ron Sigal updated JBREM-821:
----------------------------

    Priority: Major  (was: Blocker)

Given that there is a workaround for the issues Tim has discovered, I've reduced the priority from Blocker to Major.  

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:37:05 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Thu, 18 Oct 2007 14:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1114) JBoss
 Remoting fails under load
In-Reply-To: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5152785.1192732625206.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=comments#action_12383317 ] 
            
Ron Sigal commented on JBMESSAGING-1114:
----------------------------------------

I've added Tim's comments to JBREM-821 "JBoss Remoting fails under load".   I agree that issues 1) and 2) should be fixed.

Since there seems to be a workaround, I've scheduled JBREM-821 for Remoting release 2.4.0.Beta1 and reduced the priority to Major.  If any further related issues arise, of course, that can be readjusted.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBMESSAGING-1114
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000 
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Thu Oct 18 14:45:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Thu, 18 Oct 2007 14:45:03 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Created=3A_=28JBPORTAL-1?=
 =?utf-8?q?759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
Message-ID: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>

Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
-----------------------------------------------------------------------------------------------------------------

                 Key: JBPORTAL-1759
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Server
    Affects Versions: 2.6.2 Final
         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
            Reporter: Johannes Fiala
         Assigned To: Julien Viet


Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.

E.g. Entering "http://localhost:8080/portal/?test=%FC"
throws the following exception:

HTTP Status 500 -
type Exception report
message description The server encountered an internal error () that prevented it from fulfilling this request.
exception java.lang.ArrayIndexOutOfBoundsException: 4
	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.


-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 15:04:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Thu, 18 Oct 2007 15:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5257557.1192734243464.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12383320 ] 
            
Koen Aers commented on GPD-169:
-------------------------------

Can someone please attach the processdefinition.xml and the gpd.xml file for a process that produces this behaviour.

Regards,
Koen

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 15:12:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 18 Oct 2007 15:12:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
Message-ID: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>

putForExternalRead replicates when INVALIDATION used
----------------------------------------------------

                 Key: JBCACHE-1203
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
             Fix For: 2.1.0.BETA1


If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.

The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 15:14:16 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 18 Oct 2007 15:14:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
In-Reply-To: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13750399.1192734856470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1203?page=all ]

Brian Stansberry updated JBCACHE-1203:
--------------------------------------

        Fix Version/s:     (was: 2.1.0.BETA1)
    Affects Version/s: 2.1.0.BETA1

> putForExternalRead replicates when INVALIDATION used
> ----------------------------------------------------
>
>                 Key: JBCACHE-1203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>
> If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.
> The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:26:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 16:26:03 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Commented=3A_=28JBPORTAL?=
 =?utf-8?q?-1759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15038924.1192739163437.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383337 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

Thanks for reporting this.

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 16:26:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 16:26:03 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Updated=3A_=28JBPORTAL-1?=
 =?utf-8?q?759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24291366.1192739163675.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=all ]

Julien Viet updated JBPORTAL-1759:
----------------------------------

    Fix Version/s: 2.6.3 Final

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 16:36:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 18 Oct 2007 16:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4876) Re-enable JGroups
 message bundling
Message-ID: <12319302.1192739763279.JavaMail.jira@cloud.prod.atl2.jboss.com>

Re-enable JGroups message bundling
----------------------------------

                 Key: JBAS-4876
                 URL: http://jira.jboss.com/jira/browse/JBAS-4876
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


 For 4.2.0 JGroups message bundling was disabled pending investigation of JGRP-497. That is fixed in JGroups 2.4.1.SP4. Message bundling improves performance, so we should re-enable it.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:54:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1760) JSR-301 JSF
 Portlet Bridge Integration
Message-ID: <18140018.1192740843453.JavaMail.jira@cloud.prod.atl2.jboss.com>

JSR-301 JSF Portlet Bridge Integration
--------------------------------------

                 Key: JBPORTAL-1760
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1760
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales


Integrate Implementation of 301 spec into JBP.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:59:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1761) Sun RI Example
Message-ID: <14752350.1192741143929.JavaMail.jira@cloud.prod.atl2.jboss.com>

Sun RI Example
--------------

                 Key: JBPORTAL-1761
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1761
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales


Create example app using maven and the Sun 1.2+ Reference Implementation

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:59:04 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1762) Myfaces Example
Message-ID: <30135268.1192741144057.JavaMail.jira@cloud.prod.atl2.jboss.com>

Myfaces Example
---------------

                 Key: JBPORTAL-1762
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1762
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 16:59:04 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 16:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1761) Sun RI Example
In-Reply-To: <14752350.1192741143929.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11535754.1192741144209.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1761?page=all ]

Wesley Hales reassigned JBPORTAL-1761:
--------------------------------------

    Assignee: Wesley Hales

> Sun RI Example
> --------------
>
>                 Key: JBPORTAL-1761
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1761
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>
> Create example app using maven and the Sun 1.2+ Reference Implementation

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:01:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1763) RichFaces Example
Message-ID: <18141880.1192741263399.JavaMail.jira@cloud.prod.atl2.jboss.com>

RichFaces Example
-----------------

                 Key: JBPORTAL-1763
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1763
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:01:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1764) Seam 2.x Example
Message-ID: <14612276.1192741263558.JavaMail.jira@cloud.prod.atl2.jboss.com>

Seam 2.x Example
----------------

                 Key: JBPORTAL-1764
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1764
             Project: JBoss Portal
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales
         Assigned To: Wesley Hales




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:03:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1686) Maven migration
	plan
In-Reply-To: <18408104.1189534271230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8269787.1192741383353.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1686?page=all ]

Wesley Hales resolved JBPORTAL-1686.
------------------------------------

    Resolution: Done

Created initial maven structure for common module to be referenced for future conversions.

> Maven migration plan
> --------------------
>
>                 Key: JBPORTAL-1686
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1686
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:05:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1689) Maven
	documentation
In-Reply-To: <31089433.1189534391507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2038625.1192741503435.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1689?page=all ]

Wesley Hales resolved JBPORTAL-1689.
------------------------------------

    Resolution: Done

Use common module for example and also reference blog http://jbossportal.blogspot.com/2007/10/migrating-to-maven-from-ant-part-1.html

> Maven documentation
> -------------------
>
>                 Key: JBPORTAL-1689
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1689
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>         Attachments: modules-common-structure.Jpg
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:07:03 2007
From: jira-events at lists.jboss.org (Frank Langelage (JIRA))
Date: Thu, 18 Oct 2007 17:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4877) Upgrade JSF to 1.2_05
Message-ID: <1154812.1192741623777.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade JSF to 1.2_05
---------------------

                 Key: JBAS-4877
                 URL: http://jira.jboss.com/jira/browse/JBAS-4877
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Frank Langelage


JSF 1.2_05 is out for a few days. Upgrade to this from 1.2_04_P02.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:15:34 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 18 Oct 2007 17:15:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1765) Adapt the admin
 portlet to let the user set a default window state
Message-ID: <32743739.1192742134373.JavaMail.jira@cloud.prod.atl2.jboss.com>

Adapt the admin portlet to let the user set a default window state
------------------------------------------------------------------

                 Key: JBPORTAL-1765
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1765
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
            Reporter: Thomas Heute
         Assigned To: Wesley Hales
             Fix For: 2.6.3 Final


We'll need to be able to define which window (if any) of a page should be maximized when a window opens, we'll also need to define if a window must first be displayed as minimized.
The back end is not done 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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:27:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBPORTAL-1689) Maven
	documentation
In-Reply-To: <31089433.1189534391507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4789562.1192742823490.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1689?page=all ]

Wesley Hales reopened JBPORTAL-1689:
------------------------------------

             

> Maven documentation
> -------------------
>
>                 Key: JBPORTAL-1689
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1689
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>         Attachments: modules-common-structure.Jpg
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:27:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1689) Maven
	documentation
In-Reply-To: <31089433.1189534391507.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20810119.1192742823718.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1689?page=comments#action_12383341 ] 
            
Wesley Hales commented on JBPORTAL-1689:
----------------------------------------

http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide

> Maven documentation
> -------------------
>
>                 Key: JBPORTAL-1689
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1689
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Julien Viet
>         Assigned To: Wesley Hales
>             Fix For: 2.8 Final
>
>         Attachments: modules-common-structure.Jpg
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:31:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1766) Portal
	Administration Icons
Message-ID: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>

Portal Administration Icons
---------------------------

                 Key: JBPORTAL-1766
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Wesley Hales


Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:31:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Thu, 18 Oct 2007 17:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1766) Portal
	Administration Icons
In-Reply-To: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33374027.1192743063374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1766?page=all ]

Wesley Hales reassigned JBPORTAL-1766:
--------------------------------------

    Assignee: Wesley Hales

> Portal Administration Icons
> ---------------------------
>
>                 Key: JBPORTAL-1766
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>
> Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 17:53:04 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 17:53:04 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Commented=3A_=28JBPORTAL?=
 =?utf-8?q?-1759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22146406.1192744384163.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383344 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

I would like to know how this URL is generated. Has it been generated  by a PortletURL or did you manufacture it by hand ?
The correct litteral value for the umlaut char encoded for the web should be "%C3%BC" not "%FC" (x-www-formurlencoded with UTF-8). So your URL should be "http://localhost:8080/portal/?test=%C3%BC" 

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 17:55:07 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 17:55:07 -0400 (EDT)
Subject: [jboss-jira] =?utf-8?q?=5BJBoss_JIRA=5D_Commented=3A_=28JBPORTAL?=
 =?utf-8?q?-1759=29_Entering_urls_containing_German_Umlaute_=28e=2Eg=2E_?=
 =?utf-8?q?=C3=BC_=3D_=25FC=29_throws_an_ArrayIndexOutOfBoundsException_in?=
 =?utf-8?q?_FastURLDecoder?=
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22746590.1192744507950.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383345 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

However the bug should be resolved to detect that the input is wrong and it should be handled differently than a ArrayIndexOutOfBoundsException. I will consider this report as a bug in the detection of malformed input and correct it. If the URL you are giving me is manufactured by the portal, tell us how it was done with a new JIRA issue for it.

> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 18:08:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 18:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1759) FastURLDecoder
 with malformed
 input %FC throws an ArrayIndexOutOfBoundsException instead of throwing
 MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9629210.1192745283393.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=all ]

Julien Viet updated JBPORTAL-1759:
----------------------------------

    Summary: FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException  (was: Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder)

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 18:10:03 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Thu, 18 Oct 2007 18:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2951370.1192745403513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=all ]

Julien Viet resolved JBPORTAL-1759.
-----------------------------------

    Resolution: Done

fix in trunk of common module.

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 18 19:52:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 18 Oct 2007 19:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1059) Return a
 business interface from a home create method must not be allowed
In-Reply-To: <30915920.1191838939062.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10552969.1192751523266.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1059?page=all ]

Andrew Rubinger reassigned EJBTHREE-1059:
-----------------------------------------

    Assignee: Andrew Rubinger

> Return a business interface from a home create method must not be allowed
> -------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1059
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1059
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>
> EJB 3 4.6.8: The return type for a create<METHOD> method must be the session bean's remote interface type.
> Using the proxy as if it would be an EJBObject results in class cast exceptions.
> java.lang.ClassCastException: $Proxy9
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject(RemoteUnitTestCase.java:208)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 19:54:03 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Thu, 18 Oct 2007 19:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6511245.1192751643517.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=all ]

Andrew Rubinger reassigned EJBTHREE-1045:
-----------------------------------------

    Assignee: Andrew Rubinger

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 4.2.2.GA, AS 5.0.0.Beta3
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 21:07:14 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Thu, 18 Oct 2007 21:07:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1284)
 ClassCastException when using
 "<" constraint on field of type java.lang.Object containing data of type
 java.lang.Integer
Message-ID: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
------------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1284
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
         Environment: Windows XP, Eclipse 3.2
            Reporter: Justin Wick
         Assigned To: Mark Proctor


If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.

See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 21:13:07 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Thu, 18 Oct 2007 21:13:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1284)
 ClassCastException when using
 "<" constraint on field of type java.lang.Object containing data of type
 java.lang.Integer
In-Reply-To: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9601038.1192756387317.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1284?page=all ]

Justin Wick updated JBRULES-1284:
---------------------------------

    Attachment: DroolsTest.zip

A complete drools project with minimalist test code ready to be transplanted.

> ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1284
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: DroolsTest.zip
>
>
> If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.
> See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:47:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31550366.1192762023459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith updated JBAS-4818:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:48:05 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:48:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13074531.1192762085736.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith updated JBAS-4818:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

Revision 3

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:50:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6325606.1192762203368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Michael Smith updated JBAS-4820:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives  (was: TECH REVIEW: Installation Guide - Chapter 2 -  Directory Structure)

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:50:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12858643.1192762203507.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Michael Smith updated JBAS-4820:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-2.odt

Revision 2

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:52:07 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:52:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23718736.1192762327896.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

Michael Smith updated JBAS-4821:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer  (was: TECH REVIEW: Installation Guide - Chapter 3 -  The Default Server Configuration File Set)

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:52:08 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:52:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24548719.1192762328032.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

Michael Smith updated JBAS-4821:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-3.odt

Revision 2

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:54:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18285268.1192762443324.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download  (was: TECH REVIEW: Installation Guide - Chapter 4 -  Starting and Stopping JBoss)

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 22:54:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 22:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12863481.1192762443441.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Michael Smith updated JBAS-4822:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-4.odt

REvision 2

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 -
Message-ID: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 5 - 
----------------------------------------------

                 Key: JBAS-4878
                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt

Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 -
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1196786.1192763103571.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

Michael Smith updated JBAS-4878:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-5.odt

> TECH REVIEW: Installation Guide - Chapter 5 - 
> ----------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5451276.1192763223558.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

Michael Smith updated JBAS-4878:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss  (was: TECH REVIEW: Installation Guide - Chapter 5 - )

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16006072.1192763223689.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

Michael Smith updated JBAS-4878:
--------------------------------

    Description: 
Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 

  was:
Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 


> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:09:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -
Message-ID: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 6 -  
-----------------------------------------------

                 Key: JBAS-4879
                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith


Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19788485.1192763463336.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Michael Smith updated JBAS-4879:
--------------------------------

    Summary: TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation  (was: TECH REVIEW: Installation Guide - Chapter 6 -  )

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:11:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:11:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25432603.1192763463467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Michael Smith updated JBAS-4879:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-6.odt

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:39:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
Message-ID: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
---------------------------------------------------------------

                 Key: JBAS-4880
                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Installation Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Michael Smith
         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt

Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:39:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8074111.1192765143641.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4880?page=all ]

Michael Smith updated JBAS-4880:
--------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-1.odt

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4880
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:39:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4818) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <14924061.1192161723292.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12095996.1192765143749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4818?page=all ]

Michael Smith closed JBAS-4818.
-------------------------------

    Resolution: Duplicate Issue

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4818
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4818
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:46:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - Getting Started
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3392716.1192765563375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

Michael Smith updated JBAS-4825:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-1.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started
> ----------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:48:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started Guide - Chapter 2. The JBoss Server - A Quick Tour
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9935628.1192765683407.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Michael Smith updated JBAS-4826:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-2.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 18 23:48:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Thu, 18 Oct 2007 23:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24273123.1192765683566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Michael Smith updated JBAS-4826:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2   (was: TECH REVIEW: Getting Started Guide - Chapter 2. The JBoss Server - A Quick Tour)

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:01:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8542299.1192766463459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Michael Smith updated JBAS-4827:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-3.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:03:14 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:03:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5133456.1192766594974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Michael Smith updated JBAS-4828:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application  (was: TECH REVIEW: Getting Started Guide - Chapter 4. The Duke's Bank Application)

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:03:15 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:03:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4828) TECH REVIEW: Getting
 Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31086067.1192766595133.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Michael Smith updated JBAS-4828:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-4.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21940737.1192766703284.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Michael Smith updated JBAS-4829:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam  (was: TECH REVIEW: Getting Started Guide - Chapter 5. J2EE Web Services)

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:05:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18620203.1192766703427.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Michael Smith updated JBAS-4829:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-5.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <390452.1192766823532.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Michael Smith updated JBAS-4830:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases  (was: TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans)

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:07:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16271304.1192766823865.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Michael Smith updated JBAS-4830:
--------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-6.odt

Revision 2

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:09:06 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4831) TECH REVIEW: Getting
 Started Guide - Chapter 7. Container-Managed Persistence
In-Reply-To: <2964949.1192165535786.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5367118.1192766946482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4831?page=all ]

Michael Smith closed JBAS-4831.
-------------------------------

    Resolution: Out of Date

> TECH REVIEW: Getting Started Guide - Chapter 7. Container-Managed Persistence
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4831
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4831
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-7.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:09:06 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4832) TECH REVIEW: Getting
 Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33008676.1192766946755.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4832?page=all ]

Michael Smith closed JBAS-4832.
-------------------------------

    Resolution: Out of Date

> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:09:06 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 00:09:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4833) TECH REVIEW: Getting
 Started Guide - Chapter 9. Using Hibernate
In-Reply-To: <12730012.1192165536058.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24487271.1192766946896.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4833?page=all ]

Michael Smith closed JBAS-4833.
-------------------------------

    Resolution: Out of Date

> TECH REVIEW: Getting Started Guide - Chapter 9. Using Hibernate
> ---------------------------------------------------------------
>
>                 Key: JBAS-4833
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4833
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-9.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:14:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Fri, 19 Oct 2007 00:14:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1285) Time Machine to
 allow setting of "now" effective current time in Rule
Message-ID: <30930954.1192767254713.JavaMail.jira@cloud.prod.atl2.jboss.com>

Time Machine to allow setting of "now" effective current time in Rule
---------------------------------------------------------------------

                 Key: JBRULES-1285
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1285
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0


This is needed for testing effective dating.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 00:58:14 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Fri, 19 Oct 2007 00:58:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
Message-ID: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>

java.net.SocketException: Too many open files
---------------------------------------------

                 Key: JBMESSAGING-1115
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Critical


When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.

2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
java.net.SocketException: Too many open files
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
        at java.net.ServerSocket.implAccept(ServerSocket.java:450)
        at java.net.ServerSocket.accept(ServerSocket.java:421)
        at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
        at java.lang.Thread.run(Thread.java:595)
2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 02:19:03 2007
From: jira-events at lists.jboss.org (Michael Smith (JIRA))
Date: Fri, 19 Oct 2007 02:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33060066.1192774743243.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

Michael Smith updated JBAS-4825:
--------------------------------

    Summary: TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour  (was: TECH REVIEW: Getting Started Guide - Chapter 1 - Getting Started)

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 02:44:04 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Fri, 19 Oct 2007 02:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12342687.1192776244012.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

David Roberts updated GPD-169:
------------------------------

    Attachment: gpd.xml
                processdefinition.xml

I've attached the gpd.xml and the processdefinition.xml that caused me the initial problem. It has been updated quite a bit since the last time I had the problem. The node placement problem hasn't occured in a while, so I'm not sure what actually causes it. The same node placement problem happened on a completely different process two days ago. I haven't noticed any common ground though. And I can't seem to duplicate it when I want to, only hope that it doesn't happen.

However, the transition text positioning is always a problem. Try placing the text somewhere, and re-open the process. You'll notice that it doesn't save its position.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 02:48:14 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Fri, 19 Oct 2007 02:48:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1284)
 ClassCastException when
 using "<" constraint on field of type java.lang.Object containing data of
 type java.lang.Integer
In-Reply-To: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1486857.1192776494487.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1284?page=comments#action_12383376 ] 
            
Michael Neale commented on JBRULES-1284:
----------------------------------------

OK - yes well at compile time it decides to coerce to a string, yet gets a rude shock at runtime. 

not much more we can do at compile time for this, but at runtime I will see if we can do a better coercion.

> ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1284
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: DroolsTest.zip
>
>
> If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.
> See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 03:04:03 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Fri, 19 Oct 2007 03:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5334924.1192777443671.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12383377 ] 
            
David Roberts commented on GPD-169:
-----------------------------------

Okay I managed to reproduce the problem with the gpd.xml and processdefinition.xml I attached above, by doing either one of the following:

- On the graphical designer, delete the end node named "Offer Withdrawn". Then, add an end node in the same position and give it a transition line from "Withdrawn Notification" to "Offer Withdrawn", and save. Now close and re-open the processdefinition.xml in the designer, and all nodes will be messed up. Looking at the gpd.xml, the new end node has been placed at the bottom. This seems to cause the problem.

OR

- In the gpd.xml, take the line/node "Offer Withdrawn", and move it to the bottom of the gpd.xml, so it is the last node. Now close and open the processdefinition.xml with the graphical editor, the nodes will be messed up.

It seems that if an end node is at the bottom of the gpd.xml, it messes up the nodes? Well at least in this case.
Hope this helps...


> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:32:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10058969.1192782723368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

samson kittoli updated JBAS-4849:
---------------------------------

    Summary: TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel  (was: TECH REVIEW:  Server Configuration Guide - Chapter3 - Naming on JBoss)

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:32:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17790590.1192782723498.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli updated JBAS-4848:
---------------------------------

    Summary: TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss  (was: TECH REVIEW: Server Configuration Guide - Chapter4 - Connectors on JBoss)

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:32:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12903193.1192782723663.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

samson kittoli updated JBAS-4847:
---------------------------------

    Summary: TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss  (was: TECH REVIEW:  Server Configuration Guide - Chapter5 - Transactions on JBoss)

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:34:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15895283.1192782843754.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

samson kittoli updated JBAS-4846:
---------------------------------

    Summary: TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss  (was: TECH REVIEW:  Server Configuration Guide - Chapter6 - Messaging on JBoss)

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 04:34:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 04:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16212870.1192782843872.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

samson kittoli updated JBAS-4845:
---------------------------------

    Summary: TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss  (was: TECH REVIEW: Server Configuration Guide - Chapter7 - Quick Tutorial to Setup a Clustered Web Application.)

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:36:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28488085.1192790163319.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

samson kittoli updated JBAS-4851:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt

10-19-2007

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:49:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
Message-ID: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
----------------------------------------------------------------------

                 Key: JBAS-4881
                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:51:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
In-Reply-To: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31496818.1192791063329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4881?page=all ]

samson kittoli updated JBAS-4881:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4881
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:53:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4882) TECH REVIEW: Server
 Configuration Guide - Chapter9 - Web Services
Message-ID: <11998244.1192791183470.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services
-----------------------------------------------------------------

                 Key: JBAS-4882
                 URL: http://jira.jboss.com/jira/browse/JBAS-4882
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt

Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:53:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4882) TECH REVIEW: Server
 Configuration Guide - Chapter9 - Web Services
In-Reply-To: <11998244.1192791183470.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22490.1192791183809.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4882?page=all ]

samson kittoli updated JBAS-4882:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services
> -----------------------------------------------------------------
>
>                 Key: JBAS-4882
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4882
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:55:04 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:55:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
Message-ID: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
-------------------------------------------------------------------------

                 Key: JBAS-4883
                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:57:05 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:57:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
Message-ID: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
-------------------------------------------------------------------

                 Key: JBAS-4884
                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli


Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:59:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15132201.1192791543404.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

samson kittoli updated JBAS-4883:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 06:59:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 06:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
In-Reply-To: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17293184.1192791543819.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4884?page=all ]

samson kittoli updated JBAS-4884:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
> -------------------------------------------------------------------
>
>                 Key: JBAS-4884
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:01:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
Message-ID: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>

TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
---------------------------------------------------

                 Key: JBAS-4885
                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Server Configuration Guide
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: samson kittoli
         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt

Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide

1. Open document in Open Office
2. Edit -> Changes -> Record
3. Edit the document
4. Save changes and reattach to this Jira

It is important for track changes to be enabled so the re-write can be easily performed.

http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:01:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1445079.1192791663869.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

samson kittoli updated JBAS-4885:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:03:15 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:03:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30404471.1192791795518.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

samson kittoli updated JBAS-4844:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt, JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:03:15 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Fri, 19 Oct 2007 07:03:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20527598.1192791795805.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

samson kittoli updated JBAS-4843:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 07:12:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 07:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4688) Upgrade jboss
 transactions to 4.3.x (from 4.2.3.SP5)
In-Reply-To: <13450500.1189159931263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20098208.1192792323341.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4688?page=all ]

Dimitris Andreadis closed JBAS-4688.
------------------------------------

    Resolution: Done

With the help of Paul we are using jboss-integration 5.0.0.Beta4.

JBossTS now at 4.3.0.Beta2.

> Upgrade jboss transactions to 4.3.x (from 4.2.3.SP5)
> ----------------------------------------------------
>
>                 Key: JBAS-4688
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4688
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JB5-Transaction Manager
>            Reporter: Dimitris Andreadis
>         Assigned To: Jonathan Halliday
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Upgrade to a JBoss Transaction version that implements JTA 1.1

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:14:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 19 Oct 2007 09:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1767) Add support for
 exporting full CMS content (multiple language)
Message-ID: <30770226.1192799643385.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add support for exporting full CMS content (multiple language)
--------------------------------------------------------------

                 Key: JBPORTAL-1767
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1767
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final
            Reporter: Mariusz Smykula
         Assigned To: Sohil Shah


Current, after migration all data in language other than default are lost. There is no solution for full data exporting.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:14:03 2007
From: jira-events at lists.jboss.org (Mariusz Smykula (JIRA))
Date: Fri, 19 Oct 2007 09:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1767) Add support for
 exporting full CMS content (multiple language)
In-Reply-To: <30770226.1192799643385.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18806098.1192799643637.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1767?page=all ]

Mariusz Smykula updated JBPORTAL-1767:
--------------------------------------

    Description: Currently after migration all data in language other than default are lost. There is no solution for full data exporting.  (was: Current, after migration all data in language other than default are lost. There is no solution for full data exporting.)

> Add support for exporting full CMS content (multiple language)
> --------------------------------------------------------------
>
>                 Key: JBPORTAL-1767
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1767
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal CMS
>    Affects Versions: 2.6.2 Final
>            Reporter: Mariusz Smykula
>         Assigned To: Sohil Shah
>
> Currently after migration all data in language other than default are lost. There is no solution for full data exporting.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:18:03 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Fri, 19 Oct 2007 09:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3364889.1192799883436.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383431 ] 
            
Johannes Fiala commented on JBPORTAL-1759:
------------------------------------------

Julien, thank you for the quick analysis. 

The url has been manufactured manually, so I can correct it easily in my program (in fact it is a redirect url constructed manually).

However, if the user enters this url into the address field of the browser, my browsers (Mozilla Firefox 2.0.0.8/MS IE 6) transform this automatically x-www-formurlencoded with ISO-8859-1 (? becomes %FC), which would result in the error outlined above. With earlier versions of JBoss Portal 2.2.1SP3 and 2.6.1 GA this works correct as expected.

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Fri Oct 19 09:20:09 2007
From: jira-events at lists.jboss.org (Sergey Manukyan (JIRA))
Date: Fri, 19 Oct 2007 09:20:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1286) Incorrect
 information in section 2.5.7.3. Agenda Filters
Message-ID: <4085772.1192800009350.JavaMail.jira@cloud.prod.atl2.jboss.com>

Incorrect information in section 2.5.7.3. Agenda Filters
--------------------------------------------------------

                 Key: JBRULES-1286
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1286
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Manual
    Affects Versions: 4.0.2
            Reporter: Sergey Manukyan
         Assigned To: Mark Proctor


CORRECTION #1

Manual states :

To use a filter specify it while calling FireAllRules. The following example will filter out all rules ending with the text "Test":
workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );      

Should be:

To use a filter specify it while calling FireAllRules. The following example will only allow activation of rules ending with the text "Test". All others will be filtered out.:
workingMemory.fireAllRules( new RuleNameEndsWithAgendaFilter( "Test" ) );      

CORRECTION #2

Manual states :

RuleNameEndWithAgendaFilter

Should be :

RuleNameEndsWithAgendaFilter




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 09:26:16 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Fri, 19 Oct 2007 09:26:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26942602.1192800376995.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383437 ] 
            
Julien Viet commented on JBPORTAL-1759:
---------------------------------------

it looks like your form is doing a get instead of a post, isn't it ?



> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Fri Oct 19 09:44:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 09:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1300) Default a
 portlet window to maximized.
In-Reply-To: <24092633.1173097870945.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21722347.1192801444222.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1300?page=all ]

Thomas Heute resolved JBPORTAL-1300.
------------------------------------

    Resolution: Done

> Default a portlet window to maximized.
> --------------------------------------
>
>                 Key: JBPORTAL-1300
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1300
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: David Roberts
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> When adding portlets, it would be nice if there were an option where the portlet window could start out MAXIMIZED, so the entire portlet fills the screen nicely without the users having to click the maximize button. Eg. this would be very helpful when using the IFrame Portlet, so the URL being referenced fits the entire screen, and doesn't mess up the original layout of the referenced page.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:14:03 2007
From: jira-events at lists.jboss.org (Francisco Reverbel (JIRA))
Date: Fri, 19 Oct 2007 10:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20791314.1192803243314.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4830?page=comments#action_12383443 ] 
            
Francisco Reverbel commented on JBAS-4830:
------------------------------------------

The title of the Oracle section ("Setting up an XADataSource with Oracle 9i") is inconsistent with the text, which states that "For this example, we've used Oracle 10g". The reference to 9i in the title shoud be either updated to 10g or, perhaps, removed (if the example does not change across Oracle versions in a significant way -- I think this is the case, but am not sure).



> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:14:03 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 19 Oct 2007 10:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-375) Grouping of
 messages with JMSXGroupId
Message-ID: <15122370.1192803243571.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ]

Jeff Mesnil reassigned JBMESSAGING-375:
---------------------------------------

    Assignee: Jeff Mesnil  (was: Tim Fox)

> Grouping of messages with JMSXGroupId
> -------------------------------------
>
>                 Key: JBMESSAGING-375
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue.
> This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:16:03 2007
From: jira-events at lists.jboss.org (Jeff Mesnil (JIRA))
Date: Fri, 19 Oct 2007 10:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-381) Add param on
 destination to disable persistence
Message-ID: <27447596.1192803363502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]

Jeff Mesnil reassigned JBMESSAGING-381:
---------------------------------------

    Assignee: Jeff Mesnil  (was: Tim Fox)

> Add param on destination to disable persistence
> -----------------------------------------------
>
>                 Key: JBMESSAGING-381
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>             Fix For: 2.0.0 Beta 1
>
>         Attachments: patch-JBMESSAGING-381.txt
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent.
> This should give equivalent functionality to the JBossMQ NullPersistenceManager.
> in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:18:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Fri, 19 Oct 2007 10:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15158097.1192803483653.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12383444 ] 
            
Koen Aers commented on GPD-169:
-------------------------------

Thanks. This will most probably be helpful.

Cheers,
Koen

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:22:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7990827.1192803723765.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic reassigned JBMESSAGING-1099:
--------------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:22:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:22:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25222755.1192803724330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

        Fix Version/s: AS 5.0 Integration
                           (was: 1.4.0.SP1)
    Affects Version/s:     (was: 1.4.0.GA)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:24:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4886) Incorrect
 order/dependency shutting down MDBs
Message-ID: <32753121.1192803843327.JavaMail.jira@cloud.prod.atl2.jboss.com>

Incorrect order/dependency shutting down MDBs
---------------------------------------------

                 Key: JBAS-4886
                 URL: http://jira.jboss.com/jira/browse/JBAS-4886
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Clebert Suconic
         Assigned To: Weston Price
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:26:26 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:26:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4886) Incorrect
 order/dependency shutting down MDBs
In-Reply-To: <32753121.1192803843327.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31129014.1192803986370.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4886?page=all ]

Clebert Suconic updated JBAS-4886:
----------------------------------

    Description: 
Currently MDBs are being shutdown after the ServerPeer, what could cause communication error during the Connection closing, causing a waitForever in some interceptors.

We need to correctly set the dependency between MBeans

> Incorrect order/dependency shutting down MDBs
> ---------------------------------------------
>
>                 Key: JBAS-4886
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4886
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Clebert Suconic
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Currently MDBs are being shutdown after the ServerPeer, what could cause communication error during the Connection closing, causing a waitForever in some interceptors.
> We need to correctly set the dependency between MBeans

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:26:26 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 10:26:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1462211.1192803986740.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------

    Resolution: Rejected

After investigations this became a JBAS code... we opened JBAS-4886 for this.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:32:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 19 Oct 2007 10:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4886) Incorrect
 order/dependency shutting down MDBs
In-Reply-To: <32753121.1192803843327.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25387411.1192804323374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4886?page=all ]

Adrian Brock closed JBAS-4886.
------------------------------

    Resolution: Won't Fix

> Incorrect order/dependency shutting down MDBs
> ---------------------------------------------
>
>                 Key: JBAS-4886
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4886
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Clebert Suconic
>         Assigned To: Weston Price
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Currently MDBs are being shutdown after the ServerPeer, what could cause communication error during the Connection closing, causing a waitForever in some interceptors.
> We need to correctly set the dependency between MBeans

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 10:59:18 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Fri, 19 Oct 2007 10:59:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1534590.1192805958891.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=all ]

Carlo de Wolf updated EJBTHREE-1045:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 11:37:03 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 19 Oct 2007 11:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1284)
 ClassCastException when
 using "<" constraint on field of type java.lang.Object containing data of
 type java.lang.Integer
In-Reply-To: <11469210.1192756034803.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29880.1192808223853.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1284?page=comments#action_12383469 ] 
            
Justin Wick commented on JBRULES-1284:
--------------------------------------

IMHO, if this is known to be a "bad" thing to do, the compiler should at least throw a warning saying so, if not a straight-out error.  Unless, of course, the runtime coercian could be made better.

Is there a reason runtime type coercion cannot say that literals are whatever type they would be in Java?  i.e. 50 is  an integer, 50l is a long, 50.0 is a double, "50" is a String, etc?

> ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1284
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1284
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Windows XP, Eclipse 3.2
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: DroolsTest.zip
>
>
> If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint.
> See attached files for an example

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:31:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4887) Port beanshell
	deployer to VDF
Message-ID: <27777727.1192811463357.JavaMail.jira@cloud.prod.atl2.jboss.com>

Port beanshell deployer to VDF
------------------------------

                 Key: JBAS-4887
                 URL: http://jira.jboss.com/jira/browse/JBAS-4887
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Deployment services
            Reporter: Dimitris Andreadis
         Assigned To: Ales Justin
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:34:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:34:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3536) Spring Deployer
 lacks info on
 Spring compatibility, I get NoSuchMethodError....and try to find which
 Spring version to use...
In-Reply-To: <22456206.1156144632106.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <284185.1192811655479.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3536?page=all ]

Dimitris Andreadis updated JBAS-3536:
-------------------------------------

    Component/s: Spring integration
                     (was: Other)
       Assignee: Ales Justin

Assign to Ales to look at.

> Spring Deployer lacks info on Spring compatibility, I get NoSuchMethodError....and try to find which Spring version to use...
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-3536
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3536
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: WinXP, Spring-2.0-RC2,  JBOSS-AS-4.0.4-GA
>            Reporter: Morten Haavaldsen
>         Assigned To: Ales Justin
>
> I use the Spring Deployer and get NoSuchMethodError on Spring classes during deployment.
> I use the Spring Deployer 1.3 and it is the example(the fixed one as well) which gives the exception.
> So, the big question is: which Spring version is the deployer compatible with?

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:36:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2040) Spring Deployer
Message-ID: <28754905.1192811763525.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2040?page=all ]

Dimitris Andreadis updated JBAS-2040:
-------------------------------------

    Component/s: Spring integration
                     (was: Deployment services)

> Spring Deployer
> ---------------
>
>                 Key: JBAS-2040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2040
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>            Priority: Optional
>
> Complete me for release notes.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:36:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2042) Spring deployer and
 coding standards
Message-ID: <912432.1192811763777.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2042?page=all ]

Dimitris Andreadis updated JBAS-2042:
-------------------------------------

    Component/s: Spring integration
                     (was: Other)

> Spring deployer and coding standards
> ------------------------------------
>
>                 Key: JBAS-2042
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2042
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>            Priority: Trivial
>
> The spring deployer follows incorrect coding standards.
> i.e. Kernigan and Ritchie
> Also, it should not use printStackTrace(), 
> nor should it use the horrible log.error and throw paradigm
> that just leads to a console full of annoying duplicate logging of errors.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:36:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:36:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-2153) Spring-int tests
Message-ID: <21809673.1192811764037.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-2153?page=all ]

Dimitris Andreadis updated JBAS-2153:
-------------------------------------

    Component/s: Spring integration
                     (was: Test Suite)

> Spring-int tests
> ----------------
>
>                 Key: JBAS-2153
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2153
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Spring integration
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>
> Need some ant unit tests for spring-int such that we don't break it.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:38:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4666) MBean for new
	EjbDeployer
In-Reply-To: <29450369.1188919271355.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30852590.1192811883486.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4666?page=all ]

Dimitris Andreadis updated JBAS-4666:
-------------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was: JBossAS-5.0.0.GA)

> MBean for new EjbDeployer
> -------------------------
>
>                 Key: JBAS-4666
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4666
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>            Reporter: Adrian Brock
>             Fix For: JBossAS-5.0.0.CR1
>
>
> I've reinstated the MBean for the EJBDeployer since some tests were using it.
> This uses the @JMX annotation on the POJO.
> The new deployer looks to have some bits missing related to verification which it what this task is about resolving.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:38:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 12:38:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-24) Get OpenSaml2
 snapshot libraries into the JBoss Maven repository
In-Reply-To: <26707524.1164815335686.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19964589.1192811883675.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-24?page=all ]

Anil Saldhana updated SECURITY-24:
----------------------------------

    Summary: Get OpenSaml2 snapshot libraries into the JBoss Maven repository  (was: Get OpenSaml2 snapshot libraries into the JBoss repository)

> Get OpenSaml2 snapshot libraries into the JBoss Maven repository
> ----------------------------------------------------------------
>
>                 Key: SECURITY-24
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-24
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: OnDemand, Repository
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:38:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:38:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4130) Simple HelloWorld
 JSF 1.2 application does not work
In-Reply-To: <28586848.1172070275576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23312324.1192811884487.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4130?page=all ]

Dimitris Andreadis updated JBAS-4130:
-------------------------------------

    Component/s: JavaServerFaces
                     (was: Deployment services)
       Assignee: Stan Silvert  (was: Dimitris Andreadis)

Assign to Stan to look at

> Simple HelloWorld JSF 1.2 application does not work
> ---------------------------------------------------
>
>                 Key: JBAS-4130
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4130
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JavaServerFaces
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: Windows XP,  Suse 10.2
>            Reporter: sedat ciftci
>         Assigned To: Stan Silvert
>
>  I have faced with a problem while deploying my JSF 1.2 web application (sun impl) ( I build with Netbeans 5.5 Visual Web pack) to JBoss5 Beta. It works with Glassfish. In order to find the problem, I make a simple Hello world web application and try to deploy it to JBoss5Beta. However, I get the same exception.
> The first exception that I overcome is related with web-facesconfig_1_2.xsd. JBoss says that it can not resolve this schema. I solve this problem by putting this file into the jboss.jar/schema.
> The second exception that I cannot solve is although my projects managed-beans.xml file is well formed, JBoss throws such an exception:
> org.jboss.deployers.spi.DeploymentException: The xml JBoss5Ex.war/WEB-INF/managed-beans.xml is not well formed!
> at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:94)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:173)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88)
> at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59)
> at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
> at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
> at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
> at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:508)
> at java.lang.Thread.run(Thread.java:595)
> Note that JBoss5Ex.war is my web application. 
>  Here is the content of my managed-beans.xml file (starting after the #'s line):
> ######################################
> <?xml version="1.0" encoding="UTF-8"?>
> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd">
> <managed-bean>
> <managed-bean-name>SessionBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.SessionBean1</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>Page1</managed-bean-name>
> <managed-bean-class>jboss5ex.Page1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>ApplicationBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.ApplicationBean1</managed-bean-class>
> <managed-bean-scope>application</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>RequestBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.RequestBean1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> </faces-config>
> #################################################

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:40:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:40:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-1292) SFSB session
	replication
Message-ID: <12456485.1192812005257.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-1292?page=comments#action_12383478 ] 
            
Dimitris Andreadis commented on JBAS-1292:
------------------------------------------

Is this issue still current, or outdated?

> SFSB session replication
> ------------------------
>
>                 Key: JBAS-1292
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1292
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Bela Ban
>         Assigned To: Jason T. Greene
>   Original Estimate: 10 weeks
>  Remaining Estimate: 10 weeks
>
> - Issues: who instrument the user-specified object? Can it be done transparently?
>   - SFSB has states defined already and user declared it as "clusterable", can we
>     declare the fields object as "advisable" at runtime. Meaning, deployer will know
>     this bean is clusterable and it will "delegate" it to JBossAop to declare all
>     the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor
>     at run time. Check with Bill on this feature.
>   - Check modified field and do fine-grained replication only

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:47:11 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 12:47:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-24) Get OpenSaml2
 snapshot libraries into the JBoss Maven repository
In-Reply-To: <26707524.1164815335686.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26446090.1192812431385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-24?page=all ]

Anil Saldhana closed SECURITY-24.
---------------------------------

    Resolution: Done

Maven Repository has:

OpenSaml-2.0-alpha1:
maven2/opensaml/opensaml2/2.0-alpha1/

Opensaml2 openws:
maven2/opensaml/openws/1.0-alpha1/

Opensaml2 xmltooling:
maven2/opensaml/xmltooling/1.0-alpha1/

Commons-Codec:
maven2/org/apache/commons-codec/1.3/

Commons-SSL:
maven2/org/apache/commons/not-yet-commons-ssl/0.3.7

httpclient:
maven2/org/apache/httpclient/3.0.1/

joda-time:
maven2/net/sf/joda-time/1.4/

javolution:
maven2/org/javolution/4.1.0

Velocity-dep:
maven2/velocity/velocity-dep/1.5/



> Get OpenSaml2 snapshot libraries into the JBoss Maven repository
> ----------------------------------------------------------------
>
>                 Key: SECURITY-24
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-24
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: OnDemand, Repository
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: NO_VERSION
>
>
> The Open Saml version 2 development is happening in the community. To create a set of tests that will use an implementation of the Security SPI with federation capabilities, it is necessary to have snapshot archives of opensaml2 in the JBoss repositories.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:49:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 19 Oct 2007 12:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4888) Inject
 InvalidationManagerMBean into JGCacheInvalidationBridge
Message-ID: <29917340.1192812543460.JavaMail.jira@cloud.prod.atl2.jboss.com>

Inject InvalidationManagerMBean into JGCacheInvalidationBridge
--------------------------------------------------------------

                 Key: JBAS-4888
                 URL: http://jira.jboss.com/jira/browse/JBAS-4888
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For:  JBossAS-5.0.0.Beta3


Currently an ObjectName is injected, and startService() does a JMX lookup.  Just have the MC inject the service.

Will also remove the getter/setter from JGCacheInvalidationServiceMBean -- MC is doing the injection into a pojo service, and it doesn't need to be in an MBean interface for any other reason.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:49:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 19 Oct 2007 12:49:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4888) Inject
 InvalidationManagerMBean into JGCacheInvalidationBridge
In-Reply-To: <29917340.1192812543460.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11736107.1192812543600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4888?page=all ]

Brian Stansberry closed JBAS-4888.
----------------------------------

    Resolution: Done

> Inject InvalidationManagerMBean into JGCacheInvalidationBridge
> --------------------------------------------------------------
>
>                 Key: JBAS-4888
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4888
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> Currently an ObjectName is injected, and startService() does a JMX lookup.  Just have the MC inject the service.
> Will also remove the getter/setter from JGCacheInvalidationServiceMBean -- MC is doing the injection into a pojo service, and it doesn't need to be in an MBean interface for any other reason.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:51:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:51:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18802649.1192812664232.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3885?page=all ]

Dimitris Andreadis reassigned JBAS-3885:
----------------------------------------

    Assignee: Dimitris Andreadis

> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:51:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:51:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28881920.1192812664658.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3885?page=comments#action_12383481 ] 
            
Dimitris Andreadis commented on JBAS-3885:
------------------------------------------

Yes, it's this line in \jbossas\jmx-remoting\src\main\org\jboss\mx\remoting\service\JMXConnectorServerService.java:

...
      if(bindAddress == null || bindAddress.equals("0.0.0.0"))
      {
         bindAddress = InetAddress.getLocalHost().getHostName();
      }

> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:53:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3508)
 org.jboss.test.aop.test.SimpleBeanUnitTestCase fails because "ejb" is not
 bound
In-Reply-To: <15145030.1155322695616.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1507060.1192812783435.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3508?page=all ]

Dimitris Andreadis updated JBAS-3508:
-------------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> org.jboss.test.aop.test.SimpleBeanUnitTestCase fails because "ejb" is not bound
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-3508
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3508
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: win xp
>            Reporter: Jaroslaw Kijanowski
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> org.jboss.test.aop.test.SimpleBeanUnitTestCase fails because "ejb" is not bound, because of missing files in META-INF.
> Solution:
> copy following xml files to:
> testsuite\src\resources\aop\simpleejb\META-INF
> ejb-jar.xml:
> **************************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
> <ejb-jar >
>    <description><![CDATA[No Description.]]></description>
>    <display-name>Generated by XDoclet</display-name>
>    <enterprise-beans>
>       <!-- Session Beans -->
>       <session >
>          <description><![CDATA[]]></description>
>          <ejb-name>test/Simple</ejb-name>
>          <home>org.jboss.test.aop.simpleejb.SimpleHome</home>
>          <remote>org.jboss.test.aop.simpleejb.Simple</remote>
>          <ejb-class>org.jboss.test.aop.simpleejb.SimpleBean</ejb-class>
>          <session-type>Stateless</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>      <!--
>        To add session beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called session-beans.xml that contains
>        the <session></session> markup for those beans.
>      -->
>       <!-- Entity Beans -->
>      <!--
>        To add entity beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called entity-beans.xml that contains
>        the <entity></entity> markup for those beans.
>      -->
>       <!-- Message Driven Beans -->
>      <!--
>        To add message driven beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called message-driven-beans.xml that contains
>        the <message-driven></message-driven> markup for those beans.
>      -->
>    </enterprise-beans>
>    <!-- Relationships -->
>    <!-- Assembly Descriptor -->
>    <assembly-descriptor >
>      <!--
>        To add additional assembly descriptor info here, add a file to your
>        XDoclet merge directory called assembly-descriptor.xml that contains
>        the <assembly-descriptor></assembly-descriptor> markup.
>      -->
>    <!-- finder permissions -->
>    <!-- transactions -->
>    <container-transaction >
>       <method >
>          <ejb-name>test/Simple</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Required</trans-attribute>
>     </container-transaction>
>    <!-- finder transactions -->
>    </assembly-descriptor>
> </ejb-jar>
> ************************************
> ************************************
> jboss.xml:
> ******************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
> <jboss>
>    <enterprise-beans>
>      <!--
>        To add beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called jboss-beans.xml that contains
>        the <session></session>, <entity></entity> and <message-driven></message-driven>
>        markup for those beans.
>      -->
>       <session>
>          <ejb-name>test/Simple</ejb-name>
>          <jndi-name>ejb/test/Simple</jndi-name>
>       </session>
>    </enterprise-beans>
>    <resource-managers>
>    </resource-managers>
> </jboss>

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:55:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-1402) Transaction Recovery
Message-ID: <14126009.1192812903783.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ]

Dimitris Andreadis reassigned JBAS-1402:
----------------------------------------

    Assignee: Adrian Brock

Adrian, can we close this whole task & subtasks out-of-date, or do we keep the JCA tasks as still current?

> Transaction Recovery
> --------------------
>
>                 Key: JBAS-1402
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1402
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.0.1 Final
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>
> Implement optional transaction recovery
> The simplest mechanism is to do this is with a local database
> using the last resource gambit where during its "prepare" it logs the XID in a table.
> If this last resource fails to commit, recovery will not find the transaction
> in the table which means it will rollback the whole transaction.
> This has limitations where a different local resource is required within the transaction
> but not this local database used as the recovery log.
> Another implementation is a local file. Though more complicated it should give superior
> performance. 
> But, it does not work well with the last resource gambit, e.g. you cannot tell
> whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation
> before the result is returned from the db.
> The other work required:
> 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier.
> Currently the RARs need the transaction manager at deployment time. The
> recovery service needs to be an external service depending upon both the
> tm and the managed connection factories.
> At least this will require a GUID for the XID so we can avoid duplicates between
> unrecovered XIDs and any new XIDs created before recovery is complete.
> 2) JBossMQ needs to implement XAResource.recover()

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:57:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 12:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3509)
 org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
In-Reply-To: <20759834.1155322935652.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13624554.1192813023811.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3509?page=all ]

Dimitris Andreadis updated JBAS-3509:
-------------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound
> ----------------------------------------------------------------------
>
>                 Key: JBAS-3509
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3509
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: win xp
>            Reporter: Jaroslaw Kijanowski
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> org.jboss.test.cache.bean.MBeanUnitTestCase because "ejb" is not bound because of missing xml files.
> Resolve:
> Copy following xml files to testsuite\src\resources\cache\META-INF
> ************
> ejb-jar.xml:
> ************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
> <ejb-jar >
>    <description><![CDATA[No Description.]]></description>
>    <display-name>Generated by XDoclet</display-name>
>    <enterprise-beans>
>       <!-- Session Beans -->
>       <session >
>          <description><![CDATA[]]></description>
>          <ejb-name>CacheObjectMeanTester</ejb-name>
>          <home>org.jboss.test.cache.bean.CacheObjectMeanTesterHome</home>
>          <remote>org.jboss.test.cache.bean.CacheObjectMeanTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.CacheObjectMeanTesterBean</ejb-class>
>          <session-type>Stateless</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[Proxy to the TreeCache MBean.]]></description>
>          <ejb-name>test/TreeCacheTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
>          <ejb-name>test/TreeCacheAopTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheAopTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheAopTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheAopTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[EJB proxy to the TreeCache MBean service.]]></description>
>          <ejb-name>test/TreeCacheMBeanTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheMBeanTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheMBeanTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheMBeanTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>       <session >
>          <description><![CDATA[Proxy to the TreeCacheAop MBean.]]></description>
>          <ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
>          <home>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterHome</home>
>          <remote>org.jboss.test.cache.bean.TreeCacheAopMBeanTester</remote>
>          <ejb-class>org.jboss.test.cache.bean.TreeCacheAopMBeanTesterBean</ejb-class>
>          <session-type>Stateful</session-type>
>          <transaction-type>Container</transaction-type>
>       </session>
>      <!--
>        To add session beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called session-beans.xml that contains
>        the <session></session> markup for those beans.
>      -->
>       <!-- Entity Beans -->
>      <!--
>        To add entity beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called entity-beans.xml that contains
>        the <entity></entity> markup for those beans.
>      -->
>       <!-- Message Driven Beans -->
>      <!--
>        To add message driven beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called message-driven-beans.xml that contains
>        the <message-driven></message-driven> markup for those beans.
>      -->
>    </enterprise-beans>
>    <!-- Relationships -->
>    <!-- Assembly Descriptor -->
>    <assembly-descriptor >
>      <!--
>        To add additional assembly descriptor info here, add a file to your
>        XDoclet merge directory called assembly-descriptor.xml that contains
>        the <assembly-descriptor></assembly-descriptor> markup.
>      -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- finder permissions -->
>    <!-- transactions -->
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheAopTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheMBeanTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <container-transaction >
>       <method >
>          <ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
>           <method-name>*</method-name>
>        </method>
>        <trans-attribute>Supports</trans-attribute>
>     </container-transaction>
>    <!-- finder transactions -->
>    </assembly-descriptor>
> </ejb-jar>
> ************
> ************
> jboss.xml
> ************
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
> <jboss>
>    <enterprise-beans>
>      <!--
>        To add beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called jboss-beans.xml that contains
>        the <session></session>, <entity></entity> and <message-driven></message-driven>
>        markup for those beans.
>      -->
>       <session>
>          <ejb-name>CacheObjectMeanTester</ejb-name>
>          <jndi-name>test/CacheObjectMeanTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheTester</ejb-name>
>          <jndi-name>ejb/test/TreeCacheTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheAopTester</ejb-name>
>          <jndi-name>test/TreeCacheAopTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheMBeanTester</ejb-name>
>          <jndi-name>ejb/test/TreeCacheMBeanTester</jndi-name>
>       </session>
>       <session>
>          <ejb-name>test/TreeCacheAopMBeanTester</ejb-name>
>          <jndi-name>ejb/test/TreeCacheAopMBeanTester</jndi-name>
>       </session>
>    </enterprise-beans>
>    <resource-managers>
>    </resource-managers>
> </jboss>
> ***************

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:59:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 12:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17578747.1192813143841.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic reopened JBMESSAGING-1099:
------------------------------------------

             

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 12:59:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 12:59:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25678265.1192813144124.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

        Fix Version/s: 1.4.0.SP1
                           (was: AS 5.0 Integration)
    Affects Version/s: 1.4.0.GA

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:01:08 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 19 Oct 2007 13:01:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1357) Support for massive
	mbean counts
Message-ID: <32854294.1192813268429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1357?page=all ]

Dimitris Andreadis closed JBAS-1357.
------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Scott M Stark)

Re-open if there is real interest for this.

> Support for massive mbean counts
> --------------------------------
>
>                 Key: JBAS-1357
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1357
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-4.0.1 Final
>            Reporter: Scott M Stark
>
> Creating thousands of mbeans seems to incur a very large overhead in memory that needs to be investigated.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:01:08 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 19 Oct 2007 13:01:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1287) Use of reserved
 word as bound variable in a pattern results as NPE
Message-ID: <13915114.1192813268603.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use of reserved word as bound variable in a pattern results as NPE
------------------------------------------------------------------

                 Key: JBRULES-1287
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1287
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, Eclipse IDE
    Affects Versions: 4.0.2
         Environment: Eclipse 3.2, Windows XP
            Reporter: Justin Wick
         Assigned To: Mark Proctor


example:

rule "This generates an NPE"
	when
		result : ReservedWordNPEFact(data < 15)
	then
		result.setData(new Integer(1));	 
end

At least in the eclipse IDE, this generates an NPE.  Change result to something like:


rule "This generates an NPE"
	when
		f: ReservedWordNPEFact(data < 15)
	then
		f.setData(new Integer(1));	 
end

and it goes away.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:03:04 2007
From: jira-events at lists.jboss.org (Justin Wick (JIRA))
Date: Fri, 19 Oct 2007 13:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1287) Use of reserved
 word as bound variable in a pattern results as NPE
In-Reply-To: <13915114.1192813268603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18926033.1192813384498.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1287?page=all ]

Justin Wick updated JBRULES-1287:
---------------------------------

    Attachment: ReservedWordNPE.zip

A sample project which generates aforementioned NPEs, designed to be easily integrated into a junit test

> Use of reserved word as bound variable in a pattern results as NPE
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1287
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1287
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE, Drl Parser/Builder
>    Affects Versions: 4.0.2
>         Environment: Eclipse 3.2, Windows XP
>            Reporter: Justin Wick
>         Assigned To: Mark Proctor
>         Attachments: ReservedWordNPE.zip
>
>
> example:
> rule "This generates an NPE"
> 	when
> 		result : ReservedWordNPEFact(data < 15)
> 	then
> 		result.setData(new Integer(1));	 
> end
> At least in the eclipse IDE, this generates an NPE.  Change result to something like:
> rule "This generates an NPE"
> 	when
> 		f: ReservedWordNPEFact(data < 15)
> 	then
> 		f.setData(new Integer(1));	 
> end
> and it goes away.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:05:05 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:05:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1768) sanitize captcha
 parameter setup
Message-ID: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>

sanitize captcha parameter setup
--------------------------------

                 Key: JBPORTAL-1768
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
             Project: JBoss Portal
          Issue Type: Patch
      Security Level: Public (Everyone can see)
    Affects Versions: 2.6.3 Final
            Reporter: Andrew Oliver
             Fix For: 2.6.3 Final
         Attachments: captcha.patch

The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:05:06 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:05:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16106534.1192813506098.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Andrew Oliver updated JBPORTAL-1768:
------------------------------------

    Attachment: captcha.patch

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:14:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 13:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
In-Reply-To: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13991648.1192814043276.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1203?page=all ]

Manik Surtani updated JBCACHE-1203:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA

> putForExternalRead replicates when INVALIDATION used
> ----------------------------------------------------
>
>                 Key: JBCACHE-1203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.
> The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:18:03 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24975348.1192814283687.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Andrew Oliver updated JBPORTAL-1768:
------------------------------------

    Attachment: captcha2.patch

both patches are needed.  this one is against the main jsf/register/register.xhtml, the other includes only files in common.  (stupid eclipse)

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:20:05 2007
From: jira-events at lists.jboss.org (Andrew Oliver (JIRA))
Date: Fri, 19 Oct 2007 13:20:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1768) sanitize
 captcha parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26749.1192814405601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Andrew Oliver reassigned JBPORTAL-1768:
---------------------------------------

    Assignee: Emanuel Muckenhuber

patch is to admin, you seem to be the admin guy.

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.3 Final
>            Reporter: Andrew Oliver
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:22:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 13:22:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28820097.1192814523809.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Thomas Heute updated JBPORTAL-1768:
-----------------------------------

    Affects Version/s: 2.6.2 Final
                           (was: 2.6.3 Final)

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.2 Final
>            Reporter: Andrew Oliver
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:22:04 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 13:22:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23679201.1192814524644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------

    Resolution: Done

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:30:14 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 13:30:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9392080.1192815014818.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Clebert Suconic updated JBMESSAGING-1096:
-----------------------------------------

    Summary: Remove references from the old Callback Manager on the documentation  (was: Document bisocket and remove references from the old Callback Manager on the documentation)

The bisocket is already documented... we just need to remove this old refeference on docs.

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:30:15 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Fri, 19 Oct 2007 13:30:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10051438.1192815015037.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Clebert Suconic closed JBMESSAGING-1096.
----------------------------------------

    Resolution: Done

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:32:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Fri, 19 Oct 2007 13:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
Message-ID: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove svn m2_repo dir or at least clean it out
-----------------------------------------------

                 Key: JBRULES-1288
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: All
    Affects Versions: 4.0.2
            Reporter: Geoffrey De Smet
         Assigned To: Geoffrey De Smet
             Fix For: 4.1.0


Both of the jars in trunk/m2_repo are obsolete:
- jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
- mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:34:06 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Fri, 19 Oct 2007 13:34:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12562613.1192815246689.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=comments#action_12383497 ] 
            
Geoffrey De Smet commented on JBRULES-1288:
-------------------------------------------

Gonna remove both jars tomorrow if no one objects.
I 'll leave the m2_repo dir intact, maybe you guys want to reuse it later.

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:55:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 13:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7802501.1192816503319.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=comments#action_12383502 ] 
            
Manik Surtani commented on JBCACHE-1202:
----------------------------------------

Added unit test o.j.c.statetransfer.DataVersionTransferTest and implemented a fix based on putting the data version in the attribs map.  

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 13:55:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 13:55:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22584512.1192816503522.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani resolved JBCACHE-1202.
------------------------------------

    Resolution: Done

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:35:07 2007
From: jira-events at lists.jboss.org (Emanuel Muckenhuber (JIRA))
Date: Fri, 19 Oct 2007 14:35:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1768) sanitize captcha
 parameter setup
In-Reply-To: <22056010.1192813505868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11933833.1192818907170.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1768?page=all ]

Emanuel Muckenhuber updated JBPORTAL-1768:
------------------------------------------

    Priority: Minor  (was: Major)

The first spot declaration of 'showCaptcha' makes indeed no sense because it's never used - most likely a relict when portletPreferences could not be resolved. The only idea behind putting the condition into the captcha.xml was to keep the registration page as simple as possible, because it should be editable by users. Anyway i will take a look at that again. Thanks

> sanitize captcha parameter setup
> --------------------------------
>
>                 Key: JBPORTAL-1768
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1768
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.2 Final
>            Reporter: Andrew Oliver
>         Assigned To: Emanuel Muckenhuber
>            Priority: Minor
>             Fix For: 2.6.3 Final
>
>         Attachments: captcha.patch, captcha2.patch
>
>
> The captcha is configured in one spot as a variable and in another spot as a preference.  This uses the preference to configure the variable and then the variable throughout.  Moreover, it seems cleaner to not have captcha.xhtml itself worrying about whether captcha is enabled for registration, rather have registration do that.  Somewhat pedantic...

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:35:07 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:35:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-79) Principal Mapping
	Modules
In-Reply-To: <7883474.1190755242268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17358867.1192818907383.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-79?page=all ]

Anil Saldhana closed SECURITY-79.
---------------------------------

    Resolution: Done

> Principal Mapping Modules
> -------------------------
>
>                 Key: SECURITY-79
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-79
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.1-BETA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1-GA
>
>
> We need Principal Mapping Modules via the Mapping Manager.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:37:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (SECURITY-32) White Paper on
	Clustered SSO
In-Reply-To: <19027403.1173286522201.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17771888.1192819023384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-32?page=all ]

Anil Saldhana reassigned SECURITY-32:
-------------------------------------

    Assignee: Marcus Moyses  (was: Sakthi Samabsivam)

> White Paper on Clustered SSO
> ----------------------------
>
>                 Key: SECURITY-32
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-32
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: White Papers
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Marcus Moyses
>             Fix For: NO_VERSION
>
>
> White paper on the Clustered SSO offering from JBoss.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn
> http://wiki.jboss.org/wiki/Wiki.jsp?page=BuddyReplicationAndClusteredSSO
> This is important because many customers are using this along with http session replication.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:39:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-84) Update
 documentation for 2.0.1-GA Release
Message-ID: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update documentation for 2.0.1-GA Release
-----------------------------------------

                 Key: SECURITY-84
                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Documentation
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-GA


Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:41:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 19 Oct 2007 14:41:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-85) Release Security
	V2.0.1-GA
Message-ID: <25608054.1192819263974.JavaMail.jira@cloud.prod.atl2.jboss.com>

Release Security V2.0.1-GA
--------------------------

                 Key: SECURITY-85
                 URL: http://jira.jboss.com/jira/browse/SECURITY-85
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: JBossSX, Security SPI
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.1-GA




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:53:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 14:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1202) State transfer
 does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8810966.1192819983664.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani reopened JBCACHE-1202:
------------------------------------

             

> State transfer does not include optimistic node's DataVersion
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:53:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 14:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1202) State transfer
 and cache loading does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29603892.1192819983824.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani updated JBCACHE-1202:
-----------------------------------

    Summary: State transfer and cache loading does not include optimistic node's DataVersion  (was: State transfer does not include optimistic node's DataVersion)

> State transfer and cache loading does not include optimistic node's DataVersion
> -------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:53:04 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Fri, 19 Oct 2007 14:53:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1202) State transfer
 and cache loading does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21605803.1192819984518.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=comments#action_12383505 ] 
            
Manik Surtani commented on JBCACHE-1202:
----------------------------------------

Moved to o.j.c.optimistic.DataVersionTransferTest and added o.j.c.optimistic.DataVersionPersistenceTest


> State transfer and cache loading does not include optimistic node's DataVersion
> -------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 14:57:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 14:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBBUILD-423) Fix microcontainer
 poms and metatdata in maven repository
In-Reply-To: <15025489.1192719903676.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11291940.1192820223382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-423?page=all ]

Paul Gier closed JBBUILD-423.
-----------------------------

    Resolution: Done

> Fix microcontainer poms and metatdata in maven repository
> ---------------------------------------------------------
>
>                 Key: JBBUILD-423
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-423
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> The 2.0.0.Beta4 release of microcontainer is missing metadata files, and the tag has the incorrect version in a couple places.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:08:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 15:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBBUILD-414) Mavenize security
	project
In-Reply-To: <22840794.1188506058257.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10170128.1192820883707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-414?page=all ]

Paul Gier reassigned JBBUILD-414:
---------------------------------

    Assignee: Paul Gier

> Mavenize security project
> -------------------------
>
>                 Key: JBBUILD-414
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-414
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The pom of the security project should be updated to fit project standards.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:10:06 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 15:10:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBBUILD-418) Figure out why
 iiop and jmx do not build from the aggregate app server build.
In-Reply-To: <31763240.1189779072625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28270930.1192821007030.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBBUILD-418?page=comments#action_12383507 ] 
            
Paul Gier commented on JBBUILD-418:
-----------------------------------

The maven issue http://jira.codehaus.org/browse/MNG-2045 has been applied, and will be released with 2.0.8.
The app server maven builds will be dependent on the 2.0.8 release of maven.

> Figure out why iiop and jmx do not build from the aggregate app server build.
> -----------------------------------------------------------------------------
>
>                 Key: JBBUILD-418
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-418
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Currently the jmx and iiop modules build fine by themselves, but do not build correctly during the aggregate build with all the modules.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:10:07 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 15:10:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBBUILD-418) Figure out why iiop
 and jmx do not build from the aggregate app server build.
In-Reply-To: <31763240.1189779072625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <746009.1192821007482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-418?page=all ]

Paul Gier closed JBBUILD-418.
-----------------------------

    Resolution: Done

When maven 2.0.8 is released, it will become a requirement for the app server builds.

> Figure out why iiop and jmx do not build from the aggregate app server build.
> -----------------------------------------------------------------------------
>
>                 Key: JBBUILD-418
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-418
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> Currently the jmx and iiop modules build fine by themselves, but do not build correctly during the aggregate build with all the modules.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:32:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 19 Oct 2007 15:32:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4889) jboss-vfs 2.0.0.beta5
Message-ID: <6891938.1192822322261.JavaMail.jira@cloud.prod.atl2.jboss.com>

jboss-vfs 2.0.0.beta5
---------------------

                 Key: JBAS-4889
                 URL: http://jira.jboss.com/jira/browse/JBAS-4889
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Kabir Khan
         Assigned To: Kabir Khan
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:32:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 19 Oct 2007 15:32:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4889) jboss-vfs 2.0.0.beta5
In-Reply-To: <6891938.1192822322261.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21218803.1192822322554.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4889?page=all ]

Kabir Khan updated JBAS-4889:
-----------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> jboss-vfs 2.0.0.beta5
> ---------------------
>
>                 Key: JBAS-4889
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4889
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:35:09 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Fri, 19 Oct 2007 15:35:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4889) jboss-vfs 2.0.0.beta5
In-Reply-To: <6891938.1192822322261.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20900959.1192822509239.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4889?page=all ]

Kabir Khan closed JBAS-4889.
----------------------------

    Resolution: Done

> jboss-vfs 2.0.0.beta5
> ---------------------
>
>                 Key: JBAS-4889
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4889
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:42:19 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 19 Oct 2007 15:42:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the
 legacy configuration that embeds xml parsing
Message-ID: <5246661.1192822939716.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12383509 ] 
            
Ron Sigal commented on JBREM-63:
--------------------------------

org.jboss.remoting.transport.remoting.Connector can now be configured by way of an org.jboss.remoting.ServerConfiguration.  ServerConfiguration holds four components:

1. transport (supplied by constructor)
2. invokerLocatorParameters:  the is a map of all parameter names and values that will go into the org.jboss.remoting.InvokerLocator
3. serverParameters: this is a map of parameter names and values that will be used by the server but will not go into the InvokerLocator
4. invocationHandlers: this is a map of invocation handlers.  The key is the subsystem, or comma separated list of subsystems.

Note that parameter values in invokerLocatorParameters override values in serverParameters, if a parameter appears in both.

ServerConfiguration may be used programmatically, but it is primarily intended to be constructed from a jboss-beans.xml file by a microcontainer and injected into a Connector.

Unit test:  org.jboss.test.remoting.transport.config.POJOConfigurationTestCase.

Waiting for cruisecontrol results.

> Get rid of the legacy configuration that embeds xml parsing
> -----------------------------------------------------------
>
>                 Key: JBREM-63
>                 URL: http://jira.jboss.com/jira/browse/JBREM-63
>             Project: JBoss Remoting
>          Issue Type: Task
>    Affects Versions: 1.0.1 beta
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:44:03 2007
From: jira-events at lists.jboss.org (krish p (JIRA))
Date: Fri, 19 Oct 2007 15:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
Message-ID: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>

Portlet disappears in IE 7.0 after it is maximized
--------------------------------------------------

                 Key: JBPORTAL-1769
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Portlet
    Affects Versions: 2.6.1 Final
         Environment: Windows XP, Internet Explorer 7.0
            Reporter: krish p
         Assigned To: Julien Viet


I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.

Essentially, this is the problem:
* Add a portlet on the page.
* Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).

After doing a fair bit of testing, I've narrowed down the test case to the following:
* This does NOT reproduce in Firefox and happens only in IE
* Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 

I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).

It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:46:34 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 19 Oct 2007 15:46:34 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3926) Move remoting
 transports out of conf/jboss-service.xml to a remoting-beans.xml
In-Reply-To: <7741264.1165442815973.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7419622.1192823194535.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3926?page=all ]

Ron Sigal updated JBAS-3926:
----------------------------

    Assignee: Ron Sigal  (was: Dimitris Andreadis)

> Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-3926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services, Remoting
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>
> We need to remove remoting transports out of conf/jboss-service.xml to a remoting-beans.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:50:03 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 19 Oct 2007 15:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3926) Move remoting
 transports out of conf/jboss-service.xml to a remoting-beans.xml
In-Reply-To: <7741264.1165442815973.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27189442.1192823403371.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3926?page=comments#action_12383510 ] 
            
Ron Sigal commented on JBAS-3926:
---------------------------------

This issue depends on JBREM-63 "Get rid of the legacy configuration that embeds xml parsing".  For JBREM-63, org.jboss.remoting.transport.Connector has been changed so that the <config> parameter used in *-service.xml files to configure a server may now be replaced by an org.jboss.remoting.ServerConfiguration object, constructed from a jboss-beans.xml file by the microcontainer.

The changes for JBREM-63 are scheduled to be released in Remoting 2.4.0.

A unit test is ready to be committed, once Remoting 2.4.0 is available.

> Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-3926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services, Remoting
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>
> We need to remove remoting transports out of conf/jboss-service.xml to a remoting-beans.xml

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 16:01:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 16:01:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4694002.1192824063337.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=all ]

Thomas Heute updated JBPORTAL-1769:
-----------------------------------

    Fix Version/s: 2.6.3 Final

> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 16:03:03 2007
From: jira-events at lists.jboss.org (krish p (JIRA))
Date: Fri, 19 Oct 2007 16:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19012294.1192824183352.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=comments#action_12383513 ] 
            
krish p commented on JBPORTAL-1769:
-----------------------------------

It is the maximize/minimize/restore event. One of them.. I wish I could have been more specific but the problem is quite intermittent and it is hard to nail down on the simplest reproducible test case..

For instance, I tried to reproduce this again, and I got a HTTP-500 error:

URL accessed: http://portal.demo.jboss.com/auth/portal/default/default/JSPPortletWindow?windowstate=normal

Error:

javax.servlet.ServletException: java.lang.NullPointerException
	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:406)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)


root cause 

java.lang.NullPointerException
	org.jboss.portal.core.impl.model.portal.PersistentPortalObjectContainer.getObjectNode(PersistentPortalObjectContainer.java:242)
	org.jboss.portal.core.impl.model.portal.AbstractPortalObjectContainer.getContext(AbstractPortalObjectContainer.java:100)
	org.jboss.portal.core.impl.model.portal.AbstractPortalObjectContainer.getContext(AbstractPortalObjectContainer.java:80)
	org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:72)
	org.jboss.portal.core.controller.Controller.handle(Controller.java:209)
	org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
	org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
	org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:380)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)



> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 15:52:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 19 Oct 2007 15:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14715052.1192823523430.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=comments#action_12383511 ] 
            
Thomas Heute commented on JBPORTAL-1769:
----------------------------------------

Which event are you talking about ?
Can you detail "The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point" ?

I cannot reproduce the problem with the info you provided


> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 18:57:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Fri, 19 Oct 2007 18:57:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBBUILD-414) Mavenize security
	project
In-Reply-To: <22840794.1188506058257.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33478366.1192834623238.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-414?page=all ]

Paul Gier closed JBBUILD-414.
-----------------------------

    Resolution: Done

Anil did most of the work mavenizing the security project.  So I just had to make a couple of minor changes.

> Mavenize security project
> -------------------------
>
>                 Key: JBBUILD-414
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-414
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - App Server
>
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> The pom of the security project should be updated to fit project standards.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 19 19:33:18 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 19 Oct 2007 19:33:18 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29942082.1192836798418.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=comments#action_12383517 ] 
            
Tim Fox commented on JBMESSAGING-1115:
--------------------------------------

How large were the messages?

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 02:48:03 2007
From: jira-events at lists.jboss.org (Stale Pedersen (JIRA))
Date: Sat, 20 Oct 2007 02:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-265) Aspectize Java array
Message-ID: <3132734.1192862883768.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-265?page=all ]

Stale Pedersen closed JBAOP-265.
--------------------------------

    Resolution: Done

committed and tested

> Aspectize Java array
> --------------------
>
>                 Key: JBAOP-265
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-265
>             Project: JBoss AOP
>          Issue Type: Feature Request
>            Reporter: Ben Wang
>         Assigned To: Stale Pedersen
>             Fix For: 2.0.0.beta2
>
>
> For AOP, we haven't dealt with Java array. Is it possible to provide interception for array? This is required if we need to instrument Java Collection, for example, since they uses array list for internal fields.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 06:03:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5717050.1192874583877.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox reopened JBMESSAGING-1099:
----------------------------------

             
I am re-opening because Clebert's fix to ConsumerAspect is wrong and breaks failover.

Try running MergeQueueTest a few times to see it fail.

The problem with the fix is that it always closes the ClientConsumer in a finally block.

For failover a MessagingNetworkFailed exception would be thrown, and failover would eventually retry after failover.

But by then the ClientConsumer had been closed.

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 06:09:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 06:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10939888.1192874943537.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                       (was: 1.4.0.SP1)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 06:36:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sat, 20 Oct 2007 06:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3389000.1192876563303.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=all ]

Geoffrey De Smet resolved JBRULES-1288.
---------------------------------------

    Resolution: Done

cleaned out

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 07:37:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 07:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6621978.1192880223321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox reopened JBMESSAGING-1096:
----------------------------------

      Assignee: Tim Fox  (was: Clebert Suconic)
             
No the bisocket is NOT already documented.

Re-opening.

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 08:21:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 08:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19304047.1192882863692.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox closed JBMESSAGING-1096.
--------------------------------

    Resolution: Done

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 08:21:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 20 Oct 2007 08:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1114) JBoss Remoting
 fails under load
In-Reply-To: <12744736.1192556526271.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30461631.1192882863865.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=all ]

Tim Fox closed JBMESSAGING-1114.
--------------------------------

    Resolution: Done

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBMESSAGING-1114
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1114
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000 
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Sat Oct 20 09:20:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 09:20:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1199) Update
 InvalidatorInterceptorTest to use Node.isValid()
In-Reply-To: <2782171.1192635603222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15690723.1192886414171.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1199?page=all ]

Manik Surtani updated JBCACHE-1199:
-----------------------------------

    Fix Version/s: 2.1.0.CR1

> Update InvalidatorInterceptorTest to use Node.isValid()
> -------------------------------------------------------
>
>                 Key: JBCACHE-1199
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node.  See the forum link.  Need to replace with a call to isValid() whenever that is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:36:07 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:36:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1289) BRMS gives
 unusable error messages when validating DSL based rules
Message-ID: <12543965.1192890967500.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS gives unusable error messages when validating DSL based rules
------------------------------------------------------------------

                 Key: JBRULES-1289
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1289
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


The error messages that are shown when you click "Validate" when editing a business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small typo and misspell the name of an attribute (a very likely thing for a BRMS user to do), and click the Validate button, the error I get back is a big stack trace starting with "java.lang.RuntimeException: SNO: Conversion failed at org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere in that stack trace is anything that gives a hint that
the error is just a typo of an attribute name.

Contrast this with the rather helpful error message I get if I make the same typo when editing a DRL rule: "Unable to create Field Extractor for 'overtimHours'". (The error is that I misspelled overtimeHours). 

The BRMS needs to give the same type of helpful error message on validation errors when editing a DSL rule.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:42:03 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1290) BRMS does not
 allow rule names to contain an apostrophe character ( ' )
Message-ID: <25881085.1192891323312.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS does not allow rule names to contain an apostrophe character ( ' )
-----------------------------------------------------------------------

                 Key: JBRULES-1290
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1290
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


Rules with apostrophe characters are rejected by the BRMS. For example the rule name "Set employee's wage" works outside BRMS, but does not work in BRMS.

If you attempt to enter a rule through the BRMS containing an apostrophe,the error stack trace says "An error occurred executing the action.
Details
com.google.gwt.user.client.rpc.SerializableException:
javax.jcr.RepositoryException: failed to resolve path Set employee's relative to /drools:repository/drools:package_area/com.example/assets: Invalid name: Set employee's wage: Invalid name: Set employee's wage at
org.drools.brms.server.ServiceImplementation.createNewRule(ServiceImplementation.java:166)..."

If you attempt to import a .drl file with a rule that has an apostrophe in the title, you'll get this error message
(including the <pre> tags): "Unable to import into the package. [<pre>Unable to process import: javax.jcr.RepositoryException: failed
to resolve path Set employee's wage relative to /drools:repository/drools:package_area/com.soi/assets: Invalid name: Set employee's  wage: Invalid name: Set employee's wage</pre>]".

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:44:03 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1291) BRMS does not
 allow import of .dslr files
Message-ID: <26814116.1192891443260.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS does not allow import of .dslr files
-----------------------------------------

                 Key: JBRULES-1291
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1291
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


The documentation (section 6.7.3) says that .drl files that use a DSL should be renamed to .dslr to work better in the IDE. The BRMS does not allow importing of .dslr files. Renaming the file back to .drl works.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 10:46:03 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Sat, 20 Oct 2007 10:46:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1292) BRMS ignores
 "initial
 description" entered when creating new "Business rule using a DSL (text
 editor)" rule
Message-ID: <7897053.1192891563924.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS ignores "initial description" entered when creating new "Business rule using a DSL (text editor)" rule
-----------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1292
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1292
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
         Assigned To: Mark Proctor


When creating a new rule asset through the BRMS using the type "Business rule using a DSL (text editor)", the initial description you put in is ignored. You always get the description "A dsl is a language mapping from a domain specific language to the rule language."

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:41:06 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 12:41:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1202) State transfer
 and cache loading does not include optimistic node's DataVersion
In-Reply-To: <25244067.1192654323377.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21251551.1192898466524.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1202?page=all ]

Manik Surtani resolved JBCACHE-1202.
------------------------------------

    Resolution: Done

> State transfer and cache loading does not include optimistic node's DataVersion
> -------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1202
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1202
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP5, 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP4, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Here's the object that's transferred; doesn't include the DataVersion
> public class NodeData implements Externalizable
> {
>    private Fqn<?> fqn = null;
>    private Map<?, ?> attrs = null;
> }
> A hack solution that wouldn't affect wire format compatibility would be to store the version in the attrs map.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:43:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 12:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1188)
 UnversionedNode.isValid - out
 of sync (deleted/remotely deleted nodes)
In-Reply-To: <1073686.1190216951047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7602284.1192898583342.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1188?page=all ]

Manik Surtani updated JBCACHE-1188:
-----------------------------------

    Fix Version/s: 2.1.0.CR1
                   2.1.0.GA
                       (was: 2.2.0.GA)
         Assignee: Manik Surtani  (was: Mircea Markus)

> UnversionedNode.isValid - out of sync (deleted/remotely deleted nodes)
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1188
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1188
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>         Environment: all
>            Reporter: Mircea Markus
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> considering the scenario:
> thread1: 
> node = cache.get("a/b/c");
> thread2(possibly running on another node/JVM):
> cache.remove("a/b/c");
> thread1: 
> node.getAttribute("attr1");//at this point the node is not longer in the cache. we should allow user to check this through isValid
> node.getAttribute("attr2");

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:47:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 12:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1198)
 putForExternalRead not silent on remote node
In-Reply-To: <22737059.1192591803386.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23708711.1192898823482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1198?page=all ]

Manik Surtani resolved JBCACHE-1198.
------------------------------------

    Resolution: Done

> putForExternalRead not silent on remote node
> --------------------------------------------
>
>                 Key: JBCACHE-1198
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1198
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> Seeing WARN logging like this when using PFER with a replicating cache:
> 22:16:37,931  WARN pessimistic-shared:2839 - replication failure with method_call MethodName: _putForExternalRead; MethodIdInteger: 45; Args: (null, /test/com/foo/test/ENTITY/KEY, item, VALUE1) exception
> org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/test/com/foo/test/ENTITY/KEY, caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock=write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:598)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:412)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:348)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:185)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:299)
> 	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
> 	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3958)
> 	at org.jboss.cache.CacheImpl._replicate(CacheImpl.java:2826)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330)
> 	at org.jboss.cache.marshall.InactiveRegionAwareRpcDispatcher.handle(InactiveRegionAwareRpcDispatcher.java:77)
> 	at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:624)
> 	at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:533)
> 	at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:365)
> 	at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:744)
> 	at org.jgroups.JChannel.up(JChannel.java:1137)
> 	at org.jgroups.mux.Multiplexer$Task.run(Multiplexer.java:999)
> 	at org.jgroups.mux.Multiplexer$ExecuteTask.run(Multiplexer.java:1023)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.cache.lock.TimeoutException: write lock for /test/com/foo/test/ENTITY/KEY could not be acquired after 0 ms. Locks: Read lock owners: []
> Write lock owner: GlobalTransaction:<192.168.1.145:35562>:1
>  (caller=Thread[Multiplexer-2,5,MultiplexerThreads], lock info: write owner=GlobalTransaction:<192.168.1.145:35562>:1 (activeReaders=0, activeWriter=Thread[Thread-7,5,main], waitingReaders=1, waitingWriters=0, waitingUpgrader=0))
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:244)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
> 	... 33 more
> Issue seems to be that the logic in CacheImpl.putForExternalRead that makes the call a no-op if the node exists and sets the failSilently option otherwise never gets executed on the remote node.  Instead the call gets handled by _replicate which just passes the MethodCall into the interceptor chain without setting any options.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 12:51:03 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Sat, 20 Oct 2007 12:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27928854.1192899063310.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Shigeru Chiba resolved JASSIST-37.
----------------------------------

    Resolution: Done

I have implemented initializers for boolean, byte, short, char.

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 13:04:03 2007
From: jira-events at lists.jboss.org (Shigeru Chiba (JIRA))
Date: Sat, 20 Oct 2007 13:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JASSIST-37)
 CtField.getConstantValue() for just added fileds
In-Reply-To: <23682215.1192135563513.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25850183.1192899843299.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JASSIST-37?page=all ]

Shigeru Chiba closed JASSIST-37.
--------------------------------


and the initializer for float.

> CtField.getConstantValue() for just added fileds
> ------------------------------------------------
>
>                 Key: JASSIST-37
>                 URL: http://jira.jboss.com/jira/browse/JASSIST-37
>             Project: Javassist
>          Issue Type: Bug
>         Environment: Java 5, javassist 3.4.ga or  javassist 3.6.ga
>            Reporter: Vlad Skarzhevskyy
>         Assigned To: Shigeru Chiba
>         Attachments: AChildClass-generated.class
>
>
> I'm creating tool to verify Java API compatibility
> I'm converting  class files to XML and then XML to classes creating CtClass objects that have empty implementation.
> Then target is to compare new lib version to API described in XML.
> project site: http://pyx4me.com/snapshot/jour/signature.html
> This is what causing the problem:
> CtField field =  new CtField(CtClass.longType, "test", klass);
> CtField.Initializer initializer = CtField.Initializer.constant(1);
> klass.addField(field, initializer);
> // Then later when
> Object value = field.getConstantValue();
> //value is always null and can't be used for comparison.
> when I  call klass.writeFile(); The .class is created correctly and when decompiled I see that int filed is properly initialized .
> BUT When javassist  loads again the generated classes field.getConstantValue(); still null!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 13:16:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Sat, 20 Oct 2007 13:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23550129.1192900563609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Manik Surtani updated JBCACHE-1201:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097198
               Complexity: High

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 15:30:03 2007
From: jira-events at lists.jboss.org (Stan Silvert (JIRA))
Date: Sat, 20 Oct 2007 15:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4130) Simple HelloWorld
 JSF 1.2 application does not work
In-Reply-To: <28586848.1172070275576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31381363.1192908603339.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4130?page=comments#action_12383554 ] 
            
Stan Silvert commented on JBAS-4130:
------------------------------------

I tried creating a simple JSF app with visual web pack and I got this error:

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed
 to resolve schema nsURI=http://java.sun.com/JSF/Configuration location=null
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:203)

Is that the first one you saw?  Exactly which file did you put in jboss.jar to get past the problem?

It is strange that you would have a problem with that schema definition in your managed-beans.xml.  The faces-config.xml in the hellojsf-correted.war at the bottom of this page uses the exact same definition and it deploys without errors:
http://wiki.jboss.org/wiki/Wiki.jsp?page=HelloJSF

Also, I noticed that visual web pack creates a J2EE 1.4 JSF application.  It includes the jsf-impl.jar, jsf-api.jar, and jstl.jar.  You don't want to have these in your WAR on JBoss 5 because they might interfere with the versions already present in the JBoss 5 distribution.

Stan

> Simple HelloWorld JSF 1.2 application does not work
> ---------------------------------------------------
>
>                 Key: JBAS-4130
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4130
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JSF
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: Windows XP,  Suse 10.2
>            Reporter: sedat ciftci
>         Assigned To: Stan Silvert
>
>  I have faced with a problem while deploying my JSF 1.2 web application (sun impl) ( I build with Netbeans 5.5 Visual Web pack) to JBoss5 Beta. It works with Glassfish. In order to find the problem, I make a simple Hello world web application and try to deploy it to JBoss5Beta. However, I get the same exception.
> The first exception that I overcome is related with web-facesconfig_1_2.xsd. JBoss says that it can not resolve this schema. I solve this problem by putting this file into the jboss.jar/schema.
> The second exception that I cannot solve is although my projects managed-beans.xml file is well formed, JBoss throws such an exception:
> org.jboss.deployers.spi.DeploymentException: The xml JBoss5Ex.war/WEB-INF/managed-beans.xml is not well formed!
> at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:94)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:173)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88)
> at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59)
> at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
> at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
> at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
> at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
> at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
> at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:508)
> at java.lang.Thread.run(Thread.java:595)
> Note that JBoss5Ex.war is my web application. 
>  Here is the content of my managed-beans.xml file (starting after the #'s line):
> ######################################
> <?xml version="1.0" encoding="UTF-8"?>
> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd">
> <managed-bean>
> <managed-bean-name>SessionBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.SessionBean1</managed-bean-class>
> <managed-bean-scope>session</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>Page1</managed-bean-name>
> <managed-bean-class>jboss5ex.Page1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>ApplicationBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.ApplicationBean1</managed-bean-class>
> <managed-bean-scope>application</managed-bean-scope>
> </managed-bean>
> <managed-bean>
> <managed-bean-name>RequestBean1</managed-bean-name>
> <managed-bean-class>jboss5ex.RequestBean1</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> </faces-config>
> #################################################

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 20 17:38:09 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Sat, 20 Oct 2007 17:38:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1230) Not able to run
 drools if
 core-3.2.3.v_686_R32x.jar is not specified in the classpath
In-Reply-To: <27431141.1190987681381.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19450071.1192916289129.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1230?page=comments#action_12383558 ] 
            
Mark Proctor commented on JBRULES-1230:
---------------------------------------

I assume this jira is for when you are compiling and all rules are using he MVEL dialect, but it's still complaining about janino or jdt? If janino is configured it should definitely not still require jdt core.

> Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath
> -------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1230
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1230
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions:  4.0.0.GA
>         Environment: Windows XP, Dell Optiplex GX 270
>            Reporter: Krishnan Sivaramakrishna Iyer
>         Assigned To: Mark Proctor
>            Priority: Blocker
>
> hi all,
> In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies
> documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_DEPENDENCIES.txt
> , it seems I am in the compiler option
> The only jars I am including are as follows :-
> drools-compiler-4.0.0.jar
> drools-core-4.0.0.jar
> drools-decisiontables-4.0.0.jar
> drools-jsr94-4.0.0.jar
> antlr-runtime-3.0.jar
> mvel14-1.2rc1.jar
> core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I
> don't specify this, it does not work ?.]
> I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also
> expects the core to be included. Any help is appreciated.
> TIA,
> Krishnan. 
> Comments from Edson Tirelli 
> Krishnan,
>     You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix.
>     []s
>     Edson

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 04:18:08 2007
From: jira-events at lists.jboss.org (Johannes Fiala (JIRA))
Date: Sun, 21 Oct 2007 04:18:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1759) FastURLDecoder
 with
 malformed input %FC throws an ArrayIndexOutOfBoundsException instead of
 throwing MalformedInputException
In-Reply-To: <7268675.1192733103374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5109102.1192954688224.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1759?page=comments#action_12383571 ] 
            
Johannes Fiala commented on JBPORTAL-1759:
------------------------------------------

Yes, exactly - I'm issuing a GET-request (manually by editing the url address input of the browser). In this case browsers seem to neglect the correct utf-8 encoding of the url before doing the url encoding).

> FastURLDecoder with malformed input %FC throws an ArrayIndexOutOfBoundsException instead of throwing MalformedInputException
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1759
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1759
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Server
>    Affects Versions: 2.6.2 Final
>         Environment: Jboss AS 4.0.5 GA on JDK 1.4.2_14
> Tested using the browsers: Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0
>            Reporter: Johannes Fiala
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> Entering urls containing German Umlaute (e.g. ? = %FC) throws an ArrayIndexOutOfBoundsException in FastURLDecoder.
> E.g. Entering "http://localhost:8080/portal/?test=%FC"
> throws the following exception:
> HTTP Status 500 -
> type Exception report
> message description The server encountered an internal error () that prevented it from fulfilling this request.
> exception java.lang.ArrayIndexOutOfBoundsException: 4
> 	org.jboss.portal.common.text.FastURLDecoder.encodeNoCheck(FastURLDecoder.java:268)
> 	org.jboss.portal.common.text.FastURLDecoder.encode(FastURLDecoder.java:226)
> 	org.jboss.portal.common.http.QueryStringParser.parseQueryString(QueryStringParser.java:233)
> 	org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:291)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> Prior versions of Jboss Portal (2.2.1 SP3, 2.6.1 GA) handle this correctly, so this bug is newly introduced with Jboss Portal 2.6.2 GA.
> The issue does not seem to be browser specific, as it occurs with Mozilla Firefox 2.0.0.7 and MS Internet Explorer 6.0.

-- 
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

       



From jira-events at lists.jboss.org  Sun Oct 21 09:36:03 2007
From: jira-events at lists.jboss.org (Wolfgang Knauf (JIRA))
Date: Sun, 21 Oct 2007 09:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4361)
 java.util.logging.FileHandler.formatter cannot be changed to
 java.util.logging.SimpleFormatter
In-Reply-To: <24133361.1177358310492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10845202.1192973763667.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4361?page=all ]

Wolfgang Knauf closed JBAS-4361.
--------------------------------

    Resolution: Rejected

Yes, you are right, there was a space. I'm ashamed of not seeing it !

> java.util.logging.FileHandler.formatter cannot be changed to java.util.logging.SimpleFormatter
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4361
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4361
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.0.CR2
>         Environment: JDK is 1.5.0_11-b03
>            Reporter: Wolfgang Knauf
>         Assigned To: Scott M Stark
>            Priority: Minor
>
> I tried to create a plain text log output with this logging.properties file:
> handlers= java.util.logging.FileHandler, java.util.logging.ConsoleHandler
> .level= INFO
> java.util.logging.FileHandler.pattern = c:/temp/logfile.log 
> java.util.logging.FileHandler.level = INFO
> java.util.logging.FileHandler.limit = 50000
> java.util.logging.FileHandler.count = 1
> java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter 
> java.util.logging.ConsoleHandler.level = INFO
> java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
> I startup the server with this commandline:
> run.bat -c default -Djava.util.logging.config.file=c:/temp/logging.properties
> The log file is placed in c:\temp\logfile.log and contains my output, but it is in XML, not in Simple format. Console output is in SimpleFormat as expected.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 10:00:09 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Sun, 21 Oct 2007 10:00:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30844363.1192975209028.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383581 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

I did have juddi-service.sar deployed in the earlier runs.
The following tests pass when juddi-service.sar is deployed under the DEFAULT config in an EXPLODED form ONLY, which is the way i have configured hudson now.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBossWS-2.0.1.SP2-testsuite-AS4.2.x/
org.jboss.test.ws.jaxws.samples.jaxr.scout.publish.JaxrDeleteOrganizationTestCase
org.jboss.test.ws.jaxws.samples.jaxr.scout.publish.JaxrSaveOrganizationTestCase
org.jboss.test.ws.jaxws.samples.jaxr.scout.query.JaxrBusinessQueryTestCase

In the earlier runs the tests failed, when i ran against the ALL config with juddi-service deployed, because the tests were still looking for juddi-service under the DEFAULT config.

When i ran the tests using the DEFAULT config with juddi-service.sar deployed in an UNEXPLODED form the tests still failed because it could not find the scout.jar which was inside the sar.

In both the cases the error was java.lang.ClassNotFoundException: org.apache.ws.scout.registry.ConnectionFactoryImpl

I'm not sure if this is a bad test or potential bug, Thomas could you take a look?
I would like to change the hudson job to run in one of the last 2 ways mentioned above so no bugs are missed.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 11:35:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Sun, 21 Oct 2007 11:35:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4945690.1192980903327.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383592 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

Shouldn't the tests be such so they run on a out-of-the box AS? Or if they require a different configuration, create it, as part of the test?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 12:48:04 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 21 Oct 2007 12:48:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14785160.1192985284434.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=all ]

Geoffrey De Smet reopened JBRULES-1288:
---------------------------------------

             
it broke the build:
https://hudson.jboss.org/hudson/job/drools/919/testReport/

mvel is not mvel14, apparently it's a different flavor of the same version - this is probably the problem

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 21 15:09:03 2007
From: jira-events at lists.jboss.org (Geoffrey De Smet (JIRA))
Date: Sun, 21 Oct 2007 15:09:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1288) Remove svn
 m2_repo dir or at least clean it out
In-Reply-To: <28174419.1192815123545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1541355.1192993743424.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1288?page=all ]

Geoffrey De Smet resolved JBRULES-1288.
---------------------------------------

    Resolution: Partially Completed

Revert the changes for mvel, as mvel != mvel14.

> Remove svn m2_repo dir or at least clean it out
> -----------------------------------------------
>
>                 Key: JBRULES-1288
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1288
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions: 4.0.2
>            Reporter: Geoffrey De Smet
>         Assigned To: Geoffrey De Smet
>             Fix For: 4.1.0
>
>
> Both of the jars in trunk/m2_repo are obsolete:
> - jdt is available in the jboss repo: http://repository.jboss.com/maven2/org/eclipse/jdt/core/3.2.3.v_686_R32x/
> - mvel is available in the jboss repo, but not under org.mvel:mvel but instead org.mvel:mvel14

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 00:34:03 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Mon, 22 Oct 2007 00:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (BPEL-281) apache ant support
Message-ID: <19912563.1193027643410.JavaMail.jira@cloud.prod.atl2.jboss.com>

apache ant support
------------------

                 Key: BPEL-281
                 URL: http://jira.jboss.com/jira/browse/BPEL-281
             Project: JBoss jBPM BPEL
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Engine
            Reporter: Alejandro Guizar
         Assigned To: Alejandro Guizar
             Fix For: jBPM BPEL 1.1 GA


The web console provides a user interface to perform the following tasks.

1. Database administration
2. Process deployment
3. Partner registration

For integration purposes, the ability to invoke the above tasks from an Ant script is highly desirable.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:08:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1116) Fail-over
 does not complete if a node different from the "active" one fails
Message-ID: <10435351.1193029683486.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fail-over does not complete if a node different from the "active" one fails
---------------------------------------------------------------------------

                 Key: JBMESSAGING-1116
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Critical
             Fix For: 1.4.0.SP1


This is how to replicate it:

- Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A
- Start consuming concurrently using 50 parallel consumers over a connection to node A
- Kill node B

The consumption rate drop to 0 and never recovers.
Trying to close the connection on the client-side never completes.
Trying to shut down node A fails, need to eventually kill it.



-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:30:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26204852.1193031003430.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1109:
-----------------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)

I have not seen this anymore with r3237, while testing it by sending/receiving in parallel over 50-100 sessions. Probably safe to close. I will re-open if I see it again.

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:30:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6275279.1193031003696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1110:
-----------------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: Unscheduled)

I have not seen this anymore with r3237, while testing it by sending/receiving in parallel over 50-100 sessions. Probably safe to close. I will re-open if I see it again.

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:32:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27563489.1193031123444.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1112:
-----------------------------------------


I have not seen this anymore with r3237, while testing it by sending/receiving in parallel over 50-100 sessions. Probably safe to close. I will re-open if I see it again.

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>         Attachments: messkit.zip
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 01:32:03 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Mon, 22 Oct 2007 01:32:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1116) Consuming
 client grinds to
 a halt if a node different from the "active" one fails
In-Reply-To: <10435351.1193029683486.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10348228.1193031123653.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1116?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1116:
-----------------------------------------

    Summary: Consuming client grinds to a halt if a node different from the "active" one fails  (was: Fail-over does not complete if a node different from the "active" one fails)

> Consuming client grinds to a halt if a node different from the "active" one fails
> ---------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1116
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> This is how to replicate it:
> - Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A
> - Start consuming concurrently using 50 parallel consumers over a connection to node A
> - Kill node B
> The consumption rate drop to 0 and never recovers.
> Trying to close the connection on the client-side never completes.
> Trying to shut down node A fails, need to eventually kill it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:27:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1283) Unable to
 serialize rule base ( NotSerializableException:
 org.drools.base.FireAllRulesRuleBaseUpdateListener)
In-Reply-To: <638007.1192703463854.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22677479.1193034423320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1283?page=all ]

Mark Proctor closed JBRULES-1283.
---------------------------------

    Resolution: Done

> Unable to serialize rule base ( NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1283
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1283
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.2
>            Reporter: Jiri Pechanec
>         Assigned To: Mark Proctor
>            Priority: Minor
>             Fix For: 4.0.2_SOA_4.2-CP01, 4.0.3, 4.1.0
>
>
> When I am trying to serialize rulebase, I am getting the exception
> Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391)
>         at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606)
>         at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180)
>         at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147)
>         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:44:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:44:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1282) Problems uploading
 models etc. into the BRMS
In-Reply-To: <28056430.1192666083311.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8013541.1193035443257.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1282?page=all ]

Mark Proctor closed JBRULES-1282.
---------------------------------

    Resolution: Done

> Problems uploading models etc. into the BRMS
> --------------------------------------------
>
>                 Key: JBRULES-1282
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1282
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.0.2_SOA_4.2-CP01, 4.0.3, 4.1.0
>
>         Attachments: cumulative_patch.patch
>
>
> There are 2 problems (this shows up mainly in WebKIT and safary browsers): 
> 1) the return content type for a successfull upload is text/plain when it should be test/html
> 2) if any form fields are not visible, they will not be submitted to the server. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:48:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1230) Not able to run
 drools if
 core-3.2.3.v_686_R32x.jar is not specified in the classpath
In-Reply-To: <27431141.1190987681381.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9747500.1193035683517.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1230?page=comments#action_12383643 ] 
            
Mark Proctor commented on JBRULES-1230:
---------------------------------------

btw you know you actually need to remove the java dialect to avoid this? Otherwise whether you use the java dialect in a rule or not, the java dialect plugin is initialised and thus the need for the dependency.

> Not able to run drools if core-3.2.3.v_686_R32x.jar is not specified in the classpath
> -------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1230
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1230
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: All
>    Affects Versions:  4.0.0.GA
>         Environment: Windows XP, Dell Optiplex GX 270
>            Reporter: Krishnan Sivaramakrishna Iyer
>         Assigned To: Mark Proctor
>            Priority: Blocker
>
> hi all,
> In my application, I use simple drl file based rules and it is not a J2EE application. Based on the dependencies
> documentation http://anonsvn.labs.jboss.com/labs/jbossrules/tags/4.0.1.14754GA/README_DEPENDENCIES.txt
> , it seems I am in the compiler option
> The only jars I am including are as follows :-
> drools-compiler-4.0.0.jar
> drools-core-4.0.0.jar
> drools-decisiontables-4.0.0.jar
> drools-jsr94-4.0.0.jar
> antlr-runtime-3.0.jar
> mvel14-1.2rc1.jar
> core-3.2.3.v_686_R32x.jar [Can anyone explain why I need this, the documentation seems like this is optional, but when I
> don't specify this, it does not work ?.]
> I also tried not including the core but including the janino library and specifying the janino compiler at run time and that also
> expects the core to be included. Any help is appreciated.
> TIA,
> Krishnan. 
> Comments from Edson Tirelli 
> Krishnan,
>     You should not need decision tables and jsr94 jars if you are not using such feature. Regarding the compiler, you must use either core (jdt) jar or Janino jar... I'm not aware of any hard dependency on core itself... if it exists, please open a jira for us to fix.
>     []s
>     Edson

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 02:50:14 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 02:50:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16016287.1193035814662.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12383644 ] 
            
Mark Proctor commented on JBRULES-1273:
---------------------------------------

we cannot progress this without the code being attached to the jira.

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Mark Proctor
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 03:31:03 2007
From: jira-events at lists.jboss.org (David Roberts (JIRA))
Date: Mon, 22 Oct 2007 03:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-37) include snap to grid
In-Reply-To: <30030403.1168963978540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3323630.1193038263980.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-37?page=comments#action_12383648 ] 
            
David Roberts commented on GPD-37:
----------------------------------

I would love the designer to be able to simply straighten transition lines with the click of a mouse. I spend so much time trying to straighten transition lines before I deploy, and sometimes it takes me 5 minutes just to get one line to look straight. And when you have about 20 lines to neaten up, it takes forever. Then any changes to the flow, and you have to do it again. Trying to move a line ever so slightly to straighten it is near impossible, you have to move it quite a distance first, then drag it back and hope it is straight. Perhaps just right clicking on a transition line, and selecting "straighten" or "snap to grid" would save many hours of frustration for many people im sure.

> include snap to grid
> --------------------
>
>                 Key: GPD-37
>                 URL: http://jira.jboss.com/jira/browse/GPD-37
>             Project: JBoss jBPM GPD
>          Issue Type: Task
>          Components: jpdl
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.2.0.GA
>
>
> While designing processes, it would be a lot easier if there is some kind of 'snap to grid'. You can then have easier manual allignment etc. Besides that, the images look better
> - transitions should snap to the grid to
> - transitions should be perpendicular at least if there are more than three points in the line 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 04:36:03 2007
From: jira-events at lists.jboss.org (Rainer Langbehn (JIRA))
Date: Mon, 22 Oct 2007 04:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27790668.1193042163548.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12383653 ] 
            
Rainer Langbehn commented on JBRULES-1273:
------------------------------------------

Hi Mark,

some refactoring was necessary and I prepared some examples. I will attach the code shortly.

Bye

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Mark Proctor
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:03:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 06:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <293608.1193047383385.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis updated JBAS-4811:
-------------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
                       (was: JBossAS-4.2.3.GA)

Setting release version back to 2.2.2.GA

I've also recreated the tag:
https://svn.jboss.org/repos/jbossas/tags/JBoss_4_2_2_GA/

All the testsuites pass, as far as I can see.

Rajesh, can we release today (Oct/22nd) ?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:16:03 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 06:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4832) TECH REVIEW:
 Getting Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17896578.1193048163399.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4832?page=comments#action_12383656 ] 
            
Luc Texier commented on JBAS-4832:
----------------------------------

What does "Out of Date" mean for this task?

Clearly this document requires some work although it should be included in the installation guide. Installing a datasource in JBossAS is a typical task

> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:50:03 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 06:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33255918.1193050203327.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12383660 ] 
            
Luc Texier commented on JBAS-4819:
----------------------------------

The JBoss Support Team will review these documents and make the appropriate changes accordingly



> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:52:03 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 06:52:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4832) TECH REVIEW:
 Getting Started Guide - Chapter 8. Using other Databases
In-Reply-To: <23176146.1192165535925.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9937495.1193050323350.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4832?page=comments#action_12383661 ] 
            
Luc Texier commented on JBAS-4832:
----------------------------------

Oh I see, this has been moved to Chapter 6. Please discard my last comment.


> TECH REVIEW: Getting Started Guide - Chapter 8. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4832
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4832
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-8.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 06:54:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 06:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30826986.1193050443417.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12383662 ] 
            
Dimitris Andreadis commented on JBAS-4819:
------------------------------------------

Luc, this is fantastic news :-)

> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 07:58:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 07:58:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4890) EJBAccessException:
 Caller unauthorized
Message-ID: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJBAccessException: Caller unauthorized
---------------------------------------

                 Key: JBAS-4890
                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Anil Saldhana




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 07:59:26 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 07:59:26 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4890) EJBAccessException:
 Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29035286.1193054366260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4890?page=all ]

Thomas Diesler updated JBAS-4890:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED

13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.ejb.EJBAccessException: Caller unauthorized
        at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
        at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
        at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)



> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:03:03 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Mon, 22 Oct 2007 08:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1022) 3.2.1 Admin Console:
 Any user sees all users tasks
In-Reply-To: <6696155.1184871647115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25666160.1193054583522.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1022?page=all ]

Ronald van Kuijk updated JBPM-1022:
-----------------------------------

        Fix Version/s: jBPM jPDL 3.2.3
    Affects Version/s: jBPM jPDL 3.2.2

more and more people have a 'problem' with this. Although it is currently as designed (at least intended by the person who created the console) I think the term 'bug' is correct, since it is totally unexpected behaviour by lots of people and  therefore  I put 3.2.3 as a 'fix version' . Any work on this being done?

> 3.2.1 Admin Console: Any user sees all users tasks 
> ---------------------------------------------------
>
>                 Key: JBPM-1022
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1022
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions:  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>            Reporter: Burr Sutter
>         Assigned To: Tom Baeyens
>            Priority: Blocker
>             Fix For: jBPM jPDL 3.2.3
>
>
> In the current Admin Console, any given user will see all other users tasks.  Plus a user can "take" another person's assigned tasks even when they are not an "administrator".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:05:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 08:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4890)
 EJBAccessException: Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9056083.1193054703338.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4890?page=comments#action_12383667 ] 
            
Thomas Diesler commented on JBAS-4890:
--------------------------------------

The authorization comming from tomcat seems to be ok

Subject:
	Principal: kermit
	Principal: Roles(members:friend)


> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:13:03 2007
From: jira-events at lists.jboss.org (Burr Sutter (JIRA))
Date: Mon, 22 Oct 2007 08:13:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin
 Console: Any user sees all users tasks
In-Reply-To: <6696155.1184871647115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20034816.1193055183403.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12383669 ] 
            
Burr Sutter commented on JBPM-1022:
-----------------------------------

Do you believe the jBPM userbase considers this console to be something they can deploy into a production setting? Or is it still considered to be a sample/demo tool for interacting with quickly prototyped process definitions?




> 3.2.1 Admin Console: Any user sees all users tasks 
> ---------------------------------------------------
>
>                 Key: JBPM-1022
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1022
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions:  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>            Reporter: Burr Sutter
>         Assigned To: Tom Baeyens
>            Priority: Blocker
>             Fix For: jBPM jPDL 3.2.3
>
>
> In the current Admin Console, any given user will see all other users tasks.  Plus a user can "take" another person's assigned tasks even when they are not an "administrator".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:26:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 22 Oct 2007 08:26:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9255070.1193055963357.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383670 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

I am waiting on Thomas's comment on the above. The way we are running the JBossWS testsuite could be hiding a potential bug.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:45:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 22 Oct 2007 08:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1110) Client
 incorrectly initiates client-side fail over on high concurrency
In-Reply-To: <8765085.1192324928380.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32062198.1193057103468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Tim Fox closed JBMESSAGING-1110.
--------------------------------

    Resolution: Done

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:45:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 22 Oct 2007 08:45:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1112) Consumption
 with highly concurrent clients lock a JBM server node.
In-Reply-To: <8687992.1192335072684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23947477.1193057103825.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1112?page=all ]

Tim Fox closed JBMESSAGING-1112.
--------------------------------

    Resolution: Done

> Consumption with highly concurrent clients lock a JBM server node.
> ------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1112
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1112
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>         Attachments: messkit.zip
>
>
> The log of the experiment. 
> * Empty database
> mysql> CONNECT ovidiu
> Connection id:    5288
> Current database: ovidiu
> mysql> SHOW TABLES;
> Empty set (0.00 sec)
> mysql> 
> * Both cluster nodes down.
> * Start node 39 
> 2007-10-13 20:08:19,259 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 23s:774ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      39 | bounceQueue              | queue.bounceQueue              | NULL     |          7 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 17 rows in set (0.00 sec)
> * Start node 38
> 2007-10-13 20:11:58,280 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 27s:214ms
> mysql> SELECT * FROM JBM_MSG_REF;
> Empty set (0.00 sec)
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Make sure I look up a clustered but non load-balanced connection factory from node 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[1542500044, ID=t2-w06lzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Sending 50,000 10K persistent text messages to "ovidiu" on node 39.
> ofeodorov at yamato$ mess -stat send -size 10240 50000
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> sent 38 message(s) with a rate of       37.9 messages/sec,      38 message(s) sent so far
> sent 32 message(s) with a rate of       32.0 messages/sec,      70 message(s) sent so far
> sent 33 message(s) with a rate of       33.0 messages/sec,      103 message(s) sent so far
> .....
> sent 58 message(s) with a rate of       58.0 messages/sec,      49907 message(s) sent so far
> sent 41 message(s) with a rate of       41.0 messages/sec,      49948 message(s) sent so far
> 50000 message(s) sent non-transactionally at a rate of 59.1 messages/sec
> closing connection JBossConnection->ConnectionDelegate[1839586123, ID=03-t8gmzq7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> * Database content after send:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             50000 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |               0 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 0;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |          0 |           NULL | C     | 39070331482505216 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |          0 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Receiving on 50 concurrent threads, from node 39
> ofeodorov at yamato$ mess -stat -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer43 starting to consume, 1 active consumers ...
> Consumer06 starting to consume, 2 active consumers ...
> Consumer38 starting to consume, 3 active consumers ...
> Consumer13 starting to consume, 4 active consumers ...
> Consumer37 starting to consume, 5 active consumers ...
> Consumer10 starting to consume, 6 active consumers ...
> Consumer11 starting to consume, 7 active consumers ...
> Consumer25 starting to consume, 8 active consumers ...
> Consumer12 starting to consume, 9 active consumers ...
> Consumer04 starting to consume, 10 active consumers ...
> Consumer48 starting to consume, 11 active consumers ...
> Consumer32 starting to consume, 12 active consumers ...
> Consumer40 starting to consume, 13 active consumers ...
> Consumer39 starting to consume, 14 active consumers ...
> Consumer05 starting to consume, 15 active consumers ...
> Consumer09 starting to consume, 16 active consumers ...
> Consumer03 starting to consume, 17 active consumers ...
> Consumer41 starting to consume, 18 active consumers ...
> Consumer19 starting to consume, 19 active consumers ...
> Consumer07 starting to consume, 20 active consumers ...
> Consumer22 starting to consume, 21 active consumers ...
> Consumer36 starting to consume, 22 active consumers ...
> Consumer01 starting to consume, 23 active consumers ...
> Consumer46 starting to consume, 24 active consumers ...
> Consumer16 starting to consume, 25 active consumers ...
> Consumer18 starting to consume, 26 active consumers ...
> Consumer23 starting to consume, 28 active consumers ...
> Consumer33 starting to consume, 27 active consumers ...
> Consumer02 starting to consume, 29 active consumers ...
> Consumer00 starting to consume, 30 active consumers ...
> Consumer17 starting to consume, 31 active consumers ...
> Consumer15 starting to consume, 32 active consumers ...
> Consumer47 starting to consume, 33 active consumers ...
> Consumer31 starting to consume, 34 active consumers ...
> Consumer27 starting to consume, 35 active consumers ...
> Consumer49 starting to consume, 36 active consumers ...
> Consumer44 starting to consume, 37 active consumers ...
> Consumer26 starting to consume, 38 active consumers ...
> Consumer24 starting to consume, 39 active consumers ...
> Consumer42 starting to consume, 40 active consumers ...
> Consumer28 starting to consume, 41 active consumers ...
> Consumer20 starting to consume, 42 active consumers ...
> Consumer29 starting to consume, 43 active consumers ...
> Consumer35 starting to consume, 44 active consumers ...
> Consumer45 starting to consume, 45 active consumers ...
> Consumer30 starting to consume, 47 active consumers ...
> Consumer08 starting to consume, 46 active consumers ...
> received 240 message(s) with a rate of  239.3 messages/sec,     240 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       240 message(s) received so far
> received 1378 message(s) with a rate of 1,378.0 messages/sec,   1618 message(s) received so far
> received 451 message(s) with a rate of  451.0 messages/sec,     2069 message(s) received so far
> received 61 message(s) with a rate of   61.0 messages/sec,      2130 message(s) received so far
> received 348 message(s) with a rate of  348.0 messages/sec,     2478 message(s) received so far
> received 62 message(s) with a rate of   62.0 messages/sec,      2540 message(s) received so far
> received 958 message(s) with a rate of  957.0 messages/sec,     3498 message(s) received so far
> received 88 message(s) with a rate of   88.2 messages/sec,      3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       3586 message(s) received so far
> received 312 message(s) with a rate of  312.3 messages/sec,     3898 message(s) received so far
> received 681 message(s) with a rate of  681.0 messages/sec,     4579 message(s) received so far
> received 273 message(s) with a rate of  273.3 messages/sec,     4852 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4852 message(s) received so far
> received 2 message(s) with a rate of    2.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       4854 message(s) received so far
> received 153 message(s) with a rate of  153.0 messages/sec,     5007 message(s) received so far
> received 1126 message(s) with a rate of 1,124.9 messages/sec,   6133 message(s) received so far
> received 864 message(s) with a rate of  864.0 messages/sec,     6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       6997 message(s) received so far
> received 42 message(s) with a rate of   42.0 messages/sec,      7039 message(s) received so far
> received 441 message(s) with a rate of  441.4 messages/sec,     7480 message(s) received so far
> received 1803 message(s) with a rate of 1,803.0 messages/sec,   9283 message(s) received so far
> received 505 message(s) with a rate of  505.0 messages/sec,     9788 message(s) received so far
> received 974 message(s) with a rate of  975.0 messages/sec,     10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       10762 message(s) received so far
> received 597 message(s) with a rate of  597.6 messages/sec,     11359 message(s) received so far
> received 447 message(s) with a rate of  447.4 messages/sec,     11806 message(s) received so far
> received 783 message(s) with a rate of  783.0 messages/sec,     12589 message(s) received so far
> received 262 message(s) with a rate of  261.7 messages/sec,     12851 message(s) received so far
> received 267 message(s) with a rate of  267.0 messages/sec,     13118 message(s) received so far
> received 293 message(s) with a rate of  293.0 messages/sec,     13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13411 message(s) received so far
> received 197 message(s) with a rate of  196.8 messages/sec,     13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       13608 message(s) received so far
> received 201 message(s) with a rate of  200.6 messages/sec,     13809 message(s) received so far
> received 757 message(s) with a rate of  757.8 messages/sec,     14566 message(s) received so far
> received 580 message(s) with a rate of  580.0 messages/sec,     15146 message(s) received so far
> received 683 message(s) with a rate of  683.0 messages/sec,     15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> closing connection JBossConnection->ConnectionDelegate[375652924, ID=83-8dse0r7f-1-qvc9zq7f-g0vqau-31184a, SID=39] on exit ...
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15829 message(s) received so far
> received 40 message(s) with a rate of   40.0 messages/sec,      15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> received 0 message(s) with a rate of    0.0 messages/sec,       15869 message(s) received so far
> Could not just close() connection, I had to kill the java process
> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG_REF;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> 50000 - 34091 - 15869 = 40 messages unnacounted for (probably the client send the acknowledgment, but it did not actually receive it)
> * Tried to create a new connection to the server, the JNDI invocation hung.
> * Killed both servers, restarted.
> Database situation:
> mysql> SELECT COUNT(MESSAGE_ID) FROM JBM_MSG;
> +-------------------+
> | COUNT(MESSAGE_ID) |
> +-------------------+
> |             34091 | 
> +-------------------+
> mysql> SELECT MIN(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MIN(MESSAGE_ID) |
> +-----------------+
> |            8957 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 8957;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |       8957 |           NULL | C     | 39070335505044212 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT MAX(MESSAGE_ID) FROM JBM_MSG_REF;
> +-----------------+
> | MAX(MESSAGE_ID) |
> +-----------------+
> |           54192 | 
> +-----------------+
> mysql> SELECT * FROM JBM_MSG_REF WHERE MESSAGE_ID = 54192;
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> | CHANNEL_ID | MESSAGE_ID | TRANSACTION_ID | STATE | ORD               | PAGE_ORD | DELIVERY_COUNT | SCHED_DELIVERY |
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> |          0 |      54192 |           NULL | C     | 39070359199138639 |     NULL |              0 |              0 | 
> +------------+------------+----------------+-------+-------------------+----------+----------------+----------------+
> mysql> SELECT * FROM JBM_POSTOFFICE;
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | POSTOFFICE_NAME | NODE_ID | QUEUE_NAME               | COND                           | SELECTOR | CHANNEL_ID | CLUSTERED | ALL_NODES |
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> | JMS post office |      38 | DLQ                      | queue.DLQ                      | NULL     |         21 | N         | N         | 
> | JMS post office |      38 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |         22 | N         | N         | 
> ...
> | JMS post office |      38 | ovidiu                   | queue.ovidiu                   | NULL     |         20 | Y         | N         | 
> ...
> | JMS post office |      38 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |         28 | Y         | N         | 
> ...
> | JMS post office |      39 | DLQ                      | queue.DLQ                      | NULL     |          1 | N         | N         | 
> | JMS post office |      39 | ExpiryQueue              | queue.ExpiryQueue              | NULL     |          2 | N         | N         | 
> ...
> | JMS post office |      39 | ovidiu                   | queue.ovidiu                   | NULL     |         40 | Y         | N         | 
> ...
> | JMS post office |      39 | testDistributedQueue     | queue.testDistributedQueue     | NULL     |          8 | Y         | N         | 
> +-----------------+---------+--------------------------+--------------------------------+----------+------------+-----------+-----------+
> 34 rows in set (0.00 sec)
> * Pinged 39
> ofeodorov at yamato$ mess ping
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> node 39 alive
> closing connection JBossConnection->ConnectionDelegate[735699586, ID=t2-b4k51r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...
> * Browsed the queue (I don't expect any, since channel 0 does not exist anymore)
> ofeodorov at yamato$ mess browse
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> NO messages in queue
> closing connection JBossConnection->ConnectionDelegate[2002021820, ID=03-fah61r7f-1-h2w31r7f-q9dxny-31184a, SID=39] on exit ...

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:47:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Mon, 22 Oct 2007 08:47:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1109) Client-side
 race condition while receiving concurrently
In-Reply-To: <4635449.1192318623341.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5296993.1193057223555.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1109?page=all ]

Tim Fox closed JBMESSAGING-1109.
--------------------------------

    Resolution: Done

> Client-side race condition while receiving concurrently
> -------------------------------------------------------
>
>                 Key: JBMESSAGING-1109
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())
> @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
> org.jboss.jms.exception.MessagingJMSException: Failed to invoke
>         at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
>         at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
>         at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
>         at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
>         at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
>         at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
>         at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
>         at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.remoting.Client.invoke(Client.java:536)
>         at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
>         ... 17 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 08:49:04 2007
From: jira-events at lists.jboss.org (David Bala?ic (JIRA))
Date: Mon, 22 Oct 2007 08:49:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-698) Exception
 serialization issue when remotely accessing stateless session bean
In-Reply-To: <23517647.1157576669733.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18554030.1193057344675.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-698?page=comments#action_12383671 ] 
            
David Bala?ic commented on EJBTHREE-698:
----------------------------------------

I have the same problem (on version 4.0.4GA , JDK 1.5.0_12  Windows XP).

And (fanfares...) I found a workaround.
If the exception is ClassNotFoundException: [Lcom.foo.Bar;

then just add a line in the client before the remote call :

import com.foo.Bar;
...

Bar [] dummy = { new Bar() };
remObj.yourRemoteCall(x,y,z);


It seems the JVM "forgets" to load (or create, array classes can not be loaded...) the class definition for "array of SomeClass", to that line of code "forces" it to do so before the call (when the definition is then required/used).

> Exception serialization issue when remotely accessing stateless session bean
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-698
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-698
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: David Green
>
> Accessing a remote EJB (Session bean) results in exception.  Stack trace follows:
> 13:54:39,546 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> 	at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
> 	at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> 	at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
> 	at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
> 	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
> 	at org.jboss.remoting.Client.invoke(Client.java:525)
> 	at org.jboss.remoting.Client.invoke(Client.java:488)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> 	at $Proxy0.postNotification(Unknown Source)
> 	at com.hgea.hch.service.HchClientDelegate.postNotification(HchClientDelegate.java:99)
> 	at com.hgea.hch.client.RemoteHchClientTest.testRemotePostNotification(RemoteHchClientTest.java:38)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
> 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672)
> 	at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:03:03 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Mon, 22 Oct 2007 09:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22437634.1193058183334.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4880?page=all ]

Colin Mondesir reassigned JBAS-4880:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4880
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:05:31 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 09:05:31 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7807529.1193058331654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Luc Texier reassigned JBAS-4830:
--------------------------------

    Assignee: Luc Texier

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:19:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 09:19:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6546069.1193059145145.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383672 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

C'mon guys, this really looks like a non-issue to me.

Since the 'all' configuration of jboss contains an unexploded juddi-service.sar with scout.jar inside, the test classpath should be changed to look there for the libraries. Or even look for scout.jar in the client libraries directory, it is there, too.

So either make this modification and re-tag jbossws-2.0.1.SP2, or hack the hudson build (like Rajesh has done already AFAIK) and fix it later in jbossws.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:21:03 2007
From: jira-events at lists.jboss.org (Fady Matar (JIRA))
Date: Mon, 22 Oct 2007 09:21:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1073) Allow mail attribute
 'to' resolve EL Expressions
Message-ID: <18645462.1193059263442.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow mail attribute 'to' resolve EL Expressions
------------------------------------------------

                 Key: JBPM-1073
                 URL: http://jira.jboss.com/jira/browse/JBPM-1073
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2
            Reporter: Fady Matar
         Assigned To: Tom Baeyens
             Fix For: jBPM jPDL 3.2.3


Allow the attribute 'to' in the mail module to resolve EL expressions. Currently the 'to' attribute only encodes hard coded emails

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:37:35 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 09:37:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28573803.1193060255589.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383677 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

There is a switch where this is configurable.

jboss.server.instance=default

I also think this is a non-issue


> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:43:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 09:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14593321.1193060583401.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383680 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I looked at you hudson script. I think this looks ok and we really don't have a hidden issue.
AFAIK, you can close this issue.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 09:48:14 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 22 Oct 2007 09:48:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3700243.1193060894428.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383681 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

Since you had a look at the hudson script, currently i unzip the juddi-service.sar in the default/deploy directory.
unzip thirdparty/juddi-service.sar -d $WORKSPACE/$DIST_NAME/server/default/deploy/juddi-service.sar/

instead if i just copy the sar, the tests fail.
cp thirdparty/juddi-service.sar $WORKSPACE/$DIST_NAME/server/default/deploy/

Do you know why that happens?

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:00:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 22 Oct 2007 10:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-180) Problems with delete
	of start state
Message-ID: <4703392.1193061603580.JavaMail.jira@cloud.prod.atl2.jboss.com>

Problems with delete of start state
-----------------------------------

                 Key: GPD-180
                 URL: http://jira.jboss.com/jira/browse/GPD-180
             Project: JBoss jBPM GPD
          Issue Type: Bug
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
            Reporter: Koen Aers
         Assigned To: Koen Aers
             Fix For: jBPM jPDL Designer 3.1.1




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:00:03 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Mon, 22 Oct 2007 10:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (GPD-180) Problems with delete
	of start state
In-Reply-To: <4703392.1193061603580.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16544696.1193061603979.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-180?page=all ]

Koen Aers updated GPD-180:
--------------------------

    Component/s: jpdl

> Problems with delete of start state
> -----------------------------------
>
>                 Key: GPD-180
>                 URL: http://jira.jboss.com/jira/browse/GPD-180
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 10:11:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24984284.1193062267870.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383684 ] 
            
Dimitris Andreadis commented on JBAS-4811:
------------------------------------------

Because-most probably- the test puts server/default/deployjuddi-service.sar/scout.jar in the classpath. If you don't unzip, it cannot see it.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:09 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 10:11:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19871460.1193062269815.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4823?page=comments#action_12383685 ] 
            
Luc Texier commented on JBAS-4823:
----------------------------------

 The JBoss Support Team will review these documents and make the appropriate changes accordingly 

> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:10 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 10:11:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15749551.1193062270009.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383686 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

I  don't unfortunately, Maybe you should talk to Dimitris on whether this is a general issue that needs to get looked in to for 4.2.3

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:11:10 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Mon, 22 Oct 2007 10:11:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6275726.1193062270171.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12383687 ] 
            
Luc Texier commented on JBAS-4819:
----------------------------------

You're welcome Big Daddy...



> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:19:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1729) AjaxInterceptor
 with a different context root
In-Reply-To: <13290468.1191167861321.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18376798.1193062743767.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1729?page=all ]

Thomas Heute updated JBPORTAL-1729:
-----------------------------------

    Assignee: Thomas Heute

> AjaxInterceptor with a different context root
> ---------------------------------------------
>
>                 Key: JBPORTAL-1729
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1729
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.1 Final
>         Environment: fedora 7, eclipse europa, java 5 update 12
>            Reporter: Luca Stancapiano
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>         Attachments: patch_AjaxInterceptor.zip
>
>
> about org.jboss.portal.core.controller.ajax.AjaxInterceptor class
> row 75:
> pageProps.put(DynaConstants.RESOURCE_BASE_URL, "/portal-ajax/dyna");
> It uses a static hard coded link to use portal-ajax application , but if we need to change context root, it points to the same link and so in some cases there can to be redirect problems.
> In my case, I have two portal instances on two different hosts and through mod_jk I redirect the first instance using /portal* path and the second with /two_portal* path.
> I cannot o use /portal-ajax path from the second host because mod_jk see that path and it redirects to the first portal instance, then I need to use a different path else I pay a unnecessary connection.
> To resolve this problem I added a property TargetContextPath (as for org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor class) into AjaxInterceptor and substituted it to /portal-ajax/ link.
> private String targetContextPath = "/portal-ajax";
>    public String getTargetContextPath()
>    {
>       return targetContextPath;
>    }
>    public void setTargetContextPath(String context)
>    {
>       targetContextPath = context;
>    }
> it can to be configured through AjaxInterceptor MBean into META-INF/jboss-service.xml. Here there is an example:
>    <mbean
>       code="org.jboss.portal.core.controller.ajax.AjaxInterceptor"
>       name="portal:service=Interceptor,type=Command,name=Ajax"
>       xmbean-dd=""
>       xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
>       <xmbean/>
>       <attribute name="TargetContextPath">/portal-ajax</attribute>
>    </mbean>

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:21:31 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:21:31 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1730)
 IdentityServiceControllerImpl
 : unregister existing MBean service before to re register them
In-Reply-To: <4337065.1191178121268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23295407.1193062891885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=all ]

Thomas Heute updated JBPORTAL-1730:
-----------------------------------

    Assignee: Thomas Heute

> IdentityServiceControllerImpl : unregister existing MBean service before to re register them
> --------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1730
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
> the Identity Beans are registered as JMX MBeans.
> When redeploying the service, an exception is thrown, as the services are yet deployed.
> javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
> Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
> // Unregister the former service is if it is yet there.
> // This to avoid the exception when redeploying this service
> if (getServer().isRegistered(
> 		new ObjectName(module.getServiceName()))) {
> 	getServer().unregisterMBean(
> 			new ObjectName(module.getServiceName()));
> }
> Thanks,

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:29:05 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:29:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1765) Adapt the
 admin portlet to let the user set a default window state
In-Reply-To: <32743739.1192742134373.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23107729.1193063345568.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1765?page=comments#action_12383694 ] 
            
Thomas Heute commented on JBPORTAL-1765:
----------------------------------------

The back end is done ;)

One constraint is that only 1 window can be set as maximized.
But several windoes can be set as minimized.

> Adapt the admin portlet to let the user set a default window state
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1765
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1765
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Thomas Heute
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> We'll need to be able to define which window (if any) of a page should be maximized when a window opens, we'll also need to define if a window must first be displayed as minimized.
> The back end is not done 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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:33:03 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:33:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1770) Display icons in
 portlets list and provide icons for portlets
Message-ID: <25521218.1193063583429.JavaMail.jira@cloud.prod.atl2.jboss.com>

Display icons in portlets list and provide icons for portlets
-------------------------------------------------------------

                 Key: JBPORTAL-1770
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1770
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
            Reporter: Thomas Heute
         Assigned To: Wesley Hales
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:37:03 2007
From: jira-events at lists.jboss.org (Rajesh Rajasekaran (JIRA))
Date: Mon, 22 Oct 2007 10:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24212646.1193063823354.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383697 ] 
            
Rajesh Rajasekaran commented on JBAS-4811:
------------------------------------------

Since this is mostly an issue on the test side i am going to ignore this issue for this release.
Also since Thomas is not able to reproduce this, there is no point waiting here.

Not sure what the status of this issue should say, I will leave it to Dimitris.
Going ahead with the release.

I am also reverting the hudson job to the earlier way in which the error can be reproduced.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:43:14 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 10:43:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25129739.1193064194873.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4811?page=comments#action_12383701 ] 
            
Thomas Diesler commented on JBAS-4811:
--------------------------------------

Rajesh, there is no web service specific error. Please leave it as it is. Otherwise we won't be able to detect regression.

That a class from a jar from inside a sar cannot be loaded is a general AS issue.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.2.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:51:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 10:51:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4891) Cannot unmarshall
	qname elements
Message-ID: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot unmarshall qname elements
--------------------------------

                 Key: JBAS-4891
                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:53:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Mon, 22 Oct 2007 10:53:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-424) Look into
 combining default pom and jdk14 poms.
Message-ID: <26016287.1193064783660.JavaMail.jira@cloud.prod.atl2.jboss.com>

Look into combining default pom and jdk14 poms.
-----------------------------------------------

                 Key: JBBUILD-424
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-424
             Project: JBoss Build System
          Issue Type: Task
          Components: Maven
            Reporter: Paul Gier
             Fix For: Maven Build - Maint 2007


Having separate pom files (default and jdk14) is causing some problems with releases.  Maybe the poms can be combined using profiles so that we don't have to keep two separate poms up to date.
I had some issues when attempting to use profiles before:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=115157

But I think that I can get around those issues now.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:55:04 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:55:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1766) Portal
	Administration Icons
In-Reply-To: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12144902.1193064904402.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1766?page=all ]

Thomas Heute updated JBPORTAL-1766:
-----------------------------------

      Component/s: Portal Core Admin
    Fix Version/s: 2.6.3 Final

> Portal Administration Icons
> ---------------------------
>
>                 Key: JBPORTAL-1766
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:55:04 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 22 Oct 2007 10:55:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9846939.1193064904617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris reassigned JBAS-4820:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:55:06 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 22 Oct 2007 10:55:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBPORTAL-1770) Display icons in
 portlets list and provide icons for portlets
Message-ID: <15162837.1193064906366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1770?page=all ]

Thomas Heute deleted JBPORTAL-1770:
-----------------------------------


> Display icons in portlets list and provide icons for portlets
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1770
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1770
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Heute
>         Assigned To: Wesley Hales
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 10:59:03 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Mon, 22 Oct 2007 10:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBBUILD-425) Fix maven bug in
	release plugin
Message-ID: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix maven bug in release plugin
-------------------------------

                 Key: JBBUILD-425
                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
             Project: JBoss Build System
          Issue Type: Task
          Components: Maven
            Reporter: Paul Gier
         Assigned To: Paul Gier
             Fix For: Maven Build - Maint 2007


There is an issue when using a test-jar in during a release.
http://jira.codehaus.org/browse/MRELEASE-285 

This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:18:14 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 11:18:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24302861.1193066294981.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Thomas Diesler updated JBAS-4891:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
jboss descriptors cannot have qname elements like this 

  <service-ref>
    <service-ref-name>SecurePort1</service-ref-name>
    <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
    ...
  </service-ref>


Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
        at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)


> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:30:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 11:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31797832.1193067003476.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383723 ] 
            
Thomas Diesler commented on JBAS-4891:
--------------------------------------

Please note, we used to have qname elements defined like this

  <service-ref>
    <service-ref-name>SecurePort1</service-ref-name>
    <service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</service-qname>
    ...
  </service-ref>

which gave this exception 

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Characters are not allowed here
        at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal(CharactersHandler.java:118)
        at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHandler.unmarshal(RtCharactersHandler.java:64)
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1044)
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:266)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:374)
        at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)





> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:32:04 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 22 Oct 2007 11:32:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28021019.1193067124438.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383725 ] 
            
Thomas Diesler commented on JBAS-4891:
--------------------------------------

Standard descriptors like web.xml also contain <service-qname> elements. 
IMHO we should use the same syntax in our descriptors that is used in the standard descriptors

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:37:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 11:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3555144.1193067425725.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=all ]

Manik Surtani updated JBCACHE-1201:
-----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.CR1)

> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:37:05 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 11:37:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1201) OPTIMISTIC
 locking requires SyncCommitPhase to be true
In-Reply-To: <24954725.1192647303376.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16142883.1193067425865.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1201?page=comments#action_12383728 ] 
            
Manik Surtani commented on JBCACHE-1201:
----------------------------------------

as per discussion on the forum, deferring this to 2.2.0, potentially may not fix this at all.


> OPTIMISTIC locking requires SyncCommitPhase to be true
> ------------------------------------------------------
>
>                 Key: JBCACHE-1201
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1201
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Replication
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> When using OPTIMISTIC and REPL_SYNC, I find I need to set SyncCommitPhase=true in order for the following to work:
> tm.begin();
> cache1.put(fqn, KEY, VALUE1);
> tm.commit();
>       
> assertEquals("Correct node2 value", VALUE1, cache2.get(fqn, KEY));
> With SyncCommitPhase=false, cache2.get(fqn, KEY) consistently returns null.
> A simple sleep after the commit call will also make this test pass
> My understanding of distributed optimistic locking is that at the end of the prepare phase, on all nodes in the cluster the originating node's workspace modifications should have been applied to the main tree, with normal write locks held on the updated nodes.  The commit call then causes the locks to be released, as in pessimistic locking.
> The above test result implies this is not the case. That implies more work is going on in the commit phase than is appropriate for a Synchronization.afterCompletion() callback.
> Test for this is o.j.c.optimistic.FullStackInterceptorTest.testAsynchronousCommit()

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:39:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 22 Oct 2007 11:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13143893.1193067543279.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris reassigned JBAS-4822:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 11:42:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 22 Oct 2007 11:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9233610.1193067723767.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris updated JBAS-4820:
-------------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-2.odt

This chapter is fairly self explanatory (Chapter 2. Installation Alternatives) I just added suggestions that might make more obvious to users, where and how they can get each of the alternatives. And if they will be able to get it (subscription restrictions)

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:15:03 2007
From: jira-events at lists.jboss.org (Bernd Ruecker (JIRA))
Date: Mon, 22 Oct 2007 12:15:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-181) NullPointerException
 when opening processdefinition with additional elements
Message-ID: <5111725.1193069703312.JavaMail.jira@cloud.prod.atl2.jboss.com>

NullPointerException when opening processdefinition with additional elements
----------------------------------------------------------------------------

                 Key: GPD-181
                 URL: http://jira.jboss.com/jira/browse/GPD-181
             Project: JBoss jBPM GPD
          Issue Type: Bug
          Components: jpdl
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
         Environment: Eclipse Europa
            Reporter: Bernd Ruecker
         Assigned To: Koen Aers


When I add in a processdefinition an element for the simulation, the process deisgner raises a NullPointerException when opening the changed processdefinition.

This is the element I add:
	<task-node name="quick test">
		<task name="quick test" swimlane="clerk"></task>
		<resource-needed pool='test-equipment' amount='1' />
		<transition to="extended technical test" name="no defect"></transition>
		<transition to="Refund" name="defect approved"></transition>
	</task-node>

Without the "resource-needed" element everything works fine, with that element I get the following exception:

java.lang.NullPointerException
	at org.jbpm.gd.common.xml.GenericElementXmlAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.TaskNodeDomAdapter.doModelAdd(Unknown Source)
	at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.TaskNodeDomAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.ProcessDefinitionDomAdapter.doModelAdd(Unknown Source)
	at org.jbpm.gd.common.xml.XmlAdapter.initialize(Unknown Source)
	at org.jbpm.gd.jpdl.xml.ProcessDefinitionDomAdapter.initialize(Unknown Source)
	at org.jbpm.gd.common.editor.Editor.getSemanticElement(Unknown Source)
	at org.jbpm.gd.common.editor.Editor.initSourcePage(Unknown Source)
	at org.jbpm.gd.common.editor.Editor.createPages(Unknown Source)
	at org.jbpm.gd.jpdl.editor.JpdlEditor.createPages(Unknown Source)
	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
	at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
	at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
	at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
	at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2721)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2633)
	at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2625)
	at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2577)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2572)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2556)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2547)
	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644)
	at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603)
	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:285)
	at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:138)
	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:194)
	at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:175)
	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268)
	at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244)
	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:316)
	at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:613)
	at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
	at org.eclipse.core.runtime.Platform.run(Platform.java:857)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:193)
	at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818)
	at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
	at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183)
	at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
	at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
	at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
	at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1169)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:17:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:17:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
In-Reply-To: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15033235.1193069824567.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4834?page=all ]

Brian Stansberry reassigned JBAS-4834:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Clustering Guide - TRACKER
> ---------------------------------------
>
>                 Key: JBAS-4834
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>
> Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:17:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:17:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18718683.1193069824753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Brian Stansberry reassigned JBAS-4835:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:17:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:17:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11923622.1193069824928.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

Brian Stansberry reassigned JBAS-4836:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10812236.1193069943534.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

Brian Stansberry reassigned JBAS-4837:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20459241.1193069943695.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

Brian Stansberry reassigned JBAS-4838:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26916039.1193069943864.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Brian Stansberry reassigned JBAS-4839:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16137377.1193069944028.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Brian Stansberry reassigned JBAS-4840:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:19:04 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 22 Oct 2007 12:19:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31007168.1193069944226.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry reassigned JBAS-4841:
--------------------------------------

    Assignee: Brian Stansberry

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 12:50:03 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Mon, 22 Oct 2007 12:50:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-158) Non-existent
 manifest Class-Path refs produce vfs IllegalStateException
In-Reply-To: <7022011.1173599806886.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10731954.1193071803396.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-158?page=comments#action_12383746 ] 
            
Max Andersen commented on JBMICROCONT-158:
------------------------------------------

Any known workarounds around this ?! 

I'm getting this too when I'm trying to run unittests directly from the IDE where these jars might not yet be packaged up but just be on the global classpath.

> Non-existent manifest Class-Path refs produce vfs IllegalStateException
> -----------------------------------------------------------------------
>
>                 Key: JBMICROCONT-158
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-158
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>    Affects Versions:  JBossMC_2_0_0 Beta3
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> When the structure deployers parse a top-level jboss-test-entity.jar with a manifest like:
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.5.0_09-b01 (Sun Microsystems Inc.)
> Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx
>  .jar junit.jar deploy.jar
> it fails with:
> Caused by: java.lang.IllegalStateException: JarHandler at 28271403[path= context=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar
> real=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar] has no parent.
>         at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:116)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.processContext(DefaultStructureBuilder.java:131)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.populateContext(DefaultStructureBuilder.java:89)
> The invalid references should at most produce debug level warnings.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1150) Drools 4.0 BRMS
 not working with geronimo-jetty6-jee5-2.0.1
In-Reply-To: <25850901.1188508878448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <294557.1193072643925.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1150?page=all ]

Fernando Meyer reassigned JBRULES-1150:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Drools 4.0 BRMS not working with geronimo-jetty6-jee5-2.0.1
> -----------------------------------------------------------
>
>                 Key: JBRULES-1150
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1150
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>         Environment: geronimo-jetty6-jee5-2.0.1
> drools-4.0.1.SNAPSHOT-brms
>            Reporter: Bhagwath Vadyala
>         Assigned To: Fernando Meyer
>         Attachments: drools-error-screenshot.doc, jetty_2007_09_04.log, screenshot-1.jpg
>
>
> I am trying to test and see whether Drools 4.0 BRMS works with Geronimo-jetty6-jee5-2.0.1 or not.
> Drools BRMS version which I am using is drools-4.0.1.SNAPSHOT-brms.
> It deploys fine in Geronimo but when I open the BRMS error message I am getting is HTTP ERROR:404.
> Please let me know whether we can make Drools 4.0 work with Geronimo-jetty 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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:04 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1251) Cannot remove a
 category if it was used in an archived rule
In-Reply-To: <29917794.1191583443584.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24506412.1193072644644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1251?page=all ]

Fernando Meyer reassigned JBRULES-1251:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Cannot remove a category if it was used in an archived rule
> -----------------------------------------------------------
>
>                 Key: JBRULES-1251
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1251
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> The BRMS manual says you can delete a category if it is not in use by any current version of a rule. However, if you archive a rule that uses a category X, say, then you cannot remove category X in the Admin section, even if no other rules in the repository use category X. You get the following error message:
> "The category still has some assets linked to it. You will need to remove the links so you can delete the cateogory"
> (PS not the spelling mistake cateogory in the error message)
> Either the manual (Section 9.4.2.2) should be updated with a warning that you cannot remove a category used by archived rules, or is there is a bug in the remove category functionality for archived assets, as you can remove categories which are only used in old versions of a rule?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:04 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1250) Allow option to
 completely remove an asset from the repository
In-Reply-To: <16475001.1191582723288.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19502074.1193072644832.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1250?page=all ]

Fernando Meyer reassigned JBRULES-1250:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Allow option to completely remove an asset from the repository
> --------------------------------------------------------------
>
>                 Key: JBRULES-1250
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1250
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> If you use the archive feature to remove a rule or package from the BRMS it is not really seen as gone, as if you attempt to create a new rule or package with the same name as the archived rules or package then you get an error saying that the rule or package already exists (looking at the  source code, the repository does not care if an item is archived or not, so it will always throw an error if an asset with an existing name is created).
> I'm assuming this is the designed behaviour and not a bug (I've asked about this a couple of times on the user list and got no replies to the contrary).
> However, it would be very useful to be able to remove a rule or package so that you can then recreate it (e.g by importing new versions from a drl file). At present, you have to laboriously rename the rules and packages you want to remove, so that when they are archived their names do not clash with the new versions of the rules and packages you want to import or recreate. Perhaps all that is involved in implementing this new remove feature is to just automatically rename the package and its rules before archiving it?

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:05 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1249) Allow repository
 location to be specified in BRMS web client
In-Reply-To: <26599863.1191582367386.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31953539.1193072645068.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1249?page=all ]

Fernando Meyer reassigned JBRULES-1249:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Allow repository location to be specified in BRMS web client
> ------------------------------------------------------------
>
>                 Key: JBRULES-1249
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1249
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> At present, any custom location of the repository is set in a components.xml file inside the WEB-INF directory of the BRMS war file. It would be better if the user could specify the location using the BRMS web client itself, rather than have to unzip, modify and zip up the WAR file. Perhaps this functionality could be added to the Admin section of the BRMS.
> One advantage of this is that users could also then work with multiple repositories (e.g. for different projects). In effect there would be an option to create a new repository (specified by a directory given by the user), open an existing repository and close a repository.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:05 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Mon, 22 Oct 2007 13:04:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBBUILD-425) Fix maven bug in
 release plugin
In-Reply-To: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1163556.1193072645182.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBBUILD-425?page=comments#action_12383756 ] 
            
Paul Gier commented on JBBUILD-425:
-----------------------------------

Looks like this issue is related to a more general maven issue that affects a few plugins:
http://jira.codehaus.org/browse/MNG-2277

> Fix maven bug in release plugin
> -------------------------------
>
>                 Key: JBBUILD-425
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> There is an issue when using a test-jar in during a release.
> http://jira.codehaus.org/browse/MRELEASE-285 
> This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:04:05 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:04:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1242) Archived package
 assets cannot be restored
In-Reply-To: <10651989.1191324483301.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29420141.1193072645461.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1242?page=all ]

Fernando Meyer reassigned JBRULES-1242:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Archived package assets cannot be restored
> ------------------------------------------
>
>                 Key: JBRULES-1242
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1242
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets?
> The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of  archived assets.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:22 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1289) BRMS gives
 unusable error messages when validating DSL based rules
In-Reply-To: <12543965.1192890967500.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6622936.1193072782517.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1289?page=all ]

Fernando Meyer reassigned JBRULES-1289:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS gives unusable error messages when validating DSL based rules
> ------------------------------------------------------------------
>
>                 Key: JBRULES-1289
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1289
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> The error messages that are shown when you click "Validate" when editing a business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small typo and misspell the name of an attribute (a very likely thing for a BRMS user to do), and click the Validate button, the error I get back is a big stack trace starting with "java.lang.RuntimeException: SNO: Conversion failed at org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere in that stack trace is anything that gives a hint that
> the error is just a typo of an attribute name.
> Contrast this with the rather helpful error message I get if I make the same typo when editing a DRL rule: "Unable to create Field Extractor for 'overtimHours'". (The error is that I misspelled overtimeHours). 
> The BRMS needs to give the same type of helpful error message on validation errors when editing a DSL rule.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:22 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1290) BRMS does not
 allow rule names to contain an apostrophe character ( ' )
In-Reply-To: <25881085.1192891323312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17618685.1193072782722.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1290?page=all ]

Fernando Meyer reassigned JBRULES-1290:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS does not allow rule names to contain an apostrophe character ( ' )
> -----------------------------------------------------------------------
>
>                 Key: JBRULES-1290
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1290
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> Rules with apostrophe characters are rejected by the BRMS. For example the rule name "Set employee's wage" works outside BRMS, but does not work in BRMS.
> If you attempt to enter a rule through the BRMS containing an apostrophe,the error stack trace says "An error occurred executing the action.
> Details
> com.google.gwt.user.client.rpc.SerializableException:
> javax.jcr.RepositoryException: failed to resolve path Set employee's relative to /drools:repository/drools:package_area/com.example/assets: Invalid name: Set employee's wage: Invalid name: Set employee's wage at
> org.drools.brms.server.ServiceImplementation.createNewRule(ServiceImplementation.java:166)..."
> If you attempt to import a .drl file with a rule that has an apostrophe in the title, you'll get this error message
> (including the <pre> tags): "Unable to import into the package. [<pre>Unable to process import: javax.jcr.RepositoryException: failed
> to resolve path Set employee's wage relative to /drools:repository/drools:package_area/com.soi/assets: Invalid name: Set employee's  wage: Invalid name: Set employee's wage</pre>]".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:22 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:22 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1291) BRMS does not
 allow import of .dslr files
In-Reply-To: <26814116.1192891443260.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12973559.1193072782997.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1291?page=all ]

Fernando Meyer reassigned JBRULES-1291:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS does not allow import of .dslr files
> -----------------------------------------
>
>                 Key: JBRULES-1291
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1291
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> The documentation (section 6.7.3) says that .drl files that use a DSL should be renamed to .dslr to work better in the IDE. The BRMS does not allow importing of .dslr files. Renaming the file back to .drl works.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:23 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1292) BRMS ignores
 "initial
 description" entered when creating new "Business rule using a DSL (text
 editor)" rule
In-Reply-To: <7897053.1192891563924.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9800977.1193072783195.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1292?page=all ]

Fernando Meyer reassigned JBRULES-1292:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> BRMS ignores "initial description" entered when creating new "Business rule using a DSL (text editor)" rule
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1292
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1292
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>
> When creating a new rule asset through the BRMS using the type "Business rule using a DSL (text editor)", the initial description you put in is ignored. You always get the description "A dsl is a language mapping from a domain specific language to the rule language."

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:06:23 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 13:06:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14617490.1193072783631.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=all ]

Fernando Meyer reassigned JBRULES-1273:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Fernando Meyer
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:10:03 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Mon, 22 Oct 2007 13:10:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBPORTAL-1766) Portal
	Administration Icons
In-Reply-To: <19546082.1192743063242.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23641218.1193073003250.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1766?page=all ]

Wesley Hales closed JBPORTAL-1766.
----------------------------------

    Resolution: Done

> Portal Administration Icons
> ---------------------------
>
>                 Key: JBPORTAL-1766
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Wesley Hales
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:12:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 13:12:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1293) Backport for
	Eclipse 3.3
Message-ID: <12660311.1193073123217.JavaMail.jira@cloud.prod.atl2.jboss.com>

Backport for Eclipse 3.3
------------------------

                 Key: JBRULES-1293
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1293
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Eclipse IDE
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.3


We now how two parallel eclipse projects for 4.0.x.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:14:03 2007
From: jira-events at lists.jboss.org (Mark Proctor (JIRA))
Date: Mon, 22 Oct 2007 13:14:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1294) Upgrade to MVEL
	1.2.10
Message-ID: <16163147.1193073243211.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade to MVEL 1.2.10
----------------------

                 Key: JBRULES-1294
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1294
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: All
            Reporter: Mark Proctor
         Assigned To: Mark Proctor
             Fix For: 4.0.3




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:16:03 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Mon, 22 Oct 2007 13:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1117) Request for
 feature to
 close connections on server side by ip address and by connection id
Message-ID: <5418814.1193073363722.JavaMail.jira@cloud.prod.atl2.jboss.com>

Request for feature to close connections on server side by ip address and by connection id
------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1117
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1117
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: Configuration and Management
    Affects Versions: 1.4.0.GA
            Reporter: Jay Howell
         Assigned To: Tim Fox


Several customers have asked for a management method to drop client connections from the server by ip address and by client id.

So there would be two cases.
By ipaddress - this would stop the pinger and also close all connections associated with that client ip address.  Only one pinger exists for an ip address, so this would require closging of the pinger connection also.
By clientid - this would close the pinger thread only if there are no other connections present.

In each of the cases, clients should get an asynchronous onException call.  

The person writing the client will have to have this in mind.  If a client has 1000 connections and the connection logic on the client reconnects.  When the server drops the ip address, then that machine will try to reconnect all 1000 clients.  I really depends on how the connection pooling on the client works.  

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:16:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 22 Oct 2007 13:16:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1295) DSL Mapping files
 does not support comments and empty lines
Message-ID: <8445563.1193073363982.JavaMail.jira@cloud.prod.atl2.jboss.com>

DSL Mapping files does not support comments and empty lines
-----------------------------------------------------------

                 Key: JBRULES-1295
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1295
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.2
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.0.3, 4.1.0


Hi Mark,

I encountered a problem in DROOLS 4.0.2 (I was upgrading from 3.x). The 
problem consists in the fact that the DSL syntax has changed, now it 
does not accept empty lines, and lines continuing on the new line i.e.:

# this is ok
#
<--- Error, empty line
[then] name = java expression 1 \
java expression 2 <--- Error, it does not recognize anymore "\"

Now, I have a very large DSL file (sorry, I cannot disclose it) and I'm 
lazy enough not to edit that one, so instead I patched DROOLs with the 
following code (see the attached files). The code I added is a bit ugly 
(I'm in a hurry, always in a hurry :( ) I have done some basic tests, 
but since they are linked to the files that I cannot disclose (once 
again, sorry for that) they are not added here.

Anyway, here's the patch. Feel free to modify the code.
.java - my current version
.old - the svn extracted one
.diff - unified diff

I would have also some comments about the class loaders, but I will need 
to confirm that before making any comment.

Hope it will be included (in this form or another) in the next release.

Best Regards,
Radu

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:20:03 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 22 Oct 2007 13:20:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1295) DSL Mapping files
 does not support comments and empty lines
In-Reply-To: <8445563.1193073363982.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16970865.1193073603366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1295?page=all ]

Edson Tirelli closed JBRULES-1295.
----------------------------------

    Resolution: Done

Fixed.

> DSL Mapping files does not support comments and empty lines
> -----------------------------------------------------------
>
>                 Key: JBRULES-1295
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1295
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.2
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3, 4.1.0
>
>
> Hi Mark,
> I encountered a problem in DROOLS 4.0.2 (I was upgrading from 3.x). The 
> problem consists in the fact that the DSL syntax has changed, now it 
> does not accept empty lines, and lines continuing on the new line i.e.:
> # this is ok
> #
> <--- Error, empty line
> [then] name = java expression 1 \
> java expression 2 <--- Error, it does not recognize anymore "\"
> Now, I have a very large DSL file (sorry, I cannot disclose it) and I'm 
> lazy enough not to edit that one, so instead I patched DROOLs with the 
> following code (see the attached files). The code I added is a bit ugly 
> (I'm in a hurry, always in a hurry :( ) I have done some basic tests, 
> but since they are linked to the files that I cannot disclose (once 
> again, sorry for that) they are not added here.
> Anyway, here's the patch. Feel free to modify the code.
> .java - my current version
> .old - the svn extracted one
> .diff - unified diff
> I would have also some comments about the class loaders, but I will need 
> to confirm that before making any comment.
> Hope it will be included (in this form or another) in the next release.
> Best Regards,
> Radu

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 13:36:03 2007
From: jira-events at lists.jboss.org (Max Andersen (JIRA))
Date: Mon, 22 Oct 2007 13:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-158) Non-existent
 manifest Class-Path refs produce vfs IllegalStateException
In-Reply-To: <7022011.1173599806886.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15727809.1193074563770.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-158?page=comments#action_12383763 ] 
            
Max Andersen commented on JBMICROCONT-158:
------------------------------------------

note: it seems like this happen even without any manifest.mf. 

Only way I could work around it was to remove the ejb-jar.xml file.

> Non-existent manifest Class-Path refs produce vfs IllegalStateException
> -----------------------------------------------------------------------
>
>                 Key: JBMICROCONT-158
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-158
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>    Affects Versions:  JBossMC_2_0_0 Beta3
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> When the structure deployers parse a top-level jboss-test-entity.jar with a manifest like:
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.5.0_09-b01 (Sun Microsystems Inc.)
> Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx
>  .jar junit.jar deploy.jar
> it fails with:
> Caused by: java.lang.IllegalStateException: JarHandler at 28271403[path= context=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar
> real=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar] has no parent.
>         at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:116)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.processContext(DefaultStructureBuilder.java:131)
>         at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.populateContext(DefaultStructureBuilder.java:89)
> The invalid references should at most produce debug level warnings.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:00:05 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 22 Oct 2007 14:00:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1076) Ensure new
 metamodel and annotations/xml line up
Message-ID: <1082073.1193076005069.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure new metamodel and annotations/xml line up
------------------------------------------------

                 Key: EJBTHREE-1076
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1076
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
            Priority: Critical


End game here is to ensure the external API is correct before Beta 3.  Must ensure that all EJB3 annotations map to cooresponding representations in XML and the new metamodel.

Create a document to track the mappings, place on the Wiki.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:05:06 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Mon, 22 Oct 2007 14:05:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1118) Sucker
 connection created back to itself doesn't need to be created
Message-ID: <1544433.1193076306087.JavaMail.jira@cloud.prod.atl2.jboss.com>

Sucker connection created back to itself doesn't need to be created
-------------------------------------------------------------------

                 Key: JBMESSAGING-1118
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
    Affects Versions: 1.4.0.GA
            Reporter: Jay Howell
         Assigned To: Tim Fox
            Priority: Minor


The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment.  So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker.

while (iter.hasNext())
		{
			Map.Entry entry = (Map.Entry)iter.next();
			
			Integer nid = (Integer)entry.getKey();
			
			ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue();
			
			if (connections.get(nid) == null)
			{
				try
				{
   				ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword);
   				
   				log.trace(this + " created connection info " + info);
   				
   				connections.put(nid, info);
   				
   				info.start();
   						         							         			
				}
				catch (Exception e)
				{
					log.error("Failed to start connection info ", e);
				}
			}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:15:21 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 22 Oct 2007 14:15:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22156702.1193076921549.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=comments#action_12383771 ] 
            
Andrew Rubinger commented on EJBTHREE-1045:
-------------------------------------------

BindingUtils does not provide context as to which attempt to bind resulted in a CCE; a message describing the node that resulted in the failure cannot be constructed.

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:19:05 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Mon, 22 Oct 2007 14:19:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1022) 3.2.1 Admin
 Console: Any user sees all users tasks
In-Reply-To: <6696155.1184871647115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25634380.1193077145913.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1022?page=comments#action_12383772 ] 
            
Ronald van Kuijk commented on JBPM-1022:
----------------------------------------

Burr,

Completele depends on what you regard as the jbpm userbase. Really newbies (often java/web newbies as at the same time) think it can/will/should do everything. More advanced users do not and regard it as an admin console (production quality in the end) and for rapid prototyping.


> 3.2.1 Admin Console: Any user sees all users tasks 
> ---------------------------------------------------
>
>                 Key: JBPM-1022
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1022
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions:  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>            Reporter: Burr Sutter
>         Assigned To: Tom Baeyens
>            Priority: Blocker
>             Fix For: jBPM jPDL 3.2.3
>
>
> In the current Admin Console, any given user will see all other users tasks.  Plus a user can "take" another person's assigned tasks even when they are not an "administrator".

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 14:48:03 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 22 Oct 2007 14:48:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
Message-ID: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>

We should ignore nonPersistentMessages on failover
--------------------------------------------------

                 Key: JBMESSAGING-1119
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: 1.4.0.GA
            Reporter: Clebert Suconic
         Assigned To: Clebert Suconic
             Fix For: 1.4.0.SP1


There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 15:08:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 15:08:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1242) Archived package
 assets cannot be restored
In-Reply-To: <10651989.1191324483301.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18105545.1193080083640.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1242?page=all ]

Fernando Meyer closed JBRULES-1242.
-----------------------------------

    Resolution: Rejected

It isn't a bug, 
there's an open ticket for that, It just wasn't finished yet 

> Archived package assets cannot be restored
> ------------------------------------------
>
>                 Key: JBRULES-1242
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1242
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>            Reporter: Shahad Ahmed
>         Assigned To: Fernando Meyer
>
> If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets?
> The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of  archived assets.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 15:43:15 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Mon, 22 Oct 2007 15:43:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1074) Circular @EJB3
 references in session beans fail to deploy.
In-Reply-To: <7270653.1192639206697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29611582.1193082195540.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1074?page=comments#action_12383800 ] 
            
Andrew Rubinger commented on EJBTHREE-1074:
-------------------------------------------

@IgnoreDependency on one of the injected members should break the cyclic dependency.

> Circular @EJB3 references in session beans fail to deploy.
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1074
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Gunnar Grim
>
> The following circular references makes the application undeployable:
> In ArchiveBrokerBean:
>   @EJB 
>   private SeriesBrokerLocal itsSeriesBroker;	
> In SeriesBrokerBean
>   @EJB 
>   private ArchiveBrokerLocal itsArchiveBroker;	
> Circular references like these work fine in Glassfish but JBoss shows the following error message:
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
>   Depends On Me:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU
>   Depends On Me:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
> ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3
>   State: NOTYETINSTALLED
>   I Depend On:
>     jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3
>     persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 17:05:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 22 Oct 2007 17:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7096699.1193087103878.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4180?page=comments#action_12383808 ] 
            
Galder Zamarreno commented on JBAS-4180:
----------------------------------------

Second set of HA singleton election tests added based on 
Pojo bean HA singletons which passed successfully.

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 17:07:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Mon, 22 Oct 2007 17:07:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4180) Reduce coupling
 between JMX and HASingleton
In-Reply-To: <25486276.1173155171449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <236998.1193087223641.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4180?page=all ]

Galder Zamarreno resolved JBAS-4180.
------------------------------------

    Resolution: Done

> Reduce coupling between JMX and HASingleton
> -------------------------------------------
>
>                 Key: JBAS-4180
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4180
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Galder Zamarreno
>             Fix For: JBossAS-5.0.0.CR1
>
>
> Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff.
> For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX.  Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 17:36:03 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 22 Oct 2007 17:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1771) Add support for
 event listener binding to windows in admin interface
Message-ID: <33127050.1193088963161.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add support for event listener binding to windows in admin interface
--------------------------------------------------------------------

                 Key: JBPORTAL-1771
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1771
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
    Affects Versions: 2.6.2 Final, 2.8 Final
            Reporter: Chris Laprun
         Assigned To: Chris Laprun
            Priority: Minor
             Fix For: 2.6.3 Final, 2.8 Final




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:09:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 22 Oct 2007 19:09:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4811) Integrate the
 JBossWS core testsuite in the release QA
In-Reply-To: <10146565.1192089258601.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12586920.1193094555268.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4811?page=all ]

Dimitris Andreadis updated JBAS-4811:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
                       (was: JBossAS-4.2.2.GA)

Ok, so I'm just re-scheduling this for 4.2.3. Or if the same tests need to run for EAP4.3, we will face this issue again there.

I don't know what the test does exactly, so I cannot tell if this is something we need to fix in AS.

Thomas should be able to describe the failure better, and open a bug report, if this is really an AS problem.

> Integrate the JBossWS core testsuite in the release QA
> ------------------------------------------------------
>
>                 Key: JBAS-4811
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4811
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Rajesh Rajasekaran
>             Fix For: JBossAS-4.2.3.GA
>
>
> Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite.
> The jbossws core tests should be run (automated) as part of every AS community release.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:09:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 19:09:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1188)
 UnversionedNode.isValid - out
 of sync (deleted/remotely deleted nodes)
In-Reply-To: <1073686.1190216951047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1520478.1193094555529.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1188?page=all ]

Manik Surtani resolved JBCACHE-1188.
------------------------------------

    Resolution: Done

> UnversionedNode.isValid - out of sync (deleted/remotely deleted nodes)
> ----------------------------------------------------------------------
>
>                 Key: JBCACHE-1188
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1188
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>         Environment: all
>            Reporter: Mircea Markus
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> considering the scenario:
> thread1: 
> node = cache.get("a/b/c");
> thread2(possibly running on another node/JVM):
> cache.remove("a/b/c");
> thread1: 
> node.getAttribute("attr1");//at this point the node is not longer in the cache. we should allow user to check this through isValid
> node.getAttribute("attr2");

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:19:03 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 22 Oct 2007 19:19:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1077) @RunAsPrincipal
 not propagated
Message-ID: <13923257.1193095143282.JavaMail.jira@cloud.prod.atl2.jboss.com>

@RunAsPrincipal not propagated
------------------------------

                 Key: EJBTHREE-1077
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1077
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.1.GA
            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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 19:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1199) Update
 InvalidatorInterceptorTest to use Node.isValid()
In-Reply-To: <2782171.1192635603222.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21212154.1193097543333.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1199?page=all ]

Manik Surtani resolved JBCACHE-1199.
------------------------------------

    Resolution: Done

> Update InvalidatorInterceptorTest to use Node.isValid()
> -------------------------------------------------------
>
>                 Key: JBCACHE-1199
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node.  See the forum link.  Need to replace with a call to isValid() whenever that is implemented.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 19:59:03 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 19:59:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1200) Node removal with
 invalidation leaves child data accessible
In-Reply-To: <4642624.1192638724532.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19139948.1193097543460.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1200?page=all ]

Manik Surtani resolved JBCACHE-1200.
------------------------------------

    Resolution: Done

> Node removal with invalidation leaves child data accessible
> -----------------------------------------------------------
>
>                 Key: JBCACHE-1200
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1200
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 2.1.0.CR1
>
>
> With invalidation, when a node that has children is removed, on remote caches the data in the children is still visible; e..g
> cache1.put(childFqn, key, value);
> cache1.removeNode(parentFqn);
> // This assertion fails
> assertNull(cache2.get(childFqn, key));
> InvalidationInterceptorTest.testPessimisticNodeRemoval() and testOptimisticNodeRemoval() have been modified to show this issue.
> This is a significant problem for the Hibernate/JBC integration

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 21:05:03 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 22 Oct 2007 21:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1296) Drools Release
	4.0.3
Message-ID: <4893834.1193101503300.JavaMail.jira@cloud.prod.atl2.jboss.com>

Drools Release 4.0.3
--------------------

                 Key: JBRULES-1296
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1296
             Project: JBoss Drools
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 21:21:07 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 22 Oct 2007 21:21:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1203)
 putForExternalRead replicates when INVALIDATION used
In-Reply-To: <4631718.1192734724851.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18448216.1193102467827.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1203?page=all ]

Manik Surtani resolved JBCACHE-1203.
------------------------------------

    Resolution: Done

most of the failures were broken tests; although one glaring problem was in the way invalidation markers were created in CacheImpl.invalidate()



> putForExternalRead replicates when INVALIDATION used
> ----------------------------------------------------
>
>                 Key: JBCACHE-1203
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster.  There should be no impact on other cluster members at all.
> The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 21:36:03 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Mon, 22 Oct 2007 21:36:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1285) Time Machine to
 allow setting of "now" effective current time in Rule
In-Reply-To: <30930954.1192767254713.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16007487.1193103363366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1285?page=all ]

Michael Neale closed JBRULES-1285.
----------------------------------

    Resolution: Done

> Time Machine to allow setting of "now" effective current time in Rule
> ---------------------------------------------------------------------
>
>                 Key: JBRULES-1285
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1285
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>
> This is needed for testing effective dating.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 22:04:03 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Mon, 22 Oct 2007 22:04:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4821) TECH REVIEW:
 Installation Guide
 - Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14899601.1193105043323.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

cheng dan reassigned JBAS-4821:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 22:54:14 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Mon, 22 Oct 2007 22:54:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1771) Add support for
 event listener binding to windows in admin interface
In-Reply-To: <33127050.1193088963161.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10409249.1193108054540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1771?page=all ]

Chris Laprun resolved JBPORTAL-1771.
------------------------------------

    Resolution: Done

> Add support for event listener binding to windows in admin interface
> --------------------------------------------------------------------
>
>                 Key: JBPORTAL-1771
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1771
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>    Affects Versions: 2.8 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>            Priority: Minor
>             Fix For: 2.6.3 Final, 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 22:54:14 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Mon, 22 Oct 2007 22:54:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-824) Allow server to shut
 down connections from specified clients
Message-ID: <17720506.1193108054695.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow server to shut down connections from specified clients
------------------------------------------------------------

                 Key: JBREM-824
                 URL: http://jira.jboss.com/jira/browse/JBREM-824
             Project: JBoss Remoting
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Trustin Lee
             Fix For: 3.0.0.Alpha1 (Otter)


>From Jay Howell:  

Several customers have asked for a management method to drop client connections from the server by ip address and by client id.

So there would be two cases.
   By ipaddress - this would stop the pinger and also close all connections associated with that client ip address. Only one pinger exists for an ip address, so this would require closing of the pinger connection also.
   By clientid - this would close the pinger thread only if there are no other connections present.

In each of the cases, clients should get an asynchronous onException call. 

This facility would be necessary to support JBMESSAGING-1117.




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 22 23:40:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Mon, 22 Oct 2007 23:40:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4892) WebService ignores
 java.rmi.server.codebase system property
Message-ID: <6431871.1193110803625.JavaMail.jira@cloud.prod.atl2.jboss.com>

WebService ignores java.rmi.server.codebase system property
-----------------------------------------------------------

                 Key: JBAS-4892
                 URL: http://jira.jboss.com/jira/browse/JBAS-4892
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Takayoshi Kimura


server/src/main/org/jboss/web/WebService.java

The trailing semicolon of if statement is a bug.

      String codebase = getCodebase(); // This returns system property value
      if (codebase == null); // HERE
      {
         codebase = "http://" + getHost() + ":" + getPort() + "/";
         System.setProperty("java.rmi.server.codebase", codebase);
      }
      log.info("Using RMI server codebase: " + codebase);


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:05:03 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 00:05:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
Message-ID: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>

JvmRouteValve (UseJK) for non session replication setup
-------------------------------------------------------

                 Key: JBAS-4893
                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
            Reporter: Takayoshi Kimura


Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:05:04 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 00:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
In-Reply-To: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11114976.1193112304022.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ]

Takayoshi Kimura updated JBAS-4893:
-----------------------------------

    Component/s: Clustering

> JvmRouteValve (UseJK) for non session replication setup
> -------------------------------------------------------
>
>                 Key: JBAS-4893
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Takayoshi Kimura
>
> Currently JBoss doesn't install JvmRouteValve for non session
> replication setup. However, it's still useful in the following
> scenario:
> * 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
> * A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
> * The node AAA crashed
> * The request goes node BBB, lost session, recreate another
> * The node AAA recovered
> * The request comes back to the node AAA, lost session again
> Enabling JvmRouteValve can prevent last failure.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:05:04 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 00:05:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
In-Reply-To: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7168357.1193112304358.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ]

Takayoshi Kimura updated JBAS-4893:
-----------------------------------

    Description: 
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.


  was:
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.



> JvmRouteValve (UseJK) for non session replication setup
> -------------------------------------------------------
>
>                 Key: JBAS-4893
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Takayoshi Kimura
>
> Currently JBoss doesn't install JvmRouteValve for non session
> replication setup. However, it's still useful in the following
> scenario:
> * 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
> * A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
> * The node AAA crashed
> * The request goes node BBB, lost session, recreate another
> * The node AAA recovered
> * The request comes back to the node AAA, lost session again
> Enabling JvmRouteValve can prevent last failure.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 00:11:23 2007
From: jira-events at lists.jboss.org (Santiago Erquicia (JIRA))
Date: Tue, 23 Oct 2007 00:11:23 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (BPEL-282) Engine runs process
 instances in serie instead of in parallel
Message-ID: <7870750.1193112683491.JavaMail.jira@cloud.prod.atl2.jboss.com>

Engine runs process instances in serie instead of in parallel
-------------------------------------------------------------

                 Key: BPEL-282
                 URL: http://jira.jboss.com/jira/browse/BPEL-282
             Project: JBoss jBPM BPEL
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Engine
    Affects Versions: jBPM BPEL 1.1 beta 3
         Environment: RHEL
            Reporter: Santiago Erquicia
         Assigned To: Alejandro Guizar


We are stress testing a BPEL process and we found out that the engine runs all the requests it receives in serie. That means that if there are two or more concurrent users of the system, one has to wait till the first process instance stops at some point (wait state) so the other request can be processed.

On our test environment, we are calling a web service which is also calling another web service. The are connection problems with the second one, so from time to time the web service just times out. This means that a concurrent user has to wait for that time out, and whatever is left of that process instance, in order to be processed.

On our JMeter test, the throughput keeps stable even if there number of request is bigger than the throughput of the BPEL engine. The result is that the time for response of each process request increases indefinitely if the usage is bigger than the throughput. This obviously doesn't scale at all for the processing requirement we are considering.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 02:18:08 2007
From: jira-events at lists.jboss.org (Magesh Kumar B (JIRA))
Date: Tue, 23 Oct 2007 02:18:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1772) Security fixes
 for JBoss Portal 2.6.2
Message-ID: <24917505.1193120288270.JavaMail.jira@cloud.prod.atl2.jboss.com>

Security fixes for JBoss Portal 2.6.2
-------------------------------------

                 Key: JBPORTAL-1772
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1772
             Project: JBoss Portal
          Issue Type: Support Patch
      Security Level: Public (Everyone can see)
          Components: Portal Security
    Affects Versions: 2.6.2 Final
            Reporter: Magesh Kumar B
         Assigned To: Julien Viet


The patch contains fixes for the following issues:

[JBPORTAL-1741] PortalURL security not honoured
[JBPORTAL-1481] Reimplement portal security interface without JACC

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:02:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 23 Oct 2007 04:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14560763.1193126521916.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383840 ] 
            
Scott M Stark commented on JBAS-4891:
-------------------------------------

There is a usage of such qname type elments in the EjbJar3xUnitTestCase.java, and this is parsing correctly.
https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/test/java/org/jboss/test/metadata/ejb/EjbJar3xUnitTestCase.java
https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/test/resources/org/jboss/test/metadata/ejb/EjbJar3x_testServiceRefs.xml

<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
    version="3.0"
    id="ejb-jar-service-refs">
    <enterprise-beans>
        <session id="session1">
            <description>A secured trival echo session bean</description>
            <ejb-name>StatelessSession1</ejb-name>
            <home>org.jboss.test.security.interfaces.StatelessSessionHome</home>
            <remote>org.jboss.test.security.interfaces.StatelessSession</remote>
            <local-home>org.jboss.test.security.interfaces.StatelessSessionLocalHome</local-home>
            <local>org.jboss.test.security.interfaces.StatelessSessionLocal</local>
            <ejb-class>org.jboss.test.security.ejb.StatelessSessionBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>
            <service-ref id="session1-service-ref">
                <!-- JNDI name bound to the service interface in the client's environment context -->
                <service-ref-name>session1/Hello</service-ref-name>
                <!-- service interface class -->
                <service-interface>org.jboss.test.security.interfaces.HelloWorldService</service-interface>
                <service-ref-type>org.jboss.test.security.interfaces.HelloWorldRef</service-ref-type>
                <!-- placeholder for published WSDL file -->
                <wsdl-file>session1-wsdl-file</wsdl-file>
                <!-- Java<->XML mapping file -->
                <jaxrpc-mapping-file>META-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file>
                <service-qname xmlns:session1="http://www.jboss.org">session1:Session1Qname</service-qname>
                <port-component-ref>
                    <!-- service endpoint interface class -->
                    <service-endpoint-interface>org.jboss.test.security.interfaces.HelloEndPoint</service-endpoint-interface>
                </port-component-ref>
                <handler-chains>
                    <handler-chain id="session1-chain1">
                        <service-name-pattern>*</service-name-pattern>
                        <handler id="sesion1-chain1-handler1">
                            <handler-name>session1.Handler1</handler-name>
                            <handler-class>session1.Handler1</handler-class>
                            <init-param>
                                <param-name>param1</param-name>
                                <param-value>value1</param-value>
                            </init-param>
                            <soap-header xmlns:session1="http://www.jboss.org">session1:soap-header</soap-header>
                            <soap-role>session1:soap-role</soap-role>
                            <port-name>session1:soap-role</port-name>
                        </handler>
                    </handler-chain>
                </handler-chains>
            </service-ref>
        </session>

What is an example descriptor that is failing?


> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:16:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 04:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4892) WebService ignores
 java.rmi.server.codebase system property
In-Reply-To: <6431871.1193110803625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14770622.1193127361571.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4892?page=comments#action_12383842 ] 
            
Dimitris Andreadis commented on JBAS-4892:
------------------------------------------

I believe this is the very first bug recorded against 4.2.2.GA - that was fast!

> WebService ignores java.rmi.server.codebase system property
> -----------------------------------------------------------
>
>                 Key: JBAS-4892
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4892
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Takayoshi Kimura
>
> server/src/main/org/jboss/web/WebService.java
> The trailing semicolon of if statement is a bug.
>       String codebase = getCodebase(); // This returns system property value
>       if (codebase == null); // HERE
>       {
>          codebase = "http://" + getHost() + ":" + getPort() + "/";
>          System.setProperty("java.rmi.server.codebase", codebase);
>       }
>       log.info("Using RMI server codebase: " + codebase);

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:22:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 04:22:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4892) WebService ignores
 java.rmi.server.codebase system property
In-Reply-To: <6431871.1193110803625.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9241861.1193127725972.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4892?page=all ]

Dimitris Andreadis updated JBAS-4892:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA

> WebService ignores java.rmi.server.codebase system property
> -----------------------------------------------------------
>
>                 Key: JBAS-4892
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4892
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Takayoshi Kimura
>             Fix For: JBossAS-4.2.3.GA
>
>
> server/src/main/org/jboss/web/WebService.java
> The trailing semicolon of if statement is a bug.
>       String codebase = getCodebase(); // This returns system property value
>       if (codebase == null); // HERE
>       {
>          codebase = "http://" + getHost() + ":" + getPort() + "/";
>          System.setProperty("java.rmi.server.codebase", codebase);
>       }
>       log.info("Using RMI server codebase: " + codebase);

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1015)
 ServiceDelegateWrapper should
 delegate MBeanRegistration and NotificationEmitter calls
In-Reply-To: <27468169.1184596608426.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20307811.1193127843630.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1015?page=all ]

Carlo de Wolf updated EJBTHREE-1015:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls
> --------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1015
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1015
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: EJB3 Extensions
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>             Fix For: Branch_4_2
>
>
> ServiceDelegateWrapper should delegate MBeanRegistration 
> and NotificationEmitter calls to EJB3 Services if users made
> their EJB3 services implement these interfaces.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-896) Specifying an
 interceptor-order in ejb-jar.xml also creates a new instance of the
 interceptor
In-Reply-To: <33054938.1172680808955.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18888117.1193127843801.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-896?page=all ]

Carlo de Wolf updated EJBTHREE-896:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor
> ---------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-896
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-896
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: interceptor2
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> Trying to override the order of interceptors in xml from the one specified via annotations in the beans, will lead to duplicate invocations on the interceptors.
> @Interceptors({AnnotatedClassInterceptor3.class, XMLClassInterceptor3.class})
> @Stateless(name="OrderedSLSB")
> public class OrderedSLSB implements OrderedSLSBRemote
> {
> ...
> }
>       <interceptor-binding>
>          <ejb-name>OrderedSLSB</ejb-name>
>          <interceptor-order>
> 	         <interceptor-class>org.jboss.ejb3.test.interceptors2.AnnotatedClassInterceptor3</interceptor-class>
> 	         <interceptor-class>org.jboss.ejb3.test.interceptors2.XMLClassInterceptor3</interceptor-class>
> 	         <interceptor-class>org.jboss.ejb3.test.interceptors2.DefaultInterceptor</interceptor-class>
>          </interceptor-order>
>       </interceptor-binding>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-884) META-INF/orm.xml
 should be
 read for both the main persistence jar and all the explicit jars
In-Reply-To: <22344968.1171895871850.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21497694.1193127843955.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-884?page=all ]

Carlo de Wolf updated EJBTHREE-884:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> META-INF/orm.xml should be read for both the main persistence jar and all the explicit jars
> -------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-884
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-884
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Emmanuel Bernard
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> See http://opensource.atlassian.com/projects/hibernate/browse/EJB-259
> I've fixed the issue in HEM, but it worth having a testcase in the container's code base to be safe

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27598616.1193127843451.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Carlo de Wolf updated EJBTHREE-1057:
------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: Branch_4_2
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-872) Unable to call
	EJB Remotely
In-Reply-To: <14581634.1171301790240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5033701.1193127844426.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-872?page=all ]

Carlo de Wolf updated EJBTHREE-872:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Unable to call EJB Remotely
> ---------------------------
>
>                 Key: EJBTHREE-872
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-872
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: EJB3 Extensions
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: two separate, non clustered jbosses
>            Reporter: Henning Vogt
>             Fix For: Branch_4_2
>
>
> See also the linked bug for detailed descripton.
> Calling a remote SLSB does not work, if the equally named SLSB is deployed on the calling JBoss.
> See also:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96098
> and
> http://jira.jboss.com/jira/browse/EJBTHREE-823
> and numerous other topics on this.
> In my opinion, ther should be an easier way to do this, instead of writing your own interceptor, patching JBoss or the like.
> Also, in a non clustered environment, if you give a hostname to the InitialContext(), you should get the remote server session beans,
> regardless of possibly locally deployed equally named stateless sessionbeans.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-856) Use Buddy
 Replication for clustered SFSBs
In-Reply-To: <24225310.1170195680226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8545308.1193127844753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-856?page=all ]

Carlo de Wolf updated EJBTHREE-856:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Use Buddy Replication for clustered SFSBs
> -----------------------------------------
>
>                 Key: EJBTHREE-856
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-856
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: Clustering
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> Optimize the replicated SFSB cache for use with Buddy Replication.  Basically means checking cache calls to ensure unwanted data gravitations do not occur. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-835) revet to
 Hibernate's PersistenceXmlLoader
In-Reply-To: <26261978.1168895332931.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8521309.1193127845286.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-835?page=all ]

Carlo de Wolf updated EJBTHREE-835:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> revet to Hibernate's PersistenceXmlLoader
> -----------------------------------------
>
>                 Key: EJBTHREE-835
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-835
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> The default PersistenceUnitTransactionType is JTA in Java EE and RESOURCE_LOCAL in Java SE.  Currently HEM returns RESOURCE_LOCAL no matter what.  HEM is fixed but until it revs in JBoss head, I have copied the persistence.xml parsing to EJB3 project.
> Please remove org.jboss.ejb3.entity.PersistenceXmlLoader from SVN when HEM revs and revert to Hibernate 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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-832) HEM using
 JBossCache raise a CCE
In-Reply-To: <4453734.1168404686743.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6329831.1193127845499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-832?page=all ]

Carlo de Wolf updated EJBTHREE-832:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> HEM using JBossCache raise a CCE
> --------------------------------
>
>                 Key: EJBTHREE-832
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-832
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: EJB 3.0 RC9 - Patch 1
>            Reporter: Emmanuel Bernard
>         Assigned To: William DeCoste
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> Acording to Gavin
> In persistence.xml:
>          <property name="hibernate.cache.provider_class"
> value="org.hibernate.cache.OptimisticTreeCacheProvider"/>
> And I got:
> 00:39:56,421 INFO  [SettingsFactory] Cache provider:
> org.hibernate.cache.OptimisticTreeCacheProvider
> 00:39:56,421 WARN  [ServiceController] Problem starting service
> persistence.units:ear=jboss-seam-registration.ear,jar=jboss-seam-registr
> ation.jar,unitName=userDatabase
> java.lang.RuntimeException: java.lang.NoClassDefFoundError:
> org/jboss/cache/TransactionManagerLookup
> 	at
> org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrappe
> r.java:108)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
> ort.java:289)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
> Support.java:245)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
> .java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy190.start(Unknown Source)
> 	at
> org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96
> )
> 	at
> org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:
> 467)
> 	at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:317)
> 	at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp
> ort.java:289)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean
> Support.java:245)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
> .java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at
> org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.start(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.
> java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea
> nOperationInterceptor.java:142)
> 	at
> org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.ja
> va:97)
> 	at
> org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorSe
> rviceMBeanSupport.java:238)
> 	at
> org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterce
> ptor.java:92)
> 	at
> org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.sta
> rt(SubDeployerInterceptorSupport.java:188)
> 	at
> org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerIntercepto
> r.java:95)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.start(Unknown Source)
> 	at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
> 	at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
> 	at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
> 	at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.
> java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.
> java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea
> nOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav
> a:264)
> 	at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)
> 	at
> org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc
> anner.java:421)
> 	at
> org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan
> ner.java:634)
> 	at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS
> can(AbstractDeploymentScanner.java:263)
> 	at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loo
> p(AbstractDeploymentScanner.java:274)
> 	at
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run
> (AbstractDeploymentScanner.java:225)
> Caused by: java.lang.NoClassDefFoundError:
> org/jboss/cache/TransactionManagerLookup
> 	at java.lang.Class.getDeclaredConstructors0(Native Method)
> 	at java.lang.Class.privateGetDeclaredConstructors(Unknown
> Source)
> 	at java.lang.Class.getConstructor0(Unknown Source)
> 	at java.lang.Class.newInstance0(Unknown Source)
> 	at java.lang.Class.newInstance(Unknown Source)
> 	at
> org.hibernate.cfg.SettingsFactory.createCacheProvider(SettingsFactory.ja
> va:358)
> 	at
> org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:232
> )
> 	at
> org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1933)
> 	at
> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1
> 216)
> 	at
> org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Config
> uration.java:688)
> 	at
> org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFacto
> ry(HibernatePersistence.java:127)
> 	at
> org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDep
> loyment.java:264)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at
> org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrappe
> r.java:102)
> 	... 92 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-789) build.xml and
 component-info.xml - version numbers and imports need to be updated
In-Reply-To: <1955110.1163617421727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4283985.1193127845711.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-789?page=all ]

Carlo de Wolf updated EJBTHREE-789:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> build.xml and component-info.xml - version numbers and imports need to be updated
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-789
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-789
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Vladimir Ralev
>            Priority: Critical
>             Fix For: Branch_4_2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repository-zip target's comp-version, like this (use appropriate version string):
> <target name="repository-zip" depends="jars"
>     description="Create the repository.jboss.com jboss/ejb3 component contents">
>     <!-- The binary component version -->
>     <property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />
>     <!-- Pack the ejb3.deployer -->
>     <zip destfile="${build.lib}/ejb3-deployer.zip">
>       <zipfileset dir="${build.lib}">
>         <include name="ejb3.deployer/**" />
>       </zipfileset>
>     </zip>
>     <!-- Create a zip file with the component structure -->
>     <zip destfile="${build.lib}/jboss-ejb3-repo.zip">
>       <!-- The component-info.xml -->
>       <zipfileset dir="${build.etc}" prefix="${comp-version}">
>         <include name="component-info.xml" />
>       </zipfileset>
>       <!-- The bin/ejb3.deployer -->
>       <zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer">
>         <include name="ejb3-deployer.zip" />
>       </zipfileset>
>       <!-- The lib client jars -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/lib">
>         <include name="hibernate-client.jar" />
>         <include name="jboss-ejb3-client.jar" />
>       </zipfileset>
>       <!-- The resources deploy descriptors -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/resources">
>         <include name="ejb3-clustered-sfsbcache-service.xml" />
>         <include name="ejb3-entity-cache-service.xml" />
>         <include name="ejb3-interceptors-aop.xml" />
>       </zipfileset>
>     </zip>
>   </target>
> and ejb3\src\etc\component-info.xml (the version attribute):
> <project name="jboss/ejb3-component-info">
>    <component id="jboss/ejb3"
>               licenseType="lgpl"
>               version="1.0.0.CR9-jboss4.0.5"
>               description="The EJB3 deployer for integration with jboss-4.0.x">
>       <artifact id="ejb3-clustered-sfsbcache-service.xml"/>
>       <artifact id="ejb3-entity-cache-service.xml"/>
>       <artifact id="ejb3-interceptors-aop.xml"/>
>       <artifact id="ejb3.deployer" />
>       <artifact id="hibernate-client.jar"/>
>       <artifact id="jboss-ejb3-client.jar"/>
>       <import componentref="javassist">
>         <compatible version="3.2.0.CR1"/>
>         <compatible version="3.2.0.CR2"/>
>       </import>
>       <import componentref="hibernate-annotations">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="hibernate-entitymanager">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="jboss/remoting">
>         <compatible version="1.4.1_final"/>
>         <compatible version="1.4.2.GA"/>
>       </import>
>       <import componentref="jboss/aop">
>       	<compatible version="1.5.1.GA"/>
>         <compatible version="1.5.2.GA"/> <--------------- IS 1.5.2.GA COMPATIBLE?
>       </import>
>       <export>
>          <include input="hibernate-client.jar"/>
>          <include input="jboss-ejb3-client.jar"/>
>       </export>
>    </component>
> </project>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-772) Add JBoss EULA
In-Reply-To: <26119208.1162412921868.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20033634.1193127845850.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-772?page=all ]

Carlo de Wolf updated EJBTHREE-772:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Add JBoss EULA
> --------------
>
>                 Key: EJBTHREE-772
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-772
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Rajesh Rajasekaran
>             Fix For: Branch_4_2
>
>         Attachments: JBossORG-EULA.txt
>
>
> Attached is the JBossORG-EULA.txt 
> 1. The eula should be checked into the project's source tree.
> 2. The project's build should include the EULA in project
> distributables, ie, whatever is the unit of publish: zip, tgz, etc.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-757) getMessageContext
 Not Implemented
In-Reply-To: <12777268.1161683981592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26539940.1193127846430.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-757?page=all ]

Carlo de Wolf updated EJBTHREE-757:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> getMessageContext Not Implemented
> ---------------------------------
>
>                 Key: EJBTHREE-757
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-757
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 GA
>         Environment: Unit test: jaxws
>            Reporter: ppc
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> jboss-4.0.4.GA with EJB3-RC9FD  thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. 
> Form this version with the new JbossWS stack   as far i know i not anymore possible to retreive a SOAP attachement .
> With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :(

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-754) isCallerInRole
 checks should go through JACC layer (if JACC is configured)
In-Reply-To: <22848821.1161361841680.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12908346.1193127846679.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-754?page=all ]

Carlo de Wolf updated EJBTHREE-754:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> isCallerInRole checks should go through JACC layer (if JACC is configured)
> --------------------------------------------------------------------------
>
>                 Key: EJBTHREE-754
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-754
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: Security
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Anil Saldhana
>         Assigned To: Scott M Stark
>             Fix For: Branch_4_2
>
>
> Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to Scott.
> The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has configured jacc.  I am not sure what the best way to tell the xxxContext layer to use jacc helper if user desires.  Maybe a simple system property may do it.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-744) EJB3 JACC Layer
	Container Task
In-Reply-To: <25454643.1160761721812.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25816642.1193127846974.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-744?page=all ]

Carlo de Wolf updated EJBTHREE-744:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> EJB3 JACC Layer Container Task
> ------------------------------
>
>                 Key: EJBTHREE-744
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-744
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: Security
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: Branch_4_2
>
>
> Container Task for validation of the ejb3 jacc layer for correct permissions creation and checking, as per JACC 1.1 specification.
> In the future, the EJB3 security layer needs alignment with the security spi.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-661) Security:
 Deploying a bean
 without mandatory org.jboss.ejb3.security.SecurityDomain results in a
 NullPointerException
In-Reply-To: <7251726.1153836311374.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7228111.1193127847283.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-661?page=all ]

Carlo de Wolf updated EJBTHREE-661:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Security: Deploying a bean without mandatory org.jboss.ejb3.security.SecurityDomain results in a NullPointerException
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-661
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-661
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: EJB 3.0 RC7 - FD
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> When setting up security in a EJB3 bean, it is mandatory adding the 
> org.jboss.ejb3.security.SecurityDomain tag. Failure to do so results 
> on a NullPointerException. 
> AS should log a more meaningful message rather than a 
> NullPointerException.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-564) Inconsistent
 results in ConsumerUnitTestCase
Message-ID: <18824322.1193127847523.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-564?page=all ]

Carlo de Wolf updated EJBTHREE-564:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Inconsistent results in ConsumerUnitTestCase
> --------------------------------------------
>
>                 Key: EJBTHREE-564
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-564
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>            Reporter: Scott M Stark
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> If I run the ConsumerUnitTestCase multiple times I start seeing failures due to method invocation order it seems.
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>     [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 16.344 sec
> BUILD SUCCESSFUL
> Total time: 21 seconds
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>     [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 14.359 sec
>     [junit] Test org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase FAILED
> BUILD SUCCESSFUL
> Total time: 19 seconds
> [starksm at banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test
> Buildfile: build-test.xml
> init:
> test:
> test-with-jvmargs:
>    [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log
>     [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
>     [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 14.86 sec
>     [junit] Test org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase FAILED
> BUILD SUCCESSFUL
> Total time: 19 seconds
>   <testcase classname="org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase" name="testDeploymentDescriptorQueueXA" time="2.032">
>     <failure message="expected:&lt;...1&gt; but was:&lt;...2&gt;" type="junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: expected:&lt;...1&gt; but was:&lt;...2&gt;
> 	at org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA(ConsumerUnitTestCase.java:151)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> </failure>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-509) EJB 3.0
 persistense manager
 unit name is not comming up when deploying entity bean
Message-ID: <298911.1193127847852.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-509?page=all ]

Carlo de Wolf updated EJBTHREE-509:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> EJB 3.0 persistense manager unit name is not comming up when deploying entity bean
> ----------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-509
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-509
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: EJB3 Extensions
>    Affects Versions: EJB 3.0 RC5 - PFD
>         Environment: linux, jboss 4.0.2
>            Reporter: Amit Chauhan
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> trying to implement the tutorial example provided at http://docs.jboss.org/ejb3/app-servers/tutorials/entity/entity.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-477) Implement
 @WebServiceRef and <service-ref>
Message-ID: <2522300.1193127848053.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-477?page=all ]

Carlo de Wolf updated EJBTHREE-477:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Implement @WebServiceRef and <service-ref>
> ------------------------------------------
>
>                 Key: EJBTHREE-477
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-477
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Bill Burke
>         Assigned To: William DeCoste
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> This will be fun!!!!
> Take a look at code in EJB 2.1 container.  DO NOT USE THAT CODE DIRECTLY.  I want to start removing dependencies on that code.  You can also work with WS team on this too.  This should be a HIG PRIORITY task.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-421) Put
 FlushMode.NEVER back on
 track through @FlushMode, at least in a proprietary manner
Message-ID: <31463159.1193127848210.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-421?page=all ]

Carlo de Wolf updated EJBTHREE-421:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Put FlushMode.NEVER back on track through @FlushMode, at least in a proprietary manner
> --------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-421
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-421
>             Project: EJB 3.0
>          Issue Type: Feature Request
>            Reporter: Emmanuel Bernard
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-344) Deployment should
 fail for resource injection to both field and method
Message-ID: <960141.1193127848563.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-344?page=all ]

Carlo de Wolf updated EJBTHREE-344:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Deployment should fail for resource injection to both field and method
> ----------------------------------------------------------------------
>
>                 Key: EJBTHREE-344
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-344
>             Project: EJB 3.0
>          Issue Type: Bug
>         Environment: org.jboss.ejb3.test.naming.unit.BadInjectionsUnitTestCase
>            Reporter: Scott M Stark
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> I belive the indicated BadInjectionsUnitTestCase should be failing to deploy due to the attempt to inject an env-entry via both a field and method annotation. The ejb-jar.xml key env-entry value is not being injected via either mechanism it appears.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-342) Unify
 configuration file names and bootstrap
Message-ID: <16654022.1193127848752.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-342?page=all ]

Carlo de Wolf updated EJBTHREE-342:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Unify configuration file names and bootstrap
> --------------------------------------------
>
>                 Key: EJBTHREE-342
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-342
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Christian Bauer
>         Assigned To: Bill Burke
>             Fix For: Branch_4_2
>
>
> The microcontainer can be booted with StandaloneBootstrap, and it searches for jboss-beans.xml in / and META-INF.
> The E-EJB3 container is booted with EJB3StandaloneBootstrap, which searches for embedded-jboss-beans.xml in / and supports a "basepath" argument.
> Unify these two bootstrap classes. Wishlist:
> - sensible default name for the configuration file ("jboss-beans.xml" sounds good)
> - searches in default locations (/ and META-INF)
> - supports parameters to completely override not only the "basepath", but the full location of the configuration file
> The EJB3StandaloneBootstrap should _extend_ the StandaloneBootstrap, not reimplement it. The current situation makes documentation and explanation unecessarily difficult.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-322) implement
	discarding rules
Message-ID: <26444459.1193127849280.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-322?page=all ]

Carlo de Wolf updated EJBTHREE-322:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> implement discarding rules
> --------------------------
>
>                 Key: EJBTHREE-322
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-322
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC1, EJB 3.0 RC2, EJB 3.0 RC3
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>             Fix For: Branch_4_2
>
>
> we are not discarding EJB instances where appropriate.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-305) Port EJB 2.1
 tests to EJB 3.0 where appropriate
Message-ID: <10404831.1193127849461.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-305?page=all ]

Carlo de Wolf updated EJBTHREE-305:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Port EJB 2.1 tests to EJB 3.0 where appropriate
> -----------------------------------------------
>
>                 Key: EJBTHREE-305
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-305
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: EJB 3.0 RC4 - PFD
>            Reporter: Bill Burke
>         Assigned To: William DeCoste
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-217) The container
 should Instruments Hibernate classes
Message-ID: <8063433.1193127849990.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-217?page=all ]

Carlo de Wolf updated EJBTHREE-217:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> The container should Instruments Hibernate classes
> --------------------------------------------------
>
>                 Key: EJBTHREE-217
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-217
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: EJB3 Extensions
>    Affects Versions: EJB 3.0 Beta 1
>            Reporter: Emmanuel Bernard
>         Assigned To: Bill Burke
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> Right now, the user has to instrument Hibernate classes itself through a InstrumentAnt task to enable some features such as property level lazy loading
> It'd be cool if the container execute the same job at class load time in an automatic manner.
> http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#performance-fetching-lazyproperties

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-197) Deploy Hibernate
 MBean statistics in the EJB 3 Deployer
Message-ID: <29882948.1193127850160.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-197?page=all ]

Carlo de Wolf updated EJBTHREE-197:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Deploy Hibernate MBean statistics in the EJB 3 Deployer
> -------------------------------------------------------
>
>                 Key: EJBTHREE-197
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-197
>             Project: EJB 3.0
>          Issue Type: Feature Request
>            Reporter: Michael Yuan
>             Fix For: Branch_4_2
>
>
> I discussed this with Emmanuel and Steve over email. They both thought it should be fairly easy to add. The JBoss Network team needs this feature to develop profiling and monitoring tools for EJB 3 (see the linked issue).
> Can we have this feature in the JavaOne release of the product? I can demo it in the trail blazer.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-191) servlet
 initialization happens before EJB startup
Message-ID: <10910092.1193127850373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-191?page=all ]

Carlo de Wolf updated EJBTHREE-191:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> servlet initialization happens before EJB startup
> -------------------------------------------------
>
>                 Key: EJBTHREE-191
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-191
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Bill Burke
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-127) Create Docbook
	for @Consumer
Message-ID: <12882820.1193127850514.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-127?page=all ]

Carlo de Wolf updated EJBTHREE-127:
-----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Create Docbook for @Consumer
> ----------------------------
>
>                 Key: EJBTHREE-127
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-127
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>             Fix For: Branch_4_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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:24:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:24:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-27) Allowed methods
Message-ID: <21286672.1193127850744.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-27?page=all ]

Carlo de Wolf updated EJBTHREE-27:
----------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.2.GA)

> Allowed methods
> ---------------
>
>                 Key: EJBTHREE-27
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-27
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: Preview 5
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>             Fix For: Branch_4_2
>
>
> EJB specification has semanatics for what methods can be called when.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-712) Support EJBContext
 injection through ejb-jar.xml
In-Reply-To: <24653724.1158847561251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22925182.1193128083129.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-712?page=all ]

Carlo de Wolf closed EJBTHREE-712.
----------------------------------


> Support EJBContext injection through ejb-jar.xml
> ------------------------------------------------
>
>                 Key: EJBTHREE-712
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-712
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA, AS 5.0.0.Beta3, AS 4.2.1.GA, AS 4.2.0 GA
>
>
> Spec says you use <resource-env-ref> to do injection of EJBContext into a bean.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21832578.1193128083798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=all ]

Carlo de Wolf closed EJBTHREE-785.
----------------------------------


> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:04 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-786) String remove()
	method on SFSB
In-Reply-To: <10653618.1163535341622.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4332572.1193128084753.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-786?page=all ]

Carlo de Wolf closed EJBTHREE-786.
----------------------------------


> String remove() method on SFSB
> ------------------------------
>
>                 Key: EJBTHREE-786
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-786
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> I get the following exception if I try to declare a method with the signature String remove() on the local interface:
> 17:53:02,953 WARN  [ServiceController] Problem starting service jboss.j2ee:ear=MyDomain.ear,jar=MyDomain.jar,name=UserHome,service=EJB3
> java.lang.IllegalArgumentException: methods with same signature remove() but incompatible return types: void and others
> 	at sun.misc.ProxyGenerator.checkReturnTypes(ProxyGenerator.java:610)
> 	at sun.misc.ProxyGenerator.generateClassFile(ProxyGenerator.java:420)
> 	at sun.misc.ProxyGenerator.generateProxyClass(ProxyGenerator.java:306)
> 	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:501)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:58)
> 	at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:66)
> 	at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:61)
> 	at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:105)
> 	at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
> 	at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:91)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> 	at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.start(Unknown Source)
> 	at org.jboss.system.ServiceController.start(ServiceController.java:417)
> 	at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy96.start(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-815) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
In-Reply-To: <995728.1166795738121.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27402274.1193128085338.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-815?page=all ]

Carlo de Wolf closed EJBTHREE-815.
----------------------------------


> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-815
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-815
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySingleResultExceptions)
> Testcase: testQuerySingleResultExceptions took 0.058 sec
>         Caused an ERROR
> javax.persistence.NoResultException: No entity found for query
> javax.ejb.EJBException: javax.persistence.NoResultException: No entity found for query
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: javax.persistence.NoResultException: No entity found for query
>         at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:82)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySingleResultExceptions(ExceptionTestBean.java:269)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySingleResultExceptions(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySingleResultExceptions(EntityExceptionTestCa
> se.java:96)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-816) test failure -
 org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
In-Reply-To: <23148785.1166796163032.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30594639.1193128085648.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-816?page=all ]

Carlo de Wolf closed EJBTHREE-816.
----------------------------------


> test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-816
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-816
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase(testQuerySetHintAndParameter)
> Testcase: testQuerySetHintAndParameter took 0.035 sec
>         Caused an ERROR
> java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
> javax.ejb.EJBException: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
> Caused by: java.lang.IndexOutOfBoundsException: Remember that ordinal parameters are 1-based!
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterDescriptor(ParameterMetadata.java:55)
>         at org.hibernate.engine.query.ParameterMetadata.getOrdinalParameterExpectedType(ParameterMetadata.java:61)
>         at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:397)
>         at org.hibernate.impl.AbstractQueryImpl.setParameter(AbstractQueryImpl.java:369)
>         at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:234)
>         at org.jboss.ejb3.test.entityexception.ExceptionTestBean.testQuerySetHintAndParameter(ExceptionTestBean.java:311)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
>         at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
>         at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:
> 54)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263)
>         at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
>         at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681)
>         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358)
>         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412)
>         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:190)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
>         at $Proxy1.testQuerySetHintAndParameter(Unknown Source)
>         at org.jboss.ejb3.test.entityexception.unit.EntityExceptionTestCase.testQuerySetHintAndParameter(EntityExceptionTestCase.
> java:103)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:05 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-817) test failure -
 org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
In-Reply-To: <25680060.1166796342815.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4279110.1193128085853.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-817?page=all ]

Carlo de Wolf closed EJBTHREE-817.
----------------------------------


> test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-817
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-817
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase(testRuntimeException)
> Testcase: testRuntimeException took 2.058 sec
>         FAILED
> expected:<1> but was:<0>
> junit.framework.AssertionFailedError: expected:<1> but was:<0>
>         at org.jboss.ejb3.test.mdb.unit.MDBUnitTestCase.testRuntimeException(MDBUnitTestCase.java:292)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-818) test failure -
 org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
In-Reply-To: <1942068.1166797118725.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18831694.1193128086062.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-818?page=all ]

Carlo de Wolf closed EJBTHREE-818.
----------------------------------


> test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-818
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-818
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase(testRollback)
> Testcase: testRollback took 5.05 sec
>         FAILED
> null
> junit.framework.AssertionFailedError
>         at org.jboss.ejb3.test.mdbtransactions.unit.MDBUnitTestCase.testRollback(MDBUnitTestCase.java:128)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-819) test failure -
 org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
In-Reply-To: <4167073.1166798501804.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33229555.1193128086295.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-819?page=all ]

Carlo de Wolf closed EJBTHREE-819.
----------------------------------


> test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> ----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-819
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-819
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM:  Sun 1.5
>           java version "1.5.0_10"
>           Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
>           Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> EJB3 test failure - org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase(testSSLBindings)
> Testcase: testSSLBindings took 35.731 sec
>         Caused an ERROR
> Could not dereference object
> javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.remoting.CannotConnectException: Can not 
> get connection to server.  Problem establishing socket connection.]
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.ejb3.test.ssl.unit.SSLUnitTestCase.testSSLBindings(SSLUnitTestCase.java:68)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:23)
> Caused by: org.jboss.remoting.CannotConnectException: Can not get connection to server.  Problem establishing socket connection.
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:267)
>         at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
>         at org.jboss.remoting.Client.invoke(Client.java:525)
>         at org.jboss.remoting.Client.invoke(Client.java:488)
>         at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:48)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
>         at $Proxy1.createProxy(Unknown Source)
>         at org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:52)
>         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
>         at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
>         at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
>         ... 25 more
> Caused by: java.lang.reflect.InvocationTargetException
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createClientSocket(SocketClientInvoker.java:518)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.getConnection(SocketClientInvoker.java:485)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:263)
>         ... 38 more
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:742)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:678)
>         at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
>         at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2213)
>         at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2226)
>         at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2694)
>         at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:761)
>         at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
>         at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
>         at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createInputStream(ClientSocketWrapper.java:83)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
>         at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
>         ... 45 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
>         at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:723)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-838) test failure -
 org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
In-Reply-To: <8353072.1169064476539.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29568391.1193128086522.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-838?page=all ]

Carlo de Wolf closed EJBTHREE-838.
----------------------------------


> test failure - org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> -------------------------------------------------------------------
>
>                 Key: EJBTHREE-838
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-838
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: [java.version: 1.5.0_08]
> [java.vendor: BEA Systems, Inc.]
> [java.vm.version: R27.1.0-109-73164-1.5.0_08-20061129-1418-linux-ia32]
> [java.vm.name: BEA JRockit(R)]
> [java.vm.info: compiled mode]
> [os.name: Linux]
> [os.arch: i386]
> [os.version: 2.6.9-42.0.3.ELsmp]
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase
> Test:        testStackTrace
> Type:        failure
> Exception:   junit.framework.AssertionFailedError
> junit.framework.AssertionFailedError
> 	at org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testStackTrace(RemoteUnitTestCase.java:250)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:06 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-865) test failure -
 org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with
 Sun 1.5.0_11
In-Reply-To: <12695397.1170729619498.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3918439.1193128086785.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-865?page=all ]

Carlo de Wolf closed EJBTHREE-865.
----------------------------------


> test failure - org.jboss.ejb3.test.webservices.unit.WsUnitTestCase(testDeployment) - with Sun 1.5.0_11 
> -------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-865
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-865
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: Boss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.webservices.unit.WsUnitTestCase
> Test:        testDeployment
> Type:        error
> Exception:   org.jboss.deployment.DeploymentException
> Message:     Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ej
> b3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.tes
> t.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> org.jboss.deployment.DeploymentException: Could not create deployment: file:/opt/jboss-4.0.5.GA-src/ejb3/output/test-lib/webservices-ejb3.jar; - nested throwable: (org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo)
> 	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:991)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: org.jboss.ws.WSException: Could not generate wrapper type: org.jboss.ejb3.test.webservices.__JBossWS_SomeEndpointInterfaceService_SomeEndpointInterfacePort_echo
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:471)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.processWebMethod(JSR181MetaDataBuilder.java:568)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:193)
> 	at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75)
> 	at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy30.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	... 53 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: org.jboss.ws.jaxrpc.ParameterWrapping$WrapperType
> 	at javassist.CtClassType.getClassFile2(CtClassType.java:204)
> 	at javassist.CtClassType.getConstructorsCache(CtClassType.java:892)
> 	at javassist.CtClassType.getDeclaredConstructors(CtClassType.java:878)
> 	at javassist.CtNewClass.inheritAllConstructors(CtNewClass.java:87)
> 	at javassist.CtNewClass.toBytecode(CtNewClass.java:63)
> 	at javassist.CtClass.toBytecode(CtClass.java:1181)
> 	at javassist.ClassPool.toClass(ClassPool.java:883)
> 	at javassist.ClassPool.toClass(ClassPool.java:846)
> 	at org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:467)
> 	... 67 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-866) test failure -
 org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) -
 with Sun 1.5.0_11
In-Reply-To: <31270078.1170729763045.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11969895.1193128087059.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-866?page=all ]

Carlo de Wolf closed EJBTHREE-866.
----------------------------------


> test failure -  org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase (testEJBServlet) - with Sun 1.5.0_11 
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-866
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-866
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798
> OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
> JDK/JVM: Sun 1.5
>          java version "1.5.0_11"
>          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
> EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 
>            Reporter: Len DiMaggio
>         Assigned To: William DeCoste
>            Priority: Minor
>             Fix For: AS 4.2.2.GA
>
>
> Suite:       org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase
> Test:        testEJBServlet
> Type:        error
> Exception:   java.io.IOException
> Message:     Expected reply code:200, actual=500
> Expected reply code:200, actual=500
> java.io.IOException: Expected reply code:200, actual=500
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:140)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:109)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:97)
> 	at org.jboss.ejb3.test.jsp.unit.HttpUtils.accessURL(HttpUtils.java:83)
> 	at org.jboss.ejb3.test.jsp.unit.EarServletUnitTestCase.testEJBServlet(EarServletUnitTestCase.java:49)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-883) Transient
 re-injection is broken
In-Reply-To: <7687890.1171878035624.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30824092.1193128087507.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-883?page=all ]

Carlo de Wolf closed EJBTHREE-883.
----------------------------------


> Transient re-injection is broken
> --------------------------------
>
>                 Key: EJBTHREE-883
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-883
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-900) Injection of
 WebServiceContext doesn't work
In-Reply-To: <28511574.1172747349047.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33446589.1193128087731.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-900?page=all ]

Carlo de Wolf closed EJBTHREE-900.
----------------------------------


> Injection of WebServiceContext doesn't work
> -------------------------------------------
>
>                 Key: EJBTHREE-900
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-900
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.2.GA
>
>
> Injection of WebServiceContext using the @Resource annotation doesn't work.
> The following code in your bean will leave wsCts null and could lead to NullPointerExceptions.
>    @Resource
>    WebServiceContext wsCtx;

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:07 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-938) Expired messages
 are being delivered
In-Reply-To: <22096346.1175683086452.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28696158.1193128087923.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-938?page=all ]

Carlo de Wolf closed EJBTHREE-938.
----------------------------------


> Expired messages are being delivered
> ------------------------------------
>
>                 Key: EJBTHREE-938
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-938
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: mdb unit test
>            Reporter: Carlo de Wolf
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** ExpirationTestMDB onMessage 1 in org.jboss.ejb3.test.mdb.ExpirationTestMDB at 27977433
> 2007-04-04 11:58:56,566 INFO  [STDOUT] *** now = 1175680736566
> 2007-04-04 11:58:56,567 INFO  [STDOUT] *** message = SpyTextMessage {
> Header {
>    jmsDestination  : QUEUE.expirationtest
>    jmsDeliveryMode : 1
>    jmsExpiration   : 1175680735655
>    jmsPriority     : 4
>    jmsMessageID    : ID:436-11756807355552
>    jmsTimeStamp    : 1175680735555
>    jmsCorrelationID: null
>    jmsReplyTo      : null
>    jmsType         : null
>    jmsRedelivered  : false
>    jmsProperties   : {foo=bar, currentTest=testExpiration, null=null}
>    jmsPropReadWrite: false
>    msgReadOnly     : true
>    producerClientId: ID:436
> }
> Body {
>    text            :expire on server
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-986) EJB3 Remoting cause
 BindException on load
In-Reply-To: <23095690.1181134458736.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14079418.1193128088603.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-986?page=all ]

Carlo de Wolf closed EJBTHREE-986.
----------------------------------


> EJB3 Remoting cause BindException on load
> -----------------------------------------
>
>                 Key: EJBTHREE-986
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-986
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: JBoss 4.2.0 GA, JDK 1.5.0_08-b03, Windows XP SP2
>            Reporter: Yvan Borgne
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>         Attachments: ejb3-interceptors-aop.xml, InvokeRemoteInterceptor.java
>
>
> After a lot of call (>3000) to an EJB3 SLSB this exception is throwed :
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://127.0.0.1:3873/]
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy0.bar(Unknown Source)
> 	at client.Test.main(Test.java:22)
> Caused by: java.net.BindException: Address already in use: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:516)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
> 	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy0.bar(Unknown Source)
> 	at client.Test.main(Test.java:22)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
> 	... 10 more
> Jboss server and test client are on the same host.
> For each call, a new TCP connection is opened, with a different local port. So there is also a performance problem.
> Here is a simple code to reproduce :
> -- EJB3 remote Interface --
> package ejb;
> import javax.ejb.Remote;
> @Remote
> public interface Foo {
>   public void bar();
> }
> -- EJB3 Implementation --
> package ejb;
> import javax.ejb.Stateless;
> @Stateless
> public class FooBean implements Foo {
>   public void bar() {
>   }
> }
> -- client --
> package client;
> import java.util.Properties;
> import javax.naming.Context;
> import javax.naming.InitialContext;
> import ejb.Foo;
> public class Test {
>   public static void main(String[] args) {
>     try {
>       Properties env = new Properties();
>       env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
>       env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
>       env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
>       env.put("jnp.disableDiscovery", "true");
>       Context context = new InitialContext(env);
>       Foo foo = (Foo)context.lookup("FooBean/remote");
>       while(true) {
>         foo.bar();
>       }
>     } catch (Exception e) {
>       e.printStackTrace();
>     }
>   }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1003) implement
 @PoolClass for MDBs
 (minSession/maxSession does not control MDB instances)
In-Reply-To: <20325323.1183404117628.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24350606.1193128088735.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1003?page=all ]

Carlo de Wolf closed EJBTHREE-1003.
-----------------------------------


> implement @PoolClass for MDBs (minSession/maxSession does not control MDB instances)
> ------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1003
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1003
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA, Branch_4_4
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:08 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:08 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1006) EJB3 is way too
 performant on Amstrad 6218
In-Reply-To: <16542105.1183721932962.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32969984.1193128088917.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1006?page=all ]

Carlo de Wolf closed EJBTHREE-1006.
-----------------------------------


> EJB3 is way too performant on Amstrad 6218
> ------------------------------------------
>
>                 Key: EJBTHREE-1006
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1006
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: AS 4.2.1.GA
>         Environment: Amstrad 6128
>            Reporter: Dimitris Andreadis
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> Hi,
> I've just managed to install the latest EJB3 on Amstrad 6128, and it's way too fast, I cannot play my EJB3 based games.
> Could you please add a configuration parameter to make it slower?
> Thanks :)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1025) @Local and
 @Remote on a bean class must have values
In-Reply-To: <2543807.1186060789285.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8795364.1193128089815.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1025?page=all ]

Carlo de Wolf closed EJBTHREE-1025.
-----------------------------------


> @Local and @Remote on a bean class must have values
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1025
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1025
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> From the API doc:
> "When used on the bean class, declares the local business interface(s) for a session bean. When used on an interface, designates that interface as a local business interface. In this case, no value() is provided."
> Thus the following is an illegal construct:
> @Stateless
> @Local
> @Remote
> public class OrderServiceBean implements OrderService {...}

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:09 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1031) runaway SLSB
 instance creation with ThreadLocalPool
In-Reply-To: <13490824.1187375221041.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22536357.1193128089996.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1031?page=all ]

Carlo de Wolf closed EJBTHREE-1031.
-----------------------------------


> runaway SLSB instance creation with ThreadLocalPool
> ---------------------------------------------------
>
>                 Key: EJBTHREE-1031
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: Carlo de Wolf
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Use of WeakThreadLocal vs ThreadLocal is the cause.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1032) inconsistent
 results for
 CreateCount, AvailableCount, CurrentSize for StrictMaxPool SLSBs
In-Reply-To: <32360816.1187381960564.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8581101.1193128090384.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1032?page=all ]

Carlo de Wolf closed EJBTHREE-1032.
-----------------------------------


> inconsistent results for CreateCount, AvailableCount, CurrentSize for StrictMaxPool SLSBs
> -----------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1032
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1032
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - Patch 1, AS 4.2.0 GA, AS 4.2.1.GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>             Fix For: AS 4.2.2.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 04:28:10 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Tue, 23 Oct 2007 04:28:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1055) WebServiceContext
 is not injected before post construct is called
In-Reply-To: <16318321.1191406504403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22059062.1193128090601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1055?page=all ]

Carlo de Wolf closed EJBTHREE-1055.
-----------------------------------


> WebServiceContext is not injected before post construct is called
> -----------------------------------------------------------------
>
>                 Key: EJBTHREE-1055
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>             Fix For: AS 4.2.2.GA
>
>
> JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:00:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4894) port-component
	element not mapped
Message-ID: <7117396.1193130001476.JavaMail.jira@cloud.prod.atl2.jboss.com>

port-component element not mapped
---------------------------------

                 Key: JBAS-4894
                 URL: http://jira.jboss.com/jira/browse/JBAS-4894
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:04:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4894) port-component
	element not mapped
In-Reply-To: <7117396.1193130001476.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23237332.1193130241530.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4894?page=all ]

Thomas Diesler updated JBAS-4894:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
I can't find the port-component element mapped to the metadata model.

   <xsd:complexType name="generic-beanType">
      <xsd:sequence>
         <xsd:group ref="javaee:descriptionGroup"/>
         <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
         <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
         <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
         <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
         <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
         <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
         <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
      </xsd:sequence>
   </xsd:complexType>


> port-component element not mapped
> ---------------------------------
>
>                 Key: JBAS-4894
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4894
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I can't find the port-component element mapped to the metadata model.
>    <xsd:complexType name="generic-beanType">
>       <xsd:sequence>
>          <xsd:group ref="javaee:descriptionGroup"/>
>          <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
>          <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
>          <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
>          <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
>          <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
>          <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>       </xsd:sequence>
>    </xsd:complexType>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:06:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28494714.1193130365566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Thomas Diesler reassigned JBAS-4891:
------------------------------------

    Assignee: Thomas Diesler  (was: Alexey Loubyansky)

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:06:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:06:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17765485.1193130365779.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12383844 ] 
            
Thomas Diesler commented on JBAS-4891:
--------------------------------------

Let me see if this applies to jboss descriptors only ...

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:10:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 05:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Deleted: (JBAS-4894) port-component
	element not mapped
Message-ID: <33061446.1193130601470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4894?page=all ]

Thomas Diesler deleted JBAS-4894:
---------------------------------


> port-component element not mapped
> ---------------------------------
>
>                 Key: JBAS-4894
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4894
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>
> I can't find the port-component element mapped to the metadata model.
>    <xsd:complexType name="generic-beanType">
>       <xsd:sequence>
>          <xsd:group ref="javaee:descriptionGroup"/>
>          <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
>          <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
>          <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
>          <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
>          <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
>          <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
>          <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
>       </xsd:sequence>
>    </xsd:complexType>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:41:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Tue, 23 Oct 2007 05:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16503831.1193132461535.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

cheng dan reassigned JBAS-4878:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:54:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 05:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1069) persistance.xml
 with <jar-file> looks for jar file in the wrong place
In-Reply-To: <20172525.1192434603555.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22829547.1193133241746.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1069?page=all ]

Dimitris Andreadis updated EJBTHREE-1069:
-----------------------------------------

        Fix Version/s:     (was: AS 4.2.0 GA)
    Affects Version/s: AS 4.2.0 GA

> persistance.xml with <jar-file> looks for jar file in the wrong place
> ---------------------------------------------------------------------
>
>                 Key: EJBTHREE-1069
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1069
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>         Environment: JBoss AS 4.2.0.GA (Hibernate 3.3.1.GA)
>            Reporter: Magnus Sandberg
>
> When using <jar-file> references in persistance.xml the Ejb3Configuration does not look for the jar relative to the jar with the persistance.xml but relative to from where jboss is started.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 05:56:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 05:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-905)
 SessionContext.getEJBLocalObject & SessionContext.getEJBObject() fail on
 @PostConstruct
In-Reply-To: <25443719.1173215483466.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4903002.1193133361431.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-905?page=all ]

Dimitris Andreadis updated EJBTHREE-905:
----------------------------------------

    Fix Version/s: Branch_4_2
                       (was: AS 4.2.0 GA)

> SessionContext.getEJBLocalObject & SessionContext.getEJBObject() fail on @PostConstruct
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-905
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-905
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> Either call creates a new bean instance via jndi lookup. Call to getEJBLocalObject() in @PostConstruct causes infinite loop.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:03:01 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Tue, 23 Oct 2007 06:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26651825.1193133781467.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4812?page=comments#action_12383852 ] 
            
Dominik Pospisil commented on JBAS-4812:
----------------------------------------

This is NOT reproducible with current head of JBoss Cache branch 1.4.X.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:19:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 06:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4880) TECH REVIEW:
 Installation Guide - Chapter 1 -  Installing JBoss
In-Reply-To: <13326437.1192765143383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18196278.1193134741459.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4880?page=all ]

Colin Mondesir resolved JBAS-4880.
----------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
       Resolution: Done

> TECH REVIEW: Installation Guide - Chapter 1 -  Installing JBoss
> ---------------------------------------------------------------
>
>                 Key: JBAS-4880
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4880
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>             Fix For: JBossAS-4.2.2.GA
>
>         Attachments: JBAS-422-Installation_Guide-Chapter-1.odt, JBAS-422-Installation_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:21:01 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 23 Oct 2007 06:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-182) adding same node type
 twice to superstate causes exception
Message-ID: <26171474.1193134861402.JavaMail.jira@cloud.prod.atl2.jboss.com>

adding same node type twice to superstate causes exception
----------------------------------------------------------

                 Key: GPD-182
                 URL: http://jira.jboss.com/jira/browse/GPD-182
             Project: JBoss jBPM GPD
          Issue Type: Bug
          Components: jpdl
    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
            Reporter: Koen Aers
         Assigned To: Koen Aers
             Fix For: jBPM jPDL Designer 3.1.1


create empty process diagram
add superstate
add first node
add second node

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:23:07 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 23 Oct 2007 06:23:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1619) Multiple
	maximized windows
In-Reply-To: <8587201.1185976549535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28131812.1193134987568.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1619?page=all ]

Thomas Heute resolved JBPORTAL-1619.
------------------------------------

    Resolution: Done

> Multiple maximized windows
> --------------------------
>
>                 Key: JBPORTAL-1619
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature.
> If you follow the next steps:
> 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized
> 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window.
> you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window.
> If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it).
> Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:23:07 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 23 Oct 2007 06:23:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1619) Multiple
	maximized windows
In-Reply-To: <8587201.1185976549535.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15413067.1193134987961.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1619?page=comments#action_12383859 ] 
            
Thomas Heute commented on JBPORTAL-1619:
----------------------------------------

Thanks for the report

> Multiple maximized windows
> --------------------------
>
>                 Key: JBPORTAL-1619
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6 Final
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature.
> If you follow the next steps:
> 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized
> 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window.
> you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window.
> If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it).
> Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4895) JAXB based
	ServiceRef meta data
Message-ID: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>

JAXB based ServiceRef meta data
-------------------------------

                 Key: JBAS-4895
                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9936548.1193136001699.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler updated JBAS-4895:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: All service-ref based clients fail. See [JBWS-1842]

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail. See [JBWS-1842]

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:42:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5957301.1193136121478.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler updated JBAS-4895:
---------------------------------

    Description: All service-ref based clients fail.  (was: All service-ref based clients fail. See [JBWS-1842])

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:46:16 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 06:46:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4824) TECH REVIEW:
 Getting Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22426067.1193136376081.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Colin Mondesir reassigned JBAS-4824:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:52:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13387331.1193136721765.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Thomas Diesler reassigned JBAS-4891:
------------------------------------

    Assignee: Scott M Stark  (was: Thomas Diesler)

The problem seems to be related jboss descriptors that use a dtd. Generally, dtd based descriptors don't seem to support namespace attributes.

Currently schemas are not available for jboss-client.xml, jboss-web.xml that can also contain <service-qname> elements

Another point is backwards compatiblity. Folks might have AS-4.2 descriptors that use dtd based descriptors with qname elements. 

If we go back to supporting the <service-qname>{http://some-namespace}Foo</service-qname> syntax, we would have different syntaxes in the standard vs. the proprietary descriptors.

What do you think?   

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 06:58:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 06:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4896) NPE in
	JBossMetaDataWrapper
Message-ID: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in JBossMetaDataWrapper
---------------------------

                 Key: JBAS-4896
                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Scott M Stark




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:00:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 07:00:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19459601.1193137202687.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4896?page=all ]

Thomas Diesler updated JBAS-4896:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

<jboss>
  <webservices>
    <context-root>/jaxrpc-enventry</context-root>
  </webservices>
</jboss>

Caused by: java.lang.NullPointerException
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.wireOverrides(JBossMetaDataWrapper.java:247)
        at org.jboss.metadata.ejb.jboss.JBossMetaDataWrapper.<init>(JBossMetaDataWrapper.java:67)
        at org.jboss.deployment.JBossEjbParsingDeployer.parse(JBossEjbParsingDeployer.java:104)

   protected void wireOverrides()
   {
      JBossEnterpriseBeansMetaData beans = primary.getEnterpriseBeans();
      beans.setJBossMetaData(this);
   }



> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:06:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 07:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23193100.1193137561863.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4896?page=comments#action_12383876 ] 
            
Thomas Diesler commented on JBAS-4896:
--------------------------------------

BTW, I cannot build the metadata project. I suppose this is a repository issue, but

http://wiki.jboss.org/wiki/Wiki.jsp?page=Maven does not tell me how to configure this, or does it?


[tdiesler at tdvaio trunk]$ mvn
[INFO] Scanning for projects...
Downloading: http://repo1.maven.org/maven2/org/jboss/jboss-parent/3/jboss-parent-3.pom
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.jboss
ArtifactId: jboss-parent
Version: 3

Reason: Unable to download the artifact from any repository

  org.jboss:jboss-parent:pom:3

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:08:11 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 23 Oct 2007 07:08:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1195) Fix tutorial for
	2.1.0 series
In-Reply-To: <1724496.1192023483324.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3008990.1193137691952.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1195?page=all ]

Mircea Markus resolved JBCACHE-1195.
------------------------------------

    Resolution: Done

updated tutorial and updated scripts so that it runs as expcted

> Fix tutorial for 2.1.0 series
> -----------------------------
>
>                 Key: JBCACHE-1195
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>
> As a part of mavenising, the tutorial has broken.  The steps to follow in the tutorial do not produce results expected.
> Needs to be fixed for 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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:19:12 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Tue, 23 Oct 2007 07:19:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1153) Introduce a
 concept of structural nodes
In-Reply-To: <6252571.1185539387065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12960401.1193138352260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1153?page=all ]

Mircea Markus updated JBCACHE-1153:
-----------------------------------

            Fix Version/s: 2.2.0.GA
                               (was: 2.1.0.GA)
                               (was: 2.1.0.CR1)
    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121724

opened a topic on the forum and posponed to 2.2 GA
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121724

> Introduce a concept of structural nodes
> ---------------------------------------
>
>                 Key: JBCACHE-1153
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1153
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.2.0.GA
>
>
> Structural nodes should not be taken into consideration when processing regions for eviction.
> Typically are nodes that do not contain data (and are not intended to contain data), but are used to build tree structure.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:31:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 07:31:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4824) TECH REVIEW: Getting
 Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11807696.1193139061544.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Colin Mondesir updated JBAS-4824:
---------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Appendix.odt

Added a note about the Enterprise JavaBeans book from O'Reilly.

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt, JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:36:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Tue, 23 Oct 2007 07:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16108737.1193139361854.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Galder Zamarreno reassigned JBAS-4841:
--------------------------------------

    Assignee: Galder Zamarreno  (was: Brian Stansberry)

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Galder Zamarreno
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:48:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 07:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4824) TECH REVIEW:
 Getting Started Guide - Appendix A. Further Information Sources
In-Reply-To: <27170092.1192165534892.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28514600.1193140081495.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4824?page=all ]

Colin Mondesir resolved JBAS-4824.
----------------------------------

    Fix Version/s: JBossAS-4.2.2.GA
       Resolution: Done

> TECH REVIEW: Getting Started Guide - Appendix A. Further Information Sources
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-4824
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4824
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>             Fix For: JBossAS-4.2.2.GA
>
>         Attachments: JBAS-422-Getting-Started-Guide-Appendix.odt, JBAS-422-Getting-Started-Guide-Appendix.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 07:50:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 07:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4842) TECH REVIEW: Server
 Configuration Guide - TRACKER
In-Reply-To: <22836378.1192169103482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17772822.1193140201511.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4842?page=comments#action_12383889 ] 
            
Dimitris Andreadis commented on JBAS-4842:
------------------------------------------

Samson, in the respective subtasks, I see the wrong document attached to the tasks (e.g. the microkernel task has the naming document). Can you please check?

>  TECH REVIEW: Server Configuration Guide - TRACKER
> --------------------------------------------------
>
>                 Key: JBAS-4842
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4842
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 08:06:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 08:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27466405.1193141161601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris updated JBAS-4820:
-------------------------------------


Graphical Installer : (should it be identified that this is available via https://network.jboss.com ie. for subsribed users only)
ZIP download : (should it be made clear that the zip is available via both the  https://network.jboss.com with subscription, alternatively    
                              via http://labs.jboss.com/jbossas/downloads/)
RPM download (should identified that this is available via the Jboss RHN channel -http://rhn.redhat.com - for subsription users only)

I think the location where each can be quickly retrieved from is quite important for users.



> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 08:08:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 08:08:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4820) TECH REVIEW:
 Installation Guide - Chapter 2 -  Installation Alternatives
In-Reply-To: <26855101.1192162263320.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4841612.1193141281829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4820?page=all ]

Stelios Koussouris resolved JBAS-4820.
--------------------------------------

    Resolution: Done

Attached document with proposed changes

> TECH REVIEW: Installation Guide - Chapter 2 -  Installation Alternatives
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4820
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4820
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt, JBAS-422-Installation_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 2 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch02.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 08:28:01 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 23 Oct 2007 08:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-182) adding same node type
 twice to superstate causes exception
In-Reply-To: <26171474.1193134861402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16761338.1193142481395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-182?page=all ]

Koen Aers closed GPD-182.
-------------------------

    Resolution: Done

> adding same node type twice to superstate causes exception
> ----------------------------------------------------------
>
>                 Key: GPD-182
>                 URL: http://jira.jboss.com/jira/browse/GPD-182
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>            Reporter: Koen Aers
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>
> create empty process diagram
> add superstate
> add first node
> add second node

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:12 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1553) Improve google
 gadgets support
In-Reply-To: <16476033.1184001151561.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9619241.1193144953016.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1553?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1553:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Improve google gadgets support
> ------------------------------
>
>                 Key: JBPORTAL-1553
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1553
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final, 2.6 Final
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>            Priority: Optional
>             Fix For: 2.8 Final
>
>
> Parent task - Improve support for google gadgets support. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:13 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1556) Use
 'gmodules.com/ig/gadgetsettings?url=' to render google settings window
In-Reply-To: <20813385.1184001871617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12256857.1193144953579.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1556?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1556:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Use 'gmodules.com/ig/gadgetsettings?url=' to render google settings window
> --------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1556
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1556
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:14 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1558) do not append
 default parameters values when rendering gadget
In-Reply-To: <18480515.1184002116059.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4617533.1193144954373.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1558?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1558:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> do not append default parameters values when rendering gadget
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1558
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1558
>             Project: JBoss Portal
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:09:14 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:09:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1573) google
 directory query shows only 10 results
In-Reply-To: <26006578.1184166151558.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16762341.1193144954589.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1573?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1573:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> google directory query shows only 10 results
> --------------------------------------------
>
>                 Key: JBPORTAL-1573
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1573
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final, 2.6 Final
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> At the moment in Google Gadgets query against gadgets directory has hard coded limitation to to show only 10 results

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:13:02 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:13:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1561) google widget
 preferences cannot be updated after window creation
In-Reply-To: <25873473.1184018208231.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28243249.1193145182184.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1561?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1561:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> google widget preferences cannot be updated after window creation
> -----------------------------------------------------------------
>
>                 Key: JBPORTAL-1561
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1561
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final, 2.6 Final
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>            Priority: Minor
>             Fix For: 2.8 Final, 2.6.3 Final
>
>
> 1) add a google widget window to the page
> 2) go to AdminPortlet, navigate and click on the portlet window you added
> 3) there is edit window with widget preferences 
> 4) changing values and hitting 'update' does nothing

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:15:04 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1613) Refactor
 Content framework and Widget support
In-Reply-To: <24952500.1185448967039.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18248981.1193145304061.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1613?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1613:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Refactor Content framework and Widget support
> ---------------------------------------------
>
>                 Key: JBPORTAL-1613
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1613
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>    Affects Versions: 2.6.1 Final
>            Reporter: Chris Laprun
>         Assigned To: Emanuel Muckenhuber
>             Fix For: 2.8 Final
>
>
> There are several interfaces that are either duplicated or not used (when they could be: WidgetProvider is not used, ContentPortlet is under-used...).
> Several definition of edit_content mode all over the place when the definition from ContentPortlet could be used.
> Overall clean-up seems required.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:15:04 2007
From: jira-events at lists.jboss.org (Boleslaw Dawidowicz (JIRA))
Date: Tue, 23 Oct 2007 09:15:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1534) Integrate
	netvibes widgets
In-Reply-To: <31207655.1183717973218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23928202.1193145304308.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1534?page=all ]

Boleslaw Dawidowicz reassigned JBPORTAL-1534:
---------------------------------------------

    Assignee: Emanuel Muckenhuber  (was: Boleslaw Dawidowicz)

> Integrate netvibes widgets
> --------------------------
>
>                 Key: JBPORTAL-1534
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1534
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Widget
>            Reporter: Boleslaw Dawidowicz
>         Assigned To: Emanuel Muckenhuber
>            Priority: Optional
>             Fix For: 2.8 Final
>
>
> Integrate netvibes widgets into portal- similar way google gadgets are.
> http://dev.netvibes.com/doc/howto/widget_export

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:27:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 23 Oct 2007 09:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-315) Break locks for
	state transfer
Message-ID: <24844759.1193146021921.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-315?page=all ]

Manik Surtani updated JBCACHE-315:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)

Postponing pending virtual synchrony enhancements in JGroups 2.6

> Break locks for state transfer
> ------------------------------
>
>                 Key: JBCACHE-315
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-315
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.2.0.GA
>
>
> State transfer needs to acquire a lock on the root to make sure all existing TXs have been completed. However, when a TX takes more time than the lock acquisition timeout, state transfer will fail.
> Therefore, we need to forcefully acquire the locks for the state transfer by force-releasing the existing locks, and rolling back all TXs that held those locks.
> This will ensure that state transfer always succeeds, at the expense of some rolled back TXs.
> We need to investigate how this works with optimistic locking

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:27:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Tue, 23 Oct 2007 09:27:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30744775.1193146022464.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Colin Mondesir reassigned JBAS-4828:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:31:16 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Tue, 23 Oct 2007 09:31:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-905) Integrate Clover
 code coverage into hudson builds
In-Reply-To: <10530221.1166036318578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18463243.1193146276546.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-905?page=all ]

Manik Surtani updated JBCACHE-905:
----------------------------------

          Summary: Integrate Clover code coverage into hudson builds  (was: Perform code coverage analysis and add missing unit tests)
    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)
         Assignee: Manik Surtani  (was: Hany Mesha)

This was done manually in the past; changing it so it is done automatically by Hudson.

> Integrate Clover code coverage into hudson builds
> -------------------------------------------------
>
>                 Key: JBCACHE-905
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-905
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> Using a code coverage tool like Clover:
> 1) Analyse current test suite on Branch_JBossCache_1_4_0
> 2) Put up results on a wiki page
> 3) Link wiki page to this JIRA task as well as the JBossCache wiki page
> 4) Analyse gaps in the test suite and either document (on the wiki) as being too simple/obvious to test or create a unit test for this.
> Once 2.0.0 reaches CR1, perform the same on HEAD (or Branch_JBossCache_2_0_0 by then...)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:33:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 09:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7585931.1193146381646.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris reassigned JBAS-4879:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 09:52:05 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 23 Oct 2007 09:52:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4890)
 EJBAccessException: Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21397401.1193147525504.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4890?page=comments#action_12383917 ] 
            
Anil Saldhana commented on JBAS-4890:
-------------------------------------

Thomas,
  I have been waiting for some stabilization of the metamodel (which probably has happened). So I will start taking a look at this now.  We will get it done soon, in time for your Nov.1 release. :)

Anil

> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:01 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1343) Create an Ant
 task to execute a TestDriver
In-Reply-To: <15137397.1177097730166.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15576179.1193148421868.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1343?page=all ]

Julien Viet updated JBPORTAL-1343:
----------------------------------

    Assignee: Boleslaw Dawidowicz  (was: Matt Wringe)

> Create an Ant task to execute a TestDriver
> ------------------------------------------
>
>                 Key: JBPORTAL-1343
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1343
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.8 Final
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> An org.jboss.portal.common.test.driver.TestDriver is executed in Ant though the usage of the org.jboss.portal.common.test.junit.JUnitAdapter which adaps the TestDriver protocol to junit.
> It has several limitations :
> - the way to pass parameters to the test driver is convoluted and basically an hack (that works)
> - it is not possible to filter the set of tests returned by the TestDriver easily which force many times to create subclasses in order to execute each test separately

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:02 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1349) Test the test
	framework
In-Reply-To: <24874214.1177099050255.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11794439.1193148422030.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1349?page=all ]

Julien Viet updated JBPORTAL-1349:
----------------------------------

    Assignee: Julien Viet  (was: Matt Wringe)

> Test the test framework
> -----------------------
>
>                 Key: JBPORTAL-1349
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1349
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>             Fix For: 2.8 Final
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> The test framework should be itself tested.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:02 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1344) Unify the remote
 driver framework with different protocols
In-Reply-To: <19632390.1177097970204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26245713.1193148422182.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1344?page=all ]

Julien Viet updated JBPORTAL-1344:
----------------------------------

    Assignee: Julien Viet  (was: Matt Wringe)

> Unify the remote driver framework with different protocols
> ----------------------------------------------------------
>
>                 Key: JBPORTAL-1344
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1344
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Julien Viet
>             Fix For: 2.8 Final
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The framework extending the test driver framework for remoteness has 2 protocols (using the Bridge pattern) : HTTP and Web.
> It is possible to unify the two protocols using an handler mechanism that creates the next command to execute in the protocol based on a chain of responsibility.
> The benefit is to have tests that have interactions using both protocols.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:07:02 2007
From: jira-events at lists.jboss.org (Julien Viet (JIRA))
Date: Tue, 23 Oct 2007 10:07:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1346) Improve the
 parameter value handling
In-Reply-To: <29834057.1177098390300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30150423.1193148422707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1346?page=all ]

Julien Viet resolved JBPORTAL-1346.
-----------------------------------

    Resolution: Out of Date

Since it is handled differently by the new framework

> Improve the parameter value handling
> ------------------------------------
>
>                 Key: JBPORTAL-1346
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1346
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal QA
>            Reporter: Julien Viet
>         Assigned To: Matt Wringe
>             Fix For: 2.8 Final
>
>
> we have :
> MonoValuedTestParameterValue extends TestParameterValue
> MultiValuedTestParameterValue extends TestParameterValue
> and 
> TestParameterValue { public abstract Object getValue(); }
> the method getValue() should not be here : a value is either mono valued or multi valued and both have nothing in common, the code client of that needs to deal with both of them explicitely.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:09:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 23 Oct 2007 10:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16550202.1193148541843.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4812?page=all ]

Brian Stansberry updated JBAS-4812:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121968

That's good to know.  Opened a forum thread for further discussion on why this happened before you shut down any nodes.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:28:01 2007
From: jira-events at lists.jboss.org (Dominik Pospisil (JIRA))
Date: Tue, 23 Oct 2007 10:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4812) Clients getting
 javax.ejb.NoSuchEJBException when using SFSB buddy replication
In-Reply-To: <17122460.1192097224334.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3350856.1193149682000.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4812?page=all ]

Dominik Pospisil updated JBAS-4812:
-----------------------------------

    Attachment: ejb3-buddy-JBASS-4812.tgz

Attaching test log with such case.

> Clients getting javax.ejb.NoSuchEJBException when using SFSB buddy replication
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4812
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4812
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Dominik Pospisil
>         Assigned To: Brian Stansberry
>         Attachments: ejb3-buddy-JBASS-4812.tgz, ejb3-buddy.tgz
>
>
> Attaching failover test log files. Note, that clients get those errors even before simulated failover. This is reproducible only with buddy replication turned on.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:30:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4898) class-loading not
 found as a child of jboss-web
Message-ID: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>

class-loading not found as a child of jboss-web
-----------------------------------------------

                 Key: JBAS-4898
                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:34:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4898) class-loading not
 found as a child of jboss-web
In-Reply-To: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6620327.1193150041514.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4898?page=all ]

Thomas Diesler updated JBAS-4898:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test


<!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">

<jboss-web>
  <class-loading>
    <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
  </class-loading>
</jboss-web>


Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)


> class-loading not found as a child of jboss-web
> -----------------------------------------------
>
>                 Key: JBAS-4898
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
>   <class-loading>
>     <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
>   </class-loading>
> </jboss-web>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:42:05 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:42:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
Message-ID: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failed to resolve schema nsURI= location=null
---------------------------------------------

                 Key: JBAS-4899
                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Alexey Loubyansky




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:42:06 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:42:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
In-Reply-To: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19180715.1193150526557.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Thomas Diesler reassigned JBAS-4899:
------------------------------------

    Assignee: Thomas Diesler  (was: Alexey Loubyansky)

> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:48:11 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 10:48:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
In-Reply-To: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21603603.1193150891981.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Thomas Diesler updated JBAS-4899:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

         Assignee: Alexey Loubyansky  (was: Thomas Diesler)

> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 10:55:01 2007
From: jira-events at lists.jboss.org (Stale Pedersen (JIRA))
Date: Tue, 23 Oct 2007 10:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-453)
 maven-jbossaop-plugin requires
 artifact maven-jbossaop-plugin on compile classpath
In-Reply-To: <31000254.1186523875263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3305414.1193151301860.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-453?page=comments#action_12383932 ] 
            
Stale Pedersen commented on JBAOP-453:
--------------------------------------

sorry for the late response (some other issues that had higher priority before the beta release).
yes, as it is now you have to specify the dependency in the plugin and project if there is a class you inherit thats outside of the project scope. 
but afaik this is the only case where its needed and i cant see the big problem of specifing it twice as there shouldnt be many cases you need this for... 
though i can add an option that would add all project dependencies if its set, but as default i believe it shouldnt be.

> maven-jbossaop-plugin requires artifact maven-jbossaop-plugin on compile classpath
> ----------------------------------------------------------------------------------
>
>                 Key: JBAOP-453
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-453
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: maven 2
>            Reporter: Anders Andersen
>         Assigned To: Stale Pedersen
>
> In order to use the plugin I have to add the following dependencies to the client artifact dependency list.
>     <dependency>
>       <groupId>org.jboss.maven.plugins</groupId>
>       <artifactId>maven-jbossaop-plugin</artifactId>
>       <version>1.0-SNAPSHOT</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-aop</artifactId>
>       <version>2.0.0.alpha2</version>
>     </dependency>
>     <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-common</artifactId>
>       <version>4.0.2</version>
>     </dependency>
>     <dependency>
>       <groupId>concurrent</groupId>
>       <artifactId>concurrent</artifactId>
>       <version>1.3.4</version>
>     </dependency>
> This is relative wrong, because all maven internal artifacts ends up being nested dependent om the runtime artifact.
> See lists below.
> I think the statement
>       cl.addArguments(new String[] { "-cp", createClassPathList(project.getArtifacts())});
> is wrong.
> I tried to include only project.getPluginArtifacts(), but it gave me a NPE
> So I am not 100% sure what the code solution should be
> but it is not good to having maven artifacts in the resulting dependency list of the client-artifact
> list: (resulting depenency list)
> The ** marked should not be there
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.jar
> /Users/aka/.m2/repository/relaxngDatatype/relaxngDatatype/20020414/relaxngDatatype-20020414.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-opends/2.6.1-SNAPSHOT/portal-test-opends-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/isorelax/isorelax/20020414/isorelax-20020414.jar
> /Users/aka/.m2/repository/jgroups/jgroups-all/2.2.7/jgroups-all-2.2.7.jar
> /Users/aka/.m2/repository/jboss/jboss-common/4.0.2/jboss-common-4.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-xml-binding/5.0.0.Alpha/jboss-xml-binding-5.0.0.Alpha.jar
> /Users/aka/.m2/repository/jboss/jboss-cache/1.2.2/jboss-cache-1.2.2.jar
> /Users/aka/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar
> /Users/aka/.m2/repository/jboss/jboss-j2se/200504122039/jboss-j2se-200504122039.jar
> /Users/aka/.m2/repository/jboss/jbossha/4.0.2/jbossha-4.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-minimal/4.0.2/jboss-minimal-4.0.2.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-common-client/4.0.4.GA/jboss-common-client-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server/2.6.1-SNAPSHOT/portal-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-saaj/4.0.4.GA/jboss-saaj-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-system/4.0.4.GA/jboss-system-4.0.4.GA.jar
> /Users/aka/.m2/repository/xerces/xercesImpl/2.6.2/xercesImpl-2.6.2.jar
> /Users/aka/.m2/repository/org/jboss/portal/core/portal-core/2.6.1-SNAPSHOT/portal-core-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/javassist/3.4.ga/javassist-3.4.ga.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test/2.6.1-SNAPSHOT/portal-test-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/format/portal-format/2.6.1-SNAPSHOT/portal-format-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.jar
> /Users/aka/.m2/repository/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar
> /Users/aka/.m2/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> /Users/aka/.m2/repository/jboss/jboss-system/4.0.2/jboss-system-4.0.2.jar
> /Users/aka/.m2/repository/javax/mail/mail/1.4/mail-1.4.jar
> /Users/aka/.m2/repository/hibernate/hibernate/3.2.0/hibernate-3.2.0.jar
> /Users/aka/.m2/repository/jboss/jboss-j2ee/4.0.4.GA/jboss-j2ee-4.0.4.GA.jar
> /Users/aka/.m2/repository/jaxen/jaxen/1.0-FCS/jaxen-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/portal/server/portal-server-test-framework/2.6.1-SNAPSHOT/portal-server-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2.0.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-project/2.0.2/maven-project-2.0.2.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-microcontainer/4.0.4.GA/jboss-microcontainer-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common/2.6.1-SNAPSHOT/portal-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/selenium/selenium-java-client-driver/0.0/selenium-java-client-driver-0.0.jar
> /Users/aka/.m2/repository/javax/portlet/portlet-api/1.0/portlet-api-1.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/theme/portal-theme/2.6.1-SNAPSHOT/portal-theme-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.jar
> /Users/aka/.m2/repository/saxpath/saxpath/1.0-FCS/saxpath-1.0-FCS.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss/4.0.4.GA/jboss-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
> /Users/aka/.m2/repository/wsdl4j/wsdl4j/1.5.1/wsdl4j-1.5.1.jar
> /Users/aka/.m2/repository/concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/jboss/jboss-backport-concurrent/2.1.0.GA/jboss-backport-concurrent-2.1.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/server/jbosssx/4.0.4.GA/jbosssx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> /Users/aka/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> /Users/aka/.m2/repository/trove/trove/1.1-beta-5/trove-1.1-beta-5.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/2.0.0.alpha2/jboss-aop-2.0.0.alpha2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-model/2.0.2/maven-model-2.0.2.jar
> /Users/aka/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar
> /Users/aka/.m2/repository/log4j/log4j/1.2.8/log4j-1.2.8.jar
> /Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet/2.6.1-SNAPSHOT/portal-portlet-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/jboss/jboss-aspect-library/1.5/jboss-aspect-library-1.5.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-server/portal-portlet-server/2.6.1-SNAPSHOT/portal-portlet-server-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jmx/4.0.4.GA/jboss-jmx-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-impl/1.1.1/myfaces-impl-1.1.1.jar
> /Users/aka/.m2/repository/org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-metadata-2.0.2.jar
> /Users/aka/.m2/repository/jboss/jboss-aop/jboss-aop/1.5.0.GA/jboss-aop-1.5.0.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/portal-common-junit/2.6.1-SNAPSHOT/portal-common-junit-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> **/Users/aka/.m2/repository/org/apache/maven/maven-profile/2.0.2/maven-profile-2.0.2.jar
> /Users/aka/.m2/repository/org/visigoths/freemaker/freemarker/2.3.9/freemarker-2.3.9.jar
> /Users/aka/.m2/repository/org/jboss/portal/test/portal-test-agent/2.6.1-SNAPSHOT/portal-test-agent-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-dependency/4.0.4.GA/jboss-dependency-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet-federation/portal-portlet-federation/2.6.1-SNAPSHOT/portal-portlet-federation-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/msv/msv/20020414/msv-20020414.jar
> /Users/aka/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar
> /Users/aka/.m2/repository/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar
> /Users/aka/.m2/repository/slide/webdavlib/2.0/webdavlib-2.0.jar
> **/Users/aka/.m2/repository/org/jboss/maven/plugins/maven-jbossaop-plugin/1.0-SNAPSHOT/maven-jbossaop-plugin-1.0-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/web/portal-web/2.6.1-SNAPSHOT/portal-web-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/apache/myfaces/myfaces-api/1.1.1/myfaces-api-1.1.1.jar
> /Users/aka/.m2/repository/org/jboss/portal/wsrp/portal-wsrp-gen/2.6.1-SNAPSHOT/portal-wsrp-gen-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/jems/portal-jems/2.6.1-SNAPSHOT/portal-jems-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/registration/portal-registration/2.6.1-SNAPSHOT/portal-registration-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/server/jboss-jaxrpc/4.0.4.GA/jboss-jaxrpc-4.0.4.GA.jar
> /Users/aka/.m2/repository/org/jboss/portal/security/portal-security/2.6.1-SNAPSHOT/portal-security-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/api/portal-api/2.6.1-SNAPSHOT/portal-api-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/codehaus/cargo/cargo-core-uberjar/0.8/cargo-core-uberjar-0.8.jar
> /Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
> /Users/aka/.m2/repository/dom4j/dom4j/1.4/dom4j-1.4.jar
> /Users/aka/.m2/repository/org/jboss/portal/identity/portal-identity/2.6.1-SNAPSHOT/portal-identity-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/common/explode-common/2.6.1-SNAPSHOT/explode-common-2.6.1-SNAPSHOT.jar
> /Users/aka/.m2/repository/org/jboss/portal/portlet/portal-portlet-test-framework/2.6.1-SNAPSHOT/portal-portlet-test-framework-2.6.1-SNAPSHOT.jar
> **/Users/aka/.m2/repository/org/codehaus/plexus/plexus-utils/1.4.2/plexus-utils-1.4.2.jar
> /Users/aka/.m2/repository/jboss/jnpserver/3.2.3/jnpserver-3.2.3.jar
> /Users/aka/.m2/repository/opends/opends/0.0/opends-0.0.jar

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:22:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 23 Oct 2007 11:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-607) SEQUENCER: incorrect
 ordering on concurrent sends
Message-ID: <30774057.1193152921433.JavaMail.jira@cloud.prod.atl2.jboss.com>

SEQUENCER: incorrect ordering on concurrent sends
-------------------------------------------------

                 Key: JGRP-607
                 URL: http://jira.jboss.com/jira/browse/JGRP-607
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.4.1 SP5, 2.5.2, 2.6


The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:38:01 2007
From: jira-events at lists.jboss.org (Michael Newcomb (JIRA))
Date: Tue, 23 Oct 2007 11:38:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
Message-ID: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>

FLUSH not safe in simultaneous flush situation
----------------------------------------------

                 Key: JGRP-608
                 URL: http://jira.jboss.com/jira/browse/JGRP-608
             Project: JGroups
          Issue Type: Feature Request
    Affects Versions: 2.6
            Reporter: Michael Newcomb
         Assigned To: Bela Ban


I'm running into a few problems when multiple members request a FLUSH at the same time.

I am still in the process of analyzing the situation, but here are a few problems:

private void handleStartFlush(Message msg, FlushHeader fh) {
  byte oldPhase = flushPhase.transitionToFirstPhase();
  if(oldPhase == FlushPhase.START_PHASE){
    sendBlockUpToChannel();
    onStartFlush(msg.getSrc(), fh);
  }else if(oldPhase == FlushPhase.FIRST_PHASE){
    Address flushRequester = msg.getSrc();
    Address coordinator = null;
    synchronized(sharedLock){
      if(flushCoordinator != null)
        coordinator = flushCoordinator;
      else
        coordinator = flushRequester;
    }

After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().

IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().

The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.

Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.

If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.

So the following code handles that situation...

private void handleStartFlush(Message msg, FlushHeader fh) {
  ...
  }else if(oldPhase == FlushPhase.FIRST_PHASE){
    ...
    if(flushRequester.compareTo(coordinator) < 0){
      rejectFlush(fh.viewID, coordinator);
      ...
      synchronized(sharedLock){
        flushCoordinator = flushRequester;
      }
    }

If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.

I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.

I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:42:07 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 23 Oct 2007 11:42:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6722102.1193154127588.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Bela Ban reassigned JGRP-608:
-----------------------------

    Assignee: Vladimir Blagojevic  (was: Bela Ban)

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:42:07 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 23 Oct 2007 11:42:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30784152.1193154127794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Bela Ban updated JGRP-608:
--------------------------

    Fix Version/s: 2.6
         Priority: Critical  (was: Major)

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:46:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 11:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17425028.1193154361707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris updated JBAS-4822:
-------------------------------------


HI,
a few point made in this chapter:

1. There are 3 links under the Chapter header are these really necessary? The chapter is only 2 pages long
2. It is mentioned in 4.1 that the ZIP can be downloaded from http://labs.jboss.com/jbossas/downloads/ but the same document in chapter 2 it is talking about installation types for the EAP. Should we explain that this is also available from https://network.jboss.com?
3.  4.3.  Post Installation Security Configuration 
        - I found that both JMX & Web Console do not actually, in 4.2.2 ,require authentication when the installation guide says they do
        - It is mentioned that no user accounts exist, but the JBossAdmin account is present
        - The section in creating accounts/authentication is not straight forward to a new user (I propose new structure and addition of 
           enabling <security-domain> JAAS, not mentioned)

I hope this is of help

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:46:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 11:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25691630.1193154361872.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris updated JBAS-4822:
-------------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-4.odt

Attached file

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:48:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Tue, 23 Oct 2007 11:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4822) TECH REVIEW:
 Installation Guide - Chapter 4 -  Installation with ZIP Download
In-Reply-To: <10318046.1192162503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24468325.1193154481707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4822?page=all ]

Stelios Koussouris resolved JBAS-4822.
--------------------------------------

    Resolution: Done

done

> TECH REVIEW: Installation Guide - Chapter 4 -  Installation with ZIP Download
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4822
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4822
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt, JBAS-422-Installation_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 4 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch04.html

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:50:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 11:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12741129.1193154601976.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler reassigned JBAS-4895:
------------------------------------

    Assignee: Scott M Stark  (was: Thomas Diesler)

JBossServiceReferencesMetaData is probably missing. Please see dependent issue

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 11:54:12 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 23 Oct 2007 11:54:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16894414.1193154852237.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-608?page=comments#action_12383943 ] 
            
Vladimir Blagojevic commented on JGRP-608:
------------------------------------------

Michael,

I was aware of the these problems but as we were in the process of simplifying flush (JGRP-598) I never got around to verify how concurrent flush works with a revised FLUSH version. Would you please verify FLUSH.java version 1.75 that I checked in this morning and see if you still experience these problems.

Vladimir

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:09:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4900) cannot redeploy
 after deployment error
Message-ID: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>

cannot redeploy after deployment error
--------------------------------------

                 Key: JBAS-4900
                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:13:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21402911.1193155981597.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Thomas Diesler updated JBAS-4900:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"

This forces a restart of the appserver between debugging sessions.

Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
        at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
        at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
        at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
        at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
        at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
        at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
        at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
        at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
        at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
        at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
        ... 62 more
18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
...
18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

*** DEPLOYMENTS MISSING DEPLOYERS: Name

vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war

*** DEPLOYMENTS IN ERROR: Name -> Error

vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.



         Assignee: Adrian Brock

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:13:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4390989.1193155981764.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Thomas Diesler updated JBAS-4900:
---------------------------------

    Priority: Critical  (was: Major)

I put this on critical because its a major time killer.

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:30:01 2007
From: jira-events at lists.jboss.org (Michael Newcomb (JIRA))
Date: Tue, 23 Oct 2007 12:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18096460.1193157001626.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-608?page=comments#action_12383946 ] 
            
Michael Newcomb commented on JGRP-608:
--------------------------------------

I will check it out.

Upon initial inspection:

470         if(!flushInProgress){
471             flushInProgress = true;
472             sendBlockUpToChannel();
473             onStartFlush(msg.getSrc(), fh);

You might want to use an AtomicBoolean for flushInProgress and use flushInProgress.compareAndSet(false, true) as your test. As it is, it might lead to more problems because of multiple blocks going up the channel.

I do see the second problem of not notifying the winning requestor that his flush is going to be accepted has been fixed by calling onStartFlush().

484             if(flushRequester.compareTo(coordinator) < 0){
485                 rejectFlush(fh.viewID, coordinator);
486                 if(log.isDebugEnabled()){
487                     log.debug("Rejecting flush at " + localAddress
488                               + " to current flush coordinator "
489                               + coordinator
490                               + " and switching flush coordinator to "
491                               + flushRequester);
492                 }
493                 onStartFlush(flushRequester, fh);

However, the situation still exists where the flushCoordinator may not be set by the winner of the initial flushInProgress = true and another flush requestor could execute the following and flushCoordinator wasn't set yet.

477             synchronized(sharedLock){
478                 if(flushCoordinator != null)
479                     coordinator = flushCoordinator;
480                 else
481                     coordinator = flushRequester;
482             }

So, in that sense you really can't even use a boolean, you need to execute some code that sets the flushCoordinator (and other onStartFlush stuff)while checking to see if a flush is in progress (all in a protected section of code).


> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:32:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
Message-ID: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>

Reverse paths are not allowed (containing a . or ..)
----------------------------------------------------

                 Key: JBAS-4901
                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:36:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28983543.1193157361523.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Thomas Diesler updated JBAS-4901:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
This change breaks backward compatibility

IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd

To be lees strict, this should be valid

vf.findChild("foo/bar/../file.txt")

and this not

vf.findChild("foo/bar/../../../file.txt")

         Assignee: Adrian Brock

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:44:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4902) nested jar not
	deployed
Message-ID: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>

nested jar not deployed
-----------------------

                 Key: JBAS-4902
                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:46:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 12:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27013291.1193157961749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4902?page=all ]

Thomas Diesler updated JBAS-4902:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
A nested jar inside an ear is not deployed 

2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear

[tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
META-INF/
META-INF/MANIFEST.MF
jaxws-jbws1813.jar
META-INF/application.xml

<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
  
  <module>
    <java>jaxws-jbws1813.jar</java>
  </module>
  
</application>

[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
    [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

         Assignee: Scott M Stark

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:46:02 2007
From: jira-events at lists.jboss.org (Clint Popetz (JIRA))
Date: Tue, 23 Oct 2007 12:46:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-785) Local interface
 implemented by superclass
In-Reply-To: <1344938.1163535161633.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26445797.1193157962929.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-785?page=comments#action_12383952 ] 
            
Clint Popetz commented on EJBTHREE-785:
---------------------------------------

Did this fix make it into 4.2.2 GA as indicated?  Because I'm still seeing the problem with 4.2.2 that I thought was this bug, i.e. an EJB with no interfaces, but which contains an ancestor that implements an interface marked @Local:


@Local
public interface anInterface {  } 

public abstract class BaseClass implements anInterface { }

@Stateless 
public class SubClass extends BaseClass { }

still yields:

java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface: SubClass

Though the stack trace is now different:

        at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:115)
        at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.getBusinessInterfaces(EJB3InterceptorsFactory.java:172)
        at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.isBusinessMethod(EJB3InterceptorsFactory.java:122)

leading me to believe that the code in question has been updated.

> Local interface implemented by superclass
> -----------------------------------------
>
>                 Key: EJBTHREE-785
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-785
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Gavin King
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.2.GA
>
>
> Currently, local interfaces have to be directly implemented by the bean class. But it should be perfectly acceptable for a superclass of the bean class to implement them:
> 17:55:20,484 WARN  [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=MyDomain.jar
> java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
> 	at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:107)
> 	at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:115)
> 	at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:110)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:415)
> 	at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
> 	at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
> 	at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
> 	at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
> 	at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy36.create(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
> 	at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy37.create(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy6.deploy(Unknown Source)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 12:58:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 23 Oct 2007 12:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7043033.1193158681532.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Scott M Stark updated JBAS-4895:
--------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097985

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:06:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8051977.1193159161649.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=comments#action_12383957 ] 
            
Dimitris Andreadis commented on EJBTHREE-1062:
----------------------------------------------

Is there any intention of fixing this in AS 4.2.3 ?

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:16:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 13:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4903) EJB 2.1 view cannot
	be realized
Message-ID: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJB 2.1 view cannot be realized
-------------------------------

                 Key: JBAS-4903
                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:18:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 13:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4903) EJB 2.1 view cannot
	be realized
In-Reply-To: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10381561.1193159881536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4903?page=all ]

Thomas Diesler updated JBAS-4903:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test

19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
        at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
        at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
        at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
        at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)

@WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
@WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
@SOAPBinding(style = SOAPBinding.Style.RPC)
@Remote(EJB3RemoteInterface.class)
@RemoteHome(EJB3RemoteHome.class)
@RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
@Stateless(name = "FooBean01")
public class EJB3Bean01 implements EJB3RemoteInterface
{
   @WebMethod
   public String echo(String input)
   {
      return input;
   }
}


         Assignee: Carlo de Wolf

> EJB 2.1 view cannot be realized
> -------------------------------
>
>                 Key: JBAS-4903
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test
> 19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
> 19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
> 19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
> 19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
> java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
>         at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
>         at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
>         at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)
> @WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
> @WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> @Remote(EJB3RemoteInterface.class)
> @RemoteHome(EJB3RemoteHome.class)
> @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
> @Stateless(name = "FooBean01")
> public class EJB3Bean01 implements EJB3RemoteInterface
> {
>    @WebMethod
>    public String echo(String input)
>    {
>       return input;
>    }
> }

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:28:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 23 Oct 2007 13:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12589274.1193160481739.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4896?page=comments#action_12383960 ] 
            
Scott M Stark commented on JBAS-4896:
-------------------------------------

See http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenSettings for setting up the jboss repositories

> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:34:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27809378.1193160841493.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

Dimitris Andreadis reassigned JBAS-4850:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21479335.1193160961604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

Dimitris Andreadis updated JBAS-4850:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt

Attach the corrected document.

The biggest change was to remove references to the 'production' config.

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32397458.1193160961777.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4850?page=comments#action_12383962 ] 
            
Dimitris Andreadis commented on JBAS-4850:
------------------------------------------

Should I close the issue now?

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:43:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:43:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12282842.1193161383918.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

Dimitris Andreadis resolved JBAS-4850.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:45:01 2007
From: jira-events at lists.jboss.org (janssk1 (JIRA))
Date: Tue, 23 Oct 2007 13:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3040) Add
 jboss-ws4ee.sar to docs/examples/ws4ee
Message-ID: <4756350.1193161501448.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3040?page=comments#action_12383963 ] 
            
janssk1 commented on JBAS-3040:
-------------------------------

This docs/examples/ws4ee dir is not available in 4.0.5.GA.
Quite annoying..

> Add jboss-ws4ee.sar to docs/examples/ws4ee
> ------------------------------------------
>
>                 Key: JBAS-3040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3040
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>             Fix For: JBossAS-4.0.4.CR2
>
>
> The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:50:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 23 Oct 2007 13:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4856) Issues related to
 the new metadata model
In-Reply-To: <28485098.1192452063304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11694371.1193161801918.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4856?page=all ]

Thomas Diesler updated JBAS-4856:
---------------------------------

    Summary: Issues related to the new metadata model  (was: Fix web service issues related to the new metadata model)

> Issues related to the new metadata model
> ----------------------------------------
>
>                 Key: JBAS-4856
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4856
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:54:06 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:54:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-3040) Add jboss-ws4ee.sar
 to docs/examples/ws4ee
Message-ID: <15415745.1193162046320.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3040?page=all ]

Dimitris Andreadis reopened JBAS-3040:
--------------------------------------

             

> Add jboss-ws4ee.sar to docs/examples/ws4ee
> ------------------------------------------
>
>                 Key: JBAS-3040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3040
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 13:54:07 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 13:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-3040) Add jboss-ws4ee.sar to
 docs/examples/ws4ee
Message-ID: <4578148.1193162047212.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3040?page=all ]

Dimitris Andreadis closed JBAS-3040.
------------------------------------

    Fix Version/s:     (was: JBossAS-4.0.4.CR2)
       Resolution: Won't Fix

Re-open to indicate that this was actually not done.

> Add jboss-ws4ee.sar to docs/examples/ws4ee
> ------------------------------------------
>
>                 Key: JBAS-3040
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3040
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>
> The jboss-ws4ee.sar that is being replaced with the jbossws14.sar should still be available from the docs/examples/ws4ee dir of the dist so users can easily rollback to that if needed.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 14:35:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 23 Oct 2007 14:35:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <376426.1193164501589.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-608?page=comments#action_12383974 ] 
            
Vladimir Blagojevic commented on JGRP-608:
------------------------------------------

Yes you are right. flushCoordinator and flushInProgress should be in the same protected section of the code. 



> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 15:32:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Tue, 23 Oct 2007 15:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7447181.1193167921511.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=comments#action_12383989 ] 
            
Andrew Rubinger commented on EJBTHREE-1062:
-------------------------------------------

Will leave the decision to merge w/ Branch_4_2 between Dimitris and Carlo; was not ported initially as not indicated in "Fix Versions". 

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:09:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Tue, 23 Oct 2007 16:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4890) EJBAccessException:
 Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25630264.1193170141476.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4890?page=all ]

Anil Saldhana updated JBAS-4890:
--------------------------------

    JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098040

Thomas, I have added a thread for further discussion.

> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 16:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8238710.1193171761572.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis updated JBAS-4848:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt

Attach the reviewed file.

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:36:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 16:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16086461.1193171761961.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis reassigned JBAS-4848:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 16:36:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 23 Oct 2007 16:36:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12297441.1193171762229.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis resolved JBAS-4848.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:07:06 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Tue, 23 Oct 2007 18:07:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1296) Drools Release
	4.0.3
In-Reply-To: <4893834.1193101503300.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13553479.1193177226375.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1296?page=all ]

Fernando Meyer closed JBRULES-1296.
-----------------------------------

    Resolution: Done

> Drools Release 4.0.3
> --------------------
>
>                 Key: JBRULES-1296
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1296
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Fernando Meyer
>         Assigned To: Fernando Meyer
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:11:01 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
Message-ID: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow simple configuration of jbpm-mail.war.
--------------------------------------------

                 Key: JBPM-1074
                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
             Project: JBoss jBPM
          Issue Type: Feature Request
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Jboss AS
            Reporter: Chris Sweeney
         Assigned To: Tom Baeyens


Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:11:01 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
In-Reply-To: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16400254.1193177461844.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-1074?page=comments#action_12384005 ] 
            
Chris Sweeney commented on JBPM-1074:
-------------------------------------

I've attached the two files that need to be modified...

> Allow simple configuration of jbpm-mail.war.
> --------------------------------------------
>
>                 Key: JBPM-1074
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Jboss AS
>            Reporter: Chris Sweeney
>         Assigned To: Tom Baeyens
>
> Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:15:01 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
In-Reply-To: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24436158.1193177701469.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1074?page=all ]

Chris Sweeney updated JBPM-1074:
--------------------------------

    Attachment: web.xml
                InboxServlet.java

Path is jpdl/dist/src/test/resources/webapp/WEB-INF/web.xml
and
jpdl/dist/src/test/java/org/jbpm/mail/InboxServlet.java

> Allow simple configuration of jbpm-mail.war.
> --------------------------------------------
>
>                 Key: JBPM-1074
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Jboss AS
>            Reporter: Chris Sweeney
>         Assigned To: Tom Baeyens
>         Attachments: InboxServlet.java, web.xml
>
>
> Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 18:19:11 2007
From: jira-events at lists.jboss.org (Chris Sweeney (JIRA))
Date: Tue, 23 Oct 2007 18:19:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1074) Allow simple
 configuration of jbpm-mail.war.
In-Reply-To: <2552384.1193177461671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30678301.1193177951724.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1074?page=all ]

Chris Sweeney updated JBPM-1074:
--------------------------------

    Attachment: jbpm-mail.war

This is a  version that doesn't refresh the page automatically and listens on port 2525 (better for selenium testing).

> Allow simple configuration of jbpm-mail.war.
> --------------------------------------------
>
>                 Key: JBPM-1074
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1074
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Jboss AS
>            Reporter: Chris Sweeney
>         Assigned To: Tom Baeyens
>         Attachments: InboxServlet.java, jbpm-mail.war, web.xml
>
>
> Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 19:26:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 23 Oct 2007 19:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-807) Allow assignment of
 jBPM variables via EL evaluation
In-Reply-To: <31566747.1166470838937.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16747366.1193181961845.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-807?page=all ]

Ronald van Kuijk updated JBPM-807:
----------------------------------

    Fix Version/s: jBPM jPDL 3.2.3

I used seam before, I used jBPM before, but now I started using them both in one project. This feature would be really helpful. It has no 'fix version' so I put 3.2.3 on it, but not sure it is realistic. 3.3. might be. 

> Allow assignment of jBPM variables via EL evaluation
> ----------------------------------------------------
>
>                 Key: JBPM-807
>                 URL: http://jira.jboss.com/jira/browse/JBPM-807
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>            Reporter: Gavin King
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value.
> What I want is to be able to say:
> <assign variable="orderId" value="#{order.id}"/>
> when a transition occurs.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 19:50:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 23 Oct 2007 19:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-807) Allow assignment of
 jBPM variables via EL evaluation
In-Reply-To: <31566747.1166470838937.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14919659.1193183401769.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-807?page=comments#action_12384015 ] 
            
Ronald van Kuijk commented on JBPM-807:
---------------------------------------

The reason I want this is that I cannot find a good example within seam where processvariables are set. So I thought of writing a jbpm actionhandler specifically for a process that can do this.

> Allow assignment of jBPM variables via EL evaluation
> ----------------------------------------------------
>
>                 Key: JBPM-807
>                 URL: http://jira.jboss.com/jira/browse/JBPM-807
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>            Reporter: Gavin King
>         Assigned To: Tom Baeyens
>            Priority: Critical
>             Fix For: jBPM jPDL 3.2.3
>
>
> A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value.
> What I want is to be able to say:
> <assign variable="orderId" value="#{order.id}"/>
> when a transition occurs.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 20:52:10 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 20:52:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <399395.1193187130172.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-713?page=all ]

Ron Sigal updated JBREM-713:
----------------------------

    Assignee: Ron Sigal  (was: Tom  Elrod)

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 20:59:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Tue, 23 Oct 2007 20:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32085567.1193187541608.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

samson kittoli reopened JBAS-4850:
----------------------------------

             
re-opened to allow any further contributions.

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:01:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Tue, 23 Oct 2007 21:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22479020.1193187661468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli reopened JBAS-4848:
----------------------------------

             
re-opened to allow any further contribution.

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:06:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 21:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20429685.1193187961413.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384020 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

With a couple of small changes to org.jboss.remoting.transport.coyote.CoyoterInvoker, org.jboss.remoting.transport.coyote.ssl.RemotingSSLImplementation, and org.jboss.remoting.transport.coyote.ssl.RemotingSSLSupport, the http transport works with either the tomcat jars or jbossweb.jar.

Update build.xml so that tests.functional and tests.functional.core run all http related tests with both jbossweb.jar and tomcat jars.

Added jbossweb/jbossweb.jar to lib directory.  jbossweb.jar is version 2.0.0.GA.

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:12:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 21:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-825) Verify that
 CoyoteInvoker works with Apache Portable Runtime
Message-ID: <16554394.1193188321512.JavaMail.jira@cloud.prod.atl2.jboss.com>

Verify that CoyoteInvoker works with Apache Portable Runtime
------------------------------------------------------------

                 Key: JBREM-825
                 URL: http://jira.jboss.com/jira/browse/JBREM-825
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.4.0.Beta1 (Pinto)
            Reporter: Ron Sigal
         Assigned To: Trustin Lee


The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars.  When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:

21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
	at org.jboss.remoting.Client.invoke(Client.java:1632)
	at org.jboss.remoting.Client.invoke(Client.java:548)
	at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at junit.framework.TestCase.runTest(TestCase.java:154)
	at junit.framework.TestCase.runBare(TestCase.java:127)
	at junit.framework.TestResult$1.protect(TestResult.java:106)
	at junit.framework.TestResult.runProtected(TestResult.java:124)
	at junit.framework.TestResult.run(TestResult.java:109)
	at junit.framework.TestCase.run(TestCase.java:118)
	at junit.framework.TestSuite.runTest(TestSuite.java:208)
	at junit.framework.TestSuite.run(TestSuite.java:203)
	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
	... 31 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:12:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Tue, 23 Oct 2007 21:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-825) Verify that
 CoyoteInvoker works with Apache Portable Runtime
In-Reply-To: <16554394.1193188321512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10562101.1193188321631.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-825?page=all ]

Ron Sigal updated JBREM-825:
----------------------------

    Assignee:     (was: Trustin Lee)

> Verify that CoyoteInvoker works with Apache Portable Runtime
> ------------------------------------------------------------
>
>                 Key: JBREM-825
>                 URL: http://jira.jboss.com/jira/browse/JBREM-825
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>
> The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars.  When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:
> 21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
> 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
> 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
> 	at org.jboss.remoting.Client.invoke(Client.java:1632)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> 	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
> 	... 31 more

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 23 21:18:01 2007
From: jira-events at lists.jboss.org (Takayoshi Kimura (JIRA))
Date: Tue, 23 Oct 2007 21:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4893) JvmRouteValve
 (UseJK) for non session replication setup
In-Reply-To: <15617003.1193112303806.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9631690.1193188681443.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4893?page=all ]

Takayoshi Kimura updated JBAS-4893:
-----------------------------------

    Description: 
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another, JSESSIONID won't be changed
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.


  was:
Currently JBoss doesn't install JvmRouteValve for non session
replication setup. However, it's still useful in the following
scenario:

* 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
* A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
* The node AAA crashed
* The request goes node BBB, lost session, recreate another
* The node AAA recovered
* The request comes back to the node AAA, lost session again

Enabling JvmRouteValve can prevent last failure.



> JvmRouteValve (UseJK) for non session replication setup
> -------------------------------------------------------
>
>                 Key: JBAS-4893
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4893
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Takayoshi Kimura
>
> Currently JBoss doesn't install JvmRouteValve for non session
> replication setup. However, it's still useful in the following
> scenario:
> * 1 Apache HTTPD frontend and 2 JBoss AS instances without session replication, sticky session enabled
> * A request goes JBoss node AAA (JSESSIONID=xxx.AAA)
> * The node AAA crashed
> * The request goes node BBB, lost session, recreate another, JSESSIONID won't be changed
> * The node AAA recovered
> * The request comes back to the node AAA, lost session again
> Enabling JvmRouteValve can prevent last failure.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:16:06 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:16:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4821) TECH REVIEW:
 Installation Guide -
 Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28276950.1193202966325.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

cheng dan updated JBAS-4821:
----------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-3.odt

Since there is no graphical installer for 4.2.2 available now, I tested this chapter with enterprise-installer-4.2.0-2.CP01.ep1.3.jar from CSP.
1. The installer file name is not exactly.
2. During installation, language choose step is not shown.
3. Release notes step is missing in doc. 



> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:20:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4821) TECH REVIEW:
 Installation Guide
 - Chapter 3 -  Installation Using the Graphical Installer
In-Reply-To: <2628019.1192162383250.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23065425.1193203201783.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4821?page=all ]

cheng dan resolved JBAS-4821.
-----------------------------

    Resolution: Done

> TECH REVIEW: Installation Guide - Chapter 3 -  Installation Using the Graphical Installer
> -----------------------------------------------------------------------------------------
>
>                 Key: JBAS-4821
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4821
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt, JBAS-422-Installation_Guide-Chapter-3.odt
>
>
>  Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch03.html
>  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:31:03 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10477631.1193203863555.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

samson kittoli updated JBAS-4849:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:33:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32173606.1193203981407.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4849?page=comments#action_12384037 ] 
            
samson kittoli commented on JBAS-4849:
--------------------------------------

correct document attached.

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:35:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:35:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24966671.1193204101446.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

samson kittoli updated JBAS-4847:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:37:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30861959.1193204221817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

samson kittoli updated JBAS-4846:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt

transactions on JBoss file attached.

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:37:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 01:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26733902.1193204221988.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

samson kittoli updated JBAS-4845:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt

messaging on JBoss file attached

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt, JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:48:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13068076.1193204881679.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

cheng dan updated JBAS-4878:
----------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-5.odt

In linux, if JAVA_HOME didn't set, the GUI uninstaller doesn't work.
The GUI uninstaller invoke "/bin/sh -c '$JAVA_HOME/bin/java -jar /home/cdan/EnterprisePlatform-4.2.0.GA_CP01_Release/Uninstaller/uninstaller.jar'"

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt, JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 01:48:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Wed, 24 Oct 2007 01:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4878) TECH REVIEW:
 Installation Guide - Chapter 5 - Uninstall JBoss
In-Reply-To: <13205921.1192763103375.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10330210.1193204881875.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4878?page=all ]

cheng dan resolved JBAS-4878.
-----------------------------

    Resolution: Done

> TECH REVIEW: Installation Guide - Chapter 5 - Uninstall JBoss
> -------------------------------------------------------------
>
>                 Key: JBAS-4878
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4878
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Installation_Guide-Chapter-5.odt, JBAS-422-Installation_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain Chapter 5 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 02:59:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 02:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17874501.1193209141907.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

samson kittoli resolved JBAS-4848.
----------------------------------

    Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt, JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:01:01 2007
From: jira-events at lists.jboss.org (samson kittoli (JIRA))
Date: Wed, 24 Oct 2007 03:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4850) TECH REVIEW: Server
 Configuration Guide - Chapter2 - Deployment
In-Reply-To: <4709213.1192170304617.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19921518.1193209261486.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4850?page=all ]

samson kittoli resolved JBAS-4850.
----------------------------------

    Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment
> ---------------------------------------------------------------
>
>                 Key: JBAS-4850
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4850
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide - Chapter2 - Deployment.odt, JBAS-422-Server_Configuration_Guide+-+Chapter2+-+Deployment.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:16:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 24 Oct 2007 03:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-607) SEQUENCER:
 incorrect ordering on concurrent sends
In-Reply-To: <30774057.1193152921433.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20855061.1193210161605.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-607?page=comments#action_12384051 ] 
            
Bela Ban commented on JGRP-607:
-------------------------------

The bug is that, when we don't send seqnos in order, then the receiver will always keep the highest seqno, e.g. when we send
1 2 4 3, then - when 4 is received - the highest seqno will be 4 (regardless of whether there is a gap since we haven't yet received 3), and when 3 is finally received, it will get discarded.
Solution: maintain the highest received and highest delivered seqno (SeqnoTable)

Even if we synchronized down(), this wouldn't help, as 3 and 4 will get sent out in order, but a message loss of 3 might still cause receivers to receive 4 first and then the (retransmitted) 3.

> SEQUENCER: incorrect ordering on concurrent sends
> -------------------------------------------------
>
>                 Key: JGRP-607
>                 URL: http://jira.jboss.com/jira/browse/JGRP-607
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6, 2.4.1 SP5, 2.5.2
>
>
> The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:30:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 24 Oct 2007 03:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9673603.1193211001591.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=comments#action_12384052 ] 
            
Carlo de Wolf commented on EJBTHREE-1075:
-----------------------------------------

Error message must contain 'EJBTHREE-1075'.

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 03:30:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 24 Oct 2007 03:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7930100.1193211001794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=all ]

Carlo de Wolf updated EJBTHREE-1075:
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                       (was: HEAD)

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 04:13:12 2007
From: jira-events at lists.jboss.org (Jo Geraerts (JIRA))
Date: Wed, 24 Oct 2007 04:13:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1075)
 org.hibernate.hql.ast.QuerySyntaxException in
 org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds)
Message-ID: <19469021.1193213592540.JavaMail.jira@cloud.prod.atl2.jboss.com>

org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds)
----------------------------------------------------------------------------------------------------------

                 Key: JBPM-1075
                 URL: http://jira.jboss.com/jira/browse/JBPM-1075
             Project: JBoss jBPM
          Issue Type: Bug
          Components: Core Engine
    Affects Versions: jBPM jPDL 3.2.2,  jBPM jPDL 3.2.1, jBPM jPDL 3.2, jBPM jPDL 3.2 beta 2, jBPM 3.1.4
         Environment: java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)


            Reporter: Jo Geraerts
         Assigned To: Tom Baeyens


I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries. 

So we end up in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds) with the same List ( with 0 entries)

I get this Exception:

10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
ubtree [
      select distinct ti
      from org.jbpm.taskmgmt.exe.PooledActor pooledActor
           join pooledActor.taskInstances ti
      where pooledActor.actorId in (  )
        and ti.actorId is null
        and ti.isSuspended != true
        and ti.isOpen = 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

        


From jira-events at lists.jboss.org  Wed Oct 24 04:23:05 2007
From: jira-events at lists.jboss.org (Jo Geraerts (JIRA))
Date: Wed, 24 Oct 2007 04:23:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1075)
 org.hibernate.hql.ast.QuerySyntaxException in
 org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
In-Reply-To: <19469021.1193213592540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24147192.1193214185680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1075?page=all ]

Jo Geraerts updated JBPM-1075:
------------------------------

        Summary: org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)  (was: org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds))
    Description: 
I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds)  with a List with 0 entries. 

So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)

I get this Exception:

10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
ubtree [
      select distinct ti
      from org.jbpm.taskmgmt.exe.PooledActor pooledActor
           join pooledActor.taskInstances ti
      where pooledActor.actorId in (  )
        and ti.actorId is null
        and ti.isSuspended != true
        and ti.isOpen = true
  ]




  was:
I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries. 

So we end up in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds) with the same List ( with 0 entries)

I get this Exception:

10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
ubtree [
      select distinct ti
      from org.jbpm.taskmgmt.exe.PooledActor pooledActor
           join pooledActor.taskInstances ti
      where pooledActor.actorId in (  )
        and ti.actorId is null
        and ti.isSuspended != true
        and ti.isOpen = true
  ]





I reported the wrong functions.... Time for some more coffee i guess

> org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1075
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1075
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2, jBPM 3.1.4, jBPM jPDL 3.2 beta 2,  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>         Environment: java version "1.5.0_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
>            Reporter: Jo Geraerts
>         Assigned To: Tom Baeyens
>
> I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds)  with a List with 0 entries. 
> So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)
> I get this Exception:
> 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
> ubtree [
>       select distinct ti
>       from org.jbpm.taskmgmt.exe.PooledActor pooledActor
>            join pooledActor.taskInstances ti
>       where pooledActor.actorId in (  )
>         and ti.actorId is null
>         and ti.isSuspended != true
>         and ti.isOpen = 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

        


From jira-events at lists.jboss.org  Wed Oct 24 04:27:01 2007
From: jira-events at lists.jboss.org (Jo Geraerts (JIRA))
Date: Wed, 24 Oct 2007 04:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1075)
 org.hibernate.hql.ast.QuerySyntaxException in
 org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
In-Reply-To: <19469021.1193213592540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22938906.1193214421698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1075?page=all ]

Jo Geraerts updated JBPM-1075:
------------------------------

    Attachment: patch

I think this patch will fix the issue.

Sorry, it's a little verbose  but i couldnt get eclipse to make it some smaller.





> org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBPM-1075
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1075
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Core Engine
>    Affects Versions: jBPM jPDL 3.2, jBPM 3.1.4, jBPM jPDL 3.2 beta 2,  jBPM jPDL 3.2.1, jBPM jPDL 3.2.2
>         Environment: java version "1.5.0_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
>            Reporter: Jo Geraerts
>         Assigned To: Tom Baeyens
>         Attachments: patch
>
>
> I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds)  with a List with 0 entries. 
> So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)
> I get this Exception:
> 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
> ubtree [
>       select distinct ti
>       from org.jbpm.taskmgmt.exe.PooledActor pooledActor
>            join pooledActor.taskInstances ti
>       where pooledActor.actorId in (  )
>         and ti.actorId is null
>         and ti.isSuspended != true
>         and ti.isOpen = 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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:23:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13625960.1193217781788.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris updated JBAS-4879:
-------------------------------------


Chapter 6. Testing your Installation

- This geared too much towards the EAP (from what I am informed it should cover all users subscrived  & community)
- Based on that the text that appears as a result of starting the server is not representative of both as there is no "production" configuration in the community release
- Also, it goes on to explain that "production" server configuration is the default one that can be started by ./run.sh or ./rub.bat again
 non representative of both type of users. 
- I feel explaining how to start each of the configurations and then that production is only part of the EAP as well as that it will be the default one for EAP installations whilst "default" would be the default configuration fon non-EAP would be more useful
- Finally, maybe due to editor or version of editor I am unable to see figure 6.1

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt, JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:23:02 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20088643.1193217782040.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris updated JBAS-4879:
-------------------------------------

    Attachment: JBAS-422-Installation_Guide-Chapter-6.odt

File Attached

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt, JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:23:02 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4879) TECH REVIEW:
 Installation Guide - Chapter 6 -  Test Your Installation
In-Reply-To: <24207485.1192763343230.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11076814.1193217782399.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4879?page=all ]

Stelios Koussouris resolved JBAS-4879.
--------------------------------------

    Resolution: Done

Done

> TECH REVIEW: Installation Guide - Chapter 6 -  Test Your Installation
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4879
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4879
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Installation_Guide-Chapter-6.odt, JBAS-422-Installation_Guide-Chapter-6.odt
>
>
> Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide.
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 05:26:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 05:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5368537.1193217961474.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris reassigned JBAS-4826:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 06:24:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 06:24:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1034) Allow JMS
 administered objects to be created programmatically
In-Reply-To: <9067157.1186598389285.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14757411.1193221445744.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1034?page=all ]

Tim Fox updated JBMESSAGING-1034:
---------------------------------

        Summary: Allow JMS administered objects to be created programmatically  (was: Allow connection factories to be created programmatically)
    Description: We should allow connection factories, queues and topics to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI.  (was: We should allow connection factories to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI.)

> Allow JMS administered objects to be created programmatically
> -------------------------------------------------------------
>
>                 Key: JBMESSAGING-1034
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1034
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> We should allow connection factories, queues and topics to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 06:50:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 06:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-726) Create
 clustering tests for integration test suite
In-Reply-To: <1288401.1168296267440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22493791.1193223001513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-726?page=all ]

Tim Fox updated JBMESSAGING-726:
--------------------------------

              Summary: Create clustering tests for integration test suite  (was: Write/Ellect some Clustering tests to go into Integration Testsuite on ApplicationServer)
    Affects Version/s:     (was: 1.2.0.Beta1)

The AS integration test suite currently doesn't contain any JMS clustering tests.

Need to write some clustering and failover tests.

Should contain at least distributed queue, distributed topic.

Producer and consumer failover with different ack modes, transacted, auto_ack, dups_ok

> Create clustering tests for integration test suite
> --------------------------------------------------
>
>                 Key: JBMESSAGING-726
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-726
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: EAP 4.3 Integration, AS 5.0 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 06:56:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 06:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1102) JBM should use
 TransactionManagerLocator instead of the MBean API as
 that is being removed from JBAS code
In-Reply-To: <18252439.1192120804237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14149555.1193223361438.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1102?page=all ]

Tim Fox closed JBMESSAGING-1102.
--------------------------------

    Resolution: Done

> JBM should use TransactionManagerLocator instead of the MBean API as that is being removed from JBAS code
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1102
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1102
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:07:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1084) AS5
 integration code should be in AS workspace
In-Reply-To: <31013927.1190927801277.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23786202.1193224021672.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1084?page=comments#action_12384089 ] 
            
Tim Fox commented on JBMESSAGING-1084:
--------------------------------------

We currently have some dependencies on JBoss AS security implementation - need to moev this to AS codebase

> AS5 integration code  should be in AS workspace
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1084
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Anil Saldhana
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration
>
>
> It is important that the AS integration code (JBoss AS) stays in the AS workspace.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:14:04 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:14:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <33398962.1193224444665.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ]

Tim Fox updated JBMESSAGING-406:
--------------------------------

        Summary: Persistence refactoring  (was: Enabled local persistent storage per node)
    Description: 
Need to refactor persistence so each node has its own storage.

We should provide at least three local persistence manager configs:

1) JDBC local pm that works out of the box with HSQL - not recommended for production.

2) BDB based pm that customers need to download - recommended for best performance.

Should optimise for the SAN use case.

Need to consider whether we need to support replication for failover too.

  was:
Implement non shared file based persistent store.

Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this.

Also look at HOWL. http://howl.objectweb.org/


> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:18:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:18:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor
	client side model
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27792930.1193224682140.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

        Summary: Refactor client side model  (was: Refactor AOP usage)
    Description: 
Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.

Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.

We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.

The classes should be chosen to represent generic messaging, not just JMS (e.g. no need for a producer).

We also need to have an extension point so customers can add their own vanilla interceptors.

  was:
Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.

Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.

We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.


> Refactor client side model
> --------------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.
> The classes should be chosen to represent generic messaging, not just JMS (e.g. no need for a producer).
> We also need to have an extension point so customers can add their own vanilla interceptors.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:20:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:20:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18286507.1193224811635.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=comments#action_12384090 ] 
            
Tim Fox commented on JBMESSAGING-544:
-------------------------------------

The scope of this task should be extended to analsye the current wire format and alter as necessary.

A client and server side abstraction should be created allowing messages to be sent from either client or server and handlers regisstered to receive messages asynchronously.

Both synchronous and one way sends should be supported

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:22:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 07:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20795905.1193224921499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=all ]

Tim Fox updated JBMESSAGING-544:
--------------------------------

    Assignee: Jeff Mesnil  (was: Tim Fox)

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>            Priority: Critical
>             Fix For: 2.0.0 Beta 1
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 07:29:01 2007
From: jira-events at lists.jboss.org (Rainer Langbehn (JIRA))
Date: Wed, 24 Oct 2007 07:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27539266.1193225341781.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=all ]

Rainer Langbehn updated JBRULES-1273:
-------------------------------------

    Attachment: maven-drools-plugins.zip

Hi Fernando,
please take a look at the attached code.

Bye
Rainer

> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Fernando Meyer
>         Attachments: maven-drools-plugins.zip
>
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:16:02 2007
From: jira-events at lists.jboss.org (Vijesh (JIRA))
Date: Wed, 24 Oct 2007 08:16:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCLUSTER-187) Local instead of
 remote lookup happens when bean is clustered
Message-ID: <22932880.1193228162122.JavaMail.jira@cloud.prod.atl2.jboss.com>

Local instead of remote lookup happens when bean is clustered
-------------------------------------------------------------

                 Key: JBCLUSTER-187
                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-187
             Project: JBoss Clustering
          Issue Type: Bug
      Security Level: Public (Everyone can see)
         Environment: Linux/Widows 
            Reporter: Vijesh
         Assigned To: Brian Stansberry



1) Two different ejb 2.1 applications. Let's call them A1 and A2
2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.

The issue.

When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.

Expected behaviour:

In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2

Jboss; 4.0.5
jdk: 1.5_05
ejb; 2.1
stateless beans


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:16:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:16:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-373) Different
 persistance destinations for different JMS destinations
Message-ID: <28864420.1193228162331.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-373?page=all ]

Tim Fox closed JBMESSAGING-373.
-------------------------------

    Resolution: Rejected

Rejected since JBM 2 will use local storage

> Different persistance destinations for different JMS destinations
> -----------------------------------------------------------------
>
>                 Key: JBMESSAGING-373
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-373
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.0.0, 1.0.1.CR1
>            Reporter: Milena
>             Fix For: 2.0.0 Beta 1
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> We need to store the messages from different queues into a different tables, ot at least to separate them somehow.
> This is not possible with the current JBOSS Messaging as I was told.
> The motivation behind is that since we have a very high load on some of the queues, the persistance table appears a bottleneck for the rest of the messaging.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:18:01 2007
From: jira-events at lists.jboss.org (Vijesh (JIRA))
Date: Wed, 24 Oct 2007 08:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCLUSTER-187) Local instead of
 remote
 lookup happens when bean is clustered (in server to server calls)
In-Reply-To: <22932880.1193228162122.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26164995.1193228281589.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCLUSTER-187?page=all ]

Vijesh updated JBCLUSTER-187:
-----------------------------

        Summary: Local instead of remote lookup happens when bean is clustered (in server to server calls)  (was: Local instead of remote lookup happens when bean is clustered)
    Description: 
1) Two different ejb 2.1 applications. Let's call them A1 and A2
2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.

The issue.

When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.

Expected behaviour:

In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2

Jboss; 4.0.5
jdk: 1.5_05
ejb; 2.1
stateless beans


  was:

1) Two different ejb 2.1 applications. Let's call them A1 and A2
2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.

The issue.

When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.

Expected behaviour:

In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2

Jboss; 4.0.5
jdk: 1.5_05
ejb; 2.1
stateless beans



> Local instead of remote lookup happens when bean is clustered (in server to server calls)
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-187
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-187
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>         Environment: Linux/Widows 
>            Reporter: Vijesh
>         Assigned To: Brian Stansberry
>
> 1) Two different ejb 2.1 applications. Let's call them A1 and A2
> 2) Both has some common beans deployed in them (same jar). Lets call them C1, C2 etc. Each application also has their own bean: let's call them A1-a, A-b etc and A2-x, A2-y etc
> 3) A1 to A2 communication via remote call is there. And clients can call any beans (common/specific) A1 and  A2 also.
> 4) Let's say a client calls the bean  A1-a deployed in A1. A1-a in turn calls the bean C1 in application A2. Though C1 deployed in both servers are same, the data supplied them are different, so the call has to reach A2.
> The issue.
> When the beans are not clustered, call from A1-a to C1 in A2 went through as expected (in both all/default configurations).
> But when the beans are clustered, instead of calling C1 in A2, local lookup is done and invoked C1 in application A1.
> Expected behaviour:
> In both clustered and non-clustered configuration, when a remote bean look up is done from application-1 to another bean in application-2, which is also present in application-1, the call should go to application-2
> Jboss; 4.0.5
> jdk: 1.5_05
> ejb; 2.1
> stateless beans

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:18:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-314) Extend
 messaging core to be fully functioning
Message-ID: <3239503.1193228281817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ]

Tim Fox updated JBMESSAGING-314:
--------------------------------

               Summary: Extend messaging core to be fully functioning  (was: Ensure Messaging core has no dependencies on the JMS facade)
     Original Estimate:     (was: 2 days)
    Remaining Estimate:     (was: 2 days)
           Description: The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients.  (was: Messaging core still has some dependencies on the jms facade. These should be factored out.)

> Extend messaging core to be fully functioning
> ---------------------------------------------
>
>                 Key: JBMESSAGING-314
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>             Fix For: 2.0.0 Beta 1
>
>
> The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:20:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-815) Extra message
 created if server fails when send and ACK are synchronized
In-Reply-To: <5708755.1170803906788.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13573254.1193228401885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ]

Tim Fox closed JBMESSAGING-815.
-------------------------------

    Resolution: Duplicate Issue

> Extra message created if server fails when send and ACK are synchronized
> ------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-815
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-815
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.0.1.SP3
>            Reporter: Clebert Suconic
>             Fix For: 2.0.0 Beta 1
>
>
> MultiThreadFailoverTest::testFailureOnSendReceiveSynchronized fails for this bug
> This test poisons the server to wait consumer and sender to be in a same point before crashing it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:20:02 2007
From: jira-events at lists.jboss.org (Trustin Lee (JIRA))
Date: Wed, 24 Oct 2007 08:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting
	fails under load
In-Reply-To: <28762968.1192642094456.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3524353.1193228402369.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12384094 ] 
            
Trustin Lee commented on JBREM-821:
-----------------------------------

I agree with Tim that throwing a SocketException when the connection pool is exhausted doesn't make sense.  However, changing Remoting to throw RemotingException might potentially break backward compatibility although I am not sure.  Ron could clarify this.

> JBoss Remoting fails under load
> -------------------------------
>
>                 Key: JBREM-821
>                 URL: http://jira.jboss.com/jira/browse/JBREM-821
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP1
>            Reporter: Ovidiu Feodorov
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of  JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> JBoss Remoting fails with various different errors when under extreme load.
> To replicate this, set up two clustered server nodes, using a MySQL database.
> These can both be on the same machine, using ServiceBindingManager.
> On a second machine run Ovidiu's messkit toolki, first to send some messages:
> mess -stat send -size 10240 50000
> And then to receive them back using 50 concurrent consumers:
> mess -stat -sessions 50 receive all
> You will notice that JBoss Remoting fails with errors:
> I believe this is due to remoting incorrectly thinking a connection has failed and shutting down the connection. Perhaps due to the load, the ping does not get through in time to refresh the lease?
> I would like a remoting solution that *does not ping* from server to client - for us this is unnecessary.
> It also seems remoting is continually timing out and recreating connections - this could also be a source of error.
> How do we configure remoting so it does not do 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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:31:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-681) Refactor
	client side model
In-Reply-To: <27855653.1166187818679.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5210259.1193229063010.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-681?page=all ]

Tim Fox updated JBMESSAGING-681:
--------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Refactor client side model
> --------------------------
>
>                 Key: JBMESSAGING-681
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it.
> Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow.
> We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack.
> The classes should be chosen to represent generic messaging, not just JMS (e.g. no need for a producer).
> We also need to have an extension point so customers can add their own vanilla interceptors.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:31:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:31:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <1812724.1193229063131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ]

Tim Fox updated JBMESSAGING-406:
--------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:33:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-25) Microcontainer
	integration
Message-ID: <10579808.1193229181696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ]

Tim Fox updated JBMESSAGING-25:
-------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Microcontainer integration
> --------------------------
>
>                 Key: JBMESSAGING-25
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Andy Taylor
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>         Attachments: JBMESSAGING-26.tar
>
>
> We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies.
> The microcontainer can also provide MBean interfaces transparently if needed.
> This task is critical in allowing an "embedded JBM".
> This is critical to kick start ESB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 08:33:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 24 Oct 2007 08:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-544) Replace
 client-server transport with NIO based transport
In-Reply-To: <31643741.1158152193353.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29754436.1193229181948.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-544?page=all ]

Tim Fox updated JBMESSAGING-544:
--------------------------------

    Fix Version/s: 2.0.0 Alpha
                       (was: 2.0.0 Beta 1)

> Replace client-server transport with NIO based transport
> --------------------------------------------------------
>
>                 Key: JBMESSAGING-544
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Jeff Mesnil
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> For throughput and scalability we need to use a NIO model to provide connections between jms clients and server.
> Unfortunately the JBoss remoting model does not currently allows this.
> We can either drive JBoss Remoting to support this model (may take some time)
> Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
> This would also solve the problem of providing a functional and performant multiplex transport.
> Essentially we need a bidirectional channel between jms client and server.  On either end bytes can be read or witten in a non blocking fashion.
> On top of that we can introduce simple framing in order to provide multiplex functionality.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:08:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Wed, 24 Oct 2007 09:08:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4145904.1193231282109.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4828?page=comments#action_12384100 ] 
            
Colin Mondesir commented on JBAS-4828:
--------------------------------------

In section 4.4.1 is says: "you need to first of all edit the build.xml file and edit the value of jboss-dist to reflect the location where the JBoss Application Server is installed. "

In the version of the JSF-EJB3 application I have downloaded there is no "jboss-dist" in build.xml.
...
<project name="HelloWorld"
         default="main" basedir=".">
    
  <description>Hello World</description>
  <property name="projname" value="jsfejb3" />

  <property file="../build.properties"/>
  <property name="jboss.deploy"
    location="${jboss.home}/server/default/deploy"/>
...




Inaddition the build fails unless you create a "lib" directory under ".../gettingstarted/jsfejb3":
...
Buildfile: build.xml

compile:
    [javac] Compiling 4 source files to /home/cmondesir/gettingstarted/jsfejb3/build/classes

BUILD FAILED
/home/cmondesir/gettingstarted/jsfejb3/build.xml:43: /home/cmondesir/gettingstarted/jsfejb3/lib not found.
...



Otherwise all the instructions work and the application runs as described.



> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:20:06 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Wed, 24 Oct 2007 09:20:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4827) TECH REVIEW:
 Getting Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23876605.1193232006707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir reassigned JBAS-4827:
------------------------------------

    Assignee: Colin Mondesir

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:50:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 24 Oct 2007 09:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4904) Improve error
 message when binding fails
Message-ID: <21830480.1193233801646.JavaMail.jira@cloud.prod.atl2.jboss.com>

Improve error message when binding fails
----------------------------------------

                 Key: JBAS-4904
                 URL: http://jira.jboss.com/jira/browse/JBAS-4904
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Naming
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Andrew Rubinger
         Assigned To: Scott M Stark
             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA


Upon attempt to bind an a subcontext to an address already bound by an object, the following exception occurs:

java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context 
at org.jboss.util.naming.Util.createSubcontext(Util.java:69) 
at org.jboss.util.naming.Util.rebind(Util.java:125) 
at org.jboss.util.naming.Util.rebind(Util.java:113)

Error message should be in form "Can't bind subContext/obj, because subContext is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:52:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 24 Oct 2007 09:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1045) Improve error
 message when binding fails
In-Reply-To: <29362745.1188980052040.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3876232.1193233921801.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1045?page=comments#action_12384111 ] 
            
Andrew Rubinger commented on EJBTHREE-1045:
-------------------------------------------

Linked dependency

> Improve error message when binding fails
> ----------------------------------------
>
>                 Key: EJBTHREE-1045
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1045
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.1.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> 2007-09-03 14:58:50,737 WARN  [org.jboss.system.ServiceController] Problem starting service jboss.j2
> ee:ear=jbilling.ear,jar=jbilling.jar,name=com/xxx/yyy/server/item/ItemSession,service=EJB3
> java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
> 	at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
> 	at org.jboss.util.naming.Util.rebind(Util.java:125)
> 	at org.jboss.util.naming.Util.rebind(Util.java:113)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:115)
> In EJB 3 a stateful session bean can be created directly via a loopup on it's business interface. By default this one is bound to <ejb-name>/remote (or /local). The home interface is bound to <ejb-name>/home (or /localHome). If you override the JNDI name for the bean by <ejb-name> then this exception occurs. The log file should show "Binding proxy for <ejb-name> in JNDI at <jndi-name>" just before this happens.
> It should say an error message in the likes of:
> "Can't bind ItemSession/remoteHome, because ItemSession is already bound"

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:54:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Wed, 24 Oct 2007 09:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6621366.1193234041717.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Vladimir Blagojevic resolved JGRP-608.
--------------------------------------

    Resolution: Done

Commit set:
FLUSH.java 1.76


> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 09:54:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Wed, 24 Oct 2007 09:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-598) Simplify FLUSH
In-Reply-To: <10363312.1190795201069.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6211567.1193234041986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-598?page=all ]

Vladimir Blagojevic resolved JGRP-598.
--------------------------------------

    Resolution: Done

Resolved on 2.6 branch.
Commit set:
FLUSH.java 1.76


Need to be back ported to 2.5.

> Simplify FLUSH
> --------------
>
>                 Key: JGRP-598
>                 URL: http://jira.jboss.com/jira/browse/JGRP-598
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.4, 2.5
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> #1 Superfluous FLUSH-COMPLETED phase ?
> --------------------------------------
> It seems we don't need the FLUSH-COMPLETED phase, it is sufficient for
> the FLUSH leader to do a START-FLUSH and wait for all FLUSH-OK
> messages. Why ? Because the reconciliation protocol will reconcile
> messages before the view installation (or state transfer).
> Example: {A,B,C}. E sends message M and then crashes. Only C receives
> M.
> - A does a START-FLUSH
> - B and C send a FLUSH-OK back to A. This means that all multicasts
> from B will be seen by A *before* B's FLUSH-OK is received, and all
> multicasts from C will be seen by A before C's FLUSH-OK is received by
> A. HOWEVER, C will not necessarily send M to A before sending the
> FLUSH-OK message. This is only done through the reconciliation
> protocol !
> - FLUSH-COMPLETED can be removed, the digest that's part of
> FLUSH-COMPLETED has to moved to FKLUSH-OK phase.
> - FLUSH-OK is unicast *not* multicast.
> #2 Superfluous STOP-FLUSH-OK phase ?
> ------------------------------------
> Why do we need the acks here ? JGroups guarantees the STOP-FLUSH
> message is delivered to all non-faulty members, so why wait fr the
> STOP-FLUSH-OK ? 
> If we make STOP-FLUSH *OOB* (JGRP-337), then this should work ! We can
> get rid of STOP-FLUSH-OK !! Just send STOP-FLUSH as OOB multicast.
> Note: this requires the concurrent stack, so possibly check for
> concurrent stack. Throw an exception if concurrent stack is not
> present when FLUSH is used. So, these changes cannot be applied to
> 2.4, only to 2.5 and 2.6.
> #3 Timeouts
> -----------
> - ClientGmsImpl: has a hard coded timeout of 4 secs
> - CoordGmsImpl also has a timeout for block()
> - If we *need* timeouts, we should get them from the FLUSH protocol !
> CoorsGmsImpl.startFlush() should *not* have a timeout, this should be
> in FLUSH itself. startFlush() should block forever, until it gets the ack
> #4 Spurious FLUSH-OK in the diagram
> -----------------------------------
> In the JOIN diagram, probably also in the state transfer diagram

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 10:09:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 24 Oct 2007 10:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4905) Resolve EJB3 / Web
 Service integration issues
Message-ID: <10015790.1193234941460.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve EJB3 / Web Service integration issues
---------------------------------------------

                 Key: JBAS-4905
                 URL: http://jira.jboss.com/jira/browse/JBAS-4905
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
         Assigned To: Thomas Diesler
             Fix For: JBossAS-4.2.3.GA


This is a container for relevant ejb3/jbossws integration issues

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 10:58:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Wed, 24 Oct 2007 10:58:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5679608.1193237882036.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4828?page=comments#action_12384134 ] 
            
Colin Mondesir commented on JBAS-4828:
--------------------------------------

index.xhtml has a header like this: <h2>Seam POJO</h2>.
Should it not be something like <h2>JSF-EJB3 example</h2>.

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 10:58:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 10:58:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
Message-ID: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
------------------------------------------------------------------------------------

                 Key: JBAS-4906
                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Clustering, XML services
    Affects Versions: JBossAS-4.2.2.GA,  JBossAS-5.0.0.Beta3
            Reporter: Galder Zamarreno
         Assigned To: Brian Stansberry
            Priority: Minor


For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
docs/examples/binding-manager/sample-bindings.xml 

i.e.

ports-default

<service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config portName="Port" hostName="BindAddress">
<attribute name="RmiPort">1101</attribute>
<attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
<attribute name="AutoDiscoveryGroup">1102</attribute>
</delegate-config>
<binding port="1100" host="${jboss.bind.address}"/>
</service-config> 
....

ports-01

<service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config portName="Port" hostName="BindAddress">
<attribute name="RmiPort">1201</attribute>
<attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
<attribute name="AutoDiscoveryGroup">1202</attribute>
</delegate-config>
<binding port="1200" host="${jboss.bind.address}"/>
</service-config> 
...


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:11:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 11:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16320412.1193238662323.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384140 ] 
            
Brian Stansberry commented on JBAS-4906:
----------------------------------------

How would autodiscovery work if different servers are using different multicast addresses and ports?

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:11:02 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 24 Oct 2007 11:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1204) Investogate
 shutdown hook usage in an MBeanServer environment
Message-ID: <5831751.1193238662428.JavaMail.jira@cloud.prod.atl2.jboss.com>

Investogate shutdown hook usage in an MBeanServer environment
-------------------------------------------------------------

                 Key: JBCACHE-1204
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1204
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.CR1, 2.1.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:15:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 24 Oct 2007 11:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1205) Data shipped with
 NodeModified
 events different on different ccache instances in the cluster
Message-ID: <24023938.1193238901431.JavaMail.jira@cloud.prod.atl2.jboss.com>

Data shipped with NodeModified events different on different ccache instances in the cluster
--------------------------------------------------------------------------------------------

                 Key: JBCACHE-1205
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1205
             Project: JBoss Cache
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.CR1, 2.1.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:28:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Wed, 24 Oct 2007 11:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4903) EJB 2.1 view cannot
	be realized
In-Reply-To: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16314490.1193239681604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4903?page=all ]

Andrew Rubinger reassigned JBAS-4903:
-------------------------------------

    Assignee: Andrew Rubinger  (was: Carlo de Wolf)

> EJB 2.1 view cannot be realized
> -------------------------------
>
>                 Key: JBAS-4903
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Andrew Rubinger
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test
> 19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
> 19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
> 19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
> 19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
> java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
>         at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
>         at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
>         at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)
> @WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
> @WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> @Remote(EJB3RemoteInterface.class)
> @RemoteHome(EJB3RemoteHome.class)
> @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
> @Stateless(name = "FooBean01")
> public class EJB3Bean01 implements EJB3RemoteInterface
> {
>    @WebMethod
>    public String echo(String input)
>    {
>       return input;
>    }
> }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:45:12 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 11:45:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-835) revet to
 Hibernate's PersistenceXmlLoader
In-Reply-To: <26261978.1168895332931.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29840031.1193240712432.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-835?page=comments#action_12384148 ] 
            
Dimitris Andreadis commented on EJBTHREE-835:
---------------------------------------------

Is this fixed in HEAD? We use HEM 3.3.1.GA there.

> revet to Hibernate's PersistenceXmlLoader
> -----------------------------------------
>
>                 Key: EJBTHREE-835
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-835
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Bill Burke
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> The default PersistenceUnitTransactionType is JTA in Java EE and RESOURCE_LOCAL in Java SE.  Currently HEM returns RESOURCE_LOCAL no matter what.  HEM is fixed but until it revs in JBoss head, I have copied the persistence.xml parsing to EJB3 project.
> Please remove org.jboss.ejb3.entity.PersistenceXmlLoader from SVN when HEM revs and revert to Hibernate 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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:49:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 11:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-789) build.xml and
 component-info.xml - version numbers and imports need to be updated
In-Reply-To: <1955110.1163617421727.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17601904.1193240941698.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-789?page=comments#action_12384150 ] 
            
Dimitris Andreadis commented on EJBTHREE-789:
---------------------------------------------

Is this issue still current for Branch_4_2 ???

> build.xml and component-info.xml - version numbers and imports need to be updated
> ---------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-789
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-789
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Vladimir Ralev
>            Priority: Critical
>             Fix For: Branch_4_2
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The repository-zip target's comp-version, like this (use appropriate version string):
> <target name="repository-zip" depends="jars"
>     description="Create the repository.jboss.com jboss/ejb3 component contents">
>     <!-- The binary component version -->
>     <property name="comp-version" value="1.0.0.CR9-jboss4.0.5" />
>     <!-- Pack the ejb3.deployer -->
>     <zip destfile="${build.lib}/ejb3-deployer.zip">
>       <zipfileset dir="${build.lib}">
>         <include name="ejb3.deployer/**" />
>       </zipfileset>
>     </zip>
>     <!-- Create a zip file with the component structure -->
>     <zip destfile="${build.lib}/jboss-ejb3-repo.zip">
>       <!-- The component-info.xml -->
>       <zipfileset dir="${build.etc}" prefix="${comp-version}">
>         <include name="component-info.xml" />
>       </zipfileset>
>       <!-- The bin/ejb3.deployer -->
>       <zipfileset dir="${build.lib}" fullpath="${comp-version}/bin/ejb3.deployer">
>         <include name="ejb3-deployer.zip" />
>       </zipfileset>
>       <!-- The lib client jars -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/lib">
>         <include name="hibernate-client.jar" />
>         <include name="jboss-ejb3-client.jar" />
>       </zipfileset>
>       <!-- The resources deploy descriptors -->
>       <zipfileset dir="${build.lib}" prefix="${comp-version}/resources">
>         <include name="ejb3-clustered-sfsbcache-service.xml" />
>         <include name="ejb3-entity-cache-service.xml" />
>         <include name="ejb3-interceptors-aop.xml" />
>       </zipfileset>
>     </zip>
>   </target>
> and ejb3\src\etc\component-info.xml (the version attribute):
> <project name="jboss/ejb3-component-info">
>    <component id="jboss/ejb3"
>               licenseType="lgpl"
>               version="1.0.0.CR9-jboss4.0.5"
>               description="The EJB3 deployer for integration with jboss-4.0.x">
>       <artifact id="ejb3-clustered-sfsbcache-service.xml"/>
>       <artifact id="ejb3-entity-cache-service.xml"/>
>       <artifact id="ejb3-interceptors-aop.xml"/>
>       <artifact id="ejb3.deployer" />
>       <artifact id="hibernate-client.jar"/>
>       <artifact id="jboss-ejb3-client.jar"/>
>       <import componentref="javassist">
>         <compatible version="3.2.0.CR1"/>
>         <compatible version="3.2.0.CR2"/>
>       </import>
>       <import componentref="hibernate-annotations">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="hibernate-entitymanager">
>         <compatible version="3.2.0.GA"/>
>       </import>
>       <import componentref="jboss/remoting">
>         <compatible version="1.4.1_final"/>
>         <compatible version="1.4.2.GA"/>
>       </import>
>       <import componentref="jboss/aop">
>       	<compatible version="1.5.1.GA"/>
>         <compatible version="1.5.2.GA"/> <--------------- IS 1.5.2.GA COMPATIBLE?
>       </import>
>       <export>
>          <include input="hibernate-client.jar"/>
>          <include input="jboss-ejb3-client.jar"/>
>       </export>
>    </component>
> </project>

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:49:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 11:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1120) Data channel
 from
 MultiplexerChannelFactory prevents state transfers from other users of the
 shared channel
Message-ID: <2574382.1193240941938.JavaMail.jira@cloud.prod.atl2.jboss.com>

Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel
-----------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1120
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core Distributed Support
    Affects Versions: 1.4.0.GA
            Reporter: Brian Stansberry
         Assigned To: Tim Fox


JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang.

Problem is JBM's MultiplexerChannelFactory creates the data channel as follows:

public Channel createDataChannel() throws Exception
{
      return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
         new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE);
}

The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service.  JBM never calls getState(), so it *must not* pass Boolean.TRUE.  Valid usages are:

public Channel createDataChannel() throws Exception
{
      String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"};
      return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
         new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature);
}

or 

public Channel createDataChannel() throws Exception
{
      return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
         new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE);
}

The former invokes a convenience method that delegates to the latter.

Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState().  If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.)

When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState().

I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:53:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 11:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28721789.1193241181708.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384151 ] 
            
Galder Zamarreno commented on JBAS-4906:
----------------------------------------

I made the assumption that the customer was running these nodes in different 
clusters, although looking at the case again, this is not clear.

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:55:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 24 Oct 2007 11:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1273) Create a maven2
 plugin to
 allow rulebase compilation and serialization during a build (similar to the
 drools-ant task)
In-Reply-To: <18068237.1192195984477.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33368623.1193241301915.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1273?page=comments#action_12384152 ] 
            
Fernando Meyer commented on JBRULES-1273:
-----------------------------------------

Hi Rainer, I'm taking a look in your code!! :) 
regards 



> Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1273
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1273
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Rainer Langbehn
>         Assigned To: Fernando Meyer
>         Attachments: maven-drools-plugins.zip
>
>
> I already created the requested maven2 plugin and i would like to contribute it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 11:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 11:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2471582.1193241421745.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384155 ] 
            
Brian Stansberry commented on JBAS-4906:
----------------------------------------

Running the nodes in different clusters is not the standard usage of ServiceBindingManager.  We can't break the standard usage for this use case. Perhaps a wiki document explaining how to do this would be appropriate.

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:03:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 12:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4826) TECH REVIEW: Getting
 Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30343710.1193241783025.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris updated JBAS-4826:
-------------------------------------

    Attachment: JBAS-422-Getting-Started-Guide-Chapter-2.odt

Comments in the document attached

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:03:03 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 12:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4906) Add
 AutoDiscoveryAddress and
 AutoDiscoveryGroup substitutions in sample-bindings.xml
In-Reply-To: <11554664.1193237882326.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21974561.1193241783219.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4906?page=comments#action_12384159 ] 
            
Galder Zamarreno commented on JBAS-4906:
----------------------------------------

+1

Not standard usage is enough to reject it.

I'm double checking with the customer to get a better 
understanding of their use case. Should have done it 
before :$

> Add AutoDiscoveryAddress and AutoDiscoveryGroup substitutions in sample-bindings.xml
> ------------------------------------------------------------------------------------
>
>                 Key: JBAS-4906
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4906
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, XML services
>    Affects Versions:  JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Brian Stansberry
>            Priority: Minor
>
> For HAJNDI service, add AutoDiscoveryGroup and AutoDiscoveryAddress settings in
> docs/examples/binding-manager/sample-bindings.xml 
> i.e.
> ports-default
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1101</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1102</attribute>
> </delegate-config>
> <binding port="1100" host="${jboss.bind.address}"/>
> </service-config> 
> ....
> ports-01
> <service-config name="jboss:service=HAJNDI"
> delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
> <delegate-config portName="Port" hostName="BindAddress">
> <attribute name="RmiPort">1201</attribute>
> <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.1.4}</attribute>
> <attribute name="AutoDiscoveryGroup">1202</attribute>
> </delegate-config>
> <binding port="1200" host="${jboss.bind.address}"/>
> </service-config> 
> ...

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:03:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 12:03:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20519737.1193241783403.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris resolved JBAS-4826.
--------------------------------------

    Resolution: Done

Done

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:07:12 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Wed, 24 Oct 2007 12:07:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27731147.1193242032392.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

Shelly McGowan reassigned JBAS-4885:
------------------------------------

    Assignee: Shelly McGowan

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:07:12 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Wed, 24 Oct 2007 12:07:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25810647.1193242032204.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

Shelly McGowan reassigned JBAS-4844:
------------------------------------

    Assignee: Shelly McGowan

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt, JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:09:01 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Wed, 24 Oct 2007 12:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4843) TECH REVIEW: Server
 Configuration Guide - AppendixB - Use Alternative
 Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <784079.1193242141519.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

Shelly McGowan reassigned JBAS-4843:
------------------------------------

    Assignee: Shelly McGowan

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:11:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 24 Oct 2007 12:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1204) Investogate
 shutdown hook usage in an MBeanServer environment
In-Reply-To: <5831751.1193238662428.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24681982.1193242261406.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1204?page=all ]

Manik Surtani resolved JBCACHE-1204.
------------------------------------

    Resolution: Done

> Investogate shutdown hook usage in an MBeanServer environment
> -------------------------------------------------------------
>
>                 Key: JBCACHE-1204
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1204
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.CR1, 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:11:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Wed, 24 Oct 2007 12:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4829) TECH REVIEW:
 Getting Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9003905.1193242261578.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Stelios Koussouris reassigned JBAS-4829:
----------------------------------------

    Assignee: Stelios Koussouris

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:15:01 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Wed, 24 Oct 2007 12:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBBUILD-425) Fix maven bug in
	release plugin
In-Reply-To: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25446440.1193242501449.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBBUILD-425?page=all ]

Paul Gier updated JBBUILD-425:
------------------------------

    Comment: was deleted

> Fix maven bug in release plugin
> -------------------------------
>
>                 Key: JBBUILD-425
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> There is an issue when using a test-jar in during a release.
> http://jira.codehaus.org/browse/MRELEASE-285 
> This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:19:01 2007
From: jira-events at lists.jboss.org (Paul Gier (JIRA))
Date: Wed, 24 Oct 2007 12:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBBUILD-425) Fix maven bug in
 release plugin
In-Reply-To: <28500611.1193065143223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3907471.1193242741490.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBBUILD-425?page=comments#action_12384163 ] 
            
Paul Gier commented on JBBUILD-425:
-----------------------------------

This issue is caused by a bug in the maven jar plugin (http://jira.codehaus.org/browse/MJAR-75).  The current version of the jar plugin sets the wrong artifact type.  The issue is already fixed, but not released.  A version of the jar plugin with the patch should be added to the jboss repository so that it can be used by the projects that need it.

> Fix maven bug in release plugin
> -------------------------------
>
>                 Key: JBBUILD-425
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-425
>             Project: JBoss Build System
>          Issue Type: Task
>          Components: Maven
>            Reporter: Paul Gier
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> There is an issue when using a test-jar in during a release.
> http://jira.codehaus.org/browse/MRELEASE-285 
> This should be fixed since a few of our projects have dependencies like 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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:48:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 12:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5104839.1193244481831.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

Dimitris Andreadis updated JBAS-4849:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter3 - Naming_on_JBoss.odt)

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 12:53:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 12:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-609) Javadoc
	JChannelFactory
Message-ID: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>

Javadoc JChannelFactory
-----------------------

                 Key: JGRP-609
                 URL: http://jira.jboss.com/jira/browse/JGRP-609
             Project: JGroups
          Issue Type: Task
    Affects Versions: 2.5.1
            Reporter: Brian Stansberry
         Assigned To: Bela Ban


org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:00:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30940829.1193245203471.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

Dimitris Andreadis updated JBAS-4849:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt

Attached the reviewed file, really minor corrections.

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:00:03 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4849) TECH REVIEW: Server
 Configuration Guide - Chapter3 - The JBoss JMX Microkernel
In-Reply-To: <2892953.1192170304463.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30965944.1193245203811.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4849?page=all ]

Dimitris Andreadis resolved JBAS-4849.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done
         Assignee: Dimitris Andreadis

> TECH REVIEW:  Server Configuration Guide - Chapter3 - The JBoss JMX Microkernel
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4849
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4849
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt, JBAS-422-Server_Configuration_Guide-Chapter3-The_JBoss_JMX_Microkernel.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:02:15 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:02:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4848) TECH REVIEW: Server
 Configuration Guide - Chapter4 - Naming on JBoss
In-Reply-To: <23447916.1192170304313.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4608715.1193245335030.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4848?page=all ]

Dimitris Andreadis updated JBAS-4848:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter4 - Connectors_on_JBoss.odt)

> TECH REVIEW: Server Configuration Guide - Chapter4 - Naming on JBoss
> --------------------------------------------------------------------
>
>                 Key: JBAS-4848
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4848
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide+-+Chapter3+-+Naming_on_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:06:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29626567.1193245561612.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis updated JBAS-4847:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter5 - Transactions_on_JBoss.odt)

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:06:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16272103.1193245561829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis reassigned JBAS-4847:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:10:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2657363.1193245802030.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis updated JBAS-4847:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt

Attached reviewed doc. Tiny changes.

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:10:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4847) TECH REVIEW: Server
 Configuration Guide - Chapter5 - Connectors on JBoss
In-Reply-To: <30159590.1192170304172.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33252523.1193245802368.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4847?page=all ]

Dimitris Andreadis resolved JBAS-4847.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW:  Server Configuration Guide - Chapter5 - Connectors on JBoss
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4847
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4847
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter5-Connectors_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:12:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9241460.1193245921477.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis updated JBAS-4846:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter6 - Messaging_on_JBoss.odt)

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:12:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18226516.1193245921629.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis reassigned JBAS-4846:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:23:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15161788.1193246581567.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis updated JBAS-4846:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt

Attach reviewed doc. Explain that JBoss TS (JTA) is now the default transaction manager.

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:23:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 24 Oct 2007 13:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4846) TECH REVIEW: Server
 Configuration Guide - Chapter6 - Transactions on JBoss
In-Reply-To: <3257569.1192170304024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8528339.1193246581856.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4846?page=all ]

Dimitris Andreadis resolved JBAS-4846.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

> TECH REVIEW:  Server Configuration Guide - Chapter6 - Transactions on JBoss
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4846
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4846
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter6-Transactions_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:48:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 13:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1078)
 EJB3InterceptorsFactory.createPerJoinpoint() should log String
 representation of Array, not Array reference
Message-ID: <5384765.1193248081989.JavaMail.jira@cloud.prod.atl2.jboss.com>

EJB3InterceptorsFactory.createPerJoinpoint() should log String representation of Array, not Array reference
-----------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1078
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1078
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3
            Reporter: Galder Zamarreno


EJB3InterceptorsFactory.createPerJoinpoint()

InterceptorInfo[] infos = container.getInterceptorRepository().getBusinessInterceptors(container, method);
...
log.debug("Bound interceptors for joinpoint: " + method + " - " + infos);

The log message is meaningless. It will print an array reference.

This should be instead:

log.debug("Bound interceptors for joinpoint: " + method + " - " + Arrays.toString(infos));

InterceptorInfo implements toString()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 13:48:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 13:48:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1078)
 EJB3InterceptorsFactory.createPerJoinpoint() should log String
 representation of Array, not Array reference
In-Reply-To: <5384765.1193248081989.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6269592.1193248082365.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1078?page=all ]

Galder Zamarreno reassigned EJBTHREE-1078:
------------------------------------------

    Assignee: Carlo de Wolf

> EJB3InterceptorsFactory.createPerJoinpoint() should log String representation of Array, not Array reference
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1078
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1078
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 5.0.0.Beta3, AS 4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> EJB3InterceptorsFactory.createPerJoinpoint()
> InterceptorInfo[] infos = container.getInterceptorRepository().getBusinessInterceptors(container, method);
> ...
> log.debug("Bound interceptors for joinpoint: " + method + " - " + infos);
> The log message is meaningless. It will print an array reference.
> This should be instead:
> log.debug("Bound interceptors for joinpoint: " + method + " - " + Arrays.toString(infos));
> InterceptorInfo implements toString()

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:16:04 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 24 Oct 2007 14:16:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4907) JDK logging levels
 don't match our standard levels
Message-ID: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>

JDK logging levels don't match our standard levels
--------------------------------------------------

                 Key: JBAS-4907
                 URL: http://jira.jboss.com/jira/browse/JBAS-4907
             Project: JBoss Application Server
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: David Lloyd
         Assigned To: Scott M Stark
             Fix For:  JBossAS-5.0.0.Beta3


The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.

Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:18:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 24 Oct 2007 14:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4907) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12273488.1193249881463.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4907?page=all ]

David Lloyd updated JBAS-4907:
------------------------------

    Attachment: JBAS-4907.patch

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBAS-4907
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4907
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: David Lloyd
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:20:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 14:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1079)
 Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or
 jboss.xml was included in the deployment
Message-ID: <15539969.1193250002098.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or jboss.xml was included in the deployment
---------------------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1079
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1079
             Project: EJB 3.0
          Issue Type: Feature Request
    Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3
            Reporter: Galder Zamarreno
         Assigned To: Carlo de Wolf


Ejb3HandlerFactory.getInstance() could do with some DEBUG logging to 
indicate whether an ejb-jar.xml and/or jboss.xml was included in the 
deployment or not.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 14:20:02 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Wed, 24 Oct 2007 14:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1079)
 Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or
 jboss.xml was included in the deployment
In-Reply-To: <15539969.1193250002098.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16153257.1193250002329.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1079?page=all ]

Galder Zamarreno updated EJBTHREE-1079:
---------------------------------------

    Issue Type: Task  (was: Feature Request)

> Ejb3HandlerFactory.getInstance() should log whether ejb-jar.xml and/or jboss.xml was included in the deployment
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1079
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1079
>             Project: EJB 3.0
>          Issue Type: Task
>    Affects Versions: AS 5.0.0.Beta3, AS 4.2.2.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Carlo de Wolf
>
> Ejb3HandlerFactory.getInstance() could do with some DEBUG logging to 
> indicate whether an ejb-jar.xml and/or jboss.xml was included in the 
> deployment or not.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:04:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 24 Oct 2007 15:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4907) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7872899.1193252641772.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4907?page=comments#action_12384202 ] 
            
David Lloyd commented on JBAS-4907:
-----------------------------------

Forgot to add - if you want me to NOT apply this, say so in the next day or two.  Otherwise I'll do it.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBAS-4907
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4907
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-5.0.0.Beta2
>            Reporter: David Lloyd
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:10:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 24 Oct 2007 15:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Moved: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26092302.1193253001615.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

Scott M Stark moved JBAS-4907 to JBCOMMON-39:
---------------------------------------------

              Project: JBoss Common  (was: JBoss Application Server)
                  Key: JBCOMMON-39  (was: JBAS-4907)
          Component/s: common-logging-jdk
                           (was: Logging)
        Fix Version/s: 2.2.3.GA
                           (was:  JBossAS-5.0.0.Beta3)
    Affects Version/s: 2.2.2.GA
                           (was: JBossAS-5.0.0.Beta2)

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: Scott M Stark
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:10:02 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 24 Oct 2007 15:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCOMMON-39) JDK logging
 levels don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16934860.1193253002252.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

Scott M Stark reassigned JBCOMMON-39:
-------------------------------------

    Assignee: David Lloyd  (was: Scott M Stark)

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:18:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1121) Allow command
 line configuration of ServerPeerID
Message-ID: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow command line configuration of ServerPeerID
------------------------------------------------

                 Key: JBMESSAGING-1121
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
            Reporter: Brian Stansberry
         Assigned To: Tim Fox
             Fix For: AS 5.0 Integration, EAP 4.3 Integration


The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.

Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:21:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4908) Update
 sample-bindings.xml to
 reflect use of -beans.xml instead of -service.xml for clustering services.
Message-ID: <1718009.1193253661440.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update sample-bindings.xml to reflect use of -beans.xml instead of -service.xml for clustering services.
--------------------------------------------------------------------------------------------------------

                 Key: JBAS-4908
                 URL: http://jira.jboss.com/jira/browse/JBAS-4908
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Critical
             Fix For: JBossAS-5.0.0.CR1


The current file assumes things like HA-JNDI are mbeans.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:23:06 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Wed, 24 Oct 2007 15:23:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14425624.1193253786971.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384204 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1121:
----------------------------------------------

If you configure it as: 

 <attribute name="ServerPeerID">${server.peer.id}</attribute>

and then define "server.peer.id" system property with -Dserver.peer.id=77 (or whatever) , it works.






> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:27:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 24 Oct 2007 15:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-818) Release
	2.2.2.GA_CP01
In-Reply-To: <12204903.1192079883249.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16599076.1193254021717.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-818?page=comments#action_12384205 ] 
            
Ron Sigal commented on JBREM-818:
---------------------------------

Branch remoting_2_2_2_GA_CP has been tagged remoting_2_2_2_CP01.

> Release 2.2.2.GA_CP01
> ---------------------
>
>                 Key: JBREM-818
>                 URL: http://jira.jboss.com/jira/browse/JBREM-818
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA_CP01
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.GA_CP01
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:29:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4909) Remove
 JBMESSAGING-1120 workaround in JChannelFactory
Message-ID: <25619793.1193254141623.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove JBMESSAGING-1120 workaround in JChannelFactory
-----------------------------------------------------

                 Key: JBAS-4909
                 URL: http://jira.jboss.com/jira/browse/JBAS-4909
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions:  JBossAS-5.0.0.Beta3
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For: JBossAS-5.0.0.CR1


As a workaround to JBMESSAGING-1120, in org.jboss.ha.framework.server.JChannelFactory I disabled the ability to call set register_for_state_transfer to true when creating a multiplexer channel.  This JIRA is a reminder to remove the workaround once a fixed JBM release is integrated.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:33:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 15:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10942191.1193254381473.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384208 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

Right; this JIRA is a request to have the official property name defined and that system property substitution syntax added in the standard file that's integrated into the AS.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 15:58:13 2007
From: jira-events at lists.jboss.org (Michal Bali (JIRA))
Date: Wed, 24 Oct 2007 15:58:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
Message-ID: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>

DroolsCompilerAntTask.java should reset threadContextLoader to original value
-----------------------------------------------------------------------------

                 Key: JBRULES-1297
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Michal Bali


DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:02:01 2007
From: jira-events at lists.jboss.org (Michal Bali (JIRA))
Date: Wed, 24 Oct 2007 16:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
In-Reply-To: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7255356.1193256121416.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1297?page=all ]

Michal Bali updated JBRULES-1297:
---------------------------------

    Attachment: droolsAntClasspathFixPatch.txt

This patch should be applied on DroolsCompilerAntTask.java
It modifies the main execute() method to call loader.resetThreadContextLoader();
I can write some tests if needed.

> DroolsCompilerAntTask.java should reset threadContextLoader to original value
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-1297
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Bali
>         Attachments: droolsAntClasspathFixPatch.txt
>
>
> DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:10:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:10:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-113) support qname syntax
 {nsURI}localPart
Message-ID: <29512214.1193256601419.JavaMail.jira@cloud.prod.atl2.jboss.com>

support qname syntax {nsURI}localPart
-------------------------------------

                 Key: JBXB-113
                 URL: http://jira.jboss.com/jira/browse/JBXB-113
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Bug
    Affects Versions: JBossXB-1.0.0.SP1, JBossXB-2.0.0.CR4
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-2.0.0.CR5


Currently QName values in XML are supposed to follow syntax [prefix:]localPart. When the nsURI is not registered then the QName should be marshalled as {nsURI}localPart.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:12:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBXB-113) support qname syntax
 {nsURI}localPart
In-Reply-To: <29512214.1193256601419.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11688129.1193256721490.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-113?page=all ]

Alexey Loubyansky updated JBXB-113:
-----------------------------------

    Fix Version/s: JBossXB-1.0.0.SP2

> support qname syntax {nsURI}localPart
> -------------------------------------
>
>                 Key: JBXB-113
>                 URL: http://jira.jboss.com/jira/browse/JBXB-113
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4, JBossXB-1.0.0.SP1
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5, JBossXB-1.0.0.SP2
>
>
> Currently QName values in XML are supposed to follow syntax [prefix:]localPart. When the nsURI is not registered then the QName should be marshalled as {nsURI}localPart.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:12:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-113) support qname syntax
 {nsURI}localPart
In-Reply-To: <29512214.1193256601419.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18835227.1193256721617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-113?page=all ]

Alexey Loubyansky closed JBXB-113.
----------------------------------

    Resolution: Done

> support qname syntax {nsURI}localPart
> -------------------------------------
>
>                 Key: JBXB-113
>                 URL: http://jira.jboss.com/jira/browse/JBXB-113
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4, JBossXB-1.0.0.SP1
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5, JBossXB-1.0.0.SP2
>
>
> Currently QName values in XML are supposed to follow syntax [prefix:]localPart. When the nsURI is not registered then the QName should be marshalled as {nsURI}localPart.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:14:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 24 Oct 2007 16:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-817) Release 2.2.2.SP2
In-Reply-To: <27905809.1191969183754.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23687507.1193256841613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-817?page=all ]

Ron Sigal closed JBREM-817.
---------------------------

    Resolution: Done

This release was targeted for JBossAS 5.0.0.Beta3, which is currently using it.

> Release 2.2.2.SP2
> -----------------
>
>                 Key: JBREM-817
>                 URL: http://jira.jboss.com/jira/browse/JBREM-817
>             Project: JBoss Remoting
>          Issue Type: Release
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.2.2.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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:18:03 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 24 Oct 2007 16:18:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4890) EJBAccessException:
 Caller unauthorized
In-Reply-To: <17710985.1193054283354.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32637170.1193257083576.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4890?page=all ]

Anil Saldhana closed JBAS-4890.
-------------------------------

    Resolution: Done

Fixed. With the following rollback:
====================================
asaldhana~/jboss-5.0/jboss-head/tomcat/src/main/org/jboss/web/tomcat/security>svn ci -m "JBAS-4890: rollback change made by Scott during JBAS-4506 with RunAsIdentity push"
Sending        security\RunAsListener.java
Transmitting file data .
Committed revision 66397.
====================================


The test should pass now:
=================
asaldhana~/jbossws/stack/native/jbossws-native-2.0.2>ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase one-test
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 19.657 sec

BUILD SUCCESSFUL
Total time: 21 seconds
===================

> EJBAccessException: Caller unauthorized
> ---------------------------------------
>
>                 Key: JBAS-4890
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4890
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 9.324 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED
> 13:54:48,658 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
> javax.ejb.EJBAccessException: Caller unauthorized
>         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:170)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:181)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:104)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:412)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
>         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
>         at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:695)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 16:22:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 24 Oct 2007 16:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4891) Cannot unmarshall
 qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26600700.1193257321714.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4891?page=comments#action_12384224 ] 
            
Alexey Loubyansky commented on JBAS-4891:
-----------------------------------------

I just added support for {nsURI}localPart syntax.

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 17:04:11 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 24 Oct 2007 17:04:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1769) Portlet
 disappears in IE 7.0 after it is maximized
In-Reply-To: <5630938.1192823043338.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6097854.1193259851645.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1769?page=comments#action_12384230 ] 
            
Thomas Heute commented on JBPORTAL-1769:
----------------------------------------

I played again hard on the demo box, with IE 7.0.6000.16546 without experiening anything odd.
I added a portlet on the default page and hit the maximize/minimize/normal buttons for a while. Nothing.

> Portlet disappears in IE 7.0 after it is maximized
> --------------------------------------------------
>
>                 Key: JBPORTAL-1769
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1769
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Portlet
>    Affects Versions: 2.6.1 Final
>         Environment: Windows XP, Internet Explorer 7.0
>            Reporter: krish p
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>
> I am not able to reproduce the exact issue in this build, http://portal.demo.jboss.com/portal/default but I can definitely see related issues.
> Essentially, this is the problem:
> * Add a portlet on the page.
> * Maximize it, restore it, minimize it, and keep doing this a few times, and at some point, the portlet disappears for the user and cannot ever be restored (unless the portlet is chosen to be added again, and even in that case, it fails occasionally).
> After doing a fair bit of testing, I've narrowed down the test case to the following:
> * This does NOT reproduce in Firefox and happens only in IE
> * Even in IE, it happens ONLY when clicking on the maximize/minimize/restore events DOES NOT work the first time. 
> I am able to see the exact the same issue in the http://portal.demo.jboss.com/portal/default build in IE. The portlet events do not work unless repetitively tried, and in our case, the portlet disappears exactly at that point. In other words, when the portlet event does not get kicked off the first time when the portlet is in the maximized mode, the portlet ends up disappearing when we repeatedly click on that event (be it minimize or restore).
> It is a little painful to reproduce this but the problem does exist in IE. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 17:44:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 17:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1206) Improve cloning of
 configuration elements
Message-ID: <5658005.1193262241644.JavaMail.jira@cloud.prod.atl2.jboss.com>

Improve cloning of configuration elements
-----------------------------------------

                 Key: JBCACHE-1206
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1206
             Project: JBoss Cache
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA, 2.1.0.BETA1
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
            Priority: Minor
             Fix For: 2.1.0.CR1


Ensure it's a deep clone operation; no shared references to subcomponents or any other mutable elements should come out of cloning a parent component.

Implement "public XYZ clone()" wherever possible, where XYZ is the type of the class (i.e. don't just rely on superclass' "public ConfigurationComponent clone()").

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 18:01:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 24 Oct 2007 18:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1206) Improve cloning of
 configuration elements
In-Reply-To: <5658005.1193262241644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1181902.1193263261457.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1206?page=all ]

Brian Stansberry closed JBCACHE-1206.
-------------------------------------

    Resolution: Done

> Improve cloning of configuration elements
> -----------------------------------------
>
>                 Key: JBCACHE-1206
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1206
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 2.1.0.BETA1
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.1.0.CR1
>
>
> Ensure it's a deep clone operation; no shared references to subcomponents or any other mutable elements should come out of cloning a parent component.
> Implement "public XYZ clone()" wherever possible, where XYZ is the type of the class (i.e. don't just rely on superclass' "public ConfigurationComponent clone()").

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 18:15:01 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 24 Oct 2007 18:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1080) create tutorial
 for customizing ejb3-interceptors-aop.xml
Message-ID: <571489.1193264101537.JavaMail.jira@cloud.prod.atl2.jboss.com>

create tutorial for customizing ejb3-interceptors-aop.xml
---------------------------------------------------------

                 Key: EJBTHREE-1080
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1080
             Project: EJB 3.0
          Issue Type: Task
          Components: Documentation
            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

        


From jira-events at lists.jboss.org  Wed Oct 24 19:45:05 2007
From: jira-events at lists.jboss.org (Jay Howell (JIRA))
Date: Wed, 24 Oct 2007 19:45:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
In-Reply-To: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5844955.1193269505321.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Jay Howell updated JBAS-4870:
-----------------------------

    Help Desk Ticket Reference: https://na1.salesforce.com/50030000003MjZr

I added the case number from salesforce.

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 22:28:02 2007
From: jira-events at lists.jboss.org (Cloves Almeida (JIRA))
Date: Wed, 24 Oct 2007 22:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-2) process monitoring
 and statistics capabilities (BAM)
Message-ID: <17717249.1193279282776.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12384251 ] 
            
Cloves Almeida commented on JBPM-2:
-----------------------------------

Is this still a BLOCKING issue? If not, could it please be marked Closed?

Those red issues really scary admins trying to use jBPM in production.

> process monitoring and statistics capabilities (BAM)
> ----------------------------------------------------
>
>                 Key: JBPM-2
>                 URL: http://jira.jboss.com/jira/browse/JBPM-2
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>         Environment: N/A
>            Reporter: Ronald van Kuijk
>            Priority: Blocker
>
> JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=49900689
> 1.  jBPM should store the duration and start date of a state/process in the logs
> 2.  Write some detailed info on wiki
> 3.  Show processinstance and data
> 4.  day/week/month overviews
> 5.  near realtime data per process
> 6.  produce graphs of day/week/month overviews
> Some more ideas i got from a requirements document...
> -  Number of cases processed in through a particular process definition
> -  Number of cases flowing through a particular activity
> -  Longest work item delay by activity
> -  Workitems awaiting a particular task
> -  Workitems in a specific worklist claimed and/or completed by a particular user
> -  Longest end-to-end delay
> -  Mean time to approve by activity by participant
> -  Mean end-to-end completion time.
> as background info, here's what the competition says about BAM:
> http://appian.com/AppianEnt/Analytics/analytics.html
> http://www.webmethods.com/meta/default/folder/0000005936
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduction/htm/ebiz_intro_story_piew.asp
> http://www.tibco.com/software/business_optimization/activity_monitoring.jsp?m=c1
> http://www.vitria.com/products/platform/bam.html
> http://looselycoupled.com/glossary/BAM

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 23:40:11 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 24 Oct 2007 23:40:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1298) Package wizard
 for package configuration
Message-ID: <33096746.1193283611576.JavaMail.jira@cloud.prod.atl2.jboss.com>

Package wizard for package configuration
----------------------------------------

                 Key: JBRULES-1298
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1298
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: FUTURE


this is mainly for updating models and imports. Shoudl be a wizard that uploads and VALIDATES the model (and offers to import found classes). Similar when importing DRL. Could be a wizard from the package config screen, or it could be part of the model asset screen (probably former is better). 

This has been causing some confusion. 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 24 23:44:01 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Wed, 24 Oct 2007 23:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1299) better handling
 of error when dependent class not in jar file
Message-ID: <4996155.1193283841519.JavaMail.jira@cloud.prod.atl2.jboss.com>

better handling of error when dependent class not in jar file
-------------------------------------------------------------

                 Key: JBRULES-1299
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1299
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, drools-brms
    Affects Versions: 4.0.2
            Reporter: Michael Neale
         Assigned To: Michael Neale
             Fix For: 4.1.0




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 00:35:11 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 00:35:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4891) Cannot unmarshall
	qname elements
In-Reply-To: <2003009.1193064663450.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17106469.1193286911723.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4891?page=all ]

Scott M Stark resolved JBAS-4891.
---------------------------------

    Resolution: Done

jbossas trunk is using the jbossxb snapshot that supports this

> Cannot unmarshall qname elements
> --------------------------------
>
>                 Key: JBAS-4891
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4891
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> jboss descriptors cannot have qname elements like this 
>   <service-ref>
>     <service-ref-name>SecurePort1</service-ref-name>
>     <service-qname xmlns:ns1="http://org.jboss.ws/wsref">ns1:SecureEndpointService</service-qname>
>     ...
>   </service-ref>
> Caused by: org.xml.sax.SAXException: Attribute "xmlns:ns1" must be declared for element type "service-qname". @ *unknown*[21,62]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:427)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.addDTDDefaultAttrsAndValidate(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 00:37:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 00:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23603767.1193287021659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Scott M Stark resolved JBAS-4895.
---------------------------------

    Resolution: Done

The current jboss-metadata 1.0.0.snapshot (rev 1563) contains the complete standard and jboss service-ref mappings.


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:14:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 01:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4899) Failed to resolve
 schema nsURI= location=null
In-Reply-To: <854055.1193150525910.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21428636.1193289241565.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4899?page=all ]

Scott M Stark resolved JBAS-4899.
---------------------------------

    Resolution: Done

The latest jbossxb snapshot (rev 1654) will pass in the root element local name as the schemaLocation if no other schemaLocation could be found. This allows one to map the root element name to a binding class as jbossas does in its metadata-beans.xml:

   <bean name="SchemaResolverConfig"
      class="org.jboss.xb.binding.sunday.unmarshalling.SchemaResolverConfig">
      <!-- schemaLocation to JBossXBuilder binding classes -->
      <property name="bindingClassesByLocations">
         <map keyClass="java.lang.String" valueClass="java.lang.String">
            <entry>
               <key>jboss</key>
               <value>org.jboss.metadata.ejb.jboss.JBoss50DTDMetaData</value>
            </entry>            
...


> Failed to resolve schema nsURI= location=null
> ---------------------------------------------
>
>                 Key: JBAS-4899
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4899
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This happens when <jboss-web> does not contain a doctype declaration. This is more a backward compatibility issue.
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=null
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:16:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 01:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4896) NPE in
	JBossMetaDataWrapper
In-Reply-To: <22358703.1193137081592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11765802.1193289361636.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4896?page=all ]

Scott M Stark resolved JBAS-4896.
---------------------------------

    Resolution: Done

The document parses correctly with the current jbossxb/jboss-metadata snapshots. See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testNoDoctype test.


> NPE in JBossMetaDataWrapper
> ---------------------------
>
>                 Key: JBAS-4896
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4896
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:23:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 01:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21598628.1193289781478.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Scott M Stark updated JBAS-4900:
--------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098649

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 01:54:01 2007
From: jira-events at lists.jboss.org (Magesh Kumar B (JIRA))
Date: Thu, 25 Oct 2007 01:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1481) Reimplement
 portal security interface without JACC
In-Reply-To: <14757028.1181561891881.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2295689.1193291641537.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1481?page=all ]

Magesh Kumar B reassigned JBPORTAL-1481:
----------------------------------------

    Assignee: Sohil Shah

> Reimplement portal security interface without JACC
> --------------------------------------------------
>
>                 Key: JBPORTAL-1481
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1481
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6 CR3
>            Reporter: Julien Viet
>         Assigned To: Sohil Shah
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 02:13:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 02:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1156) Configuration
	profiles
In-Reply-To: <12193835.1185540767196.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14173054.1193292781666.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1156?page=comments#action_12384259 ] 
            
Brian Stansberry commented on JBCACHE-1156:
-------------------------------------------

A pretty reasonable version of what I'm thinking about is now in package org.jboss.cache.registry. I'm trying to keep this simple, since in many ways it's not a true JBC concern. I'd just do it in the AS, but it's needed for standalone Hibernate, which can't depend on the AS. I'll likely want to use the same interfaces for session mgmt stuff in the AS, so I don't want this stuff in Hibernate, since session mgmt has nothing to do with Hibernate. So, putting it in JBC makes the most sense.

Given the above, I thought the best approach to take was to define a couple basic interfaces that provide the API needed by Hibernate.  Then do a basic impl that meets the needs of standalone Hibernate. If I decide I want to do more complex stuff inside the AS, I can can expand upon this in the AS codebase.

This is pretty much ready to be resolved, other than I might think of a couple more unit tests.

> Configuration profiles
> ----------------------
>
>                 Key: JBCACHE-1156
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1156
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Brian Stansberry
>             Fix For: 2.1.0.GA, 2.1.0.CR1
>
>
> Requested by both AS clustering and Hibernate.
> The ability to use a specialised ConfigurationFactory that gives you a pre-configured cache for specific purposes.  E.g., CacheFactory.getAsyncReplicatedCache("myJGroupsMuxStackName")
> To be done as a subclass of DefaultCacheFactory (ProfileCacheFactory?)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 02:13:01 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 25 Oct 2007 02:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1299) better handling of
 error when dependent class not in jar file
In-Reply-To: <4996155.1193283841519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23402410.1193292781794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1299?page=all ]

Michael Neale closed JBRULES-1299.
----------------------------------

    Resolution: Done

> better handling of error when dependent class not in jar file
> -------------------------------------------------------------
>
>                 Key: JBRULES-1299
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1299
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder, drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>             Fix For: 4.1.0
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 02:21:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 02:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-1194)
 DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
In-Reply-To: <7298940.1191611644226.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5043343.1193293261446.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1194?page=all ]

Brian Stansberry closed JBCACHE-1194.
-------------------------------------

    Resolution: Done

> DataGravitatorInterceptor needs to use GroupRequest.ALL for RPC
> ---------------------------------------------------------------
>
>                 Key: JBCACHE-1194
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1194
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA, 1.4.1.SP5
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Critical
>             Fix For: 1.4.1.SP6
>
>
> It currently makes the RPC using GET_FIRST, so as soon as a node replies saying it doesn't have the data, JGroups stops waiting for responses.  This is the cause of the behavior reported at JBAS-4766.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:00:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 03:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-596) Document JOIN&state
 transfer, for JChannel and in the Multiplexer
In-Reply-To: <25358775.1190275215454.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8752391.1193295601497.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-596?page=all ]

Bela Ban resolved JGRP-596.
---------------------------

    Resolution: Done

> Document JOIN&state transfer, for JChannel and in the Multiplexer
> -----------------------------------------------------------------
>
>                 Key: JGRP-596
>                 URL: http://jira.jboss.com/jira/browse/JGRP-596
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>         Assigned To: Vladimir Blagojevic
>            Priority: Minor
>             Fix For: 2.6
>
>
> JOIN&STATE transfer needs to get documented in doc/manual/en/modules/api.xml. We also need to add documentation for the same for the multiplexer

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:25:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 03:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JGRP-609) Javadoc
	JChannelFactory
In-Reply-To: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18675501.1193297101636.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-609?page=all ]

Bela Ban reassigned JGRP-609:
-----------------------------

    Assignee: Vladimir Blagojevic  (was: Bela Ban)

> Javadoc JChannelFactory
> -----------------------
>
>                 Key: JGRP-609
>                 URL: http://jira.jboss.com/jira/browse/JGRP-609
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5.1
>            Reporter: Brian Stansberry
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6, 2.5.2
>
>
> org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:25:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 03:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JGRP-609) Javadoc
	JChannelFactory
In-Reply-To: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29039435.1193297101797.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-609?page=all ]

Bela Ban updated JGRP-609:
--------------------------

    Fix Version/s: 2.5.2
                   2.6

> Javadoc JChannelFactory
> -----------------------
>
>                 Key: JGRP-609
>                 URL: http://jira.jboss.com/jira/browse/JGRP-609
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5.1
>            Reporter: Brian Stansberry
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6, 2.5.2
>
>
> org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:55:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 03:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging
 levels don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9614064.1193298901419.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384266 ] 
            
Dimitris Andreadis commented on JBCOMMON-39:
--------------------------------------------

Can you explain again what the problem is? Is there a forum thread discussing it?

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 03:59:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Thu, 25 Oct 2007 03:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32213940.1193299141494.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4823?page=all ]

cheng dan reassigned JBAS-4823:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:01:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Thu, 25 Oct 2007 04:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7241297.1193299261560.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4823?page=all ]

cheng dan reassigned JBAS-4823:
-------------------------------

    Assignee:     (was: cheng dan)

> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:01:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Thu, 25 Oct 2007 04:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4825) TECH REVIEW:
 Getting Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21013941.1193299261733.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

cheng dan reassigned JBAS-4825:
-------------------------------

    Assignee: cheng dan

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:21:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Thu, 25 Oct 2007 04:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-607) SEQUENCER: incorrect
 ordering on concurrent sends
In-Reply-To: <30774057.1193152921433.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26584855.1193300461515.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-607?page=all ]

Bela Ban resolved JGRP-607.
---------------------------

    Resolution: Done

Fixed according to solution in CVS head, and 2.5 and 2.4 branches

> SEQUENCER: incorrect ordering on concurrent sends
> -------------------------------------------------
>
>                 Key: JGRP-607
>                 URL: http://jira.jboss.com/jira/browse/JGRP-607
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.4.1 SP5, 2.5.2, 2.6
>
>
> The unit test which fails is SequencerOrderTest. With SEQUENCER.down() synchronized, the test always passes

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 04:26:19 2007
From: jira-events at lists.jboss.org (Magesh Kumar B (JIRA))
Date: Thu, 25 Oct 2007 04:26:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1481) Reimplement
 portal security interface without JACC
In-Reply-To: <14757028.1181561891881.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1372982.1193300779167.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1481?page=all ]

Magesh Kumar B resolved JBPORTAL-1481.
--------------------------------------

    Fix Version/s: 2.6.3 Final
       Resolution: Done

Merged from Security Branch JBoss_Portal_2_6_2_SecurityPatch to current working JBoss_Portal_Branch_2_6

> Reimplement portal security interface without JACC
> --------------------------------------------------
>
>                 Key: JBPORTAL-1481
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1481
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6 CR3
>            Reporter: Julien Viet
>         Assigned To: Sohil Shah
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:15:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 05:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4910) NPE in
	AbstractMappedMetaData
Message-ID: <32126662.1193303701492.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in AbstractMappedMetaData
-----------------------------

                 Key: JBAS-4910
                 URL: http://jira.jboss.com/jira/browse/JBAS-4910
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:19:06 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 05:19:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4910) NPE in
	AbstractMappedMetaData
In-Reply-To: <32126662.1193303701492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16322013.1193303947019.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4910?page=all ]

Thomas Diesler updated JBAS-4910:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefClientTestCase one-test

Caused by: java.lang.NullPointerException
        at org.jboss.metadata.javaee.support.AbstractMappedMetaData.addAll(AbstractMappedMetaData.java:188)
        at org.jboss.metadata.javaee.spec.MessageDestinationsMetaData.merge(MessageDestinationsMetaData.java:66)
        at org.jboss.metadata.client.jboss.JBossClientMetaData.merge(JBossClientMetaData.java:316)
        at org.jboss.ejb3.deployers.JBossClientParsingDeployer.createMetaData(JBossClientParsingDeployer.java:63)
        at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)

To reproduce this, you need to enable the test in src/resources/test-excludes-jboss500.txt
         Assignee: Scott M Stark

> NPE in AbstractMappedMetaData
> -----------------------------
>
>                 Key: JBAS-4910
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4910
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefClientTestCase one-test
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.javaee.support.AbstractMappedMetaData.addAll(AbstractMappedMetaData.java:188)
>         at org.jboss.metadata.javaee.spec.MessageDestinationsMetaData.merge(MessageDestinationsMetaData.java:66)
>         at org.jboss.metadata.client.jboss.JBossClientMetaData.merge(JBossClientMetaData.java:316)
>         at org.jboss.ejb3.deployers.JBossClientParsingDeployer.createMetaData(JBossClientParsingDeployer.java:63)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> To reproduce this, you need to enable the test in src/resources/test-excludes-jboss500.txt

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:25:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Thu, 25 Oct 2007 05:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1720) Profile /
 enhance error message : DatePropertyAccessor
In-Reply-To: <16243687.1190700172066.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9524850.1193304301883.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1720?page=all ]

Thomas Heute updated JBPORTAL-1720:
-----------------------------------

    Assignee: Thomas Heute

> Profile / enhance error message : DatePropertyAccessor 
> -------------------------------------------------------
>
>                 Key: JBPORTAL-1720
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1720
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> Line 552
> catch (ParseException e)
>          {
>             throw new IllegalArgumentException();
>          }
> Some more information on the error will be helpfull, espcially for integration of legacy user datasource.
> Like it is done for the boolean property accessor
> something like :
> catch (ParseException e)
>          {
>             throw new IllegalArgumentException("Can't convert the date in the user profile. value=[" + value + "].", e);
>          }

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:43:12 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Thu, 25 Oct 2007 05:43:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17139263.1193305392784.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris reopened JBAS-4826:
--------------------------------------

             
Reviewed wrong doc. I will review now the later of the 2 docs originally attached

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:47:01 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 05:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4911)
 MSSQLValidConnectionChecker
 throws exception with MS SQL Server 2005 JDBC driver
Message-ID: <20099656.1193305621823.JavaMail.jira@cloud.prod.atl2.jboss.com>

MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
--------------------------------------------------------------------------------

                 Key: JBAS-4911
                 URL: http://jira.jboss.com/jira/browse/JBAS-4911
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JCA service
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Luc Texier
         Assigned To: Weston Price


After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource

<datasources>
  <local-tx-datasource>
    <jndi-name>DefaultDS</jndi-name>
    <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
    <user-name>sa</user-name>
    <password>jboss</password>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>

    <metadata>
       <type-mapping>MS SQLSERVER2000</type-mapping>
    </metadata>
  </local-tx-datasource>
</datasources>


during start-up, the following exception is throwed 


2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 05:56:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 05:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
In-Reply-To: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30525369.1193306161635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Adrian Brock updated JBAS-4870:
-------------------------------

    Attachment: testredelivery.zip

It's quite hard to write an ant unit test for this problem, because it can
only be reproduced with a server crash (rather than a clean shutdown of the server).

Attached is a simple ant project to test whether the redelivery flags are set correctly,
but it requires manual steps (step 4 below) to run the test.

1) Start JBoss
> ./run.sh
2) Send a message
> ant send
3) Receive the message in Client Acknowledge mode, but don't acknowledge (or close the session, etc. which is the same thing).
> ant receive
4) Crash the server (don't use control-c)
> kill -9 <jboss-pid>
5) Restart the server
> ./run.sh
7) Re-receive the message
> ant receive

You should see the redelivery count updated (before this fix you don't)

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>         Attachments: testredelivery.zip
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:00:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Thu, 25 Oct 2007 06:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4826) TECH REVIEW:
 Getting Started
 Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2
In-Reply-To: <24155064.1192165535115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29680425.1193306403613.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4826?page=all ]

Stelios Koussouris resolved JBAS-4826.
--------------------------------------

    Resolution: Done

I have completed the review and have nothing against this chapter. Please. ignore my previous attachment.

> TECH REVIEW: Getting Started Guide - Chapter 2. EJB3 Caveats in JBoss Application Server 4.2.2 
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4826
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4826
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBAS-422-Getting-Started-Guide-Chapter-2.odt, JBASS-422-Getting_Started_Guide-Chapter-2.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:02:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4870) Redelivery flags not
 updated in case of JBossMQ node failure
In-Reply-To: <27476471.1192628463432.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17796079.1193306521609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4870?page=all ]

Adrian Brock closed JBAS-4870.
------------------------------

    Resolution: Done

This has been fixed.

Since this is a corner case and the fix means we have to update all persistent messages
in the database before delivering the message (i.e. whether the message gets redelivered or not)
I've added an option to the destination manager so it can be reverted to the old behaviour.

<!-- Only update redelivery status of a persistent message in the database when a NACK is received -->
<attribute name="LazyRedeliveryUpdate">true</attribute>

The default is false.

> Redelivery flags not updated in case of JBossMQ node failure
> ------------------------------------------------------------
>
>                 Key: JBAS-4870
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4870
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>         Attachments: testredelivery.zip
>
>
> When the JBossMQ node fails with messages currently being delivered to the clients,
> the redelivery status is not updated after the node is recovered (either locally or on a different for HAJMS).
> The issue is that the redelivery status (in the database) is not updated until the server receives the NACK
> (which it won't do if it has crashed).
> A potential fix, is to update the status early before delivering the message to the client,
> see the forum thread for more detail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:15:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-211) Support ..
 notion in vfs paths
Message-ID: <9963001.1193307301447.JavaMail.jira@cloud.prod.atl2.jboss.com>

Support .. notion in vfs paths
------------------------------

                 Key: JBMICROCONT-211
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-211
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: VFS
    Affects Versions: JBossMC-2.0.0.Beta4
            Reporter: Adrian Brock


If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
currently the PathTokenizer will report an error if the path contains a . or ..

It should still through an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:17:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10165918.1193307421654.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Adrian Brock updated JBAS-4901:
-------------------------------

    Assignee:     (was: Adrian Brock)

I don't see how this can be backwards compatibility issue since the VFS has never supported
the .. notation.

We've discussed supporting it in the past, but nothing was ever done.
I've raised a feature request for it.

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:17:01 2007
From: jira-events at lists.jboss.org (Ovidiu Nichifor (JIRA))
Date: Thu, 25 Oct 2007 06:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1773) Unable to
 destroy instance customization
Message-ID: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>

Unable to destroy instance customization
----------------------------------------

                 Key: JBPORTAL-1773
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
             Project: JBoss Portal
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Portal Core
    Affects Versions: 2.6.1 Final
         Environment: Fedora Core 7
JVM 1.5.0_12
JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
JBoss Potal 2.6.1.GA

            Reporter: Ovidiu Nichifor
         Assigned To: Julien Viet


Create & place a window on a region of an ordinary page of your personal dashboard.
Make sure it is visible on your dashboard.
Destroy that window.
Recreate the window with the same name, content type, instance, page parent, region and order as before.

An error will appear in the console:
12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null

It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.

Sample:

`JBP_PORTLET_STATE`
PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL

`JBP_INSTANCE_PER_USER`
PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4

Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.

Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:19:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8262554.1193307541751.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir updated JBAS-4827:
---------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-3-1.odt

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3-1.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5752323.1193307662095.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir updated JBAS-4827:
---------------------------------

    Attachment:     (was: JBASS-422-Getting_Started_Guide-Chapter-3-1.odt)

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1402) Transaction Recovery
Message-ID: <21458831.1193307662555.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1402?page=all ]

Adrian Brock closed JBAS-1402.
------------------------------

    Resolution: Out of Date
      Assignee:     (was: Adrian Brock)

This issue can be closed.

The JCA issues still need resolving with some api for the a generic TM to get XAResources
during recovery. 

There is a thread about this in the JCA forum, but I'm not sure if any
JIRA issues were created beyond what is mentioned here.

I'll close the ones here and re-raise the issue in the JCA forum.

> Transaction Recovery
> --------------------
>
>                 Key: JBAS-1402
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1402
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.0.1 Final
>            Reporter: Adrian Brock
>
> Implement optional transaction recovery
> The simplest mechanism is to do this is with a local database
> using the last resource gambit where during its "prepare" it logs the XID in a table.
> If this last resource fails to commit, recovery will not find the transaction
> in the table which means it will rollback the whole transaction.
> This has limitations where a different local resource is required within the transaction
> but not this local database used as the recovery log.
> Another implementation is a local file. Though more complicated it should give superior
> performance. 
> But, it does not work well with the last resource gambit, e.g. you cannot tell
> whether the jdbc commit() suceeded or failed if it crashes just at the point of this invocation
> before the result is returned from the db.
> The other work required:
> 1) Possibly, simplify the dependencies in the JCA module so we can run the recovery earlier.
> Currently the RARs need the transaction manager at deployment time. The
> recovery service needs to be an external service depending upon both the
> tm and the managed connection factories.
> At least this will require a GUID for the XID so we can avoid duplicates between
> unrecovered XIDs and any new XIDs created before recovery is complete.
> 2) JBossMQ needs to implement XAResource.recover()

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1405) Padding should be a
	JCA option
Message-ID: <12240979.1193307662725.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1405?page=all ]

Adrian Brock closed JBAS-1405.
------------------------------

    Resolution: Out of Date

> Padding should be a JCA option
> ------------------------------
>
>                 Key: JBAS-1405
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1405
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> There should be a JCA switch that wraps any method of XAResource that takes an Xid and pads the Xid if needed by the JCA resource.  Some XAResources like Oracle need padding, others may have problems with padding.  It is stupid to have this switch on the XidFactory only.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:21:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:21:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4827) TECH REVIEW: Getting
 Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21978028.1193307662956.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir updated JBAS-4827:
---------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-3.odt

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1406) XidFactory should
	never pad Xids
Message-ID: <8899110.1193307781887.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1406?page=all ]

Adrian Brock closed JBAS-1406.
------------------------------

    Resolution: Out of Date

> XidFactory should never pad Xids
> --------------------------------
>
>                 Key: JBAS-1406
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1406
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1407) recover flags should
 be a JCA option
Message-ID: <13947702.1193307782036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1407?page=all ]

Adrian Brock closed JBAS-1407.
------------------------------

    Resolution: Out of Date

> recover flags should be a JCA option
> ------------------------------------
>
>                 Key: JBAS-1407
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1407
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> The XAResource managed by JCA should be wrapped and calls to XAResource.recover should ignore passed in flags and use a configurable set of flags to pass into the XAResource.  This is important because some XAResources are finicky about what flags are passed to them in recover().

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4827) TECH REVIEW:
 Getting Started Guide - Chapter 3. About the Example Applications
In-Reply-To: <4410208.1192165535251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22653667.1193307782467.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4827?page=all ]

Colin Mondesir resolved JBAS-4827.
----------------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 3. About the Example Applications
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4827
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4827
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt, JBASS-422-Getting_Started_Guide-Chapter-3.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1408) JCA layer should
 register Recoverables
Message-ID: <26974760.1193307782595.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1408?page=all ]

Adrian Brock closed JBAS-1408.
------------------------------

    Resolution: Out of Date

> JCA layer should register Recoverables
> --------------------------------------
>
>                 Key: JBAS-1408
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1408
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> JCA layer should provide a generic mechanism to register Recoverables with the RecoveryManager.  See http://www.jboss.org/wiki/Wiki.jsp?page=TransactionRecovery
> for more details.
> The way this will work is that the wrapper class for ManagedConnectionFactory will look at the metadata for creating the recoverable Subject and the metadata for the XAResource.recover() flags so that it can create a JCARecoverable class isntance to register with the recovery manager.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1409) JCA should have
	recovery config
Message-ID: <13697520.1193307782727.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1409?page=all ]

Adrian Brock closed JBAS-1409.
------------------------------

    Resolution: Out of Date

> JCA should have recovery config
> -------------------------------
>
>                 Key: JBAS-1409
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1409
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: JCA service
>            Reporter: Bill Burke
>
> See here:
> http://www.jboss.org/wiki/Wiki.jsp?page=TransactionRecovery
> JCA adapter should register a Recoverable with the RecoveryManager.  There should be additional switches on witch Subject or SecurityDomain should be used for recovery.  Regular XA connections may not have permission to do recovery and the app developer may not want to allow app connections to do recovery.
> Additionally, different XAResources may need different recovery switches that are passed to XAResource.recover()  For instance Informix needs only TMSTARTRSCAN while Oracle may need both TMENDRSCAN.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1410) check resources
	available
Message-ID: <2822383.1193307782857.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1410?page=all ]

Adrian Brock closed JBAS-1410.
------------------------------

    Resolution: Out of Date

> check resources available
> -------------------------
>
>                 Key: JBAS-1410
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1410
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>
> Write in the TX Log header all REcoverable IDs that are needed to recover that particular file.  If not all resources are available log error message and don't remove file.  Save it for later.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:02 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1418) test not all
	resources available
Message-ID: <6449221.1193307782986.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1418?page=all ]

Adrian Brock closed JBAS-1418.
------------------------------

    Resolution: Out of Date

> test not all resources available
> --------------------------------
>
>                 Key: JBAS-1418
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1418
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1419) test when resource
	hot-deployed
Message-ID: <31433096.1193307783131.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1419?page=all ]

Adrian Brock closed JBAS-1419.
------------------------------

    Resolution: Out of Date

> test when resource hot-deployed
> -------------------------------
>
>                 Key: JBAS-1419
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1419
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:23:03 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 06:23:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1420) last resource gambit
 recovery logger
Message-ID: <22633934.1193307783264.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1420?page=all ]

Adrian Brock closed JBAS-1420.
------------------------------

    Resolution: Out of Date

> last resource gambit recovery logger
> ------------------------------------
>
>                 Key: JBAS-1420
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1420
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>          Components: Transaction Manager
>            Reporter: Bill Burke
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:25:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14520616.1193307903722.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Thomas Diesler reassigned JBAS-4901:
------------------------------------

    Assignee: Thomas Diesler

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:25:03 2007
From: jira-events at lists.jboss.org (Ovidiu Nichifor (JIRA))
Date: Thu, 25 Oct 2007 06:25:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19623618.1193307903979.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=comments#action_12384291 ] 
            
Ovidiu Nichifor commented on JBPORTAL-1773:
-------------------------------------------

Since instance customizations are not persisted until some preferences are stored i found it very useful to create a portlet that stores/displays preferences. The attached war file contains sources and this portlet.

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:28:01 2007
From: jira-events at lists.jboss.org (Ovidiu Nichifor (JIRA))
Date: Thu, 25 Oct 2007 06:28:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28694259.1193308081601.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=all ]

Ovidiu Nichifor updated JBPORTAL-1773:
--------------------------------------

    Attachment: sample-portlet.war

A sample portlet that stores/displays its attached preferences.

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>         Attachments: sample-portlet.war
>
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1120) Data channel
 from
 MultiplexerChannelFactory prevents state transfers from other users of the
 shared channel
In-Reply-To: <2574382.1193240941938.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25232466.1193309641673.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1120?page=all ]

Tim Fox updated JBMESSAGING-1120:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1120
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Distributed Support
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang.
> Problem is JBM's MultiplexerChannelFactory creates the data channel as follows:
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE);
> }
> The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service.  JBM never calls getState(), so it *must not* pass Boolean.TRUE.  Valid usages are:
> public Channel createDataChannel() throws Exception
> {
>       String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"};
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature);
> }
> or 
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE);
> }
> The former invokes a convenience method that delegates to the latter.
> Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState().  If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.)
> When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState().
> I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1118) Sucker
 connection created back to itself doesn't need to be created
In-Reply-To: <1544433.1193076306087.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31969692.1193309642535.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1118?page=all ]

Tim Fox updated JBMESSAGING-1118:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> Sucker connection created back to itself doesn't need to be created
> -------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1118
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment.  So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker.
> while (iter.hasNext())
> 		{
> 			Map.Entry entry = (Map.Entry)iter.next();
> 			
> 			Integer nid = (Integer)entry.getKey();
> 			
> 			ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue();
> 			
> 			if (connections.get(nid) == null)
> 			{
> 				try
> 				{
>    				ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword);
>    				
>    				log.trace(this + " created connection info " + info);
>    				
>    				connections.put(nid, info);
>    				
>    				info.start();
>    						         							         			
> 				}
> 				catch (Exception e)
> 				{
> 					log.error("Failed to start connection info ", e);
> 				}
> 			}

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20244057.1193309642792.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=all ]

Tim Fox updated JBMESSAGING-1115:
---------------------------------

    Fix Version/s: 1.4.0.SP1

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 06:54:03 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 06:54:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1117) Request for
 feature to
 close connections on server side by ip address and by connection id
In-Reply-To: <5418814.1193073363722.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2164762.1193309643543.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1117?page=all ]

Tim Fox updated JBMESSAGING-1117:
---------------------------------

    Fix Version/s: Unscheduled

> Request for feature to close connections on server side by ip address and by connection id
> ------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1117
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1117
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>             Fix For: Unscheduled
>
>
> Several customers have asked for a management method to drop client connections from the server by ip address and by client id.
> So there would be two cases.
> By ipaddress - this would stop the pinger and also close all connections associated with that client ip address.  Only one pinger exists for an ip address, so this would require closging of the pinger connection also.
> By clientid - this would close the pinger thread only if there are no other connections present.
> In each of the cases, clients should get an asynchronous onException call.  
> The person writing the client will have to have this in mind.  If a client has 1000 connections and the connection logic on the client reconnects.  When the server drops the ip address, then that machine will try to reconnect all 1000 clients.  I really depends on how the connection pooling on the client works.  

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:26:06 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Thu, 25 Oct 2007 08:26:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4898) class-loading not
 found as a child of jboss-web
In-Reply-To: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15459809.1193315166235.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4898?page=comments#action_12384308 ] 
            
Alexey Loubyansky commented on JBAS-4898:
-----------------------------------------

Fixed in metadata trunk. The test is

package org.jboss.test.metadata.web;
public class JBossWebApp24UnitTestCase extends AbstractJavaEEEverythingTest


> class-loading not found as a child of jboss-web
> -----------------------------------------------
>
>                 Key: JBAS-4898
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
>   <class-loading>
>     <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
>   </class-loading>
> </jboss-web>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:40:12 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:40:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1120) Data channel
 from
 MultiplexerChannelFactory prevents state transfers from other users of the
 shared channel
In-Reply-To: <2574382.1193240941938.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <888727.1193316012366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1120?page=all ]

Tim Fox closed JBMESSAGING-1120.
--------------------------------

    Resolution: Done

> Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1120
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Distributed Support
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang.
> Problem is JBM's MultiplexerChannelFactory creates the data channel as follows:
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE);
> }
> The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service.  JBM never calls getState(), so it *must not* pass Boolean.TRUE.  Valid usages are:
> public Channel createDataChannel() throws Exception
> {
>       String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"};
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature);
> }
> or 
> public Channel createDataChannel() throws Exception
> {
>       return (Channel) server.invoke(this.channelFactory, MUX_OPERATION,
>          new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE);
> }
> The former invokes a convenience method that delegates to the latter.
> Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState().  If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.)
> When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState().
> I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:40:12 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 08:40:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4911)
 MSSQLValidConnectionChecker
 throws exception with MS SQL Server 2005 JDBC driver
In-Reply-To: <20099656.1193305621823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1175032.1193316012709.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4911?page=all ]

Luc Texier updated JBAS-4911:
-----------------------------

    Description: 
After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource

<datasources>
  <local-tx-datasource>
    <jndi-name>DefaultDS</jndi-name>
    <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
    <user-name>sa</user-name>
    <password>jboss</password>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>

    <metadata>
       <type-mapping>MS SQLSERVER2000</type-mapping>
    </metadata>
  </local-tx-datasource>
</datasources>


during start-up, the following exception is throwed 


2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)


IMPORTANT NOTE: I've been testing against MSSQL Server 2000. This issue might very well not exist at all with MS SQL Server 2005...



  was:
After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource

<datasources>
  <local-tx-datasource>
    <jndi-name>DefaultDS</jndi-name>
    <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
    <user-name>sa</user-name>
    <password>jboss</password>
   <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>

    <metadata>
       <type-mapping>MS SQLSERVER2000</type-mapping>
    </metadata>
  </local-tx-datasource>
</datasources>


during start-up, the following exception is throwed 


2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)


> MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4911
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4911
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Luc Texier
>         Assigned To: Weston Price
>
> After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource
> <datasources>
>   <local-tx-datasource>
>     <jndi-name>DefaultDS</jndi-name>
>     <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
>     <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
>     <user-name>sa</user-name>
>     <password>jboss</password>
>    <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>
>     <metadata>
>        <type-mapping>MS SQLSERVER2000</type-mapping>
>     </metadata>
>   </local-tx-datasource>
> </datasources>
> during start-up, the following exception is throwed 
> 2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
> com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
> 	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
> 	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
> 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
> 	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
> 	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
> 	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
> IMPORTANT NOTE: I've been testing against MSSQL Server 2000. This issue might very well not exist at all with MS SQL Server 2005...

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:42:01 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 08:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4911)
 MSSQLValidConnectionChecker
 throws exception with MS SQL Server 2005 JDBC driver
In-Reply-To: <20099656.1193305621823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32597148.1193316121573.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4911?page=comments#action_12384313 ] 
            
Luc Texier commented on JBAS-4911:
----------------------------------

FYI, the workaround for now is to use the parameter check-valid-connection-sql instead as follows:

<check-valid-connection-sql>SELECT 1 FROM sysobjects</check-valid-connection-sql>


> MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver
> --------------------------------------------------------------------------------
>
>                 Key: JBAS-4911
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4911
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Luc Texier
>         Assigned To: Weston Price
>
> After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource
> <datasources>
>   <local-tx-datasource>
>     <jndi-name>DefaultDS</jndi-name>
>     <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url>
>     <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
>     <user-name>sa</user-name>
>     <password>jboss</password>
>    <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name>
>     <metadata>
>        <type-mapping>MS SQLSERVER2000</type-mapping>
>     </metadata>
>   </local-tx-datasource>
> </datasources>
> during start-up, the following exception is throwed 
> 2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection.
> 2007-10-25 11:26:36,328 WARN  [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection at 9a42ef
> com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'.
> 	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
> 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
> 	at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231)
> 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200)
> 	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211)
> 	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
> 	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315)
> 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
> IMPORTANT NOTE: I've been testing against MSSQL Server 2000. This issue might very well not exist at all with MS SQL Server 2005...

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:42:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:42:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1118) Sucker
 connection created back to itself doesn't need to be created
In-Reply-To: <1544433.1193076306087.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14320530.1193316122230.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1118?page=all ]

Tim Fox closed JBMESSAGING-1118.
--------------------------------

    Resolution: Rejected

After investigating this doesn't appear to be a bug.

When starting a postoffice in clustered mode it will obtain connections to all nodes in the cluster including itself for message suckers.

If you start the post office in non clustered mode you will find no such connections get created.

> Sucker connection created back to itself doesn't need to be created
> -------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1118
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.GA
>            Reporter: Jay Howell
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment.  So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker.
> while (iter.hasNext())
> 		{
> 			Map.Entry entry = (Map.Entry)iter.next();
> 			
> 			Integer nid = (Integer)entry.getKey();
> 			
> 			ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue();
> 			
> 			if (connections.get(nid) == null)
> 			{
> 				try
> 				{
>    				ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword);
>    				
>    				log.trace(this + " created connection info " + info);
>    				
>    				connections.put(nid, info);
>    				
>    				info.start();
>    						         							         			
> 				}
> 				catch (Exception e)
> 				{
> 					log.error("Failed to start connection info ", e);
> 				}
> 			}

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:49:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16067251.1193316542316.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox closed JBMESSAGING-1119.
--------------------------------

    Resolution: Done
      Assignee: Tim Fox  (was: Clebert Suconic)

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:53:02 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 25 Oct 2007 08:53:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-27) Container
 Task:JBoss 4.2.x related Tasks for Security 2.0
In-Reply-To: <17497988.1172167236604.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27651666.1193316782129.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-27?page=all ]

Anil Saldhana updated SECURITY-27:
----------------------------------

    Fix Version/s: 2.0.2-GA
                       (was: 2.0.1-GA)

> Container Task:JBoss 4.2.x related Tasks for Security 2.0
> ---------------------------------------------------------
>
>                 Key: SECURITY-27
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-27
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.2-GA
>
>
> Container task for all 4.2.x related tasks that need to be performed for the 5.x releases of JBAS.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:57:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <27188498.1193317021862.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12384316 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

We need to support automatic failover for the case where no shared file systems is present.

In which case we need to replicate state to a buddy.

This should be configurable on a per queue level.

We can supply different levels of reliability:

1) Once and only once - with this mode we would need two streams one for replication messages and one for replication acks
We would also need to store last sequence received in the storage to avoid having to use XA

2) At most once - replication sent async. Chance of message loss.

3) No replication

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 08:59:05 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 08:59:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <15451995.1193317145729.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12384317 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

Very large messages should be stored outside the store on the file system and referenced via pointers.

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:01:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 09:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-406) Persistence
	refactoring
Message-ID: <19332013.1193317261978.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12384319 ] 
            
Tim Fox commented on JBMESSAGING-406:
-------------------------------------

Should also support active passive failover

> Persistence refactoring
> -----------------------
>
>                 Key: JBMESSAGING-406
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 2.0.0 Alpha
>
>
> Need to refactor persistence so each node has its own storage.
> We should provide at least three local persistence manager configs:
> 1) JDBC local pm that works out of the box with HSQL - not recommended for production.
> 2) BDB based pm that customers need to download - recommended for best performance.
> Should optimise for the SAN use case.
> Need to consider whether we need to support replication for failover too.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:14:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 09:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1116) Consuming
 client grinds to
 a halt if a node different from the "active" one fails
In-Reply-To: <10435351.1193029683486.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6214220.1193318041840.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1116?page=all ]

Tim Fox closed JBMESSAGING-1116.
--------------------------------

    Resolution: Done

> Consuming client grinds to a halt if a node different from the "active" one fails
> ---------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1116
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> This is how to replicate it:
> - Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A
> - Start consuming concurrently using 50 parallel consumers over a connection to node A
> - Kill node B
> The consumption rate drop to 0 and never recovers.
> Trying to close the connection on the client-side never completes.
> Trying to shut down node A fails, need to eventually kill it.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:16:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 25 Oct 2007 09:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-39) JDK logging
 levels don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2376485.1193318161482.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=comments#action_12384324 ] 
            
David Lloyd commented on JBCOMMON-39:
-------------------------------------

The problem is that if you use the JDK14LoggerPlugin, and you log a message at, say, TRACE, it shows up as FINER in the log.  And the DOMConfigurator for the JDK plugin has to map the "old" log4j names to the (roughly) equivalent JUL name.  I propose that we just create a subclass of java.util.logging.Level, and an instance for each of the log levels that WE use, e.g. TRACE, DEBUG, etc.  Then not only will the old, familiar levels be printed in the log, but then JUL will parse the log level names for us, so we don't need to map them.

No forum thread because honestly I don't know what forum is relevant for this project.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBAS-4907.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:22:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 25 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18042231.1193318521583.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

David Lloyd updated JBCOMMON-39:
--------------------------------

    Attachment: JBCOMMON-39.patch

Updated patch.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBCOMMON-39.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:22:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Thu, 25 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26495472.1193318521743.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

David Lloyd updated JBCOMMON-39:
--------------------------------

    Attachment:     (was: JBAS-4907.patch)

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBCOMMON-39.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:46:16 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 09:46:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4830) TECH REVIEW: Getting
 Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6581118.1193319976815.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Luc Texier updated JBAS-4830:
-----------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt

Here is revision 3.1

basically I've rewritten 80% of it. Now this chapter includes a section for MS SQL Server and the Oracle one has been simplified and updated. They are all refering to the latest jdbc drivers available from these vendors.

FYI while testing with MS SQL I found the following bug: JBAS-4911

Thanks to Colin for fixing the english typos

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:52:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 09:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
Message-ID: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>

Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
----------------------------------------------------------------------------------------------------------------------

                 Key: JBMICROCONT-212
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
             Project: JBoss MicroContainer
          Issue Type: Bug
    Affects Versions: JBossMC-2.0.0.Beta4
            Reporter: Adrian Brock
         Assigned To: Adrian Brock
             Fix For: JBossMC-2.0.0.Beta5


The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
when the deployment failed during deploy().

The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:52:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 09:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33069480.1193320321821.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=all ]

Adrian Brock updated JBMICROCONT-212:
-------------------------------------

    Component/s: Deployment

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:52:02 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 09:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33264365.1193320322024.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4830?page=comments#action_12384332 ] 
            
Luc Texier commented on JBAS-4830:
----------------------------------

BTW the table of content has to be double-checked and setup properly

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:54:07 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Thu, 25 Oct 2007 09:54:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4830) TECH REVIEW:
 Getting Started Guide - Chapter 6. Using other Databases
In-Reply-To: <914925.1192165535663.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7644514.1193320447309.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4830?page=all ]

Luc Texier resolved JBAS-4830.
------------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 6. Using other Databases
> ---------------------------------------------------------------------
>
>                 Key: JBAS-4830
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4830
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Luc Texier
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6.odt, JBASS-422-Getting_Started_Guide-Chapter-6_rev3.1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 09:59:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 09:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-212) Deployment
 Contexts are
 not removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12451712.1193320741923.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=comments#action_12384335 ] 
            
Adrian Brock commented on JBMICROCONT-212:
------------------------------------------

This has been fixed, but I'm not closing this until I know what release it is going in.

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 10:01:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Thu, 25 Oct 2007 10:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28577466.1193320861623.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4900?page=all ]

Adrian Brock updated JBAS-4900:
-------------------------------

    Component/s: Deployment services

This has been fixed in the trunk of the deployers-impl project.
It's need a microcontainer release to fix the problem in the appserver.

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:15:06 2007
From: jira-events at lists.jboss.org (Aslak (JIRA))
Date: Thu, 25 Oct 2007 11:15:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1122)
 *MessageCountersAsHTML LastAdd uses wrong value
Message-ID: <15674199.1193325306988.JavaMail.jira@cloud.prod.atl2.jboss.com>

*MessageCountersAsHTML LastAdd uses wrong value
-----------------------------------------------

                 Key: JBMESSAGING-1122
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122
             Project: JBoss Messaging
          Issue Type: Bug
          Components: Messaging Core
            Reporter: Aslak
         Assigned To: Tim Fox


ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value.


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:21:01 2007
From: jira-events at lists.jboss.org (Aslak (JIRA))
Date: Thu, 25 Oct 2007 11:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1122)
 *MessageCountersAsHTML LastAdd uses wrong value
In-Reply-To: <15674199.1193325306988.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23309610.1193325661741.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1122?page=all ]

Aslak updated JBMESSAGING-1122:
-------------------------------

    Attachment: JBMESSAGING-1122.patch

A patch that adds a MessageCounter.getLastAdd. It is not 100% since it only updates itself each time 
the onTime method is called, but close enough..

Also did a little clean up, using the MessageCounter 'directly' insted of hassling with the StringTokenizer/getCounterAsString/Integer.parseInt stuff..

> *MessageCountersAsHTML LastAdd uses wrong value
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1122
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>            Reporter: Aslak
>         Assigned To: Tim Fox
>         Attachments: JBMESSAGING-1122.patch
>
>
> ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:34:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Thu, 25 Oct 2007 11:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3556165.1193326441421.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-570?page=comments#action_12384367 ] 
            
Vladimir Blagojevic commented on JGRP-570:
------------------------------------------

Bela, what do you think? It would be very nice to have ThreadFactory and create threads from factory. Did you talk about exposing this API so users can hook their own factory? Maybe 2.6 afterall? 

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 11:54:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 11:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2561807.1193327641564.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Thomas Diesler reopened JBAS-4895:
----------------------------------

             
PortComponentRef should be unbounded

   /** The port-component-ref */
   private PortComponentRef portComponentRef;

     <xsd:element name="port-component-ref"
		   type="javaee:port-component-refType"
		   minOccurs="0" maxOccurs="unbounded">
	<xsd:annotation>
	  <xsd:documentation>

	    The port-component-ref element declares a client dependency
	    on the container for resolving a Service Endpoint Interface
	    to a WSDL port. It optionally associates the Service Endpoint
	    Interface with a particular port-component. This is only used
	    by the container for a Service.getPort(Class) method call.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:20:12 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Thu, 25 Oct 2007 12:20:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPM-2) process monitoring
 and statistics capabilities (BAM)
Message-ID: <21821145.1193329212670.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12384380 ] 
            
Ronald van Kuijk commented on JBPM-2:
-------------------------------------

This is NEW functionality.. so it is not dangerous at all (real admins look further than just a red flag ;-) ) It is not closed either since jbpm does not have this functionality (yet).

I do think however that an issue can hardly be blocking if no version is assigned to it.

> process monitoring and statistics capabilities (BAM)
> ----------------------------------------------------
>
>                 Key: JBPM-2
>                 URL: http://jira.jboss.com/jira/browse/JBPM-2
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>         Environment: N/A
>            Reporter: Ronald van Kuijk
>            Priority: Blocker
>
> JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=49900689
> 1.  jBPM should store the duration and start date of a state/process in the logs
> 2.  Write some detailed info on wiki
> 3.  Show processinstance and data
> 4.  day/week/month overviews
> 5.  near realtime data per process
> 6.  produce graphs of day/week/month overviews
> Some more ideas i got from a requirements document...
> -  Number of cases processed in through a particular process definition
> -  Number of cases flowing through a particular activity
> -  Longest work item delay by activity
> -  Workitems awaiting a particular task
> -  Workitems in a specific worklist claimed and/or completed by a particular user
> -  Longest end-to-end delay
> -  Mean time to approve by activity by participant
> -  Mean end-to-end completion time.
> as background info, here's what the competition says about BAM:
> http://appian.com/AppianEnt/Analytics/analytics.html
> http://www.webmethods.com/meta/default/folder/0000005936
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduction/htm/ebiz_intro_story_piew.asp
> http://www.tibco.com/software/business_optimization/activity_monitoring.jsp?m=c1
> http://www.vitria.com/products/platform/bam.html
> http://looselycoupled.com/glossary/BAM

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:20:12 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:20:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13785177.1193329212832.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384381 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

soapHeader should be of type List<QName>

   private List<String> soapHeader;

      <xsd:element name="soap-header"
		   type="javaee:xsdQNameType"
		   minOccurs="0" maxOccurs="unbounded">
	<xsd:annotation>
	  <xsd:documentation>

	    Defines the QName of a SOAP header that will be processed
	    by the handler.

	  </xsd:documentation>
	</xsd:annotation>
      </xsd:element>


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:39:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23313246.1193330343994.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384388 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

serviceNamePattern should be of type QName

   private String serviceNamePattern;

  <xsd:simpleType name="service-ref_qname-pattern">
     <xsd:annotation>
        <xsd:documentation>
	     This is used to specify the QName pattern in the
	     attribute service-name-pattern and port-name-pattern in
	     the handler-chain element

	     For example, the various forms acceptable here for
	     service-name-pattern attribute in handler-chain element
	     are :

	     Exact Name: service-name-pattern="ns1:EchoService"

		 In this case, handlers specified in this
		 handler-chain element will apply to all ports with
		 this exact service name. The namespace prefix must
		 have been declared in a namespace declaration
		 attribute in either the start-tag of the element
		 where the prefix is used or in an an ancestor
		 element (i.e. an element in whose content the
		 prefixed markup occurs)

	     Pattern : service-name-pattern="ns1:EchoService*"

		 In this case, handlers specified in this
		 handler-chain element will apply to all ports whose
		 Service names are like EchoService1, EchoServiceFoo
		 etc. The namespace prefix must have been declared in
		 a namespace declaration attribute in either the
		 start-tag of the element where the prefix is used or
		 in an an ancestor element (i.e. an element in whose
		 content the prefixed markup occurs)

	     Wild Card : service-name-pattern="*"

		In this case, handlers specified in this handler-chain
		element will apply to ports of all service names.

	    The same can be applied to port-name attribute in
	    handler-chain element.

        </xsd:documentation>
     </xsd:annotation>

     <xsd:restriction base="xsd:token">
        <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
     </xsd:restriction>

  </xsd:simpleType>


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:41:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25190627.1193330461461.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384389 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

Both should be of type QName

   private String serviceNamePattern;
   
   private String portNamePattern;


         <xsd:element name="service-name-pattern"
		      type="javaee:service-ref_qname-pattern" />
         <xsd:element name="port-name-pattern"
	              type="javaee:service-ref_qname-pattern" />


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:43:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 12:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2036372.1193330581828.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384391 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

protocolBindings should be of type String

   // TODO protocol-bindings


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:51:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 12:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27718444.1193331061733.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384396 ] 
            
Scott M Stark commented on JBAS-4895:
-------------------------------------

Attach standard and jboss xml fragments that can be incorporated into the metadata unit tests for these please.


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 12:57:01 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 25 Oct 2007 12:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24758336.1193331421645.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Galder Zamarreno updated JBAS-4841:
-----------------------------------

    Attachment: updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt

Attached can be found an updated version of the document.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Galder Zamarreno
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:01:05 2007
From: jira-events at lists.jboss.org (Galder Zamarreno (JIRA))
Date: Thu, 25 Oct 2007 13:01:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31865614.1193331665487.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4841?page=comments#action_12384401 ] 
            
Galder Zamarreno commented on JBAS-4841:
----------------------------------------

Due to lack of time, the following sections have not been incorporated:

- Explain common down_thread and up_thread attributes from http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsProtocolCommonProperties
- Cluster does not join / troubleshooting section from http://www.jgroups.org/javagroupsnew/docs/manual/html/ch02.html#ItDoesntWork
- Best practices explained in http://wiki.jboss.org/wiki/Wiki.jsp?page=TwoClustersSameNetwork 
- Effect of -b AS parameter in JGroups.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Galder Zamarreno
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:34:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 13:34:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <637905.1193333643828.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384408 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

jaxrpc <service-ref>

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/jaxrpc/serviceref/

jaxws <service-ref>

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/jaxws/webserviceref/


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:37:11 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Thu, 25 Oct 2007 13:37:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1123) When working
 with a
 snapshot release, JBM should report at boot  "r<svn-revision-number"
 instead of the next point release
Message-ID: <8939922.1193333831608.JavaMail.jira@cloud.prod.atl2.jboss.com>

When working with a snapshot release, JBM should report at boot  "r<svn-revision-number" instead of the next point release
--------------------------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1123
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1123
             Project: JBoss Messaging
          Issue Type: Feature Request
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Ovidiu Feodorov
            Priority: Minor




-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:42:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Thu, 25 Oct 2007 13:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8999279.1193334121506.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4895?page=comments#action_12384409 ] 
            
Thomas Diesler commented on JBAS-4895:
--------------------------------------

jaxws <service-ref> 

https://svn.jboss.org/repos/jbossws/framework/branches/jbossws-framework-2.0.2/src/test/resources/jaxws/samples/webserviceref/

> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 13:51:01 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 13:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10474064.1193334661498.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-480?page=comments#action_12384411 ] 
            
Jason T. Greene commented on JBAOP-480:
---------------------------------------

There are 2 unit tests in in the pojo cache project that hit it frequently, (about 1 in 4 runs triggers it on my system)

svn co https://svn.jboss.org/repos/jbosscache/pojo/trunk pojocache-trunk
cd pojocache-trunk
mvn -Dtest=LocalConcurrentTest test

The failure logs for whichever test failes are in target/surefire-reports/

Is this sufficient?





> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:03:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 14:03:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25257674.1193335382118.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384412 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

The name of the property probably becomes a discussion whose scope extends across the AS, since if there's a requirement to provide an id to each server, we might as well use that value elsewhere.  See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122241 .

Also, there should be a cmd line switch to set this.  Gone are the days of telling people in trainings, etc "fire up 2 AS instances with run - c all and you'll have a cluster."  Saying "run -i 0 - c all" and "run -i 1 -c all" is fairly palatable.  Saying "run -Dserver.peer.id=0 -c all" and "run -Dserver.peer.id=1 - c all" .... well, yuck.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:20:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Thu, 25 Oct 2007 14:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10048564.1193336401570.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Vladimir Blagojevic reopened JGRP-608:
--------------------------------------

             
Lock scope is too big. There are tests failures with this "fix".

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:46:01 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 14:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7473239.1193337961609.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Stefan Guilhen resolved JBAS-4804.
----------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
       Resolution: Rejected

The ssoid and session cookie name can now be injected by the httpHeaderForSSOAuth and sessionCookieForSSOAuth attributes of GenericHeaderAuthenticator. A web application can now perform the whole generic header auth configuration on it's own WEB-INF/context.xml file. No changes to the container config files are needed. 

This is how the WEB-INF/context.xml should look like now when using the GenericHeaderAuthenticator:

<Context>
  <Valve className="org.jboss.web.tomcat.security.GenericHeaderAuthenticator" httpHeaderForSSOAuth="sm_ssoid,ct-remote-user,HTTP_OBLIX_UID"
         sessionCookieForSSOAuth="SMSESSION,CTSESSION,ObSSOCookie"/>
</Context>

A test case named GenericHeaderAuthUnitTestCase has been developed to test this behaviour. The wiki has also been updated.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:01 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 14:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32989127.1193338321934.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Stefan Guilhen reopened JBAS-4804:
----------------------------------

             
Re-opening issue to assign to correct resolution.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For: JBossAS-4.2.3.GA,  JBossAS-5.0.0.Beta3
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:02 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 14:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5429916.1193338322096.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Stefan Guilhen resolved JBAS-4804.
----------------------------------

    Resolution: Done

Issue's resolution set to Done instead of Rejected.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:02 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 25 Oct 2007 14:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5096906.1193338322260.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Anil Saldhana reopened JBAS-4804:
---------------------------------

             
Reopen to remove the rejected tag from resolution field.

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For: JBossAS-4.2.3.GA,  JBossAS-5.0.0.Beta3
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:52:02 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Thu, 25 Oct 2007 14:52:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4804)
 GenericHeaderAuthenticator injection of ssoid, sessioncookie name
In-Reply-To: <20391927.1191610683783.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21107393.1193338322450.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4804?page=all ]

Anil Saldhana closed JBAS-4804.
-------------------------------

    Resolution: Done

> GenericHeaderAuthenticator injection of ssoid, sessioncookie name
> -----------------------------------------------------------------
>
>                 Key: JBAS-4804
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4804
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication
> Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX).  We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition.
> Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case).  This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:54:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 14:54:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24078940.1193338451727.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384424 ] 
            
Tim Fox commented on JBMESSAGING-1121:
--------------------------------------

We may be able to do away with the necessity of the user configuring a unique id by doing something like the following:

When a server starts look in it's config files for the server id, if it does not exist request one from a sequence managed by the co-ordinator. Once it obtains an id, write it into its config files

When the server starts the next time it will already have the generated id so it will know which queues in the database "belong" to it.

Server ids need to be persistent since each node owns it's own set of queues.

Alternatively we could generate the ids as GUIDs then we avoid a global sequence, but then lookups in the DB based on a GUID string will be slower than an int, potentially hitting JBM performance.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 14:56:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 14:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7760196.1193338561661.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384426 ] 
            
Tim Fox commented on JBMESSAGING-1121:
--------------------------------------

Actually I think GUIDs are the only option, since different bridged servers also need unique ids and they won't be in the same JGroups group so a shared sequence won't work.

For JBM 2.0 using a GUID becomes a non issue since each node will have its own store.

I can do an experiment and see if there is much impact in making node_id a (potentially long) string...

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:05:11 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 15:05:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13487616.1193339111806.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Jason T. Greene updated JBAOP-480:
----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098971

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:07:01 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 15:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5687725.1193339221608.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-480?page=comments#action_12384428 ] 
            
Jason T. Greene commented on JBAOP-480:
---------------------------------------

BTW, I noticed a couple of thread safety problems in GeneratedClassAdvisor, which are likely the cause, and started a forum thread here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098971


> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.beta2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:11:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 15:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15989998.1193339461582.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384430 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

That would be useful information. But, TBH, the integer approach you have now could be fine, if you regard trusting the user to pass in the correct value at startup to be adequate persistence (seems OK to me.) I used to dislike your use of integer, but now it's growing on me; i.e. it makes a perfectly good jvmRoute for the web tier.  A GUID would be a pretty long to append to web session ids.

Suggest we try and use the http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122241 thread to have a general discussion of where node ids might be needed and what format is required for each use case.  That thread's got Scott's attention. If we can come up with a single approach that meets all needs, that would be ideal.

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 15:26:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Thu, 25 Oct 2007 15:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1121) Allow
 command line configuration of ServerPeerID
In-Reply-To: <18708558.1193253481519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19707246.1193340361565.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1121?page=comments#action_12384433 ] 
            
Brian Stansberry commented on JBMESSAGING-1121:
-----------------------------------------------

LOL. This all seemed so familiar.  Then I found http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108609  .

> Allow command line configuration of ServerPeerID
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1121
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1121
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Tim Fox
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration
>
>
> The ServerPeer ServerPeerID is currently hard coded at 0 in messaging-service.xml. If you want to set up a cluster, the only way to get it to work is to manually change the value in that file in each node.  This needs to be configurable from the command line; i.e via system property substitution.
> Need to be sure any changes made in the messaging-service.xml are also reflected in docs/examples/binding-manager/sample-bindings.xml.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:11:16 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Thu, 25 Oct 2007 16:11:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6778138.1193343076481.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384439 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

I have temporarily commented out ConnectionConsumerTest::testStopWhileProcessing since it hangs the test suite until this task is complete.

Be sure to uncommented it before closing this task

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:25:01 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-409) Make a version of
 ScopedJbossClassPool that works with AS 5
In-Reply-To: <32250594.1181062448417.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5575078.1193343901554.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-409?page=all ]

Kabir Khan closed JBAOP-409.
----------------------------

    Resolution: Done

> Make a version of ScopedJbossClassPool that works with AS 5
> -----------------------------------------------------------
>
>                 Key: JBAOP-409
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-409
>             Project: JBoss AOP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.beta2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20945904.1193344082290.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Kabir Khan updated JBAOP-480:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.CR2
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-388) Allow specification
 of the exception for after-throwing and finally bindings
In-Reply-To: <12227475.1176743158464.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1599406.1193344082652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-388?page=all ]

Kabir Khan updated JBAOP-388:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Allow specification of the exception for after-throwing and finally bindings
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-388
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-388
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> We need to provide an optional attribute to the throwing/finally tags (and to the corrersponding annotation, if it has already been implemented JBAOP-386), so the user can specify an exception type.
> This task includes updating:
> - advice validation algorithm
> - overloaded advice selection algorithm
> - documentation (tutorial, reference manual, etc)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:02 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-107) The different types
 of classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <5899603.1193344082932.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan updated JBAOP-107:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-253) Before release,
 submit the jar to the Messaging team for testing
Message-ID: <29545429.1193344083188.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ]

Kabir Khan updated JBAOP-253:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Before release, submit the jar to the Messaging team for testing
> ----------------------------------------------------------------
>
>                 Key: JBAOP-253
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-253
>             Project: JBoss AOP
>          Issue Type: Task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-209) Change any usage of
 java.rmi.MarshalledObject with JBoss Serialization's equivalent.
Message-ID: <30091269.1193344083397.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-209?page=all ]

Kabir Khan updated JBAOP-209:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.
> ------------------------------------------------------------------------------------
>
>                 Key: JBAOP-209
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-209
>             Project: JBoss AOP
>          Issue Type: Feature Request
>    Affects Versions: 1.3.5
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>


-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-416) Exclude tests
 testing new functionality from precompiled-compatibility-tests
In-Reply-To: <15845906.1181767768177.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23452125.1193344083536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-416?page=all ]

Kabir Khan updated JBAOP-416:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Exclude tests testing new functionality from precompiled-compatibility-tests
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-416
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-416
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>            Priority: Optional
>             Fix For: 2.0.0.CR2
>
>
> Once that is done, can you do me a favour?
> Kabir says:
> build.sh -f build-test-jdk50.xml clean-tests compile-test-classes precompiled-compatibility-tests
> Kabir says:
> It weaves with aop 1.5.5.GA and runs with AOP 2.0
> Kabir says:
> some tests will fail, but most should pass
> Fl?via says:
> Sure
> Kabir says:
> The tests that fail will hopefully be tests where we added some functionality in AOP 2.0 that does not exist in AOP 1.5.5.GA
> Kabir says:
> Ideally we need some way to exclude tests that are newer functionality than exists in the old version
> Kabir says:
> I'll add a JIRA for that
> Kabir says:
> since it would be good to get these automated
> Kabir says:
> I only remembered this since I spoke to Jason Green earlier about backward compatibility
> Fl?via says:
> Yes. After all, we don't have a way of making new functionality work in JBAOP1.5
> Kabir says:
> Thanks

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-433) Caller Interceptor
 Chains Are Not Rebuilt
In-Reply-To: <1733027.1183437963987.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28366582.1193344083739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-433?page=all ]

Kabir Khan updated JBAOP-433:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> Caller Interceptor Chains Are Not Rebuilt
> -----------------------------------------
>
>                 Key: JBAOP-433
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-433
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha5
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> The rebuild process of interceptor chains for caller pointcuts is not taking place correctly: no pointcut rematching is being performed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:28:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:28:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-380) JBoss AOP sets info
 field to null before rebuilding a chain
In-Reply-To: <18445535.1176731518531.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29657920.1193344083916.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-380?page=all ]

Kabir Khan updated JBAOP-380:
-----------------------------

    Fix Version/s: 2.0.0.CR2
                       (was: 2.0.0.beta2)

> JBoss AOP sets info field to null before rebuilding a chain
> -----------------------------------------------------------
>
>                 Key: JBAOP-380
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-380
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha4
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR2
>
>
> Advisor sets the joinpoint info field as null before rebuilding the interceptor chain. So, for a short period of time, that joinpoint will not be intercepted.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:03 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-380) JBoss AOP sets info
 field to null before rebuilding a chain
In-Reply-To: <18445535.1176731518531.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4984019.1193344203829.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-380?page=all ]

Kabir Khan updated JBAOP-380:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> JBoss AOP sets info field to null before rebuilding a chain
> -----------------------------------------------------------
>
>                 Key: JBAOP-380
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-380
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha4
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> Advisor sets the joinpoint info field as null before rebuilding the interceptor chain. So, for a short period of time, that joinpoint will not be intercepted.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30692669.1193344204036.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-480?page=all ]

Kabir Khan updated JBAOP-480:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.CR1
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-253) Before release,
 submit the jar to the Messaging team for testing
Message-ID: <3885674.1193344204302.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ]

Kabir Khan updated JBAOP-253:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Before release, submit the jar to the Messaging team for testing
> ----------------------------------------------------------------
>
>                 Key: JBAOP-253
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-253
>             Project: JBoss AOP
>          Issue Type: Task
>            Reporter: Ovidiu Feodorov
>         Assigned To: Kabir Khan
>            Priority: Minor
>             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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-209) Change any usage of
 java.rmi.MarshalledObject with JBoss Serialization's equivalent.
Message-ID: <9168969.1193344204443.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-209?page=all ]

Kabir Khan updated JBAOP-209:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.
> ------------------------------------------------------------------------------------
>
>                 Key: JBAOP-209
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-209
>             Project: JBoss AOP
>          Issue Type: Feature Request
>    Affects Versions: 1.3.5
>            Reporter: Bill Burke
>         Assigned To: Bill Burke
>            Priority: Minor
>             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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-416) Exclude tests
 testing new functionality from precompiled-compatibility-tests
In-Reply-To: <15845906.1181767768177.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19266197.1193344204586.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-416?page=all ]

Kabir Khan updated JBAOP-416:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Exclude tests testing new functionality from precompiled-compatibility-tests
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-416
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-416
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>            Priority: Optional
>             Fix For: 2.0.0.CR1
>
>
> Once that is done, can you do me a favour?
> Kabir says:
> build.sh -f build-test-jdk50.xml clean-tests compile-test-classes precompiled-compatibility-tests
> Kabir says:
> It weaves with aop 1.5.5.GA and runs with AOP 2.0
> Kabir says:
> some tests will fail, but most should pass
> Fl?via says:
> Sure
> Kabir says:
> The tests that fail will hopefully be tests where we added some functionality in AOP 2.0 that does not exist in AOP 1.5.5.GA
> Kabir says:
> Ideally we need some way to exclude tests that are newer functionality than exists in the old version
> Kabir says:
> I'll add a JIRA for that
> Kabir says:
> since it would be good to get these automated
> Kabir says:
> I only remembered this since I spoke to Jason Green earlier about backward compatibility
> Fl?via says:
> Yes. After all, we don't have a way of making new functionality work in JBAOP1.5
> Kabir says:
> Thanks

-- 
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

       



From jira-events at lists.jboss.org  Thu Oct 25 16:30:04 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-433) Caller Interceptor
 Chains Are Not Rebuilt
In-Reply-To: <1733027.1183437963987.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6901723.1193344204765.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-433?page=all ]

Kabir Khan updated JBAOP-433:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Caller Interceptor Chains Are Not Rebuilt
> -----------------------------------------
>
>                 Key: JBAOP-433
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-433
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.5.5.GA, 2.0.0.alpha5
>            Reporter: Flavia Rainone
>         Assigned To: Stale Pedersen
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> The rebuild process of interceptor chains for caller pointcuts is not taking place correctly: no pointcut rematching is being performed.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:05 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-107) The different types
 of classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <7040881.1193344205037.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan updated JBAOP-107:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:30:05 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:30:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-388) Allow specification
 of the exception for after-throwing and finally bindings
In-Reply-To: <12227475.1176743158464.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31595471.1193344205211.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-388?page=all ]

Kabir Khan updated JBAOP-388:
-----------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.CR2)

> Allow specification of the exception for after-throwing and finally bindings
> ----------------------------------------------------------------------------
>
>                 Key: JBAOP-388
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-388
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Flavia Rainone
>         Assigned To: Flavia Rainone
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> We need to provide an optional attribute to the throwing/finally tags (and to the corrersponding annotation, if it has already been implemented JBAOP-386), so the user can specify an exception type.
> This task includes updating:
> - advice validation algorithm
> - overloaded advice selection algorithm
> - documentation (tutorial, reference manual, etc)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:32:01 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Thu, 25 Oct 2007 16:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-107) The different
 types of
 classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <3649005.1193344321523.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-107?page=comments#action_12384444 ] 
            
Kabir Khan commented on JBAOP-107:
----------------------------------

asintegration/org.jboss.aop.asintegration.jboss5 should be moved into the AS 5 source tree, once that has the MC upgraded to 2.0.0.Beta5

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 16:59:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 16:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBCOMMON-36) ExternalContext
 needs pass
 proxy interface set to the Proxy.newProxyInstance(loader, interfaces,
 handler); in createProxyContext method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11055981.1193345941491.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis reassigned JBCOMMON-36:
------------------------------------------

    Assignee: Dimitris Andreadis  (was: Vicky Kak)

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>    Affects Versions: 1.0.0.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
> >>java.lang.IllegalArgumentException: repeated interface: 

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:03:04 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Thu, 25 Oct 2007 17:03:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-1292) SFSB session
	replication
Message-ID: <31825584.1193346184761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-1292?page=all ]

Jason T. Greene closed JBAS-1292.
---------------------------------

    Resolution: Out of Date

> SFSB session replication
> ------------------------
>
>                 Key: JBAS-1292
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1292
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>            Reporter: Bela Ban
>         Assigned To: Jason T. Greene
>   Original Estimate: 10 weeks
>  Remaining Estimate: 10 weeks
>
> - Issues: who instrument the user-specified object? Can it be done transparently?
>   - SFSB has states defined already and user declared it as "clusterable", can we
>     declare the fields object as "advisable" at runtime. Meaning, deployer will know
>     this bean is clusterable and it will "delegate" it to JBossAop to declare all
>     the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor
>     at run time. Check with Bill on this feature.
>   - Check modified field and do fine-grained replication only

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:16:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2106347.1193346961698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

              Summary: Add a Classes.getAllUniqueInterfaces utility method.  (was: ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.)
           Issue Type: Feature Request  (was: Bug)
    Affects Version/s:     (was: 1.0.0.GA)
          Description: 
Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.


  was:
In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
>>java.lang.IllegalArgumentException: repeated interface: 


> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:16:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:16:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9772801.1193346961850.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis closed JBCOMMON-36.
--------------------------------------

    Resolution: Done

Added the new utility method.

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.2.3.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:18:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21083444.1193347081672.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Comment: was deleted

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:18:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:18:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13359204.1193347081834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Comment: was deleted

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:18:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:18:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-36) Add a
 Classes.getAllUniqueInterfaces utility method.
In-Reply-To: <5954950.1191330423861.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21562425.1193347082044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-36?page=all ]

Dimitris Andreadis updated JBCOMMON-36:
---------------------------------------

    Comment: was deleted

> Add a Classes.getAllUniqueInterfaces utility method.
> ----------------------------------------------------
>
>                 Key: JBCOMMON-36
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-core, common-old
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For: 2.0.6.GA, 1.2.2.GA, 1.0.5.GA, 2.2.3.GA
>
>
> Add a Classes.getAllUniqueInterfaces utility method that returns a Class[] with all the unique interfaces implemented by a Class and it's superclasses. This array can be used when creating Proxies with Proxy.newProxyInstance(loader, interfaces, handler), without the fear of specifying duplicate interfaces, due to inheritence.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:40:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4753) ExternalContext
 needs pass proxy
 interface set to the Proxy.newProxyInstance(loader, interfaces, handler);
 in createProxyContext method.
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32615750.1193348401510.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4753?page=all ]

Dimitris Andreadis reassigned JBAS-4753:
----------------------------------------

    Assignee: Dimitris Andreadis  (was: Vicky Kak)

> ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.5.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can  populate the ifaces with the duplicate Interface entries .
> When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler);  it results in the exception 
> >>java.lang.IllegalArgumentException: repeated interface:

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:42:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4753) ExternalContext can
 pass
 duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5595344.1193348521540.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4753?page=all ]

Dimitris Andreadis updated JBAS-4753:
-------------------------------------

              Summary: ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)  (was: ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.)
        Fix Version/s: JBossAS-4.2.3.GA
    Affects Version/s: JBossAS-4.2.2.GA
                       JBossAS-4.2.1.GA
                       JBossAS-4.2.0.GA
                       JBossAS-5.0.0.Beta2
                           (was: JBossAS-4.0.5.GA)
          Description: 
The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).





  was:
In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can  populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler);  it results in the exception 
>>java.lang.IllegalArgumentException: repeated interface:







> ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 17:49:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 17:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4753) ExternalContext
 can pass
 duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15858262.1193348941707.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4753?page=comments#action_12384448 ] 
            
Dimitris Andreadis commented on JBAS-4753:
------------------------------------------

I didn't change the existing Classes.getAllInterfaces(..) for compatibility reasons.

I added a new utility method in JBCOMMON-36 that can be used to construct the array of implemented interfaces, in presence of duplicates.

To avoid generating yet another jboss-common release just for this fix, I copied the body of the utility method inside server/src/main/org/jboss/naming/ExternalContext.java.

After we update Branch_4_2 to jboss common 1.2.2 and HEAD to jboss common-core 2.2.3, this can be properly replaced with a call to the Classes.getAllUniqueInterfaces(..) utility.

> ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 18:00:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Thu, 25 Oct 2007 18:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4753) ExternalContext can
 pass duplicate
 interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
In-Reply-To: <15754758.1190780692870.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31826824.1193349601746.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4753?page=all ]

Dimitris Andreadis closed JBAS-4753.
------------------------------------

    Resolution: Done

Done.

> ExternalContext can pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4753
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4753
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>            Reporter: Vicky Kak
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> The fix for JBAS-4048 made it possible to pass duplicate interfaces to Proxy.newProxyInstance(loader, interfaces, handler).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 18:33:01 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Thu, 25 Oct 2007 18:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4701) JaasSecurityDomain
 doesn't handle encrypted truststore passwords properly
In-Reply-To: <19151046.1189539013902.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <497067.1193351581861.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4701?page=all ]

Stefan Guilhen closed JBAS-4701.
--------------------------------


The fix code has been added to Brach_4_0, Branch_4_2 and Trunk.

> JaasSecurityDomain doesn't handle encrypted truststore passwords properly
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4701
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4701
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.5.GA
>            Reporter: Stefan Guilhen
>         Assigned To: Stefan Guilhen
>             Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.2.GA
>
>
> In a recent support case, the user reported that he could not set an encrypted password for the truststore in the same way he does for the keystore. The application server fails to start when the encrypted truststore password is used, displaying the following exception:
> java.io.IOException: Keystore was tampered with, or password was incorrect.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 18:56:11 2007
From: jira-events at lists.jboss.org (Phil Verghese (JIRA))
Date: Thu, 25 Oct 2007 18:56:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1300) BRMS -
 misspelling in label in "create new category" dialog
Message-ID: <7924962.1193352971576.JavaMail.jira@cloud.prod.atl2.jboss.com>

BRMS - misspelling in label in "create new category" dialog
-----------------------------------------------------------

                 Key: JBRULES-1300
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1300
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.2
            Reporter: Phil Verghese
            Priority: Trivial


In BRMS, go to Admin > Manage Categories > Create new category. The dialog box has a misspelling in the first label "Cateogory name" should say "Category name"

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 20:13:12 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 25 Oct 2007 20:13:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-851) Provide RuleFlow
 editing capabilities within JBRMS
In-Reply-To: <10955939.1179153237844.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17473218.1193357592189.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-851?page=comments#action_12384464 ] 
            
Michael Neale commented on JBRULES-851:
---------------------------------------

Oh man that would be nice. No sorry to let everyone down but my chops aren't that great ! Maybe after ruleflow has matured some more, we could have this. I think there are still a few iterations to go in adding features to rule flow, after that point we could look at how to do it on the web. I have seen demos on how to do it, it can be done but the moment its not really that easy. (and time wise am always pressed). 

Always happy to be pressured and bribed to make this happen. 

No, I know next to nothing about ajax (I never though ajax was hard, just a clever use of old tech).

> Provide RuleFlow editing capabilities within JBRMS
> --------------------------------------------------
>
>                 Key: JBRULES-851
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-851
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Anstis
>         Assigned To: Fernando Meyer
>
> Ruleflow should be available in the JBRMS (apologies is this JIRA should have been raised against JBRMS).

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 20:19:01 2007
From: jira-events at lists.jboss.org (Michael Neale (JIRA))
Date: Thu, 25 Oct 2007 20:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1150) Drools 4.0 BRMS
 not working with geronimo-jetty6-jee5-2.0.1
In-Reply-To: <25850901.1188508878448.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29773365.1193357941535.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1150?page=comments#action_12384466 ] 
            
Michael Neale commented on JBRULES-1150:
----------------------------------------

ah yes - there could be java 6 issues - I haven't had a chance to check at this stage, but will shortly. With trunk we are moving to java 5 and up, so that will make it easier to get rid of the legacy that would be holding back for java 6 support. I believe most containers have some issues with java 6 at this stage (but they should be getting resolved rapidly). 

> Drools 4.0 BRMS not working with geronimo-jetty6-jee5-2.0.1
> -----------------------------------------------------------
>
>                 Key: JBRULES-1150
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1150
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>         Environment: geronimo-jetty6-jee5-2.0.1
> drools-4.0.1.SNAPSHOT-brms
>            Reporter: Bhagwath Vadyala
>         Assigned To: Fernando Meyer
>         Attachments: drools-error-screenshot.doc, jetty_2007_09_04.log, screenshot-1.jpg
>
>
> I am trying to test and see whether Drools 4.0 BRMS works with Geronimo-jetty6-jee5-2.0.1 or not.
> Drools BRMS version which I am using is drools-4.0.1.SNAPSHOT-brms.
> It deploys fine in Geronimo but when I open the BRMS error message I am getting is HTTP ERROR:404.
> Please let me know whether we can make Drools 4.0 work with Geronimo-jetty 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

        


From jira-events at lists.jboss.org  Thu Oct 25 21:55:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 21:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4895) JAXB based
	ServiceRef meta data
In-Reply-To: <16759707.1193136001444.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18209321.1193363701548.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4895?page=all ]

Scott M Stark resolved JBAS-4895.
---------------------------------

    Resolution: Done

These changes are in the latest metadata snapshot (rev 1678).


> JAXB based ServiceRef meta data
> -------------------------------
>
>                 Key: JBAS-4895
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4895
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> All service-ref based clients fail.

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 21:57:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 21:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4898) class-loading not
 found as a child of jboss-web
In-Reply-To: <23377077.1193149801645.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17451757.1193363821468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4898?page=all ]

Scott M Stark resolved JBAS-4898.
---------------------------------

    Resolution: Done

This is included in the current metadata snapshot (rev 1678).

> class-loading not found as a child of jboss-web
> -----------------------------------------------
>
>                 Key: JBAS-4898
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4898
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.jbws1581.JBWS1581EarTestCase one-test
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
>   <class-loading>
>     <loader-repository>jbossws.jbws1581:domain=jaxws-jbws1581.war</loader-repository>
>   </class-loading>
> </jboss-web>
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: class-loading not found as a child of jboss-web
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:393)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 21:59:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 21:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4910) NPE in
	AbstractMappedMetaData
In-Reply-To: <32126662.1193303701492.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11028878.1193363941449.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4910?page=all ]

Scott M Stark resolved JBAS-4910.
---------------------------------

    Resolution: Done

These changes are in the latest metadata snapshot (rev 1678).

> NPE in AbstractMappedMetaData
> -----------------------------
>
>                 Key: JBAS-4910
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4910
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefClientTestCase one-test
> Caused by: java.lang.NullPointerException
>         at org.jboss.metadata.javaee.support.AbstractMappedMetaData.addAll(AbstractMappedMetaData.java:188)
>         at org.jboss.metadata.javaee.spec.MessageDestinationsMetaData.merge(MessageDestinationsMetaData.java:66)
>         at org.jboss.metadata.client.jboss.JBossClientMetaData.merge(JBossClientMetaData.java:316)
>         at org.jboss.ejb3.deployers.JBossClientParsingDeployer.createMetaData(JBossClientParsingDeployer.java:63)
>         at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> To reproduce this, you need to enable the test in src/resources/test-excludes-jboss500.txt

-- 
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

        


From jira-events at lists.jboss.org  Thu Oct 25 22:01:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Thu, 25 Oct 2007 22:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27460093.1193364061441.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Scott M Stark updated JBAS-4901:
--------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was:  JBossAS-5.0.0.Beta3)

This also is not a metadata issue.

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For: JBossAS-5.0.0.CR1
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 00:45:07 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Fri, 26 Oct 2007 00:45:07 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAOP-480) NPE in concurrent
 join point generation
In-Reply-To: <20016371.1192498983215.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8080334.1193373907028.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAOP-480?page=comments#action_12384472 ] 
            
Flavia Rainone commented on JBAOP-480:
--------------------------------------

Yes, those examples are excelent to reproduce the error. Thanks Jason!

> NPE in concurrent join point generation
> ---------------------------------------
>
>                 Key: JBAOP-480
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-480
>             Project: JBoss AOP
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.beta1
>            Reporter: Jason T. Greene
>         Assigned To: Flavia Rainone
>             Fix For: 2.0.0.CR1
>
>
> Recently I have noticed intermittent failures in join point generation. It appears to happen when there are concurrent inocations on an advised method. 
> Caused by: java.lang.RuntimeException: Error generating joinpoint class for joinpoint Method[method=public java.lang.Object org.jboss.cache.pojo.impl.PojoCacheImpl.detach(org.jboss.cache.Fqn,java.lang.String) throws org.jboss.cache.pojo.PojoCacheException]
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:304)
> 	at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
> 	at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1627)
> 	at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:240)
> 	at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1020)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$PojoCacheImplInstanceAdvisor.detach_N_6302035201148273652(PojoCacheImpl$PojoCacheImplInstanceAdvisor.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:135)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.org$jboss$cache$pojo$impl$PojoCacheImpl$attach$aop(PojoCacheImpl.java:100)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl$JoinPoint_attach3085019539260813833.dispatch(PojoCacheImpl$JoinPoint_attach3085019539260813833.java)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxUndoSynchronizationInterceptor.invoke(PojoTxUndoSynchronizationInterceptor.java:42)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxLockInterceptor.invoke(PojoTxLockInterceptor.java:38)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoFailedTxMockupInterceptor.invoke(PojoFailedTxMockupInterceptor.java:46)
> 	at org.jboss.cache.pojo.impl.JoinPoint_attach3085019539260813833_1.invokeNext(JoinPoint_attach3085019539260813833_1.java)
> 	at org.jboss.cache.pojo.interceptors.PojoTxInterceptor.invoke(PojoTxInterceptor.java:77)
> 	... 14 more
> Caused by: java.lang.NullPointerException
> 	at org.jboss.aop.JoinPointInfo.getAdviceString(JoinPointInfo.java:184)
> 	at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:263)
> 	... 33 more

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:03:01 2007
From: jira-events at lists.jboss.org (Flavia Rainone (JIRA))
Date: Fri, 26 Oct 2007 01:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-459) Memory leaks
In-Reply-To: <18921234.1189678031248.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20406458.1193374981507.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-459?page=all ]

Flavia Rainone updated JBAOP-459:
---------------------------------

    Fix Version/s: 2.0.0.CR1
                       (was: 2.0.0.beta2)

> Memory leaks 
> -------------
>
>                 Key: JBAOP-459
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-459
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 1.3.6
>            Reporter: Kabir Khan
>         Assigned To: Flavia Rainone
>             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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:20:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 01:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBXB-112) Failed to create a
	new SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19698025.1193376001636.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Thomas Diesler reopened JBXB-112:
---------------------------------

             
 There are more occurances of this. I actually found 4, only one of them is fixed.

Caused by: java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
        at javax.xml.parsers.SAXParser.isXIncludeAware(SAXParser.java:511)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:204)
        ... 24 more


> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:39:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Fri, 26 Oct 2007 01:39:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4825) TECH REVIEW: Getting
 Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14322369.1193377141532.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

cheng dan updated JBAS-4825:
----------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-1.odt

made some small changes.

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 01:42:01 2007
From: jira-events at lists.jboss.org (cheng dan (JIRA))
Date: Fri, 26 Oct 2007 01:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4825) TECH REVIEW:
 Getting Started Guide - Chapter 1 - A Quick Tour
In-Reply-To: <4229214.1192165535001.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13086937.1193377321545.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4825?page=all ]

cheng dan resolved JBAS-4825.
-----------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 1 - A Quick Tour
> -------------------------------------------------------------
>
>                 Key: JBAS-4825
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4825
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: cheng dan
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt, JBASS-422-Getting_Started_Guide-Chapter-1.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 02:17:02 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 02:17:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13339060.1193379422252.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384483 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

To elaborate on the changes, they involve adding 

1. method event() to CoyoteInvoker
2. method getSSLSupport(SSLSession session) to RemotingSSLImplementation, and
3. constructor RemotingSSLSupport(SSLSession session) to RemotingSSLSupport(SSLSession.

The important thing to note is that, while these changes are necessary to achieve source compatibility with JBossWeb, they are not necessary for binary compatibility.  The CoyoteInvoker.event() method would only be called when the coyote system is in "comet" mode, and the RemotingSSLImplementation.getSSLSupport(SSLSession session)  would only be called by the Http11NioProtocol coyote class.  Neither of these is relevant to the current use of the coyote system by Remotig.

So current Remoting releases running in, for example, JBossAS 4.2.0.GA, will work with jbossweb.jar that ships with JBossAS.

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 03:45:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 03:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-610) Problems with large
 return value and FC
Message-ID: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>

Problems with large return value and FC
---------------------------------------

                 Key: JGRP-610
                 URL: http://jira.jboss.com/jira/browse/JGRP-610
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.6


When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:25:01 2007
From: jira-events at lists.jboss.org (joshmoore (JIRA))
Date: Fri, 26 Oct 2007 04:25:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3012) MemoryLeak in
 JaasSecurityManager::DomainInfo
Message-ID: <22847974.1193387101704.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3012?page=comments#action_12384499 ] 
            
joshmoore commented on JBAS-3012:
---------------------------------

Scott, could you clarify what you think the cause is here? We are running into this as well. A long running server had over 100K login modules plus 400K SimplePrincipals and 100K SecurityAssociationHandlers, SimpleGroups, etc. which eventually brought it to its knees. I've posted a screen shot from jprofiler at https://trac.openmicroscopy.org.uk/omero/ticket/818 , and confirmed that calling DynamicLoginConfig's flushAuthenticationCaches does free almost everything up. Not, however, the SecurityAssociation$SubjectContext instances. I'm still looking into that.

My planned work-around is to periodically call flushAuthenticationCaches. Any thoughts?

Many thanks,
Josh Moore
Glencoe Software, Inc.
The Open Microscopy Environment


From: jboss-service.xml

   <mbean code="org.jboss.security.auth.login.DynamicLoginConfig"
      name="omero:service=LoginConfig">
      <attribute name="AuthConfig">META-INF/jboss-login.xml</attribute>
      <depends optional-attribute-name="LoginConfigService">
         jboss.security:service=XMLLoginConfig
      </depends>
      <depends optional-attribute-name="SecurityManagerService">
         jboss.security:service=JaasSecurityManager
      </depends>
   </mbean>

From: jboss-login.xml

 <policy>
   <application-policy name="OmeroSecurity">
      <authentication>
          <login-module code = "ome.security.JBossLoginModule" flag = "required">
            <module-option name = "unauthenticatedIdentity">guest</module-option>
            <module-option name = "dsJndiName">java:/omeroDS</module-option>
            <module-option name = "hashAlgorithm">MD5</module-option>


> MemoryLeak in JaasSecurityManager::DomainInfo
> ---------------------------------------------
>
>                 Key: JBAS-3012
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3012
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Security
>            Reporter: Adrian Brock
>         Assigned To: Scott M Stark
>             Fix For: No Release
>
>
> There is a memory leak caused by the JaasSecurityManager::DomainInfo
> holding a reference to the LoginContext.
> Internally, this holds a reference to the context classloader.
> If this information is cached and then the classloader undeployed,
> the classloader and all associated classes/proxies/static data
> don't get garbage collected until this information is flushed.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:27:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Fri, 26 Oct 2007 04:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13857706.1193387221662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=all ]

Thomas Heute updated JBPORTAL-1773:
-----------------------------------

    Fix Version/s: 2.6.3 Final
         Assignee: Thomas Heute  (was: Julien Viet)

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>         Attachments: sample-portlet.war
>
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:38:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 04:38:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16761738.1193387881624.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12384500 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

Might be a UNICAST retransmission issue in connection with FRAG(2). If FRAG2 mangles the (unicast) headers, then we have an issue in unicast.

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 04:40:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 04:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24639860.1193388001407.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12384501 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

Not possible: FRAG2 is on top of UNICAST ! But possibly UNICAST's retransmission mangles the fragmentation IDs (FragHeader) ?

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 05:02:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 05:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
Message-ID: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>

Unwrap MetaValue in MetaValueFactory
------------------------------------

                 Key: JBMICROCONT-213
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: General
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta5


Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.

   /**
    * Unwrap meta value.
    * Supports simple and generic meta value.
    *
    * @param metaValue meta value
    * @return meta value's value
    */
   public abstract Object unwrap(MetaValue metaValue);

   /**
    * Unwrap meta value.
    * Supports simple and generic meta value.
    *
    * @param metaValue meta value
    * @param type the type
    * @return meta value's value
    */
   public abstract Object unwrap(MetaValue metaValue, Type type);

   /**
    * Unwrap meta value.
    * Supports simple and generic meta value.
    *
    * @param metaValue meta value
    * @param type the type
    * @return meta value's value
    */
   public abstract Object unwrap(MetaValue metaValue, TypeInfo type);




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 05:04:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 05:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27166065.1193389441395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=all ]

Ales Justin resolved JBMICROCONT-213.
-------------------------------------

    Resolution: Done

Implemented in DefaultMetaValueFactory.
We currently support all types of MetaValue except TableValue.

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 05:47:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Fri, 26 Oct 2007 05:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-611) MergeTask GMS
 ConcurrentModificationException
Message-ID: <32335654.1193392021705.JavaMail.jira@cloud.prod.atl2.jboss.com>

MergeTask GMS ConcurrentModificationException
---------------------------------------------

                 Key: JGRP-611
                 URL: http://jira.jboss.com/jira/browse/JGRP-611
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
         Assigned To: Bela Ban
             Fix For: 2.5.2, 2.6


[Vivek Sar]

I'm using JGroups 2.5 GA and have 3 members in the group using udp
gossip router (stack below). Occasionally, we have seen the following
exception if a node goes down and comes up again. This happens over
and over, only way to recover would then be to stop all the members
and start them again.


 2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - exception while merging
java.util.ConcurrentModificationException
	at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
	at java.util.AbstractList$Itr.next(Unknown Source)
	at org.jgroups.protocols.pbcast.CoordGmsImpl.removeRejectedMergeRequests(CoordGmsImpl.java:749)
	at org.jgroups.protocols.pbcast.CoordGmsImpl.access$500(CoordGmsImpl.java:26)
	at org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask.run(CoordGmsImpl.java:817)
	at java.lang.Thread.run(Unknown Source)
2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:27,237 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
...
...

Protocol Stack,

<config>
    <UDP
		 ip_mcast="false"
		 mcast_addr="228.10.10.10"
		 mcast_port="3092"
		 bind_addr="${jgroups.bindaddress.ip:jgroupshost}"
		 bind_port="${jgroups.bindaddress.port:3092}"		 		
         tos="16"
         ucast_recv_buf_size="200000"
         ucast_send_buf_size="640000"
         mcast_recv_buf_size="250000"
         mcast_send_buf_size="640000"
         loopback="true"
         discard_incompatible_packets="true"
         max_bundle_size="64000"
         max_bundle_timeout="30"
         use_incoming_packet_handler="true"
         use_outgoing_packet_handler="false"
         ip_ttl="32"
         enable_bundling="true"
		 use_concurrent_stack="true"
		 thread_pool.enabled="true"
		 thread_pool.min_threads="1"
		 thread_pool.max_threads="100"
		 thread_pool.keep_alive_time="20000"
		 thread_pool.queue_enabled="false"
		 thread_pool.queue_max_size="10"
		 thread_pool.rejection_policy="Run"
		 oob_thread_pool.enabled="true"
		 oob_thread_pool.min_threads="1"
		 oob_thread_pool.max_threads="4"
		 oob_thread_pool.keep_alive_time="30000"
		 oob_thread_pool.queue_enabled="true"
		 oob_thread_pool.queue_max_size="10"
		 oob_thread_pool.rejection_policy="Run"/>

    <PING gossip_host="${jgroups.gossiprouter.ip:jgroupshost}"
gossip_port="${jgroups.gossiprouter.port:3091}"
		    gossip_refresh="15000"
		    timeout="3000"
            num_initial_members="3"/>
	
	<MERGE2 min_interval="5000" max_interval="10000"
		down_thread="false" up_thread="false"/>
	
	<FD_SOCK up_thread="false" down_thread="false"/>
	
    <FD timeout="10000" max_tries="5" shun="true"/>

    <VERIFY_SUSPECT timeout="1500"/>
	
    <pbcast.NAKACK max_xmit_size="60000"
                   use_mcast_xmit="false" gc_lag="0"
                   retransmit_timeout="100,200,300,600,1200,2400,4800"
                   discard_delivered_msgs="true"/>
	
    <UNICAST timeout="300,600,1200,2400,3600"/>
	
    <ENCRYPT key_store_name="keystore" store_password="xxx"
key_password="xxx" alias="xxx"/>
	
    <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
                   max_bytes="400000"/>
	
    <VIEW_SYNC avg_send_interval="60000"/>

	
	
	<AUTH auth_class="org.jgroups.auth.MD5Token"
        auth_value="xxx"
        token_hash="MD5"/>
		
    <pbcast.GMS print_local_addr="true" join_timeout="5000"
                join_retry_timeout="2000" shun="true"/>
	
     <FC max_credits="2000000"
         min_threshold="0.10"/>
	
	<FRAG2 frag_size="60000"/>
	
    <pbcast.STATE_TRANSFER  />
</config>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 06:03:01 2007
From: jira-events at lists.jboss.org (Colin Mondesir (JIRA))
Date: Fri, 26 Oct 2007 06:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4828) TECH REVIEW:
 Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
In-Reply-To: <10791133.1192165535395.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13337769.1193392981490.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4828?page=all ]

Colin Mondesir resolved JBAS-4828.
----------------------------------

    Resolution: Done

> TECH REVIEW: Getting Started Guide - Chapter 4. Sample JSF-EJB3 Application
> ---------------------------------------------------------------------------
>
>                 Key: JBAS-4828
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4828
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Colin Mondesir
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-4.odt, JBASS-422-Getting_Started_Guide-Chapter-4.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:38:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 07:38:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4913) wsdl-override not
 found as a child of service-ref
Message-ID: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>

wsdl-override not found as a child of service-ref
-------------------------------------------------

                 Key: JBAS-4913
                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 07:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15721110.1193398801607.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4913?page=all ]

Thomas Diesler updated JBAS-4913:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test

Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
        at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

         Assignee: Alexey Loubyansky

> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:40:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 07:40:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9281629.1193398802065.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4913?page=comments#action_12384533 ] 
            
Thomas Diesler commented on JBAS-4913:
--------------------------------------

<!DOCTYPE jboss-client PUBLIC "-//JBoss//DTD Application Client 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss-client_4_0.dtd">

<jboss-client>
  <jndi-name>benchmark-client</jndi-name>

  <service-ref>
    <service-ref-name>service/BenchmarkJSE</service-ref-name>
    <wsdl-override>http://@jboss.bind.address@:8080/jaxrpc-benchmark-doc/jse?wsdl</wsdl-override>
  </service-ref>
  <service-ref>
    <service-ref-name>service/BenchmarkEJB</service-ref-name>
    <wsdl-override>http://@jboss.bind.address@:8080/jaxrpc-benchmark-doc-ejb?wsdl</wsdl-override>
  </service-ref>

</jboss-client>


> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:48:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 26 Oct 2007 07:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20070716.1193399281737.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=all ]

Adrian Brock updated JBMICROCONT-212:
-------------------------------------

    Fix Version/s: JBossMC-2.0.0.Beta6
                       (was: JBossMC-2.0.0.Beta5)

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta6
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 07:50:01 2007
From: jira-events at lists.jboss.org (Adrian Brock (JIRA))
Date: Fri, 26 Oct 2007 07:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-212) Deployment
 Contexts are not
 removed from the Microcontainer if the deployment failed when the
 deployment is undeployed
In-Reply-To: <16616734.1193320321603.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23568949.1193399401476.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-212?page=all ]

Adrian Brock closed JBMICROCONT-212.
------------------------------------

    Resolution: Done

Resolved in beta6

> Deployment Contexts are not removed from the Microcontainer if the deployment failed when the deployment is undeployed
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMICROCONT-212
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-212
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Adrian Brock
>             Fix For: JBossMC-2.0.0.Beta6
>
>
> The DeploymentControllerContexts are not getting removed from the Microcontainer at undeploy()
> when the deployment failed during deploy().
> The DeploymentControllerContext is in the ERROR state, but it still needs to be uninstalled.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:11:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Fri, 26 Oct 2007 08:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1124) Cannot find
 replicant to
 remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
Message-ID: <21857133.1193400661417.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
-----------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1124
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1124
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Tim Fox
         Assigned To: Tim Fox
            Priority: Minor
             Fix For: EAP 4.3 Integration


Get the following exception in logs when shutting down JBoss 4.2.1.GA server with JBM by pressing CTRL-C

Seems benign but annoying.

13:00:12,932 WARN  [ConnectionFactory] Stopping failed jboss.messaging.connectionfactory:service=ConnectionFactory
java.lang.IllegalStateException: Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory
        at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.unregisterConnectionFactory(ConnectionFactoryJNDIMapper.java:274)
        at org.jboss.jms.server.connectionfactory.ConnectionFactory.stopService(ConnectionFactory.java:239)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
        at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:206)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
        at $Proxy0.stop(Unknown Source)
        at org.jboss.system.ServiceController.stop(ServiceController.java:508)
        at org.jboss.system.ServiceController.stop(ServiceController.java:499)
        at org.jboss.system.ServiceController.stop(ServiceController.java:499)
        at org.jboss.system.ServiceController.stop(ServiceController.java:499)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.stop(Unknown Source)
        at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:336)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy51.stop(Unknown Source)
        at org.jboss.deployment.XSLSubDeployer.stop(XSLSubDeployer.java:202)
        at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
        at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
        at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:516)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:1058)
        at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:1033)
        at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:996)
13:00:12,968 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at c971d55 undeployed
13:00:13,063 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 7451b0af undeployed


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:37:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Fri, 26 Oct 2007 08:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27090207.1193402221523.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=comments#action_12384547 ] 
            
Dimitris Andreadis commented on JBMICROCONT-213:
------------------------------------------------

You can't have both Affects the Fixed version the same! If Beta5 was released on the 20th, the fixed version should be Beta6.

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:45:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21724839.1193402701605.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=all ]

Ales Justin updated JBMICROCONT-213:
------------------------------------

    Affects Version/s: JBossMC-2.0.0.Beta4
                           (was: JBossMC-2.0.0.Beta5)

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:47:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-213) Unwrap
 MetaValue in MetaValueFactory
In-Reply-To: <28745784.1193389321501.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8309743.1193402821815.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-213?page=all ]

Ales Justin updated JBMICROCONT-213:
------------------------------------

    Comment: was deleted

> Unwrap MetaValue in MetaValueFactory
> ------------------------------------
>
>                 Key: JBMICROCONT-213
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-213
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: General
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Add a way to get the initial value from which you created the MetaValue - unwrapping the MetaValue in MetaValueFactory.
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, Type type);
>    /**
>     * Unwrap meta value.
>     * Supports simple and generic meta value.
>     *
>     * @param metaValue meta value
>     * @param type the type
>     * @return meta value's value
>     */
>    public abstract Object unwrap(MetaValue metaValue, TypeInfo type);

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:54:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-210) Change
 KernelBus implementation
In-Reply-To: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3341158.1193403241482.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-210?page=all ]

Ales Justin updated JBMICROCONT-210:
------------------------------------

    Affects Version/s: JBossMC-2.0.0.Beta4
                           (was: JBossMC-2.0.0.Beta5)

> Change KernelBus implementation
> -------------------------------
>
>                 Key: JBMICROCONT-210
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
> Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:54:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-209) Trim string
	value
In-Reply-To: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30825176.1193403241616.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-209?page=all ]

Ales Justin updated JBMICROCONT-209:
------------------------------------

    Affects Version/s: JBossMC-2.0.0.Beta4
                           (was: JBossMC-2.0.0.Beta5)

> Trim string value
> -----------------
>
>                 Key: JBMICROCONT-209
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: MetaData
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 08:58:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 08:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMICROCONT-205) Accessing
 content of vfsfile url fails
In-Reply-To: <22654520.1188863898204.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18654671.1193403481842.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-205?page=all ]

Ales Justin reassigned JBMICROCONT-205:
---------------------------------------

    Assignee: Ales Justin

> Accessing content of vfsfile url fails
> --------------------------------------
>
>                 Key: JBMICROCONT-205
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-205
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: VFS
>            Reporter: Scott M Stark
>         Assigned To: Ales Justin
>             Fix For: JBossMC-2.0.0.CR1
>
>
> When trying to create a ManagedProperty for a URL type with a vfsfile: url value, the content fails to be obtained:
> Caused by: java.net.UnknownServiceException: no content-type
>         at java.net.URLConnection.getContentHandler(URLConnection.java:1167)
>         at java.net.URLConnection.getContent(URLConnection.java:683)
>         at java.net.URL.getContent(URL.java:1021)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
>         at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
>         at org.jboss.beans.info.plugins.AbstractPropertyInfo.get(AbstractPropertyInfo.java:172)
>         at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:238)
>         at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:371)
>         ... 23 more
> VirtualFileURLConnection should be overriding the getContent method to return the VirtualFile I suppose.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:00:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-210) Change KernelBus
 implementation
In-Reply-To: <28072211.1191841083401.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5491781.1193403601431.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-210?page=all ]

Ales Justin closed JBMICROCONT-210.
-----------------------------------


> Change KernelBus implementation
> -------------------------------
>
>                 Key: JBMICROCONT-210
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-210
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> Change the basic KernelBus implementation to use (Invoke|Attribute)DispatchContext notion.
> Add the same notion to Kernel objects registered directly to KernelRegistry.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:02:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMICROCONT-211) Support ..
 notion in vfs paths
In-Reply-To: <9963001.1193307301447.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30252399.1193403721548.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-211?page=all ]

Ales Justin reassigned JBMICROCONT-211:
---------------------------------------

    Assignee: Ales Justin

> Support .. notion in vfs paths
> ------------------------------
>
>                 Key: JBMICROCONT-211
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-211
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: VFS
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>
> If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
> in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
> currently the PathTokenizer will report an error if the path contains a . or ..
> It should still through an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:02:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMICROCONT-211) Support ..
 notion in vfs paths
In-Reply-To: <9963001.1193307301447.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1232033.1193403721754.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-211?page=all ]

Ales Justin updated JBMICROCONT-211:
------------------------------------

    Description: 
If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
currently the PathTokenizer will report an error if the path contains a . or ..

It should still throw an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

  was:
If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
currently the PathTokenizer will report an error if the path contains a . or ..

It should still through an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.


> Support .. notion in vfs paths
> ------------------------------
>
>                 Key: JBMICROCONT-211
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-211
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: VFS
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>
> If a VFS path contains a .. it should be possible to invoke getParent() to navigate the path
> in AbstractVirtualFileHandler's structuredFindChild() and simpleFindChild()
> currently the PathTokenizer will report an error if the path contains a . or ..
> It should still throw an error if it "goes off the top" of the VFS context. i.e. you try to a .. on a virtual file handler with no parent.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:06:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 09:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4914) NPE in JBossWebRealm
Message-ID: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in JBossWebRealm
--------------------

                 Key: JBAS-4914
                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:06:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Fri, 26 Oct 2007 09:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-209) Trim string
	value
In-Reply-To: <14916954.1191838630164.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16314963.1193403961742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-209?page=all ]

Ales Justin closed JBMICROCONT-209.
-----------------------------------


> Trim string value
> -----------------
>
>                 Key: JBMICROCONT-209
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-209
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: MetaData
>    Affects Versions: JBossMC-2.0.0.Beta4
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta5
>
>
> In terms of the value's whitespace behavior, StringValueMetaData should also have a trim property that is also true by default. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:06:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 09:06:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14430629.1193403962044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Thomas Diesler updated JBAS-4914:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED

java.lang.NullPointerException
        at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
        at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
        at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
        at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
        at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

         Assignee: Anil Saldhana

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:17:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 09:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26588129.1193404621677.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Anil Saldhana reassigned JBAS-4914:
-----------------------------------

    Assignee: Scott M Stark  (was: Anil Saldhana)

Assigned to Scott temporarily to resolve the metadata.

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 09:19:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 09:19:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9108579.1193404744622.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12384557 ] 
            
Anil Saldhana commented on JBAS-4914:
-------------------------------------

============
  ServletMetaData servletMD = metaData.getServlets().get(servletName);
  SecurityRoleRefsMetaData roleRefs = servletMD.getSecurityRoleRefs();
==================

servletMD is null.

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:01:02 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:01:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4843) TECH REVIEW: Server
 Configuration
 Guide - AppendixB - Use Alternative Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29537681.1193407262006.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

Shelly McGowan updated JBAS-4843:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt

Updates.

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:03:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Fri, 26 Oct 2007 10:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <986864.1193407381569.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

Right, all are fixed now in trunk.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:09:12 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:09:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4843) TECH REVIEW: Server
 Configuration Guide - AppendixB - Use Alternative
 Databases With JBoss AS
In-Reply-To: <10668566.1192170303483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16270629.1193407752500.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4843?page=all ]

Shelly McGowan resolved JBAS-4843.
----------------------------------

    Resolution: Done

updates are in attachment #2 - pls be sure to get the latest updates

> TECH REVIEW: Server Configuration Guide - AppendixB - Use Alternative Databases With JBoss AS
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4843
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4843
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422 - Server_Configuration_Guide - AppendixB - Use_Alternative_Databases_With_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt, JBAS-422-Server_Configuration_Guide-AppendixB-Use_Alternative_Databases_with_JBoss_AS.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:13:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Fri, 26 Oct 2007 10:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31792115.1193407981521.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4913?page=comments#action_12384571 ] 
            
Alexey Loubyansky commented on JBAS-4913:
-----------------------------------------

Is it org.jboss.metadata.javaee.spec.ServiceReferenceMetaData that is bound to service-ref? Could you tell which property in that class is supposed to be bound to wsdl-override element?

> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:22:01 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22893885.1193408521709.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

Shelly McGowan updated JBAS-4885:
---------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt

minor edit attached

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt, JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:22:02 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:22:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4885) TECH REVIEW:
 Chapter1 - Section12 - The CMP Engine
In-Reply-To: <10818570.1192791663551.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19178241.1193408522027.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4885?page=all ]

Shelly McGowan resolved JBAS-4885.
----------------------------------

    Resolution: Done

marking resolved to indicate a full chapter review was done

> TECH REVIEW:  Chapter1 - Section12 - The CMP Engine
> ---------------------------------------------------
>
>                 Key: JBAS-4885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4885
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt, JBAS-422-Server_Configuration_Guide-Chapter12-The_CMP_Engine.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:36:01 2007
From: jira-events at lists.jboss.org (Shelly McGowan (JIRA))
Date: Fri, 26 Oct 2007 10:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4844) TECH REVIEW: Server
 Configuration Guide - AppendixA - Book Example Installation
In-Reply-To: <3244437.1192170303634.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16644743.1193409361582.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4844?page=all ]

Shelly McGowan resolved JBAS-4844.
----------------------------------

    Resolution: Done

no changes

> TECH REVIEW: Server Configuration Guide - AppendixA - Book Example Installation
> -------------------------------------------------------------------------------
>
>                 Key: JBAS-4844
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4844
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Shelly McGowan
>         Attachments: JBAS-422-Server_Configuration_Guide - AppendixA - Book_Example_Installation.odt, JBAS-422-Server_Configuration_Guide-AppendixA-Book_Example_Installation.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 10:59:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 10:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-85) Release Security
	V2.0.1.GA
In-Reply-To: <25608054.1192819263974.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5418268.1193410741800.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-85?page=all ]

Anil Saldhana updated SECURITY-85:
----------------------------------

    Summary: Release Security V2.0.1.GA  (was: Release Security V2.0.1-GA)

> Release Security V2.0.1.GA
> --------------------------
>
>                 Key: SECURITY-85
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-85
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:01:01 2007
From: jira-events at lists.jboss.org (Prakash Chellappa (JIRA))
Date: Fri, 26 Oct 2007 11:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1302) Drools
	ConsequenceException
Message-ID: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>

Drools ConsequenceException
---------------------------

                 Key: JBRULES-1302
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: drools-brms
    Affects Versions: 4.0.1
         Environment: Unix 
            Reporter: Prakash Chellappa
             Fix For: 4.0.1


Hi 

We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.

org.drools.spi.ConsequenceException: java.lang.NullPointerException
    at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
    at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
    at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
    at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
    at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
    at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
    at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
    at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
    at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
    at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
    at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
    at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
    at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
    at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
    at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
    at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
    at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
    at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
    at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
    at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
    at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
    at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
    at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
    at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
    at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
    at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
    at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
    at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
    at org.drools.reteoo.Rete.retractObject(Rete.java:214)
    at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
    at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
    at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
    at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
    at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
    at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
    at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)

We get the error message when we retract the object.The piece of code is given below

                if( c instanceof TransactionBulkBean ) {
                        retract(c);
                        }

                if( t instanceof TransactionBulkBean )  {
                        retract(t);
                        }


                // Retract Old Events
                for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
                         ev.setMessage(null) ; retract (ev);
                }

We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.

We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.

Thanks
Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:19:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 11:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-85) Release Security
	V2.0.1.GA
In-Reply-To: <25608054.1192819263974.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25683851.1193411941665.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-85?page=all ]

Anil Saldhana closed SECURITY-85.
---------------------------------

    Resolution: Done

Tagged and released. The docs trunk needs to be tagged and released by SECURITY-84

> Release Security V2.0.1.GA
> --------------------------
>
>                 Key: SECURITY-85
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-85
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX, Security SPI
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:41:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Fri, 26 Oct 2007 11:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17704985.1193413261504.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4913?page=comments#action_12384595 ] 
            
Thomas Diesler commented on JBAS-4913:
--------------------------------------

Its actually JBossServiceReferenceMetaData, because <wsdl-override> is a proprietary extension to the <service-ref> element in jboss-client.xml, jboss.xml, jboss-web.xml

Please see the service-ref dtd include in the respective jboss dtds

> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 11:58:06 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 11:58:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-84) Update
 documentation for 2.0.1.GA Release
In-Reply-To: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <224507.1193414286666.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-84?page=all ]

Anil Saldhana updated SECURITY-84:
----------------------------------

    Summary: Update documentation for 2.0.1.GA Release  (was: Update documentation for 2.0.1-GA Release)

> Update documentation for 2.0.1.GA Release
> -----------------------------------------
>
>                 Key: SECURITY-84
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>
> Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 12:00:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Fri, 26 Oct 2007 12:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4829) TECH REVIEW: Getting
 Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15606117.1193414403294.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Stelios Koussouris updated JBAS-4829:
-------------------------------------

    Attachment: JBASS-422-Getting_Started_Guide-Chapter-5.odt

changes so far

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 12:00:03 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Fri, 26 Oct 2007 12:00:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4829) TECH REVIEW:
 Getting Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13860687.1193414403576.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4829?page=comments#action_12384605 ] 
            
Stelios Koussouris commented on JBAS-4829:
------------------------------------------

Almost complete. Problem in deploying SEAM example. Investigating

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 13:51:01 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Fri, 26 Oct 2007 13:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
Message-ID: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
---------------------------------------------------------------------------------------

                 Key: EJBTHREE-1081
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
             Project: EJB 3.0
          Issue Type: Feature Request
         Environment: JBoss 4.2.2.GA
            Reporter: Michael McKibben
            Priority: Minor


I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:09:01 2007
From: jira-events at lists.jboss.org (Emmanuel Bernard (JIRA))
Date: Fri, 26 Oct 2007 14:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
In-Reply-To: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17071543.1193422141729.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1081?page=comments#action_12384635 ] 
            
Emmanuel Bernard commented on EJBTHREE-1081:
--------------------------------------------

I'm not user it's a good idea. The annotation processor can look at the super class without having to use @Inherited. Plus @Inherited does not propagates to interfaces.

> Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1081
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
>             Project: EJB 3.0
>          Issue Type: Feature Request
>         Environment: JBoss 4.2.2.GA
>            Reporter: Michael McKibben
>            Priority: Minor
>
> I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:09:02 2007
From: jira-events at lists.jboss.org (Emmanuel Bernard (JIRA))
Date: Fri, 26 Oct 2007 14:09:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
In-Reply-To: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3473221.1193422142066.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1081?page=comments#action_12384636 ] 
            
Emmanuel Bernard commented on EJBTHREE-1081:
--------------------------------------------

user => sure

> Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1081
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
>             Project: EJB 3.0
>          Issue Type: Feature Request
>         Environment: JBoss 4.2.2.GA
>            Reporter: Michael McKibben
>            Priority: Minor
>
> I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:19:01 2007
From: jira-events at lists.jboss.org (vivek v (JIRA))
Date: Fri, 26 Oct 2007 14:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26975466.1193422741433.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12384639 ] 
            
vivek v commented on JGRP-610:
------------------------------

Could this be related to - JGRP-590?

We have also seen this problem on our system, when a large return value (when using RpcDispatcher) never gets to the caller and the caller always times out (with TimeoutException).  (http://sourceforge.net/mailarchive/message.php?msg_id=a206fb7e0710042312g71c60d7ar4ef5b43ec8b48db5%40mail.gmail.com)

We use Gossip Router with UDP. 

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:32:28 2007
From: jira-events at lists.jboss.org (Michael McKibben (JIRA))
Date: Fri, 26 Oct 2007 14:32:28 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1081) Add @Inherited
 meta
 annotation to org.jboss.annotation.ejb.* annotations where possible
In-Reply-To: <12277906.1193421061701.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26546516.1193423548085.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1081?page=comments#action_12384643 ] 
            
Michael McKibben commented on EJBTHREE-1081:
--------------------------------------------

hmm, perhaps this is a bug with the annotation processor then, because I can only get JBoss to recognize my @AspectDomain and @RemoteBindings annotation if I have them on the actual ejb type, and not on a base type.

> Add @Inherited meta annotation to org.jboss.annotation.ejb.* annotations where possible
> ---------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1081
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1081
>             Project: EJB 3.0
>          Issue Type: Feature Request
>         Environment: JBoss 4.2.2.GA
>            Reporter: Michael McKibben
>            Priority: Minor
>
> I am using @AspectDomain and @RemoteBindings in some of my ejbs to inject my own aspects, and it would be very convenient not having to specify these annotations on each ejb that inherit from the same base class. I'm sure there are other jboss ejb3 annotations besides the @AspectDomain and @RemoteBindings that could also use the @Inherited annotation as well.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 14:44:11 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 14:44:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
Message-ID: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>

ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
----------------------------------------------------------------

                 Key: JBPM-1076
                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
             Project: JBoss jBPM
          Issue Type: Feature Request
    Affects Versions: jBPM jPDL 3.2.2
         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
            Reporter: Flavio Crispim
         Assigned To: Tom Baeyens


I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:37:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-86) Adapt Resource
 Interface for ACL
Message-ID: <877125.1193427421449.JavaMail.jira@cloud.prod.atl2.jboss.com>

Adapt Resource Interface for ACL
--------------------------------

                 Key: SECURITY-86
                 URL: http://jira.jboss.com/jira/browse/SECURITY-86
             Project: JBoss Security and Identity Management
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Security SPI
    Affects Versions: 2.0.1.GA
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.2-BETA


The Authorization framework interface "Resource" needs to be adapted for the ACL implementation.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:37:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-87)
 AuthorizationManager interface needs ACL semantics
Message-ID: <19665680.1193427421571.JavaMail.jira@cloud.prod.atl2.jboss.com>

AuthorizationManager interface needs ACL semantics
--------------------------------------------------

                 Key: SECURITY-87
                 URL: http://jira.jboss.com/jira/browse/SECURITY-87
             Project: JBoss Security and Identity Management
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Security SPI
    Affects Versions: 2.0.1.GA
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.2-BETA


The AuthorizationManager interface needs to be upgraded to handle the fast ACL implementation needs.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:39:16 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:39:16 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-88) Refactor
 JaasSecurityManager into JBossAuthenticationManager
Message-ID: <11984892.1193427556659.JavaMail.jira@cloud.prod.atl2.jboss.com>

Refactor JaasSecurityManager into JBossAuthenticationManager
------------------------------------------------------------

                 Key: SECURITY-88
                 URL: http://jira.jboss.com/jira/browse/SECURITY-88
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.1.GA
            Reporter: Anil Saldhana
         Assigned To: Anil Saldhana
             Fix For: 2.0.2.GA


The code that exists in JaasSecurityManager needs to be pulled into a generic delegate in JBossSX such that the JaasSecurityManager in the AS security integration as well as the default AuthenticationManager can reuse.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 15:50:17 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 15:50:17 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (SECURITY-89) Fast ACL
	Implementation
Message-ID: <18943842.1193428217352.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fast ACL Implementation
-----------------------

                 Key: SECURITY-89
                 URL: http://jira.jboss.com/jira/browse/SECURITY-89
             Project: JBoss Security and Identity Management
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: ACL
            Reporter: Anil Saldhana
         Assigned To: Stefan Guilhen
             Fix For: 2.0.2.GA


We need to implement a FAST ACL implementation to be used by the non JBAS projects such as JBoss Rules, Portal etc.

The key here is performance.

We basically have a tuple (key, CRUD) where key is an object instance.  We need to devise some mechanism by which the projects can plug in their key (similar to hibernate primary key mapping).

The ACL implementation should not assume any strategies, which need to be pluggable. The strategies can be Hibernate, Cache or ldap depending on user needs.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 16:09:04 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 16:09:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (SECURITY-74) Policy Management
 Console using JBoss SEAM
In-Reply-To: <14814510.1186178449283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8422719.1193429344076.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-74?page=all ]

Anil Saldhana reassigned SECURITY-74:
-------------------------------------

    Assignee: Marcus Moyses  (was: Anil Saldhana)

Marcus has shown a lot of initiative in learning more on the JBoss Admin Console.  He is driving the Policy Plugin.

> Policy Management Console using JBoss SEAM
> ------------------------------------------
>
>                 Key: SECURITY-74
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-74
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossXACML-Console
>            Reporter: Anil Saldhana
>         Assigned To: Marcus Moyses
>             Fix For: NO_VERSION
>
>
> Need for a progressive Policy Management console using JBoss SEAM.  The JAXB2 object model provided with JBoss XACML can be used to construct the policies.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 16:27:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 16:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (SECURITY-74) Policy Management
 Console using JBoss Admin Console/JBoss SEAM
In-Reply-To: <14814510.1186178449283.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24243632.1193430421618.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-74?page=all ]

Anil Saldhana updated SECURITY-74:
----------------------------------

    Summary: Policy Management Console using JBoss Admin Console/JBoss SEAM  (was: Policy Management Console using JBoss SEAM)

> Policy Management Console using JBoss Admin Console/JBoss SEAM
> --------------------------------------------------------------
>
>                 Key: SECURITY-74
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-74
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossXACML-Console
>            Reporter: Anil Saldhana
>         Assigned To: Marcus Moyses
>             Fix For: NO_VERSION
>
>
> Need for a progressive Policy Management console using JBoss SEAM.  The JAXB2 object model provided with JBoss XACML can be used to construct the policies.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 16:33:02 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 16:33:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1300) BRMS -
 misspelling in label in "create new category" dialog
In-Reply-To: <7924962.1193352971576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31591863.1193430782012.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1300?page=all ]

Fernando Meyer reassigned JBRULES-1300:
---------------------------------------

    Assignee: Fernando Meyer

> BRMS - misspelling in label in "create new category" dialog
> -----------------------------------------------------------
>
>                 Key: JBRULES-1300
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1300
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>            Priority: Trivial
>
> In BRMS, go to Admin > Manage Categories > Create new category. The dialog box has a misspelling in the first label "Cateogory name" should say "Category name"

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:18:15 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 17:18:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10854987.1193433495637.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

Brian Stansberry updated JBAS-4836:
-----------------------------------

    Attachment: updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section1+-+Clustered-JNDI-Services.odt

My edits to the HA-JNDI section are attached.

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section1+-+Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:20:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 17:20:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4836) TECH REVIEW:
 Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
In-Reply-To: <5125488.1192167303802.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16266506.1193433602137.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4836?page=all ]

Brian Stansberry reassigned JBAS-4836:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

Note that there are a couple places where I added things along the lines of 'see the "XYZ" section..' where hyperlinks should be added.

> TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4836
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4836
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section1 - Clustered-JNDI-Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section1+-+Clustered-JNDI-Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:51:14 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 17:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
In-Reply-To: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25454885.1193435474513.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1297?page=all ]

Fernando Meyer reassigned JBRULES-1297:
---------------------------------------

    Assignee: Fernando Meyer

> DroolsCompilerAntTask.java should reset threadContextLoader to original value
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-1297
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Bali
>         Assigned To: Fernando Meyer
>         Attachments: droolsAntClasspathFixPatch.txt
>
>
> DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:53:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 17:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1297)
 DroolsCompilerAntTask.java
 should reset threadContextLoader to original value
In-Reply-To: <530035.1193255893218.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30951061.1193435581489.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1297?page=all ]

Fernando Meyer closed JBRULES-1297.
-----------------------------------

    Fix Version/s: 4.1.0
       Resolution: Done

patch applied Thanks

> DroolsCompilerAntTask.java should reset threadContextLoader to original value
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-1297
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1297
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michal Bali
>         Assigned To: Fernando Meyer
>             Fix For: 4.1.0
>
>         Attachments: droolsAntClasspathFixPatch.txt
>
>
> DroolsCompilerAntTask.java sets the thread context class loader but it is never sets  it back to its original state. This causes problems in subsequent ant task running in the same thread.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 17:58:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 17:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8212368.1193435881739.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=all ]

Fernando Meyer reassigned JBRULES-1302:
---------------------------------------

    Assignee: Mark Proctor

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Mark Proctor
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:00:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 18:00:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29174468.1193436001642.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=all ]

Fernando Meyer reassigned JBRULES-1302:
---------------------------------------

    Assignee: Fernando Meyer  (was: Mark Proctor)

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:07:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25149924.1193436421563.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12384674 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

It's important to note that jbossweb.jar is built with jdk 1.5, so the http transport can work with jbossweb only if Remoting is also built with jdk 1.5.  

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:09:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 18:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (SECURITY-84) Update
 documentation for 2.0.1.GA Release
In-Reply-To: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15583802.1193436541434.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/SECURITY-84?page=all ]

Anil Saldhana closed SECURITY-84.
---------------------------------

    Resolution: Done

> Update documentation for 2.0.1.GA Release
> -----------------------------------------
>
>                 Key: SECURITY-84
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>
> Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:11:05 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 18:11:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1300) BRMS -
 misspelling in label in "create new category" dialog
In-Reply-To: <7924962.1193352971576.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25415289.1193436665580.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1300?page=all ]

Fernando Meyer resolved JBRULES-1300.
-------------------------------------

    Fix Version/s: 4.1.0
       Resolution: Done

> BRMS - misspelling in label in "create new category" dialog
> -----------------------------------------------------------
>
>                 Key: JBRULES-1300
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1300
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.2
>            Reporter: Phil Verghese
>         Assigned To: Fernando Meyer
>            Priority: Trivial
>             Fix For: 4.1.0
>
>
> In BRMS, go to Admin > Manage Categories > Create new category. The dialog box has a misspelling in the first label "Cateogory name" should say "Category name"

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:15:01 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Fri, 26 Oct 2007 18:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (SECURITY-84) Update
 documentation for 2.0.1.GA Release
In-Reply-To: <26189116.1192819143240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28507239.1193436901438.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/SECURITY-84?page=comments#action_12384675 ] 
            
Anil Saldhana commented on SECURITY-84:
---------------------------------------

http://labs.jboss.com/file-access/default/members/jbosssecurity/freezone/releases/guide/2.0.1.GA/jbosssecurity.html

> Update documentation for 2.0.1.GA Release
> -----------------------------------------
>
>                 Key: SECURITY-84
>                 URL: http://jira.jboss.com/jira/browse/SECURITY-84
>             Project: JBoss Security and Identity Management
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Anil Saldhana
>         Assigned To: Anil Saldhana
>             Fix For: 2.0.1.GA
>
>
> Update the security docbook project for documentation towards 2.0.1-GA release.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:26:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-825) Verify that
 CoyoteInvoker works with Apache Portable Runtime
In-Reply-To: <16554394.1193188321512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26360995.1193437561536.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-825?page=all ]

Ron Sigal updated JBREM-825:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)

> Verify that CoyoteInvoker works with Apache Portable Runtime
> ------------------------------------------------------------
>
>                 Key: JBREM-825
>                 URL: http://jira.jboss.com/jira/browse/JBREM-825
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> The http transport - org.jboss.remoting.transport.coyote.CoyoteInvoker, in particular - now works with either jbossweb.jar or the tomcat jars.  When the APR native libraries are deposited in a directory on the system path on a Windows machine, the http transport tests run successfully, but the https tests fail:
> 21:10:14,906 DEBUG [main] [HTTPClientInvoker] Error invoking http client invoker.
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
> 	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
> 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
> 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:276)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:123)
> 	at org.jboss.remoting.Client.invoke(Client.java:1632)
> 	at org.jboss.remoting.Client.invoke(Client.java:548)
> 	at org.jboss.test.remoting.transport.http.ssl.basic.HTTPSInvokerTestClient.testInvocationWithHeaders(HTTPSInvokerTestClient.java:77)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at junit.framework.TestCase.runTest(TestCase.java:154)
> 	at junit.framework.TestCase.runBare(TestCase.java:127)
> 	at junit.framework.TestResult$1.protect(TestResult.java:106)
> 	at junit.framework.TestResult.runProtected(TestResult.java:124)
> 	at junit.framework.TestResult.run(TestResult.java:109)
> 	at junit.framework.TestCase.run(TestCase.java:118)
> 	at junit.framework.TestSuite.runTest(TestSuite.java:208)
> 	at junit.framework.TestSuite.run(TestSuite.java:203)
> 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> 	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
> 	... 31 more

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:26:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-823)
 ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value
 is IPv6
In-Reply-To: <9184117.1192689903468.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31501383.1193437561804.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-823?page=all ]

Ron Sigal updated JBREM-823:
----------------------------

        Fix Version/s: 2.4.0.Beta1 (Pinto)
    Affects Version/s: 2.2.2.SP2
                       2.2.2.GA_CP01
                       2.4.0.Beta1 (Pinto)
                           (was: 3.0.0.Alpha1 (Otter))

> ServerInvoker#getMBeanObjectName() returns invalid ObjectName if host value is IPv6
> -----------------------------------------------------------------------------------
>
>                 Key: JBREM-823
>                 URL: http://jira.jboss.com/jira/browse/JBREM-823
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01, 2.2.2.SP2
>            Reporter: Takayoshi Kimura
>         Assigned To: Trustin Lee
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: JBREM-823.patch
>
>
> IPv6 address contains ":" character, so it cannot be used in ObjectName.
> 2007-10-18 15:37:40,476 WARN  [org.jboss.remoting.transport.Connector] Error registering invoker SocketServerInvoker[UNINITIALIZED] with MBeanServer.
> javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
> 	at javax.management.ObjectName.construct(ObjectName.java:529)
> 	at javax.management.ObjectName.<init>(ObjectName.java:1304)
> 	at org.jboss.remoting.transport.Connector.init(Connector.java:402)
> 	at org.jboss.remoting.transport.Connector.create(Connector.java:760)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
> 	at $Proxy0.create(Unknown Source)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:330)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:349)
> 	at org.jboss.system.ServiceController.create(ServiceController.java:273)
> 	at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy4.create(Unknown Source)
> 	at org.jboss.deployment.SARDeployer.create(SARDeployer.java:258)
> 	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
> 	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy5.deploy(Unknown Source)
> 	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
> 	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
> 	at org.jboss.Main.boot(Main.java:200)
> 	at org.jboss.Main$1.run(Main.java:508)
> 	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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:30:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:30:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the
 legacy configuration that embeds xml parsing
Message-ID: <9204450.1193437801785.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12384677 ] 
            
Ron Sigal commented on JBREM-63:
--------------------------------

Need to update Remoting Guide.

> Get rid of the legacy configuration that embeds xml parsing
> -----------------------------------------------------------
>
>                 Key: JBREM-63
>                 URL: http://jira.jboss.com/jira/browse/JBREM-63
>             Project: JBoss Remoting
>          Issue Type: Task
>    Affects Versions: 1.0.1 beta
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:30:02 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:30:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the
 legacy configuration that embeds xml parsing
Message-ID: <31706621.1193437802119.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12384678 ] 
            
Ron Sigal commented on JBREM-63:
--------------------------------

Unit test passed on cruisecontrol.

> Get rid of the legacy configuration that embeds xml parsing
> -----------------------------------------------------------
>
>                 Key: JBREM-63
>                 URL: http://jira.jboss.com/jira/browse/JBREM-63
>             Project: JBoss Remoting
>          Issue Type: Task
>    Affects Versions: 1.0.1 beta
>            Reporter: Scott M Stark
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. 

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:30:02 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 26 Oct 2007 18:30:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15551455.1193437802447.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=comments#action_12384679 ] 
            
Edson Tirelli commented on JBRULES-1302:
----------------------------------------

Prakash,

Please, can you update to the 4.0.3 version of drools, since we fixed a number of bugs. If the problem still persists, we will need a self contained test case from you showing the problem, so that we can fix it.

Thanks,
Edson

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Fernando Meyer
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:37:01 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Fri, 26 Oct 2007 18:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1302) Drools
	ConsequenceException
In-Reply-To: <23070676.1193410861703.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9033746.1193438221742.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1302?page=all ]

Edson Tirelli reassigned JBRULES-1302:
--------------------------------------

    Assignee: Edson Tirelli  (was: Fernando Meyer)

> Drools ConsequenceException
> ---------------------------
>
>                 Key: JBRULES-1302
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1302
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>    Affects Versions: 4.0.1
>         Environment: Unix 
>            Reporter: Prakash Chellappa
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.1
>
>
> Hi 
> We are from UBS Investment Bank and are facing a critical problem in one of production System currently using Drools.We require your urgent assistance to get this resolved asap.Below is the details of the error message we are getting.
> org.drools.spi.ConsequenceException: java.lang.NullPointerException
>     at org.drools.base.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:14)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:553)
>     at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:462)
>     at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:424)
>     at com.ubs.tsna.rhino.matcher2.pb.engine.PBMatchingEngine.doMatching(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.engine.MatchingEngine.match(Unknown Source)
>     at com.ubs.tsna.rhino.matcher2.action.MatchingAction.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeSingleAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.executeAction(Unknown Source)
>     at com.ubs.tsna.workflow.process.ProcessFlow.execute(Unknown Source)
>     at com.ubs.tsna.workflow.process.BaseProcess.processMessage(Unknown Source)
>     at com.ubs.tsna.workflow.process.Process.run(Unknown Source)
>     at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.NullPointerException
>     at org.drools.base.com.ubs.tsna.rhino.matcher2.pb.model.TransactionEvent11782857$getMessage.getValue(Unknown Source)
>     at org.drools.base.extractors.BaseObjectClassFieldExtractor.getHashCode(BaseObjectClassFieldExtractor.java:139)
>     at org.drools.base.ClassFieldExtractor.getHashCode(ClassFieldExtractor.java:225)
>     at org.drools.rule.Declaration.getHashCode(Declaration.java:272)
>     at org.drools.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:489)
>     at org.drools.util.TupleIndexHashTable.remove(TupleIndexHashTable.java:203)
>     at org.drools.reteoo.NotNode.retractTuple(NotNode.java:208)
>     at org.drools.reteoo.SingleTupleSinkAdapter.propagateRetractTuple(SingleTupleSinkAdapter.java:38)
>     at org.drools.reteoo.JoinNode.retractObject(JoinNode.java:181)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:375)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.SingleObjectSinkAdapter.propagateRetractObject(SingleObjectSinkAdapter.java:32)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.AlphaNode.retractObject(AlphaNode.java:158)
>     at org.drools.reteoo.CompositeObjectSinkAdapter.propagateRetractObject(CompositeObjectSinkAdapter.java:366)
>     at org.drools.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:180)
>     at org.drools.reteoo.Rete.retractObject(Rete.java:214)
>     at org.drools.reteoo.ReteooRuleBase.retractObject(ReteooRuleBase.java:220)
>     at org.drools.reteoo.ReteooWorkingMemory.doRetract(ReteooWorkingMemory.java:79)
>     at org.drools.common.AbstractWorkingMemory.retract(AbstractWorkingMemory.java:999)
>     at org.drools.base.DefaultKnowledgeHelper.retract(DefaultKnowledgeHelper.java:115)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0.consequence(Rule_Match_0.java:55)
>     at com.ubs.tsna.rhino.matcher.rules.Rule_Match_0ConsequenceInvoker.evaluate(Rule_Match_0ConsequenceInvoker.java:26)
>     at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)
> We get the error message when we retract the object.The piece of code is given below
>                 if( c instanceof TransactionBulkBean ) {
>                         retract(c);
>                         }
>                 if( t instanceof TransactionBulkBean )  {
>                         retract(t);
>                         }
>                 // Retract Old Events
>                 for( TransactionEvent ev : MATCHER.retractUnMatchedEvents(c, t) ) {
>                          ev.setMessage(null) ; retract (ev);
>                 }
> We dont have support contract at this point of time,But we dont mind going in one by future.We would like to get your help to get this issue addressed ASAP.
> We would like to call and speak to you on urgent basis.Give us a call on 203 719 4625 or give us the no we can reach you at.
> Thanks
> Prakash

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 18:54:01 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Fri, 26 Oct 2007 18:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17327326.1193439241744.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-675?page=all ]

Ron Sigal reassigned JBREM-675:
-------------------------------

    Assignee: Ron Sigal  (was: Tom  Elrod)

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.0.0.GA (Boon), 1.4.6.GA
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:04:01 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11972326.1193439841593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Flavio Crispim updated JBPM-1076:
---------------------------------

    Attachment: hibernate.queries.hbm.xml.patch

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:04:01 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33115959.1193439841775.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Flavio Crispim updated JBPM-1076:
---------------------------------

    Attachment: JbpmContext.java.patch

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:04:01 2007
From: jira-events at lists.jboss.org (Flavio Crispim (JIRA))
Date: Fri, 26 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24367979.1193439841943.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Flavio Crispim updated JBPM-1076:
---------------------------------

    Attachment: TaskMgmtSession.java.patch

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 19:23:01 2007
From: jira-events at lists.jboss.org (Ovidiu Feodorov (JIRA))
Date: Fri, 26 Oct 2007 19:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6669554.1193440981503.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=comments#action_12384684 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-1115:
----------------------------------------------

Happened again with r3237. I am analyzing the log, I will follow up with more details.

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 22:51:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 22:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1293) Backport for
	Eclipse 3.3
In-Reply-To: <12660311.1193073123217.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21330690.1193453461960.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1293?page=all ]

Fernando Meyer closed JBRULES-1293.
-----------------------------------

    Resolution: Done

> Backport for Eclipse 3.3
> ------------------------
>
>                 Key: JBRULES-1293
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1293
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Eclipse IDE
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>
> We now how two parallel eclipse projects for 4.0.x.

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 22:51:02 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Fri, 26 Oct 2007 22:51:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1294) Upgrade to MVEL
	1.2.10
In-Reply-To: <16163147.1193073243211.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22297299.1193453462890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1294?page=all ]

Fernando Meyer closed JBRULES-1294.
-----------------------------------

    Resolution: Done

> Upgrade to MVEL 1.2.10
> ----------------------
>
>                 Key: JBRULES-1294
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1294
>             Project: JBoss Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: All
>            Reporter: Mark Proctor
>         Assigned To: Mark Proctor
>             Fix For: 4.0.3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 23:27:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 23:27:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15484039.1193455622394.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Brian Stansberry updated JBAS-4840:
-----------------------------------

    Attachment: updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section5+-+Clustered_JMS_Services.odt

My edits attached.

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section5+-+Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 23:27:03 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Fri, 26 Oct 2007 23:27:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4840) TECH REVIEW:
 Chapter1 - Section5 - Clustered JMS Services
In-Reply-To: <886505.1192167304600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8725513.1193455623069.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4840?page=all ]

Brian Stansberry reassigned JBAS-4840:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson

> TECH REVIEW:  Chapter1 - Section5 - Clustered JMS Services
> ----------------------------------------------------------
>
>                 Key: JBAS-4840
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4840
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section5 - Clustered_JMS_Services.odt, updated-26-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section5+-+Clustered_JMS_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Fri Oct 26 23:52:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Fri, 26 Oct 2007 23:52:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-114) Reusing a model group
Message-ID: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>

Reusing a model group
---------------------

                 Key: JBXB-114
                 URL: http://jira.jboss.com/jira/browse/JBXB-114
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Feature Request
            Reporter: Scott M Stark
             Fix For: JBossXB-2.0.0.CR5


We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:

<!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
 exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
 security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
 resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
 cluster-config?, method-attributes?, depends*,
 ior-security-config?, port-component*,  ejb-timeout-identity?)>

See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:

org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
...
Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
	... 41 more


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 00:27:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Sat, 27 Oct 2007 00:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBXB-114) Reusing a model group
In-Reply-To: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21015085.1193459221432.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-114?page=all ]

Scott M Stark updated JBXB-114:
-------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099525

> Reusing a model group
> ---------------------
>
>                 Key: JBXB-114
>                 URL: http://jira.jboss.com/jira/browse/JBXB-114
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>            Reporter: Scott M Stark
>             Fix For: JBossXB-2.0.0.CR5
>
>
> We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:
> <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
>  exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
>  security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
>  resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
>  cluster-config?, method-attributes?, depends*,
>  ior-security-config?, port-component*,  ejb-timeout-identity?)>
> See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:
> org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
> 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
> ...
> Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
> 	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
> 	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
> 	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
> 	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
> 	... 41 more

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 02:55:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Sat, 27 Oct 2007 02:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27667189.1193468101518.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

Brian Stansberry updated JBAS-4837:
-----------------------------------

    Attachment: updated-27-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section2+-+Clustered_Session_EJBs.odt

My edits attached.

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt, updated-27-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section2+-+Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 02:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Sat, 27 Oct 2007 02:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4837) TECH REVIEW:
 Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
In-Reply-To: <282018.1192167304036.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27306519.1193468221659.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4837?page=all ]

Brian Stansberry reassigned JBAS-4837:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson

> TECH REVIEW:  Clustering - Chapter1 - Section2 - Clustered_Session_EJBs
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4837
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4837
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section2 - Clustered_Session_EJBs.odt, updated-27-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section2+-+Clustered_Session_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 04:46:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 04:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5681558.1193474761717.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=comments#action_12384702 ] 
            
Tim Fox commented on JBMESSAGING-1115:
--------------------------------------

Can you explain what you were doing when you saw this, then I can replicate?

> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 04:56:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Sat, 27 Oct 2007 04:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4913) wsdl-override not
 found as a child of service-ref
In-Reply-To: <1084100.1193398681458.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18932921.1193475361488.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4913?page=all ]

Scott M Stark resolved JBAS-4913.
---------------------------------

    Resolution: Done

The jboss extensions are resolved with metadata snapshot update rev 1693.


> wsdl-override not found as a child of service-ref
> -------------------------------------------------
>
>                 Key: JBAS-4913
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4913
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.benchmark.jaxrpc.BenchmarkDocEJBTestCase one-test
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: wsdl-override not found as a child of service-ref
>         at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:412)
>         at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 06:59:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 06:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1125) Allow
 replication to be turned off for transacted sessions
Message-ID: <32410117.1193482741436.JavaMail.jira@cloud.prod.atl2.jboss.com>

Allow replication to be turned off for transacted sessions
----------------------------------------------------------

                 Key: JBMESSAGING-1125
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1125
             Project: JBoss Messaging
          Issue Type: Feature Request
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 2.0.0 Beta


We should allow the ability to turn off session replication for transacted sessions.

Replicating transacted sessions is only needed to cope with the possibility that another session grabs unacked messages from the queue before the original session.

If the user never has more than one session on the queue at any one time this becomes unnecessary.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:12:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8889768.1193483521666.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384711 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

ClusteredClientCrashTest also fails because of this

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:12:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:12:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22141827.1193483521893.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Fix Version/s: 1.4.0.SP1
                       (was: AS 5.0 Integration)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:49:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19145867.1193485741832.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox reopened JBMESSAGING-1119:
----------------------------------

             

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:49:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21725489.1193485742173.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox updated JBMESSAGING-1119:
---------------------------------

    Priority: Minor  (was: Major)

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:49:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1119) We should
 ignore nonPersistentMessages on failover
In-Reply-To: <31178723.1193078883520.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23832701.1193485742408.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1119?page=all ]

Tim Fox closed JBMESSAGING-1119.
--------------------------------

    Resolution: Done

> We should ignore nonPersistentMessages on failover
> --------------------------------------------------
>
>                 Key: JBMESSAGING-1119
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1119
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> There is no guarantee over nonPersistentMessages anyway.. .we should just ignore them avoiding problems with paging & persistence

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:51:19 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:51:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19497536.1193485879967.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox reopened JBMESSAGING-1096:
----------------------------------

             

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:51:20 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:51:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32474023.1193485880108.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox updated JBMESSAGING-1096:
---------------------------------

    Priority: Minor  (was: Major)

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 07:51:20 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 07:51:20 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1096) Remove
 references from the old Callback Manager on the documentation
In-Reply-To: <16840792.1191448503312.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19034578.1193485880297.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1096?page=all ]

Tim Fox closed JBMESSAGING-1096.
--------------------------------

    Resolution: Done

> Remove references from the old Callback Manager on the documentation
> --------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1096
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1096
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Documentation and Training
>    Affects Versions: 1.4.0.GA
>            Reporter: Clebert Suconic
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: 1.4.0.SP1
>
>
> Documentation still refer the old callback mechanism:
> http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.GA/html/configuration.html#conf.callback
> We only support Bisocket now!

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 08:07:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 08:07:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1122)
 *MessageCountersAsHTML LastAdd uses wrong value
In-Reply-To: <15674199.1193325306988.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2109328.1193486821683.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1122?page=all ]

Tim Fox updated JBMESSAGING-1122:
---------------------------------

    Fix Version/s: Unscheduled
         Priority: Minor  (was: Major)

> *MessageCountersAsHTML LastAdd uses wrong value
> -----------------------------------------------
>
>                 Key: JBMESSAGING-1122
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>            Reporter: Aslak
>         Assigned To: Tim Fox
>            Priority: Minor
>             Fix For: Unscheduled
>
>         Attachments: JBMESSAGING-1122.patch
>
>
> ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:09:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5248440.1193490541707.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Fix Version/s: AS 5.0 Integration
                   EAP 4.3 Integration

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:09:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20864318.1193490541970.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384712 ] 
            
Tim Fox commented on JBMESSAGING-1099:
--------------------------------------

I have commented out ClusteredClientCrashTest until this task is fixed

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Critical
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:09:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:09:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15332602.1193490542228.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Tim Fox updated JBMESSAGING-1099:
---------------------------------

    Priority: Blocker  (was: Critical)

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> Need to investigate

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 09:11:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Sat, 27 Oct 2007 09:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1126)
 ClusterViewUpdateTest::testGarbageCollectionOnClusteredCF fails on Hudson
Message-ID: <7233444.1193490661446.JavaMail.jira@cloud.prod.atl2.jboss.com>

ClusterViewUpdateTest::testGarbageCollectionOnClusteredCF fails on Hudson
-------------------------------------------------------------------------

                 Key: JBMESSAGING-1126
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1126
             Project: JBoss Messaging
          Issue Type: Bug
            Reporter: Tim Fox
         Assigned To: Clebert Suconic
             Fix For: AS 5.0 Integration, EAP 4.3 Integration


This test fails on Hudson.

The test makes assumptions about when Garbage collection is going to occur so IMHO is not a valid test.

We cannot ever be sure GC is going to occur - this is up the JVM implementation to decide.

The test has been commented out until this is resolved.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 10:21:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Sat, 27 Oct 2007 10:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPM-1076) ie.
 JbpmContext.getGroupTaskList(List actorIds, String taskName)
In-Reply-To: <21931004.1193424251697.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11250703.1193494861502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ]

Ronald van Kuijk updated JBPM-1076:
-----------------------------------


workaround exists: apply the patches attached to to this issue

> ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)
> ----------------------------------------------------------------
>
>                 Key: JBPM-1076
>                 URL: http://jira.jboss.com/jira/browse/JBPM-1076
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>    Affects Versions: jBPM jPDL 3.2.2
>         Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3
>            Reporter: Flavio Crispim
>         Assigned To: Tom Baeyens
>         Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch
>
>
> I need to use the tasks pool, but they should be a pool per task.

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 12:46:01 2007
From: jira-events at lists.jboss.org (Wesley Hales (JIRA))
Date: Sat, 27 Oct 2007 12:46:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1765) Adapt the admin
 portlet to let the user set a default window state
In-Reply-To: <32743739.1192742134373.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8263031.1193503561799.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1765?page=all ]

Wesley Hales resolved JBPORTAL-1765.
------------------------------------

    Resolution: Done

> Adapt the admin portlet to let the user set a default window state
> ------------------------------------------------------------------
>
>                 Key: JBPORTAL-1765
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1765
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core Admin
>            Reporter: Thomas Heute
>         Assigned To: Wesley Hales
>             Fix For: 2.6.3 Final
>
>
> We'll need to be able to define which window (if any) of a page should be maximized when a window opens, we'll also need to define if a window must first be displayed as minimized.
> The back end is not done 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

        


From jira-events at lists.jboss.org  Sat Oct 27 14:55:02 2007
From: jira-events at lists.jboss.org (Fang Tianying (JIRA))
Date: Sat, 27 Oct 2007 14:55:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1082) Exception
 wrapping and delivering
Message-ID: <8075056.1193511302237.JavaMail.jira@cloud.prod.atl2.jboss.com>

Exception wrapping and delivering
---------------------------------

                 Key: EJBTHREE-1082
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1082
             Project: EJB 3.0
          Issue Type: Bug
          Components: EJB3 Extensions
    Affects Versions: AS 4.2.1.GA
         Environment: SUN jdk1.5  ,  windows XP ,  JBoss4.2.1GA
            Reporter: Fang Tianying


hi, 

This problem is easy to recur.
When SLSB A(transaction att:requried) calls SLSB B(transaction att: not supported ) though B's local interface, and B throws a RuntimeException, then A will recieve just this very RuntimeException rather than an EJBException. 
I mean the EJB Container should wrap the rt. ex thrown by SLSB B to an EJBException, and then deliver the EJBException to it's caller - SLSB A. 

If it is a bug, I'm appriciated to any responses.  fangtianying at yahoo.cn

best regards,
FangTianying

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:30:15 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:30:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
Message-ID: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve testsuite issues introduced by metadata refactoring
-----------------------------------------------------------

                 Key: EJBTHREE-1083
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:34:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:34:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1084) Resolve Failure:
 org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
Message-ID: <8059247.1193517241440.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
-------------------------------------------------------------------------------------

                 Key: EJBTHREE-1084
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1084
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase

JAR does not deploy due to error:

Caused by: org.xml.sax.SAXException: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

@IgnoreDependency is not used in this test, but is defined in jboss.xml

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:43:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1085) Resolve Failure:
Message-ID: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: 
-----------------

                 Key: EJBTHREE-1085
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger


Error on JAR deployment:


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:43:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1085) Resolve Failure:
 org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
In-Reply-To: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23492057.1193517781668.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1085?page=all ]

Andrew Rubinger updated EJBTHREE-1085:
--------------------------------------

          Summary: Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase  (was: Resolve Failure: )
    Fix Version/s: HEAD
      Description: 
Error on JAR deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

  was:
Error on JAR deployment:


         Assignee: Andrew Rubinger

> Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1085
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> Error on JAR deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:45:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1085) Resolve Failure:
 org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
In-Reply-To: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24231875.1193517901662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1085?page=all ]

Andrew Rubinger updated EJBTHREE-1085:
--------------------------------------

    Description: 
shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase

Error on JAR deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

  was:
Error on JAR deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[


> Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1085
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> Error on JAR deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:47:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1086) Resolve Failure:
 org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
Message-ID: <12693205.1193518021659.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
-----------------------------------------------------------------------

                 Key: EJBTHREE-1086
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1086
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase

Error on JAR Deployment:

Caused by: java.lang.RuntimeException: org.jboss.xb.binding.JBossXBException: Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]


-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:47:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32721822.1193518021817.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=all ]

Andrew Rubinger updated EJBTHREE-1083:
--------------------------------------

    Priority: Critical  (was: Major)

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:50:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1087) Resolve Failure:
 org.jboss.ejb3.test.container.unit.ContainerTestCase
Message-ID: <27563923.1193518201480.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.container.unit.ContainerTestCase
---------------------------------------------------------------------

                 Key: EJBTHREE-1087
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1087
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.container.unit.ContainerTestCase

Error on JAR Deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:52:21 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:52:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21281168.1193518341873.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=comments#action_12384728 ] 
            
Andrew Rubinger commented on EJBTHREE-1083:
-------------------------------------------

Many issues failing due to the same underlying error:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

This is discussed in the linked JBoss Forum Reference.

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:54:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13336615.1193518441956.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=all ]

Andrew Rubinger updated EJBTHREE-1083:
--------------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119764

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Rubinger
>         Assigned To: Andrew Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 16:56:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 16:56:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1088) Resolve Failure:
 org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
Message-ID: <27878026.1193518561424.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
----------------------------------------------------------------

                 Key: EJBTHREE-1088
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1088
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell>  ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase

Error on Deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Sat Oct 27 17:01:01 2007
From: jira-events at lists.jboss.org (Andrew Rubinger (JIRA))
Date: Sat, 27 Oct 2007 17:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1089) Resolve Failure:
 org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
Message-ID: <3816689.1193518861438.JavaMail.jira@cloud.prod.atl2.jboss.com>

Resolve Failure: org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
---------------------------------------------------------------------------

                 Key: EJBTHREE-1089
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1089
             Project: EJB 3.0
          Issue Type: Sub-task
            Reporter: Andrew Rubinger
         Assigned To: Andrew Rubinger
             Fix For: HEAD


shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase

Error on JAR Deployment:

Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:44:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1303) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <7852123.1193582641743.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1303
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1303
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
         Environment: MacBook running Leopard, Eclipse Europa, Java 1.5 (Mac OSX), Drools 4.0.3
            Reporter: John Dunning


The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:48:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1304) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <15904136.1193582881635.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1304
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1304
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: John Dunning




-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:54:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1305) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <13001809.1193583241581.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1305
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1305
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
            Reporter: John Dunning


The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 10:58:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 10:58:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
Message-ID: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>

Memory Leak when reusing cached RuleBase and retracting Facts
-------------------------------------------------------------

                 Key: JBRULES-1306
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
            Reporter: John Dunning


The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 11:03:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 11:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21084981.1193583781644.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1306?page=all ]

John Dunning updated JBRULES-1306:
----------------------------------

    Attachment: Archive.zip

3 Separate Eclipse Projects 

Lib - contains common library code
RuleRunner - invokes the drools engine
SpeedTest - how to invoke the tests and re-create the bug.

Run

et.tplusplus.test.drools.speedtest.SpeedTest1

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1306
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>         Attachments: Archive.zip
>
>
> The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.
> The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.
> The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).
> The rules are described below:
> package net.tplusplus.drools.speedtest.rules.test1;
> import net.tplusplus.drools.speedtest.facts.*;
> import net.tplusplus.drools.speedtest.bank.*;
> rule "Test 01 - Credit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Credit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Debit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Debit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Print Balance"
> 	salience 90
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		UpdatingAccount( $accountNo : accountNo, $account : account)
> 		not AccountingPeriod( start < $start)
> 	then
> 		//System.out.print("Period End: "+$end);
> 		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
> end
> rule "Test 01 - Retract Period"
> 	salience 80
> 	when
> 		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
> 		not AccountingPeriod( start < $start)
> 	then
> 		retract($accountingPeriod);
> end
> rule "Test 01 - Retract Remaining AccountingPeriods"
> 	salience 1
> 	when
> 		$fact : AccountingPeriod( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining Cashflows"
> 	salience 1
> 	when
> 		$fact : Cashflow( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining UpdatingAccounts"
> 	salience 1
> 	when
> 		$fact : UpdatingAccount( )
> 	then
> 		retract($fact);
> end
> The code is as follows:
> package net.tplusplus.drools.speedtest.bank;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> /**
>  * This class provides a simple Bank Account.
>  * 
>  * @author DunningJ
>  *
>  */
> public class Account
> {
> 	private long accountNo;
> 	private double balance=0;
> 	
> 	public Account(){};
> 	
> 	public Account(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public double getBalance()
> 	{
> 		return balance;
> 	}
> 	public void setBalance(double balance)
> 	{
> 		this.balance = balance;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Account objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Account account = (Account) obj;
> 		
> 		return (getAccountNo()==account.getAccountNo());
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Account[" 
> 				+"accountNo="+accountNo
> 				+",balance="+balance
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.rules.runner.rao.Fact;
> /**
>  * Each bank transaction must fall within an AccountingPeriod - which
>  * is normally a quarter.  A separate AccountingPeriod fact is passed to the
>  * Drools engine for each accounting period for which we are processing 
>  * calculations.
>  * 
>  * @author DunningJ
>  *
>  */
> public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
> {
> 	private Date start;
> 	private long startl;
> 	private Long startL;
> 	private Date end;
> 	private long endl;
> 	private Long endL;
> 	
> 	public AccountingPeriod(){}
> 	
> 	public AccountingPeriod(Date start, Date end)
> 	{
> 		this.start = start;
> 		this.startl = start.getTime();
> 		this.startL = start.getTime();
> 		this.end = end;
> 		this.endl = end.getTime();
> 		this.endL = end.getTime();
> 	}
> 	public Date getStart()
> 	{
> 		return start;
> 	}
> 	
> 	public long getStartl()
> 	{
> 		return startl;
> 	}
> 	
> 	public long getStartL()
> 	{
> 		return startL;
> 	}
> 	public void setStart(Date start)
> 	{
> 		this.start = start;
> 	}
> 	public Date getEnd()
> 	{
> 		return end;
> 	}
> 	public long getEndl()
> 	{
> 		return endl;
> 	}
> 	
> 	public Long getEndL()
> 	{
> 		return endL;
> 	}
> 	public void setEnd(Date end)
> 	{
> 		this.end = end;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  AccountingPeriod by period start date.
> 	 */
> 	public int compareTo(AccountingPeriod accountingPeriod)
> 	{
> 		if(this.start.after(accountingPeriod.getStart()))
> 		{
> 			return 1;
> 		}
> 		if(this.start.before(accountingPeriod.getStart()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}	
> 	
> 	/**
> 	 *  This method enables the comparison of AccountingPeriod objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof AccountingPeriod))
> 		{
> 			return false;
> 		}
> 		
> 		AccountingPeriod ap = (AccountingPeriod) obj;
> 		
> 		return getStart().equals(ap.getStart());
> 	}
> 	public String toString()
> 	{
> 		return "AccountingPeriod[" 
> 				+"start="+start
> 				+",end="+end
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class Cashflow implements Fact, Comparable<Cashflow>
> {	
> 	public static final int CREDIT = 0;
> 	public static final int DEBIT = 1;
> 	
> 	private Date date;
> 	private long datel;
> 	private Long dateL;
> 	private double amount;
> 	private int type;
> 	private Account account;
> 	
> 	public Cashflow()
> 	{
> 	}
> 	
> 	public Cashflow(Date date, double amount, int type, Account account)
> 	{
> 		this();
> 		
> 		this.date = date;
> 		this.datel= date.getTime();
> 		this.dateL = date.getTime();
> 		this.amount = amount;
> 		this.type = type;
> 		this.account = account;
> 	}
> 	public Date getDate()
> 	{
> 		return date;
> 	}
> 	
> 	public void setDate(Date date)
> 	{
> 		this.date = date;
> 	}
> 	
> 	public double getAmount()
> 	{
> 		return amount;
> 	}
> 	
> 	public void setAmount(double amount)
> 	{
> 		this.amount = amount;
> 	}
> 	
> 	public int getType()
> 	{
> 		return type;
> 	}
> 	public void setType(int type)
> 	{
> 		this.type = type;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	public long getDatel()
> 	{
> 		return datel;
> 	}
> 	
> 	public long getDateL()
> 	{
> 		return dateL;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  Cashflow by cashflow date.
> 	 */	
> 	public int compareTo(Cashflow cashflow)
> 	{
> 		if(getDate().after(cashflow.getDate()))
> 		{
> 			return 1;
> 		}
> 		if(getDate().before(cashflow.getDate()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Cashflow objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Cashflow cashflow = (Cashflow) obj;
> 		
> 		if(!getAccount().equals(cashflow.getAccount())) return false;
> 		if(getAmount()!=cashflow.getAmount()) return false;
> 		if(!getDate().equals(cashflow.getDate())) return false;
> 		if(getType()!=cashflow.getType()) return false;
> 		
> 		return true;
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Cashflow["
> 				//+"account="+account
> 				+"date="+date
> 				+",amount="+amount
> 				+",type="+(type==CREDIT?"Credit":"Debit")
> 				+"]";
> 	}
> 	
> 	
> }
> package net.tplusplus.drools.speedtest.facts;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
> {
> 	private long accountNo;
> 	private Account account;
> 	
> 	public UpdatingAccount(long accountNo, Account account)
> 	{
> 		this.accountNo = accountNo;
> 		this.account = account;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  UpdatingAccount by account no.
> 	 */	
> 	public int compareTo(UpdatingAccount updatingAccount)
> 	{
> 		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
> 		
> 		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of UpdatingAccount objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof UpdatingAccount))
> 		{
> 			return false;
> 		}
> 		
> 		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
> 		
> 		return (getAccountNo()==updatingAccount.getAccountNo());	
> 	}		
> }
> package net.tplusplus.test.drools.speedtest.data;
> import java.util.ArrayList;
> import java.util.Date;
> import java.util.List;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.utils.SimpleDate;
> public class TestData
> {
> 	private static Date startDate;
> 	private static Date endDate;
> 	
> 	private static List<Account> accounts;
> 	private static List<UpdatingAccount> updatingAccounts;
> 	private static List<Cashflow> cashflows;
> 	private static List<AccountingPeriod> accountingPeriods;
> 	
> 	static
> 	{
> 		try
> 		{
> 			startDate = new SimpleDate("01/01/2007");
> 			endDate = new SimpleDate("31/12/2007");
> 		}
> 		catch(Exception e){}
> 	}
> 	
> 	private static List<Account> getAllAccounts()
> 	{
> 		if(accounts==null)
> 		{
> 			accounts = new ArrayList<Account>();
> 		
> 			accounts.add(new Account(1));
> 		}
> 		
> 		return accounts;
> 	}
> 	
> 	public static List<UpdatingAccount> getAllUpdatingAccounts()
> 	{
> 		if(updatingAccounts==null)
> 		{
> 			updatingAccounts = new ArrayList<UpdatingAccount>();
> 			
> 			for(Account account : getAllAccounts())
> 			{
> 				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
> 			}
> 		}
> 		
> 		return updatingAccounts;
> 	}
> 	
> 	public static List<Cashflow> getAllCashflows()
> 	throws Exception
> 	{
> 		if(cashflows==null)
> 		{
> 			cashflows = new ArrayList<Cashflow>();		
> 				
> 			for(Date date = startDate; !date.after(endDate);)
> 			{
> 				int adj = 0;
> 				
> 				for(Account acct : getAllAccounts())
> 				{
> 					adj++;
> 					
> 					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
> 					int[] debits = new int[]{ 200, 50, 50, 30};
> 					
> 					for(int credit : credits)
> 					{
> 						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
> 						cashflows.add(c);
> 					}
> 					
> 					for(int debit : debits)
> 					{
> 						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
> 						cashflows.add(c);
> 					}	
> 				}
> 				
> 				long newDate = date.getTime() + 24l*60l*60l*1000l;
> 				date = new Date(newDate);
> 			}
> 		}
> 		
> 		return cashflows;
> 	}
> 	
> 	public static List<AccountingPeriod> getAccountingPeriods()
> 	throws Exception
> 	{
> 		if(accountingPeriods==null)
> 		{
> 			accountingPeriods = new ArrayList<AccountingPeriod>();
> 			
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
> 		}
> 		
> 		return accountingPeriods;
> 	}
> 	
> 	public static List<Fact> getAllFacts()
> 	throws Exception
> 	{
> 		List<Fact> facts = new ArrayList<Fact>();
> 		
> 		facts.addAll(getAccountingPeriods());
> 		facts.addAll(getAllCashflows());
> 		facts.addAll(getAllUpdatingAccounts());
> 		
> 		return facts;		
> 	}
> 	
> 	public static void resetAccounts()
> 	{
> 		for(Account account : getAllAccounts())
> 		{
> 			account.setBalance(0);
> 		}
> 	}
> }
> package net.tplusplus.test.drools.speedtest;
> import java.util.List;
> import org.drools.RuleBase;
> import org.drools.WorkingMemory;
> import net.tplusplus.rules.runner.RuleRunner;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.test.drools.speedtest.data.TestData;
> import net.tplusplus.utils.TimedResults;
> public class SpeedTest1
> {
> 	public static void main(String[] args)
> 	throws Exception
> 	{
> 		int iterations = 1000;
> 		
> 		//runTest1(iterations);
> 		runTest2(iterations);
> 		runTest3(iterations);
> 		runTest4(iterations);
> 		runTest5(iterations);
> 		runTest6(iterations);
> 	}
> 	
> 	public static void runTest1(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 1 - NO CACHING");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			runner.createRuleBase();
> 			runner.createWorkingMemory();
> 			runner.runRules();
> 			
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest2(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		RuleBase cachedRuleBase = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			System.out.println(i);
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedRuleBase==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setRuleBase(cachedRuleBase);
> 				runner.createWorkingMemory();
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest3(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest4(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest5(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest6(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> }
> package net.tplusplus.rules.runner;
> import java.io.File;
> import java.io.FileReader;
> import java.net.URL;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.List;
> import java.util.Iterator;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.rules.runner.rao.Global;
> import org.drools.FactHandle;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.spi.ActivationGroup;
> import org.drools.spi.AgendaGroup;
> public class RuleRunner
> {
> 	private RuleBase ruleBase;
> 	private WorkingMemory workingMemory;
> 	
> 	private List<String> rules;
> 	private List<Global> globals;
> 	private List<Fact> facts;
> 	
> 	public RuleRunner()
> 	{
> 		rules = new ArrayList<String>();
> 		globals = new ArrayList<Global>();
> 		facts = new ArrayList<Fact>();	
> 	}
> 	
> 	public void addRules(String... rules)
> 	{
> 		this.rules.addAll(Arrays.asList(rules));
> 	}
> 	
> 	public void addGlobals(Global... globals)
> 	{
> 		this.globals.addAll(Arrays.asList(globals));
> 	}
> 	
> 	public void addFacts(Fact... facts)
> 	{
> 		this.facts.addAll(Arrays.asList(facts));
> 	}
> 	
> 	public void addFacts(List<? extends Fact> facts)
> 	{
> 		this.facts.addAll(facts);
> 	}	
> 	
> 	public List<Fact> getFacts()
> 	{
> 		return this.facts;
> 	}
> 	
> 	public void clearFacts()
> 	{
> 		this.facts = new ArrayList<Fact>();
> 	}
> 	
> 	public RuleBase createRuleBase()
> 	throws Exception
> 	{
> 		if(rules==null)
> 		{
> 			throw new Exception("No rules provided for Engine");
> 		}
> 		
> 		ruleBase = RuleBaseFactory.newRuleBase();
> 		PackageBuilder builder = new PackageBuilder();		
> 		
> 		for(String ruleFile : rules)
> 		{
> 			URL resource = this.getClass().getResource(ruleFile);
> 			
> 			if(resource==null)
> 			{
> 				System.err.println("Could not find resource: "+ruleFile);
> 				continue;
> 			}
> 			File file = new File(this.getClass().getResource(ruleFile).getPath());
> 			if(!file.exists())
> 			{
> 				System.err.println("Could not find rule file: "+file.getPath());
> 				continue;
> 			}
> 			
> 			builder.addPackageFromDrl(new FileReader(file.getPath()));
> 		}
> 		
> 		org.drools.rule.Package pkg = builder.getPackage();		
> 		ruleBase.addPackage(pkg);	
> 		
> 		return ruleBase;
> 	}
> 	
> 	public void setRuleBase(RuleBase ruleBase)
> 	{
> 		this.ruleBase = ruleBase;
> 	}
> 	
> 	public RuleBase getRuleBase()
> 	{
> 		return ruleBase;
> 	}
> 	
> 	public WorkingMemory createWorkingMemory()
> 	throws Exception
> 	{
> 		if(ruleBase==null)
> 		{
> 			createRuleBase();
> 		}
> 		
> 		workingMemory = null;
> 		
> 		workingMemory = ruleBase.newStatefulSession();
> 		
> 		return workingMemory;
> 	}
> 	
> 	public void setWorkingMemory(WorkingMemory workingMemory)
> 	{
> 		this.workingMemory = workingMemory;
> 	}
> 	
> 	public WorkingMemory getWorkingMemory()
> 	{
> 		return workingMemory;
> 	}
> 	
> 	public void runRules()
> 	throws Exception
> 	{		
> 		if(workingMemory==null)
> 		{
> 			throw new Exception("No workingMemory created for Engine");
> 		}
> 		
> 		System.gc();
> 		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
> 		
> 		
> 		if(globals!=null)
> 		{
> 			for(Global global : globals)
> 			{
> 				workingMemory.setGlobal(global.getName(), global.getValue());
> 			}
> 		}
> 		if(facts!=null)
> 		{
> 			for(Fact fact : facts)
> 			{
> 				workingMemory.insert(fact);
> 			}
> 		}
> 		workingMemory.fireAllRules();
> 	}
> }
> package net.tplusplus.rules.runner.rao;
> public interface Fact
> {
> }
> package net.tplusplus.rules.runner.rao;
> public class Global
> {
> 	private String name;
> 	private Object value;
> 	
> 	public Global(String name, Object value)
> 	{
> 		this.name = name;
> 		this.value = value;
> 	}
> 	public String getName()
> 	{
> 		return name;
> 	}
> 	public void setName(String name)
> 	{
> 		this.name = name;
> 	}
> 	public Object getValue()
> 	{
> 		return value;
> 	}
> 	public void setValue(Object value)
> 	{
> 		this.value = value;
> 	}
> 	
> 	public String toString()
> 	{
> 		return "Global["
> 				+"name="+name
> 				+"value="+value
> 				+"]";
> 	}
> }
> package net.tplusplus.utils;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> public class SimpleDate extends Date
> {
> 	public static final long serialVersionUID = 1;
> 	
> 	public SimpleDate(String datestr)
> 	throws Exception
> 	{
> 		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
> 		this.setTime(format.parse(datestr).getTime());
> 	}
> }
> package net.tplusplus.utils;
> import java.util.HashMap;
> import java.util.Map;
> public class TimedResults
> {
> 	private long fastest = -1;
> 	private long slowest = -1;
> 	
> 	private Map<Long,Long> results = new HashMap<Long,Long>();
> 	
> 	public TimedResults()
> 	{
> 	}
> 	
> 	public void addTime(long time)
> 	throws Exception
> 	{
> 		if(time < 0)
> 		{
> 			throw new Exception("Invalid Time");
> 		}
> 		
> 		Long key = System.currentTimeMillis();
> 		results.put(key,time);
> 		
> 		if(fastest==-1 || fastest>time) fastest=time;
> 		if(slowest==-1 || slowest<time) slowest=time;
> 	}
> 	
> 	public Map<Long,Long> getResults()
> 	{
> 		return results;
> 	}
> 	
> 	public long getFastest()
> 	{
> 		return fastest;
> 	}
> 	
> 	public long getSlowest()
> 	{
> 		return slowest;
> 	}
> 	
> 	public long getAverage()
> 	{
> 		long time = 0;
> 		
> 		for(Long timetaken : results.values())
> 		{
> 			time += timetaken;
> 		}
> 		
> 		return time / results.size();
> 	}
> }

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 11:07:50 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 11:07:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <940479.1193584070550.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1306?page=all ]

John Dunning updated JBRULES-1306:
----------------------------------

    Description: 
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.


The rules and code are listed below and attached as eclipse projects.

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}



  was:
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}




> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1306
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>         Attachments: Archive.zip
>
>
> The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.
> The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.
> The rules and code are listed below and attached as eclipse projects.
> package net.tplusplus.drools.speedtest.rules.test1;
> import net.tplusplus.drools.speedtest.facts.*;
> import net.tplusplus.drools.speedtest.bank.*;
> rule "Test 01 - Credit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Credit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Debit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Debit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Print Balance"
> 	salience 90
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		UpdatingAccount( $accountNo : accountNo, $account : account)
> 		not AccountingPeriod( start < $start)
> 	then
> 		//System.out.print("Period End: "+$end);
> 		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
> end
> rule "Test 01 - Retract Period"
> 	salience 80
> 	when
> 		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
> 		not AccountingPeriod( start < $start)
> 	then
> 		retract($accountingPeriod);
> end
> rule "Test 01 - Retract Remaining AccountingPeriods"
> 	salience 1
> 	when
> 		$fact : AccountingPeriod( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining Cashflows"
> 	salience 1
> 	when
> 		$fact : Cashflow( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining UpdatingAccounts"
> 	salience 1
> 	when
> 		$fact : UpdatingAccount( )
> 	then
> 		retract($fact);
> end
> The code is as follows:
> package net.tplusplus.drools.speedtest.bank;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> /**
>  * This class provides a simple Bank Account.
>  * 
>  * @author DunningJ
>  *
>  */
> public class Account
> {
> 	private long accountNo;
> 	private double balance=0;
> 	
> 	public Account(){};
> 	
> 	public Account(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public double getBalance()
> 	{
> 		return balance;
> 	}
> 	public void setBalance(double balance)
> 	{
> 		this.balance = balance;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Account objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Account account = (Account) obj;
> 		
> 		return (getAccountNo()==account.getAccountNo());
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Account[" 
> 				+"accountNo="+accountNo
> 				+",balance="+balance
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.rules.runner.rao.Fact;
> /**
>  * Each bank transaction must fall within an AccountingPeriod - which
>  * is normally a quarter.  A separate AccountingPeriod fact is passed to the
>  * Drools engine for each accounting period for which we are processing 
>  * calculations.
>  * 
>  * @author DunningJ
>  *
>  */
> public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
> {
> 	private Date start;
> 	private long startl;
> 	private Long startL;
> 	private Date end;
> 	private long endl;
> 	private Long endL;
> 	
> 	public AccountingPeriod(){}
> 	
> 	public AccountingPeriod(Date start, Date end)
> 	{
> 		this.start = start;
> 		this.startl = start.getTime();
> 		this.startL = start.getTime();
> 		this.end = end;
> 		this.endl = end.getTime();
> 		this.endL = end.getTime();
> 	}
> 	public Date getStart()
> 	{
> 		return start;
> 	}
> 	
> 	public long getStartl()
> 	{
> 		return startl;
> 	}
> 	
> 	public long getStartL()
> 	{
> 		return startL;
> 	}
> 	public void setStart(Date start)
> 	{
> 		this.start = start;
> 	}
> 	public Date getEnd()
> 	{
> 		return end;
> 	}
> 	public long getEndl()
> 	{
> 		return endl;
> 	}
> 	
> 	public Long getEndL()
> 	{
> 		return endL;
> 	}
> 	public void setEnd(Date end)
> 	{
> 		this.end = end;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  AccountingPeriod by period start date.
> 	 */
> 	public int compareTo(AccountingPeriod accountingPeriod)
> 	{
> 		if(this.start.after(accountingPeriod.getStart()))
> 		{
> 			return 1;
> 		}
> 		if(this.start.before(accountingPeriod.getStart()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}	
> 	
> 	/**
> 	 *  This method enables the comparison of AccountingPeriod objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof AccountingPeriod))
> 		{
> 			return false;
> 		}
> 		
> 		AccountingPeriod ap = (AccountingPeriod) obj;
> 		
> 		return getStart().equals(ap.getStart());
> 	}
> 	public String toString()
> 	{
> 		return "AccountingPeriod[" 
> 				+"start="+start
> 				+",end="+end
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class Cashflow implements Fact, Comparable<Cashflow>
> {	
> 	public static final int CREDIT = 0;
> 	public static final int DEBIT = 1;
> 	
> 	private Date date;
> 	private long datel;
> 	private Long dateL;
> 	private double amount;
> 	private int type;
> 	private Account account;
> 	
> 	public Cashflow()
> 	{
> 	}
> 	
> 	public Cashflow(Date date, double amount, int type, Account account)
> 	{
> 		this();
> 		
> 		this.date = date;
> 		this.datel= date.getTime();
> 		this.dateL = date.getTime();
> 		this.amount = amount;
> 		this.type = type;
> 		this.account = account;
> 	}
> 	public Date getDate()
> 	{
> 		return date;
> 	}
> 	
> 	public void setDate(Date date)
> 	{
> 		this.date = date;
> 	}
> 	
> 	public double getAmount()
> 	{
> 		return amount;
> 	}
> 	
> 	public void setAmount(double amount)
> 	{
> 		this.amount = amount;
> 	}
> 	
> 	public int getType()
> 	{
> 		return type;
> 	}
> 	public void setType(int type)
> 	{
> 		this.type = type;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	public long getDatel()
> 	{
> 		return datel;
> 	}
> 	
> 	public long getDateL()
> 	{
> 		return dateL;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  Cashflow by cashflow date.
> 	 */	
> 	public int compareTo(Cashflow cashflow)
> 	{
> 		if(getDate().after(cashflow.getDate()))
> 		{
> 			return 1;
> 		}
> 		if(getDate().before(cashflow.getDate()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Cashflow objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Cashflow cashflow = (Cashflow) obj;
> 		
> 		if(!getAccount().equals(cashflow.getAccount())) return false;
> 		if(getAmount()!=cashflow.getAmount()) return false;
> 		if(!getDate().equals(cashflow.getDate())) return false;
> 		if(getType()!=cashflow.getType()) return false;
> 		
> 		return true;
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Cashflow["
> 				//+"account="+account
> 				+"date="+date
> 				+",amount="+amount
> 				+",type="+(type==CREDIT?"Credit":"Debit")
> 				+"]";
> 	}
> 	
> 	
> }
> package net.tplusplus.drools.speedtest.facts;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
> {
> 	private long accountNo;
> 	private Account account;
> 	
> 	public UpdatingAccount(long accountNo, Account account)
> 	{
> 		this.accountNo = accountNo;
> 		this.account = account;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  UpdatingAccount by account no.
> 	 */	
> 	public int compareTo(UpdatingAccount updatingAccount)
> 	{
> 		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
> 		
> 		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of UpdatingAccount objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof UpdatingAccount))
> 		{
> 			return false;
> 		}
> 		
> 		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
> 		
> 		return (getAccountNo()==updatingAccount.getAccountNo());	
> 	}		
> }
> package net.tplusplus.test.drools.speedtest.data;
> import java.util.ArrayList;
> import java.util.Date;
> import java.util.List;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.utils.SimpleDate;
> public class TestData
> {
> 	private static Date startDate;
> 	private static Date endDate;
> 	
> 	private static List<Account> accounts;
> 	private static List<UpdatingAccount> updatingAccounts;
> 	private static List<Cashflow> cashflows;
> 	private static List<AccountingPeriod> accountingPeriods;
> 	
> 	static
> 	{
> 		try
> 		{
> 			startDate = new SimpleDate("01/01/2007");
> 			endDate = new SimpleDate("31/12/2007");
> 		}
> 		catch(Exception e){}
> 	}
> 	
> 	private static List<Account> getAllAccounts()
> 	{
> 		if(accounts==null)
> 		{
> 			accounts = new ArrayList<Account>();
> 		
> 			accounts.add(new Account(1));
> 		}
> 		
> 		return accounts;
> 	}
> 	
> 	public static List<UpdatingAccount> getAllUpdatingAccounts()
> 	{
> 		if(updatingAccounts==null)
> 		{
> 			updatingAccounts = new ArrayList<UpdatingAccount>();
> 			
> 			for(Account account : getAllAccounts())
> 			{
> 				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
> 			}
> 		}
> 		
> 		return updatingAccounts;
> 	}
> 	
> 	public static List<Cashflow> getAllCashflows()
> 	throws Exception
> 	{
> 		if(cashflows==null)
> 		{
> 			cashflows = new ArrayList<Cashflow>();		
> 				
> 			for(Date date = startDate; !date.after(endDate);)
> 			{
> 				int adj = 0;
> 				
> 				for(Account acct : getAllAccounts())
> 				{
> 					adj++;
> 					
> 					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
> 					int[] debits = new int[]{ 200, 50, 50, 30};
> 					
> 					for(int credit : credits)
> 					{
> 						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
> 						cashflows.add(c);
> 					}
> 					
> 					for(int debit : debits)
> 					{
> 						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
> 						cashflows.add(c);
> 					}	
> 				}
> 				
> 				long newDate = date.getTime() + 24l*60l*60l*1000l;
> 				date = new Date(newDate);
> 			}
> 		}
> 		
> 		return cashflows;
> 	}
> 	
> 	public static List<AccountingPeriod> getAccountingPeriods()
> 	throws Exception
> 	{
> 		if(accountingPeriods==null)
> 		{
> 			accountingPeriods = new ArrayList<AccountingPeriod>();
> 			
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
> 		}
> 		
> 		return accountingPeriods;
> 	}
> 	
> 	public static List<Fact> getAllFacts()
> 	throws Exception
> 	{
> 		List<Fact> facts = new ArrayList<Fact>();
> 		
> 		facts.addAll(getAccountingPeriods());
> 		facts.addAll(getAllCashflows());
> 		facts.addAll(getAllUpdatingAccounts());
> 		
> 		return facts;		
> 	}
> 	
> 	public static void resetAccounts()
> 	{
> 		for(Account account : getAllAccounts())
> 		{
> 			account.setBalance(0);
> 		}
> 	}
> }
> package net.tplusplus.test.drools.speedtest;
> import java.util.List;
> import org.drools.RuleBase;
> import org.drools.WorkingMemory;
> import net.tplusplus.rules.runner.RuleRunner;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.test.drools.speedtest.data.TestData;
> import net.tplusplus.utils.TimedResults;
> public class SpeedTest1
> {
> 	public static void main(String[] args)
> 	throws Exception
> 	{
> 		int iterations = 1000;
> 		
> 		//runTest1(iterations);
> 		runTest2(iterations);
> 		runTest3(iterations);
> 		runTest4(iterations);
> 		runTest5(iterations);
> 		runTest6(iterations);
> 	}
> 	
> 	public static void runTest1(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 1 - NO CACHING");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			runner.createRuleBase();
> 			runner.createWorkingMemory();
> 			runner.runRules();
> 			
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest2(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		RuleBase cachedRuleBase = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			System.out.println(i);
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedRuleBase==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setRuleBase(cachedRuleBase);
> 				runner.createWorkingMemory();
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest3(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest4(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest5(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest6(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> }
> package net.tplusplus.rules.runner;
> import java.io.File;
> import java.io.FileReader;
> import java.net.URL;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.List;
> import java.util.Iterator;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.rules.runner.rao.Global;
> import org.drools.FactHandle;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.spi.ActivationGroup;
> import org.drools.spi.AgendaGroup;
> public class RuleRunner
> {
> 	private RuleBase ruleBase;
> 	private WorkingMemory workingMemory;
> 	
> 	private List<String> rules;
> 	private List<Global> globals;
> 	private List<Fact> facts;
> 	
> 	public RuleRunner()
> 	{
> 		rules = new ArrayList<String>();
> 		globals = new ArrayList<Global>();
> 		facts = new ArrayList<Fact>();	
> 	}
> 	
> 	public void addRules(String... rules)
> 	{
> 		this.rules.addAll(Arrays.asList(rules));
> 	}
> 	
> 	public void addGlobals(Global... globals)
> 	{
> 		this.globals.addAll(Arrays.asList(globals));
> 	}
> 	
> 	public void addFacts(Fact... facts)
> 	{
> 		this.facts.addAll(Arrays.asList(facts));
> 	}
> 	
> 	public void addFacts(List<? extends Fact> facts)
> 	{
> 		this.facts.addAll(facts);
> 	}	
> 	
> 	public List<Fact> getFacts()
> 	{
> 		return this.facts;
> 	}
> 	
> 	public void clearFacts()
> 	{
> 		this.facts = new ArrayList<Fact>();
> 	}
> 	
> 	public RuleBase createRuleBase()
> 	throws Exception
> 	{
> 		if(rules==null)
> 		{
> 			throw new Exception("No rules provided for Engine");
> 		}
> 		
> 		ruleBase = RuleBaseFactory.newRuleBase();
> 		PackageBuilder builder = new PackageBuilder();		
> 		
> 		for(String ruleFile : rules)
> 		{
> 			URL resource = this.getClass().getResource(ruleFile);
> 			
> 			if(resource==null)
> 			{
> 				System.err.println("Could not find resource: "+ruleFile);
> 				continue;
> 			}
> 			File file = new File(this.getClass().getResource(ruleFile).getPath());
> 			if(!file.exists())
> 			{
> 				System.err.println("Could not find rule file: "+file.getPath());
> 				continue;
> 			}
> 			
> 			builder.addPackageFromDrl(new FileReader(file.getPath()));
> 		}
> 		
> 		org.drools.rule.Package pkg = builder.getPackage();		
> 		ruleBase.addPackage(pkg);	
> 		
> 		return ruleBase;
> 	}
> 	
> 	public void setRuleBase(RuleBase ruleBase)
> 	{
> 		this.ruleBase = ruleBase;
> 	}
> 	
> 	public RuleBase getRuleBase()
> 	{
> 		return ruleBase;
> 	}
> 	
> 	public WorkingMemory createWorkingMemory()
> 	throws Exception
> 	{
> 		if(ruleBase==null)
> 		{
> 			createRuleBase();
> 		}
> 		
> 		workingMemory = null;
> 		
> 		workingMemory = ruleBase.newStatefulSession();
> 		
> 		return workingMemory;
> 	}
> 	
> 	public void setWorkingMemory(WorkingMemory workingMemory)
> 	{
> 		this.workingMemory = workingMemory;
> 	}
> 	
> 	public WorkingMemory getWorkingMemory()
> 	{
> 		return workingMemory;
> 	}
> 	
> 	public void runRules()
> 	throws Exception
> 	{		
> 		if(workingMemory==null)
> 		{
> 			throw new Exception("No workingMemory created for Engine");
> 		}
> 		
> 		System.gc();
> 		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
> 		
> 		
> 		if(globals!=null)
> 		{
> 			for(Global global : globals)
> 			{
> 				workingMemory.setGlobal(global.getName(), global.getValue());
> 			}
> 		}
> 		if(facts!=null)
> 		{
> 			for(Fact fact : facts)
> 			{
> 				workingMemory.insert(fact);
> 			}
> 		}
> 		workingMemory.fireAllRules();
> 	}
> }
> package net.tplusplus.rules.runner.rao;
> public interface Fact
> {
> }
> package net.tplusplus.rules.runner.rao;
> public class Global
> {
> 	private String name;
> 	private Object value;
> 	
> 	public Global(String name, Object value)
> 	{
> 		this.name = name;
> 		this.value = value;
> 	}
> 	public String getName()
> 	{
> 		return name;
> 	}
> 	public void setName(String name)
> 	{
> 		this.name = name;
> 	}
> 	public Object getValue()
> 	{
> 		return value;
> 	}
> 	public void setValue(Object value)
> 	{
> 		this.value = value;
> 	}
> 	
> 	public String toString()
> 	{
> 		return "Global["
> 				+"name="+name
> 				+"value="+value
> 				+"]";
> 	}
> }
> package net.tplusplus.utils;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> public class SimpleDate extends Date
> {
> 	public static final long serialVersionUID = 1;
> 	
> 	public SimpleDate(String datestr)
> 	throws Exception
> 	{
> 		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
> 		this.setTime(format.parse(datestr).getTime());
> 	}
> }
> package net.tplusplus.utils;
> import java.util.HashMap;
> import java.util.Map;
> public class TimedResults
> {
> 	private long fastest = -1;
> 	private long slowest = -1;
> 	
> 	private Map<Long,Long> results = new HashMap<Long,Long>();
> 	
> 	public TimedResults()
> 	{
> 	}
> 	
> 	public void addTime(long time)
> 	throws Exception
> 	{
> 		if(time < 0)
> 		{
> 			throw new Exception("Invalid Time");
> 		}
> 		
> 		Long key = System.currentTimeMillis();
> 		results.put(key,time);
> 		
> 		if(fastest==-1 || fastest>time) fastest=time;
> 		if(slowest==-1 || slowest<time) slowest=time;
> 	}
> 	
> 	public Map<Long,Long> getResults()
> 	{
> 		return results;
> 	}
> 	
> 	public long getFastest()
> 	{
> 		return fastest;
> 	}
> 	
> 	public long getSlowest()
> 	{
> 		return slowest;
> 	}
> 	
> 	public long getAverage()
> 	{
> 		long time = 0;
> 		
> 		for(Long timetaken : results.values())
> 		{
> 			time += timetaken;
> 		}
> 		
> 		return time / results.size();
> 	}
> }

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 11:15:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Sun, 28 Oct 2007 11:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1305) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <13001809.1193583241581.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23654956.1193584501635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1305?page=all ]

John Dunning updated JBRULES-1305:
----------------------------------

    Description: 
THIS BUG IS RAISED IN 

Key: JBRULES-1306
URL: http://jira.jboss.com/jira/browse/JBRULES-1306

browser problems when submitting :(

  was:
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}




> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1305
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1305
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306
> browser problems when submitting :(

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 14:50:02 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 14:50:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6933239.1193597402181.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Andrew Lee Rubinger updated EJBTHREE-1057:
------------------------------------------

    Fix Version/s: HEAD

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 16:09:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 16:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21192254.1193602141704.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1075.
-------------------------------------------

    Resolution: Done

Verified OK in Automated QA

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 16:11:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 16:11:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1071) Business
 Interface must not extend EJBObject or EJBLocalObject
In-Reply-To: <18467162.1192494129846.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3821063.1193602261677.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1071?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1071.
-------------------------------------------

    Resolution: Done

Satisfied as a result of resolving linked issue EJBTHREE-1075

> Business Interface must not extend EJBObject or EJBLocalObject
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-1071
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1071
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> EJB3 Spec 4.6.6 Bullet 1:
> "The following are the requirements for the session bean's business interface:
>      * The interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface."
> ...thus the following construct:
> public interface StatefulRemote extends EJBObject{...}
> ...and:
> @Stateful
> @Remote(StatefulRemote.class)
> @RemoteBinding(jndiBinding = StatefulRemote.JNDI_NAME_REMOTE)
> public class StatefulRemoteBean 
> ...should fail with a deployment exception referencing the specification.

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 16:47:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 16:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24766630.1193604421601.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=comments#action_12384739 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1057:
-----------------------------------------------

Fix for Branch_4_2 introduces regression into:

org.jboss.ejb3.test.mdb.unit.ConcurrentMDBUnitTestCase.testQueue
org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 17:03:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 17:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11038069.1193605381607.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=comments#action_12384742 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1057:
-----------------------------------------------

Both:

org.jboss.ejb3.test.mdb.unit.ConcurrentMDBUnitTestCase.testQueue
org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA

...use temporal-based waiting to ensure that the tests pass.  On manual single runs, verified OK; these tests should not be affected by code changes to resolve this issue.


> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Sun Oct 28 17:05:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Sun, 28 Oct 2007 17:05:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4145280.1193605501512.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1057.
-------------------------------------------

    Resolution: Done

Completed

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: Branch_4_2, HEAD
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 04:23:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 04:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11776518.1193646181440.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=comments#action_12384762 ] 
            
Carlo de Wolf commented on EJBTHREE-1083:
-----------------------------------------

Rename the workspace in all tests to the new one.

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 05:40:02 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 05:40:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1082) Exception
 wrapping and delivering
In-Reply-To: <8075056.1193511302237.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31747697.1193650802395.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1082?page=all ]

Carlo de Wolf updated EJBTHREE-1082:
------------------------------------

    Component/s:     (was: EJB3 Extensions)
        Affects:   (was: [Interactive Demo/Tutorial, Compatibility/Configuration])
       Assignee: Andrew Lee Rubinger
     Complexity:   (was: Low)

> Exception wrapping and delivering
> ---------------------------------
>
>                 Key: EJBTHREE-1082
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1082
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.1.GA
>         Environment: SUN jdk1.5  ,  windows XP ,  JBoss4.2.1GA
>            Reporter: Fang Tianying
>         Assigned To: Andrew Lee Rubinger
>
> hi, 
> This problem is easy to recur.
> When SLSB A(transaction att:requried) calls SLSB B(transaction att: not supported ) though B's local interface, and B throws a RuntimeException, then A will recieve just this very RuntimeException rather than an EJBException. 
> I mean the EJB Container should wrap the rt. ex thrown by SLSB B to an EJBException, and then deliver the EJBException to it's caller - SLSB A. 
> If it is a bug, I'm appriciated to any responses.  fangtianying at yahoo.cn
> best regards,
> FangTianying

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 06:19:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Mon, 29 Oct 2007 06:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1304) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <15904136.1193582881635.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32390495.1193653141757.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1304?page=all ]

John Dunning updated JBRULES-1304:
----------------------------------

    Description: 
THIS BUG IS RAISED IN 

Key: JBRULES-1306 
URL: http://jira.jboss.com/jira/browse/JBRULES-1306 

browser problems when submitting :( 


> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1304
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1304
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 06:21:01 2007
From: jira-events at lists.jboss.org (John Dunning (JIRA))
Date: Mon, 29 Oct 2007 06:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1303) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <7852123.1193582641743.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19180210.1193653261794.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1303?page=all ]

John Dunning updated JBRULES-1303:
----------------------------------

    Description: 
THIS BUG IS RAISED IN 

Key: JBRULES-1306 
URL: http://jira.jboss.com/jira/browse/JBRULES-1306 

browser problems when submitting :( 


  was:
The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.

The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.

The code has been emailed to Mark Proctor, and I can email it over again (contact me on john at tplusplus.net).

The rules are described below:

package net.tplusplus.drools.speedtest.rules.test1;

import net.tplusplus.drools.speedtest.facts.*;
import net.tplusplus.drools.speedtest.bank.*;

rule "Test 01 - Credit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Credit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Debit Cashflow"
	salience 100
	when
		AccountingPeriod( $start : start, $end : end )
		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
		not AccountingPeriod( start < $start)
	then 
		//System.out.println("Debit "+$amount);
		$account.setBalance($account.getBalance()+$amount);
		retract($cashflow);
end

rule "Test 01 - Print Balance"
	salience 90
	when
		AccountingPeriod( $start : start, $end : end )
		UpdatingAccount( $accountNo : accountNo, $account : account)
		not AccountingPeriod( start < $start)
	then
		//System.out.print("Period End: "+$end);
		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
end

rule "Test 01 - Retract Period"
	salience 80
	when
		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
		not AccountingPeriod( start < $start)
	then
		retract($accountingPeriod);
end

rule "Test 01 - Retract Remaining AccountingPeriods"
	salience 1
	when
		$fact : AccountingPeriod( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining Cashflows"
	salience 1
	when
		$fact : Cashflow( )
	then
		retract($fact);
end

rule "Test 01 - Retract Remaining UpdatingAccounts"
	salience 1
	when
		$fact : UpdatingAccount( )
	then
		retract($fact);
end

The code is as follows:

package net.tplusplus.drools.speedtest.bank;

import net.tplusplus.drools.speedtest.facts.Cashflow;

/**
 * This class provides a simple Bank Account.
 * 
 * @author DunningJ
 *
 */
public class Account
{
	private long accountNo;
	private double balance=0;
	
	public Account(){};
	
	public Account(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public double getBalance()
	{
		return balance;
	}

	public void setBalance(double balance)
	{
		this.balance = balance;
	}
	
	/**
	 *  This method enables the comparison of Account objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Account account = (Account) obj;
		
		return (getAccountNo()==account.getAccountNo());
	}	
	
	public String toString()
	{
		return "Account[" 
				+"accountNo="+accountNo
				+",balance="+balance
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.rules.runner.rao.Fact;

/**
 * Each bank transaction must fall within an AccountingPeriod - which
 * is normally a quarter.  A separate AccountingPeriod fact is passed to the
 * Drools engine for each accounting period for which we are processing 
 * calculations.
 * 
 * @author DunningJ
 *
 */
public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
{
	private Date start;
	private long startl;
	private Long startL;
	private Date end;
	private long endl;
	private Long endL;
	
	public AccountingPeriod(){}
	
	public AccountingPeriod(Date start, Date end)
	{
		this.start = start;
		this.startl = start.getTime();
		this.startL = start.getTime();
		this.end = end;
		this.endl = end.getTime();
		this.endL = end.getTime();
	}

	public Date getStart()
	{
		return start;
	}
	
	public long getStartl()
	{
		return startl;
	}
	
	public long getStartL()
	{
		return startL;
	}

	public void setStart(Date start)
	{
		this.start = start;
	}

	public Date getEnd()
	{
		return end;
	}

	public long getEndl()
	{
		return endl;
	}
	
	public Long getEndL()
	{
		return endL;
	}

	public void setEnd(Date end)
	{
		this.end = end;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  AccountingPeriod by period start date.
	 */
	public int compareTo(AccountingPeriod accountingPeriod)
	{
		if(this.start.after(accountingPeriod.getStart()))
		{
			return 1;
		}
		if(this.start.before(accountingPeriod.getStart()))
		{
			return -1;
		}	
		
		return 0;
	}	
	
	/**
	 *  This method enables the comparison of AccountingPeriod objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof AccountingPeriod))
		{
			return false;
		}
		
		AccountingPeriod ap = (AccountingPeriod) obj;
		
		return getStart().equals(ap.getStart());
	}

	public String toString()
	{
		return "AccountingPeriod[" 
				+"start="+start
				+",end="+end
				+"]";
	}
}


package net.tplusplus.drools.speedtest.facts;

import java.util.Date;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class Cashflow implements Fact, Comparable<Cashflow>
{	
	public static final int CREDIT = 0;
	public static final int DEBIT = 1;
	
	private Date date;
	private long datel;
	private Long dateL;
	private double amount;
	private int type;
	private Account account;
	
	public Cashflow()
	{
	}
	
	public Cashflow(Date date, double amount, int type, Account account)
	{
		this();
		
		this.date = date;
		this.datel= date.getTime();
		this.dateL = date.getTime();
		this.amount = amount;
		this.type = type;
		this.account = account;
	}

	public Date getDate()
	{
		return date;
	}
	
	public void setDate(Date date)
	{
		this.date = date;
	}
	
	public double getAmount()
	{
		return amount;
	}
	
	public void setAmount(double amount)
	{
		this.amount = amount;
	}
	
	public int getType()
	{
		return type;
	}

	public void setType(int type)
	{
		this.type = type;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	public long getDatel()
	{
		return datel;
	}
	
	public long getDateL()
	{
		return dateL;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  Cashflow by cashflow date.
	 */	
	public int compareTo(Cashflow cashflow)
	{
		if(getDate().after(cashflow.getDate()))
		{
			return 1;
		}
		if(getDate().before(cashflow.getDate()))
		{
			return -1;
		}	
		
		return 0;
	}
	
	/**
	 *  This method enables the comparison of Cashflow objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof Cashflow))
		{
			return false;
		}
		
		Cashflow cashflow = (Cashflow) obj;
		
		if(!getAccount().equals(cashflow.getAccount())) return false;
		if(getAmount()!=cashflow.getAmount()) return false;
		if(!getDate().equals(cashflow.getDate())) return false;
		if(getType()!=cashflow.getType()) return false;
		
		return true;
	}	
	
	public String toString()
	{
		return "Cashflow["
				//+"account="+account
				+"date="+date
				+",amount="+amount
				+",type="+(type==CREDIT?"Credit":"Debit")
				+"]";
	}
	
	
}


package net.tplusplus.drools.speedtest.facts;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.rules.runner.rao.Fact;


public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
{
	private long accountNo;
	private Account account;
	
	public UpdatingAccount(long accountNo, Account account)
	{
		this.accountNo = accountNo;
		this.account = account;
	}

	public long getAccountNo()
	{
		return accountNo;
	}

	public void setAccountNo(long accountNo)
	{
		this.accountNo = accountNo;
	}

	public Account getAccount()
	{
		return account;
	}

	public void setAccount(Account account)
	{
		this.account = account;
	}
	
	/**
	 *  This method enables the Collections api to sort the 
	 *  UpdatingAccount by account no.
	 */	
	public int compareTo(UpdatingAccount updatingAccount)
	{
		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
		
		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
	}
	
	/**
	 *  This method enables the comparison of UpdatingAccount objects
	 */	
	@Override
	public boolean equals(Object obj) 
	{
		if(obj==null || !(obj instanceof UpdatingAccount))
		{
			return false;
		}
		
		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
		
		return (getAccountNo()==updatingAccount.getAccountNo());	
	}		
}


package net.tplusplus.test.drools.speedtest.data;

import java.util.ArrayList;
import java.util.Date;
import java.util.List;

import net.tplusplus.drools.speedtest.bank.Account;
import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
import net.tplusplus.drools.speedtest.facts.Cashflow;
import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.utils.SimpleDate;


public class TestData
{
	private static Date startDate;
	private static Date endDate;
	
	private static List<Account> accounts;
	private static List<UpdatingAccount> updatingAccounts;
	private static List<Cashflow> cashflows;
	private static List<AccountingPeriod> accountingPeriods;
	
	static
	{
		try
		{
			startDate = new SimpleDate("01/01/2007");
			endDate = new SimpleDate("31/12/2007");
		}
		catch(Exception e){}
	}
	
	private static List<Account> getAllAccounts()
	{
		if(accounts==null)
		{
			accounts = new ArrayList<Account>();
		
			accounts.add(new Account(1));
		}
		
		return accounts;
	}
	
	public static List<UpdatingAccount> getAllUpdatingAccounts()
	{
		if(updatingAccounts==null)
		{
			updatingAccounts = new ArrayList<UpdatingAccount>();
			
			for(Account account : getAllAccounts())
			{
				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
			}
		}
		
		return updatingAccounts;
	}
	
	public static List<Cashflow> getAllCashflows()
	throws Exception
	{
		if(cashflows==null)
		{
			cashflows = new ArrayList<Cashflow>();		
				
			for(Date date = startDate; !date.after(endDate);)
			{
				int adj = 0;
				
				for(Account acct : getAllAccounts())
				{
					adj++;
					
					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
					int[] debits = new int[]{ 200, 50, 50, 30};
					
					for(int credit : credits)
					{
						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
						cashflows.add(c);
					}
					
					for(int debit : debits)
					{
						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
						cashflows.add(c);
					}	
				}
				
				long newDate = date.getTime() + 24l*60l*60l*1000l;
				date = new Date(newDate);
			}
		}
		
		return cashflows;
	}
	
	public static List<AccountingPeriod> getAccountingPeriods()
	throws Exception
	{
		if(accountingPeriods==null)
		{
			accountingPeriods = new ArrayList<AccountingPeriod>();
			
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
		}
		
		return accountingPeriods;
	}
	
	public static List<Fact> getAllFacts()
	throws Exception
	{
		List<Fact> facts = new ArrayList<Fact>();
		
		facts.addAll(getAccountingPeriods());
		facts.addAll(getAllCashflows());
		facts.addAll(getAllUpdatingAccounts());
		
		return facts;		
	}
	
	public static void resetAccounts()
	{
		for(Account account : getAllAccounts())
		{
			account.setBalance(0);
		}
	}
}


package net.tplusplus.test.drools.speedtest;

import java.util.List;

import org.drools.RuleBase;
import org.drools.WorkingMemory;

import net.tplusplus.rules.runner.RuleRunner;
import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.test.drools.speedtest.data.TestData;
import net.tplusplus.utils.TimedResults;


public class SpeedTest1
{
	public static void main(String[] args)
	throws Exception
	{
		int iterations = 1000;
		
		//runTest1(iterations);
		runTest2(iterations);
		runTest3(iterations);
		runTest4(iterations);
		runTest5(iterations);
		runTest6(iterations);

	}
	
	public static void runTest1(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 1 - NO CACHING");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			runner.createRuleBase();
			runner.createWorkingMemory();
			runner.runRules();
			
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest2(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		RuleBase cachedRuleBase = null;
		
		for(int i=0;i<iterations;i++)
		{
			System.out.println(i);
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedRuleBase==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setRuleBase(cachedRuleBase);
				runner.createWorkingMemory();
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest3(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest4(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}	
	
	public static void runTest5(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
	
	public static void runTest6(int iterations)
	throws Exception
	{		
		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
		TimedResults results = new TimedResults();
		
		RuleRunner runner = new RuleRunner();
		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
		
		List<Fact> allFacts = TestData.getAllFacts();
		runner.addFacts(allFacts);

		WorkingMemory cachedWorkingMemory = null;
		
		for(int i=0;i<iterations;i++)
		{
			TestData.resetAccounts();
			
			long starttime = System.currentTimeMillis();
			
			if(cachedWorkingMemory==null)
			{
				runner.createWorkingMemory();
			}
			else
			{
				runner.setWorkingMemory(cachedWorkingMemory);
			}
			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
			
			results.addTime(timetaken);
		}
		
		System.out.println("Iterations: "+iterations);
		System.out.println("Number of facts: "+runner.getFacts().size());
		System.out.println("fastest time: "+results.getFastest()+" (ms)");
		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
		System.out.println("average time: "+results.getAverage()+" (ms)");
	}
}


package net.tplusplus.rules.runner;

import java.io.File;
import java.io.FileReader;
import java.net.URL;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import java.util.Iterator;

import net.tplusplus.rules.runner.rao.Fact;
import net.tplusplus.rules.runner.rao.Global;

import org.drools.FactHandle;
import org.drools.RuleBase;
import org.drools.RuleBaseFactory;
import org.drools.WorkingMemory;
import org.drools.compiler.PackageBuilder;
import org.drools.spi.ActivationGroup;
import org.drools.spi.AgendaGroup;


public class RuleRunner
{
	private RuleBase ruleBase;
	private WorkingMemory workingMemory;
	
	private List<String> rules;
	private List<Global> globals;
	private List<Fact> facts;
	
	public RuleRunner()
	{
		rules = new ArrayList<String>();
		globals = new ArrayList<Global>();
		facts = new ArrayList<Fact>();	
	}
	
	public void addRules(String... rules)
	{
		this.rules.addAll(Arrays.asList(rules));
	}
	
	public void addGlobals(Global... globals)
	{
		this.globals.addAll(Arrays.asList(globals));
	}
	
	public void addFacts(Fact... facts)
	{
		this.facts.addAll(Arrays.asList(facts));
	}
	
	public void addFacts(List<? extends Fact> facts)
	{
		this.facts.addAll(facts);
	}	
	
	public List<Fact> getFacts()
	{
		return this.facts;
	}
	
	public void clearFacts()
	{
		this.facts = new ArrayList<Fact>();
	}
	
	public RuleBase createRuleBase()
	throws Exception
	{
		if(rules==null)
		{
			throw new Exception("No rules provided for Engine");
		}
		
		ruleBase = RuleBaseFactory.newRuleBase();
		PackageBuilder builder = new PackageBuilder();		
		
		for(String ruleFile : rules)
		{
			URL resource = this.getClass().getResource(ruleFile);
			
			if(resource==null)
			{
				System.err.println("Could not find resource: "+ruleFile);
				continue;
			}

			File file = new File(this.getClass().getResource(ruleFile).getPath());
			if(!file.exists())
			{
				System.err.println("Could not find rule file: "+file.getPath());
				continue;
			}
			
			builder.addPackageFromDrl(new FileReader(file.getPath()));
		}
		
		org.drools.rule.Package pkg = builder.getPackage();		
		ruleBase.addPackage(pkg);	
		
		return ruleBase;
	}
	
	public void setRuleBase(RuleBase ruleBase)
	{
		this.ruleBase = ruleBase;
	}
	
	public RuleBase getRuleBase()
	{
		return ruleBase;
	}
	
	public WorkingMemory createWorkingMemory()
	throws Exception
	{
		if(ruleBase==null)
		{
			createRuleBase();
		}
		
		workingMemory = null;
		
		workingMemory = ruleBase.newStatefulSession();
		
		return workingMemory;
	}
	
	public void setWorkingMemory(WorkingMemory workingMemory)
	{
		this.workingMemory = workingMemory;
	}
	
	public WorkingMemory getWorkingMemory()
	{
		return workingMemory;
	}
	
	public void runRules()
	throws Exception
	{		
		if(workingMemory==null)
		{
			throw new Exception("No workingMemory created for Engine");
		}
		
		System.gc();
		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
		
		
		if(globals!=null)
		{
			for(Global global : globals)
			{
				workingMemory.setGlobal(global.getName(), global.getValue());
			}
		}

		if(facts!=null)
		{
			for(Fact fact : facts)
			{
				workingMemory.insert(fact);
			}
		}

		workingMemory.fireAllRules();
	}
}


package net.tplusplus.rules.runner.rao;

public interface Fact
{

}


package net.tplusplus.rules.runner.rao;

public class Global
{
	private String name;
	private Object value;
	
	public Global(String name, Object value)
	{
		this.name = name;
		this.value = value;
	}

	public String getName()
	{
		return name;
	}

	public void setName(String name)
	{
		this.name = name;
	}

	public Object getValue()
	{
		return value;
	}

	public void setValue(Object value)
	{
		this.value = value;
	}
	
	public String toString()
	{
		return "Global["
				+"name="+name
				+"value="+value
				+"]";
	}
}


package net.tplusplus.utils;

import java.text.SimpleDateFormat;
import java.util.Date;

public class SimpleDate extends Date
{
	public static final long serialVersionUID = 1;
	
	public SimpleDate(String datestr)
	throws Exception
	{
		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
		this.setTime(format.parse(datestr).getTime());
	}
}


package net.tplusplus.utils;

import java.util.HashMap;
import java.util.Map;

public class TimedResults
{
	private long fastest = -1;
	private long slowest = -1;
	
	private Map<Long,Long> results = new HashMap<Long,Long>();
	
	public TimedResults()
	{
	}
	
	public void addTime(long time)
	throws Exception
	{
		if(time < 0)
		{
			throw new Exception("Invalid Time");
		}
		
		Long key = System.currentTimeMillis();
		results.put(key,time);
		
		if(fastest==-1 || fastest>time) fastest=time;
		if(slowest==-1 || slowest<time) slowest=time;
	}
	
	public Map<Long,Long> getResults()
	{
		return results;
	}
	
	public long getFastest()
	{
		return fastest;
	}
	
	public long getSlowest()
	{
		return slowest;
	}
	
	public long getAverage()
	{
		long time = 0;
		
		for(Long timetaken : results.values())
		{
			time += timetaken;
		}
		
		return time / results.size();
	}
}




> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1303
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1303
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook running Leopard, Eclipse Europa, Java 1.5 (Mac OSX), Drools 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:02:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9926094.1193655721557.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis updated JBAS-4845:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter7 - Quick_Tutorial_to_Setup_a_Clustered_Web_Application.odt)

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:02:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8744550.1193655721752.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis reassigned JBAS-4845:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:13:01 2007
From: jira-events at lists.jboss.org (Stelios Koussouris (JIRA))
Date: Mon, 29 Oct 2007 07:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4829) TECH REVIEW:
 Getting Started Guide - Chapter 5. Using Seam
In-Reply-To: <24288348.1192165535542.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22833540.1193656381593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4829?page=all ]

Stelios Koussouris resolved JBAS-4829.
--------------------------------------

    Resolution: Done

Completed

> TECH REVIEW: Getting Started Guide - Chapter 5. Using Seam
> ----------------------------------------------------------
>
>                 Key: JBAS-4829
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4829
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>         Assigned To: Stelios Koussouris
>         Attachments: JBAS-422-Getting-Started-Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt, JBASS-422-Getting_Started_Guide-Chapter-5.odt
>
>
> Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:20:01 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Mon, 29 Oct 2007 07:20:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAOP-107) The different types
 of classloader integration for AOP belong in the related release not
 jboss-head
Message-ID: <20442553.1193656801550.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan updated JBAOP-107:
-----------------------------

    Priority: Major  (was: Minor)

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:33:14 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 29 Oct 2007 07:33:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBXB-114) Reusing a model
	group
In-Reply-To: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22124747.1193657594080.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBXB-114?page=comments#action_12384780 ] 
            
Alexey Loubyansky commented on JBXB-114:
----------------------------------------

There seems to be a missing if statement

   @XmlElement(type=JBossEnvironmentRefsGroupMetaData.class)
   public void setJndiEnvironmentRefsGroup(Environment env)
   {
      if (env == null)
         throw new IllegalArgumentException("Null jndiEnvironmentRefsGroup");   // line 265


> Reusing a model group
> ---------------------
>
>                 Key: JBXB-114
>                 URL: http://jira.jboss.com/jira/browse/JBXB-114
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>            Reporter: Scott M Stark
>             Fix For: JBossXB-2.0.0.CR5
>
>
> We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:
> <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
>  exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
>  security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
>  resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
>  cluster-config?, method-attributes?, depends*,
>  ior-security-config?, port-component*,  ejb-timeout-identity?)>
> See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:
> org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
> 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
> ...
> Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
> 	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
> 	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
> 	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
> 	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
> 	... 41 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:33:14 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:33:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4915) service-ref merge
	looses data
Message-ID: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>

service-ref merge looses data
-----------------------------

                 Key: JBAS-4915
                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:36:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26989598.1193657761434.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4915?page=all ]

Thomas Diesler updated JBAS-4915:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
In the following scenario only jboss-client.xml contains <service-ref> elements

<application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
  
  <display-name>TestEndpointService</display-name>
  
</application-client>

<jboss-client>
  <jndi-name>jbossws-client</jndi-name>
  
  <!-- 
  @WebServiceRef(name = "Service1")
  -->
  <service-ref>
    <service-ref-name>Service1</service-ref-name>
    <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
    <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Service2")
  -->
  <service-ref>
    <service-ref-name>Service2</service-ref-name>
    <config-name>Custom Client</config-name>
    <config-file>META-INF/jbossws-client-config.xml</config-file>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Service3")
  -->
  <service-ref>
    <service-ref-name>Service3</service-ref-name>
    <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
    <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Service4")
  -->
  <service-ref>
    <service-ref-name>Service4</service-ref-name>
    <port-component-ref>
      <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
      <config-name>Custom Client</config-name>
      <config-file>META-INF/jbossws-client-config.xml</config-file>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Port1", type = TestEndpoint.class)
  -->
  <service-ref>
    <service-ref-name>Port1</service-ref-name>
    <port-component-ref>
      <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
      <config-name>Custom Client</config-name>
      <config-file>META-INF/jbossws-client-config.xml</config-file>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Port2")
  -->
  <service-ref>
    <service-ref-name>Port2</service-ref-name>
    <port-component-ref>
      <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
      <config-name>Custom Client</config-name>
      <config-file>META-INF/jbossws-client-config.xml</config-file>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
  <!-- 
  @WebServiceRef(name = "Port3")
  -->
  <service-ref>
    <service-ref-name>Port3</service-ref-name>
    <port-component-ref>
      <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
      <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
      <stub-property>
        <prop-name>javax.xml.ws.security.auth.username</prop-name>
        <prop-value>kermit</prop-value>
      </stub-property>
      <stub-property>
        <prop-name>javax.xml.ws.security.auth.password</prop-name>
        <prop-value>thefrog</prop-value>
      </stub-property>
    </port-component-ref>
    <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
  </service-ref>
  
</jboss-client>

These are lost by

   public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
         ServiceReferencesMetaData overriden,
         String overridenFile, String overrideFile)
   {
      if (override == null && overriden == null)
         return null;

      JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
      JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
      return merged;
   }

because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:40:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:40:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22507513.1193658001420.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4915?page=comments#action_12384782 ] 
            
Thomas Diesler commented on JBAS-4915:
--------------------------------------

[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase one-test

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
    [junit] javax.naming.NamingException: Could not dereference object [Root exception is org.jboss.ws.WSException: Cannot create service]
    [junit]     at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1337)
    [junit]     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:765)
    [junit]     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
    [junit]     at org.jboss.ejb3.JndiUtil.lookup(JndiUtil.java:44)
    [junit]     at org.jboss.injection.JndiFieldInjector.lookup(JndiFieldInjector.java:82)
    [junit]     at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:101)
    [junit]     at org.jboss.ejb3.client.ClientContainer.<init>(ClientContainer.java:120)
    [junit]     at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:76)
    [junit]     at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:179)
    [junit]     at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at junit.framework.TestCase.runTest(TestCase.java:154)
    [junit]     at junit.framework.TestCase.runBare(TestCase.java:127)
    [junit]     at junit.framework.TestResult$1.protect(TestResult.java:106)
    [junit]     at junit.framework.TestResult.runProtected(TestResult.java:124)
    [junit]     at junit.framework.TestResult.run(TestResult.java:109)
    [junit]     at junit.framework.TestCase.run(TestCase.java:118)
    [junit]     at junit.framework.TestSuite.runTest(TestSuite.java:208)
    [junit]     at junit.framework.TestSuite.run(TestSuite.java:203)
    [junit]     at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
    [junit]     at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
    [junit]     at junit.framework.TestResult.runProtected(TestResult.java:124)
    [junit]     at junit.extensions.TestSetup.run(TestSetup.java:23)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672)
    [junit]     at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567)
    [junit] Caused by: org.jboss.ws.WSException: Cannot create service
    [junit]     at org.jboss.ws.WSException.rethrow(WSException.java:60)
    [junit]     at org.jboss.ws.core.jaxws.client.ServiceObjectFactoryJAXWS.getObjectInstance(ServiceObjectFactoryJAXWS.java:201)
    [junit]     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    [junit]     at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1312)
    [junit]     at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1329)
    [junit]     ... 28 more
    [junit] Caused by: java.lang.IllegalArgumentException: Cannot create generic javax.xml.ws.Service without wsdlLocation: org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointClientOne/port4
    [junit]     at org.jboss.ws.core.jaxws.client.ServiceObjectFactoryJAXWS.getObjectInstance(ServiceObjectFactoryJAXWS.java:139)
    [junit]     ... 31 more
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 1,399.484 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED


> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:42:03 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 07:42:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <330287.1193658123007.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4915?page=all ]

Thomas Diesler reassigned JBAS-4915:
------------------------------------

    Assignee: Scott M Stark

> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:49:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 07:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-1075) Ensure Session
 Beans with Incomplete 2.1 View Fail Deployment
In-Reply-To: <14148182.1192656903357.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7651061.1193658541418.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1075?page=all ]

Carlo de Wolf reopened EJBTHREE-1075:
-------------------------------------

             
Code does not work with assertions enabled.

> Ensure Session Beans with Incomplete 2.1 View Fail Deployment
> -------------------------------------------------------------
>
>                 Key: EJBTHREE-1075
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1075
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: AS 5.0.0.Beta3
>
>
> For an EJB 2.1 view to be realized, ensure both Home/LocalHome and Remote/Local interfaces are provided.  If only one is, an exception should be thrown on deployment with descriptive error message to the bean provider.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 07:57:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 29 Oct 2007 07:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBXB-114) Reusing a model
	group
In-Reply-To: <17045443.1193457121388.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6779958.1193659021460.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBXB-114?page=comments#action_12384788 ] 
            
Alexey Loubyansky commented on JBXB-114:
----------------------------------------

It's because of this change

 - - - @XmlElement(type=JBossEnvironmentRefsGroupMetaData.class)
-- - - public- void- setJndiEnvironmentRefsGroup(Environment- jndiEnvironmentRefsGroup)
+- - - public- void- setJndiEnvironmentRefsGroup(Environment- env)
- - - {
-- - - - - - if(this.jndiEnvironmentRefsGroup- !=- null)
-- - - - - - - - - throw- new- IllegalArgumentException("jndiEnvironmentRefsGroup- already- set");
-- - - - - - this.jndiEnvironmentRefsGroup- =- (JBossEnvironmentRefsGroupMetaData)- jndiEnvironmentRefsGroup;
+- - - - - - if- (env- ==- null)
+- - - - - - - - - throw- new- IllegalArgumentException("Null- jndiEnvironmentRefsGroup");
+- - - - - - JBossEnvironmentRefsGroupMetaData- jenv- =- (JBossEnvironmentRefsGroupMetaData)- env;
+- - - - - - if(jndiEnvironmentRefsGroup- !=- null)
+- - - - - - - - - jndiEnvironmentRefsGroup.merge(jenv,- null,- null,- "jboss.xml",- "ejb-jar.xml",- false);
+- - - - - - else
+- - - - - - - - - jndiEnvironmentRefsGroup- =- jenv;
- - - } 

> Reusing a model group
> ---------------------
>
>                 Key: JBXB-114
>                 URL: http://jira.jboss.com/jira/browse/JBXB-114
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>            Reporter: Scott M Stark
>             Fix For: JBossXB-2.0.0.CR5
>
>
> We have an issue with mapping legacy schemas onto the jboss_5_0.xsd environment model group. The jboss_4_2.dtd specifies elements that are in the environment model group, but there are elements like security-identity interleaved with this:
> <!ELEMENT session (ejb-name , jndi-name? , local-jndi-name?, call-by-value?,
>  exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
>  security-proxy? , ejb-ref* ,  ejb-local-ref* , service-ref*, security-identity? ,
>  resource-ref* , resource-env-ref*, message-destination-ref* , clustered? ,
>  cluster-config?, method-attributes?, depends*,
>  ior-security-config?, port-component*,  ejb-timeout-identity?)>
> See the org.jboss.test.metadata.ejb.JBoss42UnitTestCase.testExcludedMethods that parses a conforming jboss_4_2.dtd document, but fails to parse with:
> org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/JBossHead/projects/metadata/trunk/target/eclipse-classes/org/jboss/test/metadata/ejb/JBoss42_testExcludedMethods.xml at 46,34
> 	at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:194)
> ...
> Caused by: java.lang.IllegalArgumentException: jndiEnvironmentRefsGroup already set
> 	at org.jboss.metadata.ejb.jboss.JBossEnterpriseBeanMetaData.setJndiEnvironmentRefsGroup(JBossEnterpriseBeanMetaData.java:265)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
> 	at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108)
> 	at org.jboss.beans.info.plugins.AbstractPropertyInfo.set(AbstractPropertyInfo.java:182)
> 	at org.jboss.xb.spi.AbstractBeanAdapter.set(AbstractBeanAdapter.java:95)
> 	at org.jboss.xb.builder.runtime.PropertyHandler.handle(PropertyHandler.java:61)
> 	... 41 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 08:22:01 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 08:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1057)
 SessionContext.getEJBObject
 should throw an IllegalStateException if there is no remote interface
 defined
In-Reply-To: <22903232.1191569943221.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29262820.1193660521874.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1057?page=all ]

Carlo de Wolf updated EJBTHREE-1057:
------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
                       (was: HEAD)

> SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1057
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. 
> (Similar for getEJBLocalObject.)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:03:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2451904.1193662981687.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis updated JBAS-4845:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt

Attach reviewed file.

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:05:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:05:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4845) TECH REVIEW: Server
 Configuration Guide - Chapter7 - Messaging on JBoss
In-Reply-To: <1513115.1192170303777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30718435.1193663101503.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4845?page=all ]

Dimitris Andreadis resolved JBAS-4845.
--------------------------------------

    Resolution: Done

> TECH REVIEW: Server Configuration Guide - Chapter7 - Messaging on JBoss
> -----------------------------------------------------------------------
>
>                 Key: JBAS-4845
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4845
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter7-Messaging_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:11:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
In-Reply-To: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32672979.1193663462117.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4881?page=all ]

Dimitris Andreadis updated JBAS-4881:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4881
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:11:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4881) TECH REVIEW: Server
 Configuration Guide - Chapter8 - Security on JBoss
In-Reply-To: <9426468.1192790943405.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26845746.1193663462313.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4881?page=all ]

Dimitris Andreadis resolved JBAS-4881.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done
         Assignee: Dimitris Andreadis

Reviewed with tiny changes.

> TECH REVIEW: Server Configuration Guide - Chapter8 - Security on JBoss
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4881
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4881
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter8-Security_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:13:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7595114.1193663581468.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

Dimitris Andreadis reassigned JBAS-4883:
----------------------------------------

    Assignee: Dimitris Andreadis

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:15:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 09:15:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
Message-ID: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>

Invalid content was found starting with element 'env-entry'
-----------------------------------------------------------

                 Key: JBAS-4916
                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler
             Fix For:  JBossAS-5.0.0.Beta3




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:15:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 09:15:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9590157.1193663702846.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4916?page=all ]

Thomas Diesler updated JBAS-4916:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test

<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
  version="2.4">

  <servlet>
    <servlet-name>TestService</servlet-name>
    <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
  </servlet>

  <servlet-mapping>
    <servlet-name>TestService</servlet-name>
    <url-pattern>/*</url-pattern>
  </servlet-mapping>

  <env-entry>
   <env-entry-name>jsr109/entry1</env-entry-name>
   <env-entry-type>java.lang.String</env-entry-type>
   <env-entry-value>web</env-entry-value>
  </env-entry>
  
  <env-entry>
   <env-entry-name>jsr109/entry2</env-entry-name>
   <env-entry-type>java.lang.Integer</env-entry-type>
   <env-entry-value>8</env-entry-value>
  </env-entry>

</web-app>

Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
        at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
        at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

         Assignee: Alexey Loubyansky

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:17:02 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 09:17:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-761)
 SessionContext.getCallerPrincipal() throws NullPointerException in embedded
 container
In-Reply-To: <10842764.1161790961554.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1472943.1193663822577.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-761?page=all ]

Carlo de Wolf reassigned EJBTHREE-761:
--------------------------------------

    Assignee: Carlo de Wolf

> SessionContext.getCallerPrincipal() throws NullPointerException in embedded container
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-761
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-761
>             Project: EJB 3.0
>          Issue Type: Patch
>          Components: Security
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: John Gilbert
>         Assigned To: Carlo de Wolf
>
> The exception happens in org.jboss.security.plugins.JaasSecurityManager.getPrincipal(Principal principal) when it is synchronized on domainCache. domainCache is null because org.jboss.ejb3.embedded.JaasSecurityManagerService does not initialize it.
> There are two possible fixes:
> 1 - org.jboss.security.plugins.JaasSecurityManager should check for null first like it does in most of the methods.
> 2 - have org.jboss.ejb3.embedded.JaasSecurityManagerService initialize the cache with a mock cache policy. This is what I did to fix mine.
> 	private static JaasSecurityManager getSecurityManager(String name) {
>                        ...
> 			manager = new JaasSecurityManager(name,
> 					new SecurityAssociationHandler());
> 			manager.setCachePolicy(new MockCachePolicy());               //MockCachePolicy is just a noop impl
>                         ...
> 	}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:17:03 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Mon, 29 Oct 2007 09:17:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-761)
 SessionContext.getCallerPrincipal() throws NullPointerException in embedded
 container
In-Reply-To: <10842764.1161790961554.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4268660.1193663823024.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-761?page=all ]

Carlo de Wolf resolved EJBTHREE-761.
------------------------------------

    Resolution: Duplicate Issue

> SessionContext.getCallerPrincipal() throws NullPointerException in embedded container
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-761
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-761
>             Project: EJB 3.0
>          Issue Type: Patch
>          Components: Security
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: John Gilbert
>         Assigned To: Carlo de Wolf
>
> The exception happens in org.jboss.security.plugins.JaasSecurityManager.getPrincipal(Principal principal) when it is synchronized on domainCache. domainCache is null because org.jboss.ejb3.embedded.JaasSecurityManagerService does not initialize it.
> There are two possible fixes:
> 1 - org.jboss.security.plugins.JaasSecurityManager should check for null first like it does in most of the methods.
> 2 - have org.jboss.ejb3.embedded.JaasSecurityManagerService initialize the cache with a mock cache policy. This is what I did to fix mine.
> 	private static JaasSecurityManager getSecurityManager(String name) {
>                        ...
> 			manager = new JaasSecurityManager(name,
> 					new SecurityAssociationHandler());
> 			manager.setCachePolicy(new MockCachePolicy());               //MockCachePolicy is just a noop impl
>                         ...
> 	}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:22:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16398900.1193664121563.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

Dimitris Andreadis updated JBAS-4883:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:22:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:22:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4883) TECH REVIEW: Server
 Configuration Guide - Chapter10 - Additional Services
In-Reply-To: <21141123.1192791304115.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3142064.1193664121713.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4883?page=all ]

Dimitris Andreadis resolved JBAS-4883.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done

Done.

> TECH REVIEW: Server Configuration Guide - Chapter10 - Additional Services
> -------------------------------------------------------------------------
>
>                 Key: JBAS-4883
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4883
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter10-Additional_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:33:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 09:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4882) TECH REVIEW: Server
 Configuration Guide - Chapter9 - Web Services
In-Reply-To: <11998244.1192791183470.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2785602.1193664781917.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4882?page=all ]

Dimitris Andreadis reassigned JBAS-4882:
----------------------------------------

    Assignee: Thomas Diesler

Thomas, can you or someone from the ws team review this document? It probably needs updating to reflect the switch to jbossws-2.0.x.

> TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services
> -----------------------------------------------------------------
>
>                 Key: JBAS-4882
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4882
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Thomas Diesler
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:41:02 2007
From: jira-events at lists.jboss.org (Brendan Sibre (JIRA))
Date: Mon, 29 Oct 2007 09:41:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1127) Use SSL
 certificate for client authentication
Message-ID: <15518406.1193665262950.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use SSL certificate for client authentication
---------------------------------------------

                 Key: JBMESSAGING-1127
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1127
             Project: JBoss Messaging
          Issue Type: Feature Request
          Components: JMS Remoting, JMS Security
    Affects Versions: 1.4.0.GA
         Environment: JBAS 4.2.1 on Solaris 9 and 10, Sun JVM 1.5.0
            Reporter: Brendan Sibre
         Assigned To: Tim Fox


Clients connect to JBM using the sslbisocket connector.  They should be able to use a client certificate to authenticate them via my custom loginmodule (which has been tested and works with EJBs, Tomcat, etc).

Use the principal created by the SSL connection for the getConnection() so that I do not need to pass a username and password.  It seems that the callback handler used by the JBoss Messaging and the remoting SSLBisocket connector needs to be able to handle an X509Callback.  This probably means that
it will need to be a HandshakeCompletedListener on the remoting connector.

Ideally, this method of authentication would be configured with the connector and then JBoss Messaging would use a CallerIdentityLoginModule to
accept the Subject that already exists so that JBoss Messaging will continue to work with EJBs (JmsXA) etc.

Forum posts include links to other potentially related JIRA issues.  Hopefully JBoss Messaging can address this issue as it fits in the junction between
JBM and remoting.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 09:46:02 2007
From: jira-events at lists.jboss.org (Martin Putz (JIRA))
Date: Mon, 29 Oct 2007 09:46:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1774) CMS metadata is
 lost on export
Message-ID: <33128493.1193665562021.JavaMail.jira@cloud.prod.atl2.jboss.com>

CMS metadata is lost on export
------------------------------

                 Key: JBPORTAL-1774
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1774
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal CMS
    Affects Versions: 2.6.2 Final, 2.4.1 SP1
            Reporter: Martin Putz
         Assigned To: Sohil Shah


CMS metadata, such as title or description, is not being exported. If you do an export/import cycle of CMS data, you will therefore lose information.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:06:01 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Mon, 29 Oct 2007 10:06:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1306) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <26662351.1193583481586.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9651084.1193666761840.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1306?page=all ]

Edson Tirelli resolved JBRULES-1306.
------------------------------------

    Fix Version/s: 4.0.3
       Resolution: Rejected
         Assignee: Edson Tirelli

John,

I checked your test case and apparently the only problem is that you are not calling dispose() on the stateful session after using it (http://downloads.jboss.com/drools/docs/4.0.3.15993.GA/html/index.html section 2.5.5). Remember that all stateful sessions must be disposed after use:

public class RuleRunner
{
        ...
	private StatefulSession workingMemory;

       ...
    public void dispose() {
        workingMemory.dispose();
    }
      ...	
}

	public static void runTest2(int iterations)
	throws Exception
	{		
         ...			
			runner.runRules();
			long endtime = System.currentTimeMillis();
			long timetaken = endtime - starttime;
            
            runner.dispose();
            ...
	}
	
After adding the dispose() call, I get stable and consistent results (snippet bellow):

...
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
409
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
410
Heap/Used/Free Memory: 82Mb / 9Mb / 73Mb
411
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
412
Heap/Used/Free Memory: 82Mb / 8Mb / 74Mb
413
...

Can you double check and reopen the issue in case you find any other problem? thanks.

Edson

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1306
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1306
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.3
>
>         Attachments: Archive.zip
>
>
> The RuleBase is cached.  A set of approximately 5000 facts are inserted.  As the facts are processed, they are retracted.  Ultimately all facts are retracted.
> The rulebase is then re-acquired and the same set of facts are inserted and processed as before.  For the First 100 iterations the jvm free memory (heap) remains consistent, between 100 and 200 iterations the free memory drops by about 1/5th.  After iteration 200 the free memory drops to a constant value, at about 1/20th the original heap size.  Iteration 215 consistently fails with OutOfMemory in both version 4.0.3 and 4.0.2.
> The rules and code are listed below and attached as eclipse projects.
> package net.tplusplus.drools.speedtest.rules.test1;
> import net.tplusplus.drools.speedtest.facts.*;
> import net.tplusplus.drools.speedtest.bank.*;
> rule "Test 01 - Credit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.CREDIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Credit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Debit Cashflow"
> 	salience 100
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		$cashflow : Cashflow( $account : account, $date : date <= $end && date >= $start, $amount : amount, type==Cashflow.DEBIT )
> 		not AccountingPeriod( start < $start)
> 	then 
> 		//System.out.println("Debit "+$amount);
> 		$account.setBalance($account.getBalance()+$amount);
> 		retract($cashflow);
> end
> rule "Test 01 - Print Balance"
> 	salience 90
> 	when
> 		AccountingPeriod( $start : start, $end : end )
> 		UpdatingAccount( $accountNo : accountNo, $account : account)
> 		not AccountingPeriod( start < $start)
> 	then
> 		//System.out.print("Period End: "+$end);
> 		//System.out.println(" - Account "+$accountNo+" - balance: "+$account.getBalance());
> end
> rule "Test 01 - Retract Period"
> 	salience 80
> 	when
> 		$accountingPeriod : AccountingPeriod( $start : start, $end : end )
> 		not AccountingPeriod( start < $start)
> 	then
> 		retract($accountingPeriod);
> end
> rule "Test 01 - Retract Remaining AccountingPeriods"
> 	salience 1
> 	when
> 		$fact : AccountingPeriod( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining Cashflows"
> 	salience 1
> 	when
> 		$fact : Cashflow( )
> 	then
> 		retract($fact);
> end
> rule "Test 01 - Retract Remaining UpdatingAccounts"
> 	salience 1
> 	when
> 		$fact : UpdatingAccount( )
> 	then
> 		retract($fact);
> end
> The code is as follows:
> package net.tplusplus.drools.speedtest.bank;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> /**
>  * This class provides a simple Bank Account.
>  * 
>  * @author DunningJ
>  *
>  */
> public class Account
> {
> 	private long accountNo;
> 	private double balance=0;
> 	
> 	public Account(){};
> 	
> 	public Account(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public double getBalance()
> 	{
> 		return balance;
> 	}
> 	public void setBalance(double balance)
> 	{
> 		this.balance = balance;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Account objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Account account = (Account) obj;
> 		
> 		return (getAccountNo()==account.getAccountNo());
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Account[" 
> 				+"accountNo="+accountNo
> 				+",balance="+balance
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.rules.runner.rao.Fact;
> /**
>  * Each bank transaction must fall within an AccountingPeriod - which
>  * is normally a quarter.  A separate AccountingPeriod fact is passed to the
>  * Drools engine for each accounting period for which we are processing 
>  * calculations.
>  * 
>  * @author DunningJ
>  *
>  */
> public class AccountingPeriod implements Fact, Comparable<AccountingPeriod>
> {
> 	private Date start;
> 	private long startl;
> 	private Long startL;
> 	private Date end;
> 	private long endl;
> 	private Long endL;
> 	
> 	public AccountingPeriod(){}
> 	
> 	public AccountingPeriod(Date start, Date end)
> 	{
> 		this.start = start;
> 		this.startl = start.getTime();
> 		this.startL = start.getTime();
> 		this.end = end;
> 		this.endl = end.getTime();
> 		this.endL = end.getTime();
> 	}
> 	public Date getStart()
> 	{
> 		return start;
> 	}
> 	
> 	public long getStartl()
> 	{
> 		return startl;
> 	}
> 	
> 	public long getStartL()
> 	{
> 		return startL;
> 	}
> 	public void setStart(Date start)
> 	{
> 		this.start = start;
> 	}
> 	public Date getEnd()
> 	{
> 		return end;
> 	}
> 	public long getEndl()
> 	{
> 		return endl;
> 	}
> 	
> 	public Long getEndL()
> 	{
> 		return endL;
> 	}
> 	public void setEnd(Date end)
> 	{
> 		this.end = end;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  AccountingPeriod by period start date.
> 	 */
> 	public int compareTo(AccountingPeriod accountingPeriod)
> 	{
> 		if(this.start.after(accountingPeriod.getStart()))
> 		{
> 			return 1;
> 		}
> 		if(this.start.before(accountingPeriod.getStart()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}	
> 	
> 	/**
> 	 *  This method enables the comparison of AccountingPeriod objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof AccountingPeriod))
> 		{
> 			return false;
> 		}
> 		
> 		AccountingPeriod ap = (AccountingPeriod) obj;
> 		
> 		return getStart().equals(ap.getStart());
> 	}
> 	public String toString()
> 	{
> 		return "AccountingPeriod[" 
> 				+"start="+start
> 				+",end="+end
> 				+"]";
> 	}
> }
> package net.tplusplus.drools.speedtest.facts;
> import java.util.Date;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class Cashflow implements Fact, Comparable<Cashflow>
> {	
> 	public static final int CREDIT = 0;
> 	public static final int DEBIT = 1;
> 	
> 	private Date date;
> 	private long datel;
> 	private Long dateL;
> 	private double amount;
> 	private int type;
> 	private Account account;
> 	
> 	public Cashflow()
> 	{
> 	}
> 	
> 	public Cashflow(Date date, double amount, int type, Account account)
> 	{
> 		this();
> 		
> 		this.date = date;
> 		this.datel= date.getTime();
> 		this.dateL = date.getTime();
> 		this.amount = amount;
> 		this.type = type;
> 		this.account = account;
> 	}
> 	public Date getDate()
> 	{
> 		return date;
> 	}
> 	
> 	public void setDate(Date date)
> 	{
> 		this.date = date;
> 	}
> 	
> 	public double getAmount()
> 	{
> 		return amount;
> 	}
> 	
> 	public void setAmount(double amount)
> 	{
> 		this.amount = amount;
> 	}
> 	
> 	public int getType()
> 	{
> 		return type;
> 	}
> 	public void setType(int type)
> 	{
> 		this.type = type;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	public long getDatel()
> 	{
> 		return datel;
> 	}
> 	
> 	public long getDateL()
> 	{
> 		return dateL;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  Cashflow by cashflow date.
> 	 */	
> 	public int compareTo(Cashflow cashflow)
> 	{
> 		if(getDate().after(cashflow.getDate()))
> 		{
> 			return 1;
> 		}
> 		if(getDate().before(cashflow.getDate()))
> 		{
> 			return -1;
> 		}	
> 		
> 		return 0;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of Cashflow objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof Cashflow))
> 		{
> 			return false;
> 		}
> 		
> 		Cashflow cashflow = (Cashflow) obj;
> 		
> 		if(!getAccount().equals(cashflow.getAccount())) return false;
> 		if(getAmount()!=cashflow.getAmount()) return false;
> 		if(!getDate().equals(cashflow.getDate())) return false;
> 		if(getType()!=cashflow.getType()) return false;
> 		
> 		return true;
> 	}	
> 	
> 	public String toString()
> 	{
> 		return "Cashflow["
> 				//+"account="+account
> 				+"date="+date
> 				+",amount="+amount
> 				+",type="+(type==CREDIT?"Credit":"Debit")
> 				+"]";
> 	}
> 	
> 	
> }
> package net.tplusplus.drools.speedtest.facts;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.rules.runner.rao.Fact;
> public class UpdatingAccount implements Fact, Comparable<UpdatingAccount>
> {
> 	private long accountNo;
> 	private Account account;
> 	
> 	public UpdatingAccount(long accountNo, Account account)
> 	{
> 		this.accountNo = accountNo;
> 		this.account = account;
> 	}
> 	public long getAccountNo()
> 	{
> 		return accountNo;
> 	}
> 	public void setAccountNo(long accountNo)
> 	{
> 		this.accountNo = accountNo;
> 	}
> 	public Account getAccount()
> 	{
> 		return account;
> 	}
> 	public void setAccount(Account account)
> 	{
> 		this.account = account;
> 	}
> 	
> 	/**
> 	 *  This method enables the Collections api to sort the 
> 	 *  UpdatingAccount by account no.
> 	 */	
> 	public int compareTo(UpdatingAccount updatingAccount)
> 	{
> 		if(getAccountNo()==updatingAccount.getAccountNo()) return 0;
> 		
> 		return (getAccountNo()>updatingAccount.getAccountNo()) ? 1 : -1;
> 	}
> 	
> 	/**
> 	 *  This method enables the comparison of UpdatingAccount objects
> 	 */	
> 	@Override
> 	public boolean equals(Object obj) 
> 	{
> 		if(obj==null || !(obj instanceof UpdatingAccount))
> 		{
> 			return false;
> 		}
> 		
> 		UpdatingAccount updatingAccount = (UpdatingAccount) obj;
> 		
> 		return (getAccountNo()==updatingAccount.getAccountNo());	
> 	}		
> }
> package net.tplusplus.test.drools.speedtest.data;
> import java.util.ArrayList;
> import java.util.Date;
> import java.util.List;
> import net.tplusplus.drools.speedtest.bank.Account;
> import net.tplusplus.drools.speedtest.facts.AccountingPeriod;
> import net.tplusplus.drools.speedtest.facts.Cashflow;
> import net.tplusplus.drools.speedtest.facts.UpdatingAccount;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.utils.SimpleDate;
> public class TestData
> {
> 	private static Date startDate;
> 	private static Date endDate;
> 	
> 	private static List<Account> accounts;
> 	private static List<UpdatingAccount> updatingAccounts;
> 	private static List<Cashflow> cashflows;
> 	private static List<AccountingPeriod> accountingPeriods;
> 	
> 	static
> 	{
> 		try
> 		{
> 			startDate = new SimpleDate("01/01/2007");
> 			endDate = new SimpleDate("31/12/2007");
> 		}
> 		catch(Exception e){}
> 	}
> 	
> 	private static List<Account> getAllAccounts()
> 	{
> 		if(accounts==null)
> 		{
> 			accounts = new ArrayList<Account>();
> 		
> 			accounts.add(new Account(1));
> 		}
> 		
> 		return accounts;
> 	}
> 	
> 	public static List<UpdatingAccount> getAllUpdatingAccounts()
> 	{
> 		if(updatingAccounts==null)
> 		{
> 			updatingAccounts = new ArrayList<UpdatingAccount>();
> 			
> 			for(Account account : getAllAccounts())
> 			{
> 				updatingAccounts.add(new UpdatingAccount(account.getAccountNo(), account));
> 			}
> 		}
> 		
> 		return updatingAccounts;
> 	}
> 	
> 	public static List<Cashflow> getAllCashflows()
> 	throws Exception
> 	{
> 		if(cashflows==null)
> 		{
> 			cashflows = new ArrayList<Cashflow>();		
> 				
> 			for(Date date = startDate; !date.after(endDate);)
> 			{
> 				int adj = 0;
> 				
> 				for(Account acct : getAllAccounts())
> 				{
> 					adj++;
> 					
> 					int[] credits = new int[]{ 300, 150, 200, 50, 120, 20, 10};
> 					int[] debits = new int[]{ 200, 50, 50, 30};
> 					
> 					for(int credit : credits)
> 					{
> 						Cashflow c = new Cashflow(date, credit+adj, Cashflow.CREDIT, acct);
> 						cashflows.add(c);
> 					}
> 					
> 					for(int debit : debits)
> 					{
> 						Cashflow c = new Cashflow(date, debit+adj, Cashflow.DEBIT, acct);		
> 						cashflows.add(c);
> 					}	
> 				}
> 				
> 				long newDate = date.getTime() + 24l*60l*60l*1000l;
> 				date = new Date(newDate);
> 			}
> 		}
> 		
> 		return cashflows;
> 	}
> 	
> 	public static List<AccountingPeriod> getAccountingPeriods()
> 	throws Exception
> 	{
> 		if(accountingPeriods==null)
> 		{
> 			accountingPeriods = new ArrayList<AccountingPeriod>();
> 			
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/01/2007"),new SimpleDate("31/03/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/04/2007"),new SimpleDate("30/06/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/07/2007"),new SimpleDate("30/09/2007")));
> 			accountingPeriods.add(new AccountingPeriod(new SimpleDate("01/10/2007"),new SimpleDate("31/12/2007")));
> 		}
> 		
> 		return accountingPeriods;
> 	}
> 	
> 	public static List<Fact> getAllFacts()
> 	throws Exception
> 	{
> 		List<Fact> facts = new ArrayList<Fact>();
> 		
> 		facts.addAll(getAccountingPeriods());
> 		facts.addAll(getAllCashflows());
> 		facts.addAll(getAllUpdatingAccounts());
> 		
> 		return facts;		
> 	}
> 	
> 	public static void resetAccounts()
> 	{
> 		for(Account account : getAllAccounts())
> 		{
> 			account.setBalance(0);
> 		}
> 	}
> }
> package net.tplusplus.test.drools.speedtest;
> import java.util.List;
> import org.drools.RuleBase;
> import org.drools.WorkingMemory;
> import net.tplusplus.rules.runner.RuleRunner;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.test.drools.speedtest.data.TestData;
> import net.tplusplus.utils.TimedResults;
> public class SpeedTest1
> {
> 	public static void main(String[] args)
> 	throws Exception
> 	{
> 		int iterations = 1000;
> 		
> 		//runTest1(iterations);
> 		runTest2(iterations);
> 		runTest3(iterations);
> 		runTest4(iterations);
> 		runTest5(iterations);
> 		runTest6(iterations);
> 	}
> 	
> 	public static void runTest1(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 1 - NO CACHING");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			runner.createRuleBase();
> 			runner.createWorkingMemory();
> 			runner.runRules();
> 			
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest2(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 2 - CACHING RULEBASE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		RuleBase cachedRuleBase = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			System.out.println(i);
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedRuleBase==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setRuleBase(cachedRuleBase);
> 				runner.createWorkingMemory();
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest3(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 3 - CACHING WORKINGSTORE");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test01.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest4(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 4 - OPTIMISED DRL - changed order of facts");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test02.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}	
> 	
> 	public static void runTest5(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 5 - OPTIMISED DRL - using long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test03.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> 	
> 	public static void runTest6(int iterations)
> 	throws Exception
> 	{		
> 		System.out.println("\nRunning Speed Test 6 - OPTIMISED DRL - using Long instead of Date");
> 		TimedResults results = new TimedResults();
> 		
> 		RuleRunner runner = new RuleRunner();
> 		runner.addRules("/net/tplusplus/drools/speedtest/rules/test1/test04.drl");
> 		
> 		List<Fact> allFacts = TestData.getAllFacts();
> 		runner.addFacts(allFacts);
> 		WorkingMemory cachedWorkingMemory = null;
> 		
> 		for(int i=0;i<iterations;i++)
> 		{
> 			TestData.resetAccounts();
> 			
> 			long starttime = System.currentTimeMillis();
> 			
> 			if(cachedWorkingMemory==null)
> 			{
> 				runner.createWorkingMemory();
> 			}
> 			else
> 			{
> 				runner.setWorkingMemory(cachedWorkingMemory);
> 			}
> 			
> 			runner.runRules();
> 			long endtime = System.currentTimeMillis();
> 			long timetaken = endtime - starttime;
> 			
> 			results.addTime(timetaken);
> 		}
> 		
> 		System.out.println("Iterations: "+iterations);
> 		System.out.println("Number of facts: "+runner.getFacts().size());
> 		System.out.println("fastest time: "+results.getFastest()+" (ms)");
> 		System.out.println("slowest time: "+results.getSlowest()+" (ms)");
> 		System.out.println("average time: "+results.getAverage()+" (ms)");
> 	}
> }
> package net.tplusplus.rules.runner;
> import java.io.File;
> import java.io.FileReader;
> import java.net.URL;
> import java.util.ArrayList;
> import java.util.Arrays;
> import java.util.List;
> import java.util.Iterator;
> import net.tplusplus.rules.runner.rao.Fact;
> import net.tplusplus.rules.runner.rao.Global;
> import org.drools.FactHandle;
> import org.drools.RuleBase;
> import org.drools.RuleBaseFactory;
> import org.drools.WorkingMemory;
> import org.drools.compiler.PackageBuilder;
> import org.drools.spi.ActivationGroup;
> import org.drools.spi.AgendaGroup;
> public class RuleRunner
> {
> 	private RuleBase ruleBase;
> 	private WorkingMemory workingMemory;
> 	
> 	private List<String> rules;
> 	private List<Global> globals;
> 	private List<Fact> facts;
> 	
> 	public RuleRunner()
> 	{
> 		rules = new ArrayList<String>();
> 		globals = new ArrayList<Global>();
> 		facts = new ArrayList<Fact>();	
> 	}
> 	
> 	public void addRules(String... rules)
> 	{
> 		this.rules.addAll(Arrays.asList(rules));
> 	}
> 	
> 	public void addGlobals(Global... globals)
> 	{
> 		this.globals.addAll(Arrays.asList(globals));
> 	}
> 	
> 	public void addFacts(Fact... facts)
> 	{
> 		this.facts.addAll(Arrays.asList(facts));
> 	}
> 	
> 	public void addFacts(List<? extends Fact> facts)
> 	{
> 		this.facts.addAll(facts);
> 	}	
> 	
> 	public List<Fact> getFacts()
> 	{
> 		return this.facts;
> 	}
> 	
> 	public void clearFacts()
> 	{
> 		this.facts = new ArrayList<Fact>();
> 	}
> 	
> 	public RuleBase createRuleBase()
> 	throws Exception
> 	{
> 		if(rules==null)
> 		{
> 			throw new Exception("No rules provided for Engine");
> 		}
> 		
> 		ruleBase = RuleBaseFactory.newRuleBase();
> 		PackageBuilder builder = new PackageBuilder();		
> 		
> 		for(String ruleFile : rules)
> 		{
> 			URL resource = this.getClass().getResource(ruleFile);
> 			
> 			if(resource==null)
> 			{
> 				System.err.println("Could not find resource: "+ruleFile);
> 				continue;
> 			}
> 			File file = new File(this.getClass().getResource(ruleFile).getPath());
> 			if(!file.exists())
> 			{
> 				System.err.println("Could not find rule file: "+file.getPath());
> 				continue;
> 			}
> 			
> 			builder.addPackageFromDrl(new FileReader(file.getPath()));
> 		}
> 		
> 		org.drools.rule.Package pkg = builder.getPackage();		
> 		ruleBase.addPackage(pkg);	
> 		
> 		return ruleBase;
> 	}
> 	
> 	public void setRuleBase(RuleBase ruleBase)
> 	{
> 		this.ruleBase = ruleBase;
> 	}
> 	
> 	public RuleBase getRuleBase()
> 	{
> 		return ruleBase;
> 	}
> 	
> 	public WorkingMemory createWorkingMemory()
> 	throws Exception
> 	{
> 		if(ruleBase==null)
> 		{
> 			createRuleBase();
> 		}
> 		
> 		workingMemory = null;
> 		
> 		workingMemory = ruleBase.newStatefulSession();
> 		
> 		return workingMemory;
> 	}
> 	
> 	public void setWorkingMemory(WorkingMemory workingMemory)
> 	{
> 		this.workingMemory = workingMemory;
> 	}
> 	
> 	public WorkingMemory getWorkingMemory()
> 	{
> 		return workingMemory;
> 	}
> 	
> 	public void runRules()
> 	throws Exception
> 	{		
> 		if(workingMemory==null)
> 		{
> 			throw new Exception("No workingMemory created for Engine");
> 		}
> 		
> 		System.gc();
> 		System.out.println("Free Memory: "+Runtime.getRuntime().freeMemory());
> 		
> 		
> 		if(globals!=null)
> 		{
> 			for(Global global : globals)
> 			{
> 				workingMemory.setGlobal(global.getName(), global.getValue());
> 			}
> 		}
> 		if(facts!=null)
> 		{
> 			for(Fact fact : facts)
> 			{
> 				workingMemory.insert(fact);
> 			}
> 		}
> 		workingMemory.fireAllRules();
> 	}
> }
> package net.tplusplus.rules.runner.rao;
> public interface Fact
> {
> }
> package net.tplusplus.rules.runner.rao;
> public class Global
> {
> 	private String name;
> 	private Object value;
> 	
> 	public Global(String name, Object value)
> 	{
> 		this.name = name;
> 		this.value = value;
> 	}
> 	public String getName()
> 	{
> 		return name;
> 	}
> 	public void setName(String name)
> 	{
> 		this.name = name;
> 	}
> 	public Object getValue()
> 	{
> 		return value;
> 	}
> 	public void setValue(Object value)
> 	{
> 		this.value = value;
> 	}
> 	
> 	public String toString()
> 	{
> 		return "Global["
> 				+"name="+name
> 				+"value="+value
> 				+"]";
> 	}
> }
> package net.tplusplus.utils;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> public class SimpleDate extends Date
> {
> 	public static final long serialVersionUID = 1;
> 	
> 	public SimpleDate(String datestr)
> 	throws Exception
> 	{
> 		SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
> 		this.setTime(format.parse(datestr).getTime());
> 	}
> }
> package net.tplusplus.utils;
> import java.util.HashMap;
> import java.util.Map;
> public class TimedResults
> {
> 	private long fastest = -1;
> 	private long slowest = -1;
> 	
> 	private Map<Long,Long> results = new HashMap<Long,Long>();
> 	
> 	public TimedResults()
> 	{
> 	}
> 	
> 	public void addTime(long time)
> 	throws Exception
> 	{
> 		if(time < 0)
> 		{
> 			throw new Exception("Invalid Time");
> 		}
> 		
> 		Long key = System.currentTimeMillis();
> 		results.put(key,time);
> 		
> 		if(fastest==-1 || fastest>time) fastest=time;
> 		if(slowest==-1 || slowest<time) slowest=time;
> 	}
> 	
> 	public Map<Long,Long> getResults()
> 	{
> 		return results;
> 	}
> 	
> 	public long getFastest()
> 	{
> 		return fastest;
> 	}
> 	
> 	public long getSlowest()
> 	{
> 		return slowest;
> 	}
> 	
> 	public long getAverage()
> 	{
> 		long time = 0;
> 		
> 		for(Long timetaken : results.values())
> 		{
> 			time += timetaken;
> 		}
> 		
> 		return time / results.size();
> 	}
> }

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:14:01 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Mon, 29 Oct 2007 10:14:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4916) Invalid content
 was found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33133957.1193667241667.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4916?page=comments#action_12384834 ] 
            
Alexey Loubyansky commented on JBAS-4916:
-----------------------------------------

This is thrown by Xerces. It's validation against the XSD. I tried a small validation test but it passed

   public void testMain() throws Exception
   {
      String xml = "<web-app xmlns='http://java.sun.com/xml/ns/j2ee' " +
         "xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' " +
         "xsi:schemaLocation='http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd' " +
         "version='2.4'>" +
         "<servlet>" +
         "  <servlet-name>TestService</servlet-name>" +
         "  <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>" +
         "</servlet>" +
         "<servlet-mapping>" +
         "  <servlet-name>TestService</servlet-name>" +
         "  <url-pattern>/*</url-pattern>" +
         "</servlet-mapping>" +
         "<env-entry>" +
         "  <env-entry-name>jsr109/entry1</env-entry-name>" +
         "  <env-entry-type>java.lang.String</env-entry-type>" +
         "  <env-entry-value>web</env-entry-value>" +
         "</env-entry>" +
         "<env-entry>" +
         "  <env-entry-name>jsr109/entry2</env-entry-name>" +
         "  <env-entry-type>java.lang.Integer</env-entry-type>" +
         "  <env-entry-value>8</env-entry-value>" +
         "</env-entry>" +
         "</web-app>";

      Validator.assertValidXml(xml, new EntityResolver()
      {
         public InputSource resolveEntity(String publicId, String systemId) throws SAXException, IOException
         {            
            String path = "file:///e:/cvsroot/projects/metadata/trunk/src/main/resources/schema/";
            if(systemId != null && systemId.startsWith(path))
            {
               path = systemId;
            }
            else if("http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd".equals(systemId))
            {
               path += "web-app_2_4.xsd";
            }
            else if("http://www.w3.org/2001/xml.xsd".equals(systemId))
            {
               path += "xml.xsd";
            }
            else if("http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd".endsWith(systemId))
            {
               path += "j2ee_web_services_client_1_1.xsd";
            }
            else
            {
               System.out.println("resolveEntity: '" + publicId + "' '" + systemId + "'");
               return null;
            }
            
            return new InputSource(path);
         }}
      );
   }

Could you try to come up with a test like this that fails? I tried creating a test in the metadata project but that would also pass. I can commit it if you want.

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Alexey Loubyansky
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:31:04 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:31:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
In-Reply-To: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4154067.1193668264587.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4884?page=all ]

Dimitris Andreadis updated JBAS-4884:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt

> TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
> -------------------------------------------------------------------
>
>                 Key: JBAS-4884
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:31:05 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:31:05 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4884) TECH REVIEW: Server
 Configuration Guide - Chapter11 - EJBs on JBoss
In-Reply-To: <1113174.1192791425709.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19150643.1193668265586.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4884?page=all ]

Dimitris Andreadis resolved JBAS-4884.
--------------------------------------

    Fix Version/s: No Release
       Resolution: Done
         Assignee: Dimitris Andreadis

Reviewed.

> TECH REVIEW: Server Configuration Guide - Chapter11 - EJBs on JBoss
> -------------------------------------------------------------------
>
>                 Key: JBAS-4884
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4884
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Dimitris Andreadis
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt, JBAS-422-Server_Configuration_Guide-Chapter11-EJBs_On_JBoss.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:33:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:33:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33457023.1193668381561.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis updated JBAS-4851:
-------------------------------------

    Attachment:     (was: JBAS-422-Server_Configuration_Guide - Chapter1 - Enterprise_Applications_with_EJB3_Services.odt)

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:41:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:41:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4301364.1193668862973.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4916?page=all ]

Thomas Diesler reassigned JBAS-4916:
------------------------------------

    Assignee: Thomas Diesler  (was: Alexey Loubyansky)

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:43:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28077719.1193668981582.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis updated JBAS-4851:
-------------------------------------

    Attachment: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt

Attach reviewed file.

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:43:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4916) Invalid content was
 found starting with element 'env-entry'
In-Reply-To: <2052317.1193663702665.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30446857.1193668981701.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4916?page=all ]

Thomas Diesler resolved JBAS-4916.
----------------------------------

    Resolution: Done

The application-client.xml was invalid

> Invalid content was found starting with element 'env-entry'
> -----------------------------------------------------------
>
>                 Key: JBAS-4916
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4916
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxrpc.enventry.EnvEntryJSETestCase one-test
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>   version="2.4">
>   <servlet>
>     <servlet-name>TestService</servlet-name>
>     <servlet-class>org.jboss.test.ws.jaxrpc.enventry.EnvEntryBeanJSE</servlet-class>
>   </servlet>
>   <servlet-mapping>
>     <servlet-name>TestService</servlet-name>
>     <url-pattern>/*</url-pattern>
>   </servlet-mapping>
>   <env-entry>
>    <env-entry-name>jsr109/entry1</env-entry-name>
>    <env-entry-type>java.lang.String</env-entry-type>
>    <env-entry-value>web</env-entry-value>
>   </env-entry>
>   
>   <env-entry>
>    <env-entry-name>jsr109/entry2</env-entry-name>
>    <env-entry-type>java.lang.Integer</env-entry-type>
>    <env-entry-value>8</env-entry-value>
>   </env-entry>
> </web-app>
> Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'env-entry'. One of '{"http://java.sun.com/xml/ns/j2ee":service-ref, "http://java.sun.com/xml/ns/j2ee":resource-ref, "http://java.sun.com/xml/ns/j2ee":resource-env-ref, "http://java.sun.com/xml/ns/j2ee":message-destination-ref, "http://java.sun.com/xml/ns/j2ee":callback-handler, "http://java.sun.com/xml/ns/j2ee":message-destination}' is expected. @ *unknown*[24,14]
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:437)
>         at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
>         at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
>         at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
>         at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
>         at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>         at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>         at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:209)

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:43:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4851) TECH REVIEW: Server
 Configuration Guide - Chapter1 - Enterprise
 Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1454511.1193668981949.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis reassigned JBAS-4851:
----------------------------------------

    Assignee: Carlo de Wolf

Carlo, can you or someone from EJB3 review this document? I made a first pass with some minor changes.

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Carlo de Wolf
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:45:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 10:45:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4851) TECH REVIEW: Server
 Configuration
 Guide - Chapter1 - Enterprise Applications with EJB3 Services
In-Reply-To: <45449.1192170304765.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13013619.1193669101798.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4851?page=all ]

Dimitris Andreadis updated JBAS-4851:
-------------------------------------

    Fix Version/s: No Release

> TECH REVIEW: Server Configuration Guide - Chapter1 - Enterprise Applications with EJB3 Services
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4851
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4851
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Server Configuration Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Carlo de Wolf
>             Fix For: No Release
>
>         Attachments: JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt, JBAS-422-Server_Configuration_Guide-Chapter1-Enterprise_Applications_with_EJB3_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:49:02 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:49:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-923) Acquired node lock
 never released after transaction timeout
In-Reply-To: <9534770.1167949167059.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33224877.1193669342344.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-923?page=all ]

Manik Surtani updated JBCACHE-923:
----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> Acquired node lock never released after transaction timeout
> -----------------------------------------------------------
>
>                 Key: JBCACHE-923
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-923
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.0.SP1, 1.4.1.GA, 1.4.1.SP4
>         Environment: Windows XP, Weblogic 9.1
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: AsyncRollbackTxTest.zip
>
>
> Under weblogic 9.1 (and probably earlier version too, not tested) in some situations locks aquired on nodes are never released. Only way to release locks is stop and start again treecache.
> On WebLogic the rollback after a tx timeout is handled in a separate thread (and all registered transaction synchronization handlers are invoked in separated thread! In treecache information about InvocationContext (GlobalTransaction, Transaction etc) is stored in ThreadLocal. In this situation SynchronizationHandler is scrubbing NOT correct invocationContext with information about currend rolled-back transaction, but new created empty invocationContext !!!! Informations from TransactionTable are correctly removed, because mapping of transactions is not stored in ThreadLocal variable.
> This caused unexpected effects:
> Information about GlobalTransaction is not cleared and when in main thread TransactionTimedOutException is catched and put/get operations without explicity created transaction are invoked, TreeCache is trying aquire RL/WL on node and caller is set to non-exist and cleared GlobalTransaction. Lock is aquired but not added to LockTable! (and not released).
> From now every access to locked node failed, because RL/WL can't be aquired in 10 secs. Only way to get system working is stop and start again TreeCache.
> 2007-01-04 10:13:42,092 DEBUG  - calling aftercompletion for GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - Running rollback phase
> 2007-01-04 10:13:42,092 DEBUG  -  running rollback for GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - PessimisticLockInterceptor invoked for method rollback(GlobalTransaction:<192.168.141.1:2100>:1)
> 2007-01-04 10:13:42,092 DEBUG  - called to rollback cache with GlobalTransaction=GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - _remove(GlobalTransaction:<192.168.141.1:2100>:1, "/NODEA/NODEB", systemProperty)
> 2007-01-04 10:13:42,092 DEBUG  - _remove(GlobalTransaction:<192.168.141.1:2100>:1, "/NODEA/NODEB")
> 2007-01-04 10:13:42,092 DEBUG  - removed child NODEB
> 2007-01-04 10:13:42,092 DEBUG  - releasing lock for /NODEA/NODEB (<unlocked>)
> 2007-01-04 10:13:42,092 DEBUG  - releasing lock for /NODEA (read owners=[GlobalTransaction:<192.168.141.1:2100>:1])
> 2007-01-04 10:13:42,092 DEBUG  - removing local transaction Name=FooManager.foo,Xid=BEA1-00068143BD8A02E8BAA1(4771853),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 20 seconds 
> BEA1-00068143BD8A02E8BAA1],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=30,seconds left=20,activeThread=Thread[Timer-5,5,Pooled Threads],XAServerResourceInfo[dataSource]=(ServerResourceInfo[dataSource]=(state=rolledback,assigned=AdminServer),xar=dataSource,re-Registered = false),SCInfo[sample_domain+AdminServer]=(state=rolledback),properties=({weblogic.transaction.name=FooManager.foo}),local properties=({weblogic.jdbc.jta.dataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+10.1.1.218:9002+sample_domain+admin+, XAResources={dataSource, WLStore_sample_domain__WLS_AdminServer},NonXAResources={})],CoordinatorURL=AdminServer+10.1.1.218:9002+sample_domain+admin+) and global transaction GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - bypassed locking as method rollback() doesn't require locking
> 2007-01-04 10:13:42,092 DEBUG  - Suppressing invocation of method rollback(GlobalTransaction:<192.168.141.1:2100>:1) on cache.
> 2007-01-04 10:13:42,092 DEBUG  - Attempting to release locks on current thread.  Lock table is {}
> 2007-01-04 10:13:42,092 DEBUG  - Finished local commit/rollback method for GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:13:42,092 DEBUG  - Finished rollback phase
> (...)
> 2007-01-04 10:14:12,302 DEBUG  - Non-tx and non crud meth
> 2007-01-04 10:14:37,310 DEBUG  - (192.168.141.1:2100) call on method [_get(/NODEC, NODE_VALUE, true)]
> 2007-01-04 10:14:37,310 DEBUG  - PessimisticLockInterceptor invoked for method _get(/NODEC, NODE_VALUE, true)
> 2007-01-04 10:14:37,310 DEBUG  - Attempting to lock node /NODEC for owner GlobalTransaction:<192.168.141.1:2100>:1
> 2007-01-04 10:14:37,310 DEBUG  - acquiring RL: fqn=/NODEC, caller=GlobalTransaction:<192.168.141.1:2100>:1, lock=<unlocked>
> 2007-01-04 10:14:37,310 DEBUG  - acquired RL: fqn=/NODEC, caller=GlobalTransaction:<192.168.141.1:2100>:1, lock=read owners=[GlobalTransaction:<192.168.141.1:2100>:1]
> 2007-01-04 10:14:37,310 ERROR  - transaction entry not found for (gtx=GlobalTransaction:<192.168.141.1:2100>:1)
> 2007-01-04 10:14:37,310 DEBUG  - Invoking method _get(/NODEC, NODE_VALUE, true) on cache.
> 2007-01-04 10:14:37,310 DEBUG  - _get("/NODEC", NODE_VALUE, "true")
> 2007-01-04 10:14:37,310 DEBUG  - Attempting to release locks on current thread.  Lock table is {} 
> 	

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1164)
 NodeNotExistException with concurrent put/remove operations
In-Reply-To: <18249492.1187299741540.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27824345.1193669474712.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1164?page=all ]

Manik Surtani updated JBCACHE-1164:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> NodeNotExistException with concurrent put/remove operations
> -----------------------------------------------------------
>
>                 Key: JBCACHE-1164
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1164
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: Windows XP, Sun jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: ConcurentOperationsTest.java
>
>
> When 2 Threads are putting/removing data from this same node, put operation fails with exception
> org.jboss.cache.NodeNotExistsException: node /a/b/c/d not found (gtx=GlobalTransaction::2, caller=Thread[Thread-0,5,main]) 
> at org.jboss.cache.TreeCache._put(TreeCache.java:4618) 
> at org.jboss.cache.TreeCache._put(TreeCache.java:4579) 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
> at java.lang.reflect.Method.invoke(Unknown Source) 
> at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:330) 
> at org.jboss.cache.interceptors.CallInterceptor.invoke(CallInterceptor.java:52) 
> at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) 
> at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:89) 
> at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) 
> at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32) 
> at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) 
> (...) 
> Thread 1 is calling: 
> 	cache.remove("/a/b/c/d");
> 	cache.remove("/a");
>  Thread 2 is calling: 
> 	cache.putObject("/a/b/c/d", "text" + x);

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock
 could be not released after async transaction rollback
In-Reply-To: <19139966.1189557851483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20587157.1193669474834.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]

Manik Surtani updated JBCACHE-1183:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                   2.1.0.GA
                       (was: 1.4.1.SP6)

> Acquired WL lock could be not released after async transaction rollback
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-1183
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: WindowsXP, jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: AsyncRollbackTxLockTest.java
>
>
> In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:14 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1166) UpgradeException
 on concurrent put/remove operation
In-Reply-To: <33448482.1187338441457.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19069834.1193669474959.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1166?page=all ]

Manik Surtani updated JBCACHE-1166:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> UpgradeException on concurrent put/remove operation
> ---------------------------------------------------
>
>                 Key: JBCACHE-1166
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1166
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: Windows XP, Sun jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: ConcurentOperationTest.java, ConcurentOperationTestCore.java
>
>
> When 2 Threads simultanous are attaching/detaching object from this same region sometimes TreeCache fails with Exception:
> upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock
> Full StackTrace:
> org.jboss.cache.pojo.PojoCacheException: detach /a/b/c/d failed
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:158)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.putObjectII(PojoCacheDelegate.java:143)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.putObject(PojoCacheImpl.java:136)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:101)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93)
> 	at org.jboss.cache.aop.ConcurentOperationTest$WorkThread.run(ConcurentOperationTest.java:80)
> Caused by: org.jboss.cache.lock.UpgradeException: failure upgrading lock: fqn=/__JBossInternal__/a/b/c/d/_ID_/a1170-d7nvs9-f5gejrti-1-f5gejrti-2, caller=GlobalTransaction:<10.1.1.252:4508>:19, lock=read owners=[GlobalTransaction:<10.1.1.252:4508>:18, GlobalTransaction:<10.1.1.252:4508>:19] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=1, waitingUpgrader=1)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:508)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:579)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:393)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:329)
> 	at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:187)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:34)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:298)
> 	at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:97)
> 	at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
> 	at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
> 	at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3939)
> 	at org.jboss.cache.CacheImpl.put(CacheImpl.java:1598)
> 	at org.jboss.cache.pojo.impl.PojoCacheDelegate.removeObject(PojoCacheDelegate.java:273)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.removeObject(PojoCacheImpl.java:170)
> 	at org.jboss.cache.pojo.impl.PojoCacheImpl.detach(PojoCacheImpl.java:153)
> 	... 5 more
> Caused by: org.jboss.cache.lock.UpgradeException: acquireWriteLock(): lock upgrade failed for /__JBossInternal__/a/b/c/d/_ID_/a1170-d7nvs9-f5gejrti-1-f5gejrti-2 (caller=GlobalTransaction:<10.1.1.252:4508>:19, lock info: read owners=[GlobalTransaction:<10.1.1.252:4508>:18, GlobalTransaction:<10.1.1.252:4508>:19] (activeReaders=1, activeWriter=null, waitingReaders=0, waitingWriters=1, waitingUpgrader=1))
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:209)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:167)
> 	at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:497)
> 	... 25 more
> Caused by: org.jboss.cache.lock.UpgradeException: upgradeLockAttempt(): more than one reader trying to simultaneously upgrade to write lock
> 	at org.jboss.cache.lock.ReadWriteLockWithUpgrade.upgradeLockAttempt(ReadWriteLockWithUpgrade.java:107)
> 	at org.jboss.cache.lock.LockStrategyRepeatableRead.upgradeLockAttempt(LockStrategyRepeatableRead.java:43)
> 	at org.jboss.cache.lock.IdentityLock.acquireWriteLock0(IdentityLock.java:203)
> 	... 27 more

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1168) Sometimes
 acquired locks are not released
In-Reply-To: <30832886.1187878698592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28550792.1193669475429.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1168?page=all ]

Manik Surtani updated JBCACHE-1168:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                   2.1.0.GA
                       (was: 1.4.1.SP6)

> Sometimes acquired locks are not released
> -----------------------------------------
>
>                 Key: JBCACHE-1168
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4
>         Environment: Windows XP, jrockit90_150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: jbosscache.log, output.txt, TransactionStormTest.java
>
>
> Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache.
> Main loop:
> 		while (true) {
> 			for (int x = 0; x < 2; x++) {
> 				WorkThread t = new WorkThread(x == 1);
> 				threads.add(t);
> 				t.start();
> 			}
> 			for (WorkThread separateThread : threads) {
> 				separateThread.join();
> 				if (separateThread.getException() != null) {
> 					//separateThread.getException().getMessage();
> 				}
> 			}
> 			int locksNum = getNumberOfLocksHeld();
> //			System.out.println("Locks="+locksNum);
> 			// checkpoint
> 			if (cache.getNumberOfLocksHeld()>0){
> 				System.out.println("ERROR, locks="+locksNum);
> 				doDomethingOnCache(1);
> 			}
> 			assertEquals(0, locksNum);
> 		}
> Exception - after //checkpoint line numberOfLocks is grater than 0!
> JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1165) Endless loop in
 PessimisticLockInterceptor
In-Reply-To: <14669904.1187336057521.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7700087.1193669475593.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1165?page=all ]

Manik Surtani updated JBCACHE-1165:
-----------------------------------

    Fix Version/s: 1.4.1.SP7
                       (was: 1.4.1.SP6)

> Endless loop in PessimisticLockInterceptor
> ------------------------------------------
>
>                 Key: JBCACHE-1165
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1165
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: Windows XP, Sun jdk150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 1.4.1.SP7
>
>         Attachments: ConcurentPutRemoveTest.java, ConsoleOut.log
>
>
> When 2 Threads are simulatanous putting/removing values from this same node TreeCache hang's up and goes into endless loop.
> Main loop looks like:
> 				for (int x = 0; x < 1000; x++) {
> 					tm.begin();
> 					System.out.println("R" + Thread.currentThread().getName());
> 					//inside transaction
> 					cache.remove("/a");
> 					System.out.println("AR" + Thread.currentThread().getName());
> 					tm.commit();
> 					//outside transaction
> 					System.out.println("P" + Thread.currentThread().getName());
> 					cache.put("/a/b/c/d", "text"+x,"b");
> 					System.out.println("AP" + Thread.currentThread().getName());
> 				}

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock
 could be not released after async transaction rollback
In-Reply-To: <19139966.1189557851483.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14383441.1193669475736.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]

Manik Surtani updated JBCACHE-1183:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

> Acquired WL lock could be not released after async transaction rollback
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-1183
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP4
>         Environment: WindowsXP, jdk150_06 
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: AsyncRollbackTxLockTest.java
>
>
> In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:51:15 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 10:51:15 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1168) Sometimes
 acquired locks are not released
In-Reply-To: <30832886.1187878698592.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32847394.1193669475904.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1168?page=all ]

Manik Surtani updated JBCACHE-1168:
-----------------------------------

    Fix Version/s:     (was: 2.1.0.GA)

> Sometimes acquired locks are not released
> -----------------------------------------
>
>                 Key: JBCACHE-1168
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP4
>         Environment: Windows XP, jrockit90_150_06 
> Solaris 10
>            Reporter: Jacek Halat
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP7
>
>         Attachments: jbosscache.log, output.txt, TransactionStormTest.java
>
>
> Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache.
> Main loop:
> 		while (true) {
> 			for (int x = 0; x < 2; x++) {
> 				WorkThread t = new WorkThread(x == 1);
> 				threads.add(t);
> 				t.start();
> 			}
> 			for (WorkThread separateThread : threads) {
> 				separateThread.join();
> 				if (separateThread.getException() != null) {
> 					//separateThread.getException().getMessage();
> 				}
> 			}
> 			int locksNum = getNumberOfLocksHeld();
> //			System.out.println("Locks="+locksNum);
> 			// checkpoint
> 			if (cache.getNumberOfLocksHeld()>0){
> 				System.out.println("ERROR, locks="+locksNum);
> 				doDomethingOnCache(1);
> 			}
> 			assertEquals(0, locksNum);
> 		}
> Exception - after //checkpoint line numberOfLocks is grater than 0!
> JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:53:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6083220.1193669581676.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12384851 ] 
            
Thomas Diesler commented on JBAS-4902:
--------------------------------------

Same is true for nested wars

[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws128 test

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxrpc.jbws128.JBWS128TestCase
    [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.724 sec
    [junit] Test org.jboss.test.ws.jaxrpc.jbws128.JBWS128TestCase FAILED


> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 10:53:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Mon, 29 Oct 2007 10:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20767518.1193669581888.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4902?page=all ]

Thomas Diesler updated JBAS-4902:
---------------------------------

    Priority: Critical  (was: Major)

Raising this to 'critical' because most CTS tests deploy eras

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:15:01 2007
From: jira-events at lists.jboss.org (=?UTF-8?Q?Fran=EF=BF=A7ois_Karman_=28JIRA=29?=)
Date: Mon, 29 Oct 2007 11:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4917) remote call to
 LoaderRepository.getPackageClassLoaders throws a NotSerializableException
Message-ID: <30267597.1193670901823.JavaMail.jira@cloud.prod.atl2.jboss.com>

remote call to LoaderRepository.getPackageClassLoaders throws a NotSerializableException
----------------------------------------------------------------------------------------

                 Key: JBAS-4917
                 URL: http://jira.jboss.com/jira/browse/JBAS-4917
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: JMX
         Environment: I have tested this problems on Windows Platform only.
            Reporter: Fran?ois Karman
         Assigned To: Dimitris Andreadis


A call to the getPackageClassLoaders operation of the MBean : JMImplementation:name=Default,service=LoaderRepository throws an exception.

The simpliest way to view the bug : 
twiddle invoke "JMImplementation:name=Default,service=LoaderRepository" getPackageClassLoaders javax.ejb.EntityBean

Start of the trace :
java.io.NotSerializableException: org.jboss.mx.loading.ClassLoaderUtils$RepositoryClassLoaderComparator
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
	at java.util.TreeSet.writeObject(TreeSet.java:458)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)

The comparator used by the result TreeSet is not serializable and could not be send to the remote client. (twiddle or a J2EE Client application)

http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jmx/src/main/org/jboss/mx/loading/ClassLoaderUtils.java?view=markup


-- 
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

       



From jira-events at lists.jboss.org  Mon Oct 29 11:29:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 29 Oct 2007 11:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMICROCONT-214) Extend the
 demand/supply dependency
Message-ID: <1166215.1193671741496.JavaMail.jira@cloud.prod.atl2.jboss.com>

Extend the demand/supply dependency
-----------------------------------

                 Key: JBMICROCONT-214
                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-214
             Project: JBoss MicroContainer
          Issue Type: Feature Request
          Components: Kernel
    Affects Versions: JBossMC-2.0.0.Beta5
            Reporter: Ales Justin
         Assigned To: Ales Justin
            Priority: Minor
             Fix For: JBossMC-2.0.0.Beta6


Add a way to do a demand 'matching' on supplied items.
See forum thread for more details.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:29:01 2007
From: jira-events at lists.jboss.org (John Scott (JIRA))
Date: Mon, 29 Oct 2007 11:29:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1307) Update and expand
 documentation for decision tables to show actual uses
 for all keywords
Message-ID: <18860217.1193671741757.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update and expand documentation for decision tables to show actual uses for all keywords
----------------------------------------------------------------------------------------

                 Key: JBRULES-1307
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1307
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.2
         Environment: Drools 4.0.3, Rational Application Developer 7.0.0, XP SP2,
            Reporter: John Scott
            Priority: Minor


I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL, but reading the documentation for the UNLOOP keyword, this is the only description:

"Indicates that if there cell values in this column, the no-loop attribute should be set"

In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?

Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.

Thanks

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:41:01 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Mon, 29 Oct 2007 11:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMICROCONT-214) Extend the
 demand/supply dependency
In-Reply-To: <1166215.1193671741496.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24969461.1193672461600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-214?page=all ]

Ales Justin closed JBMICROCONT-214.
-----------------------------------

    Resolution: Done

> Extend the demand/supply dependency
> -----------------------------------
>
>                 Key: JBMICROCONT-214
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-214
>             Project: JBoss MicroContainer
>          Issue Type: Feature Request
>          Components: Kernel
>    Affects Versions: JBossMC-2.0.0.Beta5
>            Reporter: Ales Justin
>         Assigned To: Ales Justin
>            Priority: Minor
>             Fix For: JBossMC-2.0.0.Beta6
>
>
> Add a way to do a demand 'matching' on supplied items.
> See forum thread for more details.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:49:01 2007
From: jira-events at lists.jboss.org (John Scott (JIRA))
Date: Mon, 29 Oct 2007 11:49:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1307) Update and expand
 documentation for decision tables to show actual uses
 for all keywords
In-Reply-To: <18860217.1193671741757.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22053191.1193672941419.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1307?page=all ]

John Scott updated JBRULES-1307:
--------------------------------

    Description: 
I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL and using "no-loop" solved the problem, but reading the documentation for the UNLOOP keyword to turn on no-loop, this is the only description:

"Indicates that if there cell values in this column, the no-loop attribute should be set"

In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?

Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.

Thanks

  was:
I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL, but reading the documentation for the UNLOOP keyword, this is the only description:

"Indicates that if there cell values in this column, the no-loop attribute should be set"

In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?

Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.

Thanks


> Update and expand documentation for decision tables to show actual uses for all keywords
> ----------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1307
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1307
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.2
>         Environment: Drools 4.0.3, Rational Application Developer 7.0.0, XP SP2,
>            Reporter: John Scott
>            Priority: Minor
>
> I'm trying to implement a decision table for implementing some very simple rules.  Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method.  I had this happen when I implemented the same rules as a DRL and using "no-loop" solved the problem, but reading the documentation for the UNLOOP keyword to turn on no-loop, this is the only description:
> "Indicates that if there cell values in this column, the no-loop attribute should be set"
> In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive.  Which column?  What values?  The no-loop attribute SHOULD be set?
> Would it be possible to show an example of where and how each of these keywords would be used?  These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these.  I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this.
> Thanks

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 11:53:01 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Mon, 29 Oct 2007 11:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCOMMON-39) JDK logging levels
 don't match our standard levels
In-Reply-To: <33225096.1193249764768.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22563080.1193673181700.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCOMMON-39?page=all ]

David Lloyd closed JBCOMMON-39.
-------------------------------

    Resolution: Done

Committed in rev. 2661 of trunk.

> JDK logging levels don't match our standard levels
> --------------------------------------------------
>
>                 Key: JBCOMMON-39
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-39
>             Project: JBoss Common
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: common-logging-jdk
>    Affects Versions: 2.2.2.GA
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: 2.2.3.GA
>
>         Attachments: JBCOMMON-39.patch
>
>
> The JDK logger implementation in org.jboss.logging.jdk uses the JDK logging levels.  It should use levels that reflect the existing standard for JBossAS, since this is what users are used to, and to simplify the parsing of the logging XML config.
> Attached it a patch that does so.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 12:01:01 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Mon, 29 Oct 2007 12:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1205) Data shipped with
 NodeModified events different on different ccache instances in the cluster
In-Reply-To: <24023938.1193238901431.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14396829.1193673661960.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1205?page=all ]

Manik Surtani resolved JBCACHE-1205.
------------------------------------

    Fix Version/s:     (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)
       Resolution: Cannot Reproduce Bug

> Data shipped with NodeModified events different on different ccache instances in the cluster
> --------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1205
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1205
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 12:09:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 29 Oct 2007 12:09:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-612) ChannelFactory should
 have only channel create methods
Message-ID: <1245470.1193674141792.JavaMail.jira@cloud.prod.atl2.jboss.com>

ChannelFactory should have only channel create methods
------------------------------------------------------

                 Key: JGRP-612
                 URL: http://jira.jboss.com/jira/browse/JGRP-612
             Project: JGroups
          Issue Type: Task
    Affects Versions: 2.5, 2.6, 2.7, 2.x
            Reporter: Vladimir Blagojevic
         Assigned To: Bela Ban
             Fix For: 3.0


ChannelFactory should not have setMultiplexerConfig methods but rather only create channel methods. Multiplexer configuration can be initialized through implementors constructor. 

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 12:15:01 2007
From: jira-events at lists.jboss.org (Jason T. Greene (JIRA))
Date: Mon, 29 Oct 2007 12:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBCACHE-704) Externalise the TM
 used in the test suite so the TM can be injected when running tests.
In-Reply-To: <32285530.1153238351263.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26001158.1193674501761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-704?page=all ]

Jason T. Greene closed JBCACHE-704.
-----------------------------------

    Fix Version/s: 2.0.0.BETA1
                       (was: 2.1.0.GA)
                       (was: 2.1.0.CR1)
       Resolution: Done

> Externalise the TM used in the test suite so the TM can be injected when running tests.
> ---------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-704
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-704
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Jason T. Greene
>             Fix For: 2.0.0.BETA1
>
>
> Allows for QA to certify JBC on other TMs like JBossTS and JBossTM.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:01:01 2007
From: jira-events at lists.jboss.org (Matthew Sandoz (JIRA))
Date: Mon, 29 Oct 2007 13:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (GPD-183) Cut/Copy/Paste of
 transitions and nodes in the process designer
Message-ID: <26128738.1193677261486.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cut/Copy/Paste of transitions and nodes in the process designer
---------------------------------------------------------------

                 Key: GPD-183
                 URL: http://jira.jboss.com/jira/browse/GPD-183
             Project: JBoss jBPM GPD
          Issue Type: Feature Request
          Components: jpdl
            Reporter: Matthew Sandoz
         Assigned To: Koen Aers


It would be very useful to support cut/copy/paste in the process designer. These operations would have the challenge of creating new element names where there were conflicts and determining which transitions to carry along - only connected transitions - that is those whose source and target nodes are also in the selection.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:08:01 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Mon, 29 Oct 2007 13:08:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1090) NPE when
 combining AOP and EJB3 interceptors
Message-ID: <21367962.1193677681731.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE when combining AOP and EJB3 interceptors
--------------------------------------------

                 Key: EJBTHREE-1090
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1090
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA
            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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:10:02 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Mon, 29 Oct 2007 13:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20018066.1193677802330.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic updated JBMESSAGING-1099:
-----------------------------------------

    Description: 
When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.

HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

  was:Need to investigate


> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.
> HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:21:01 2007
From: jira-events at lists.jboss.org (Seth Wilcox (JIRA))
Date: Mon, 29 Oct 2007 13:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3275) Can't chain ldap
 login modules together using useFirstPass=password-stacking
Message-ID: <24519741.1193678461452.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3275?page=all ]

Seth Wilcox updated JBAS-3275:
------------------------------

    Attachment: LDAPAuth.patch

Patch to fix password stacking in LDAPExtLoginModule on version 4.0.5 GA

> Can't chain ldap login modules together using useFirstPass=password-stacking
> ----------------------------------------------------------------------------
>
>                 Key: JBAS-3275
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3275
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>         Attachments: LDAPAuth.patch
>
>
> The way roles are pulled in from the authentication phase validatePassword callback precludes chaining of ldap login modules. If one server does authentication and another authorization this cannot be configured to work currently.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:32:01 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Mon, 29 Oct 2007 13:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11136557.1193679121478.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12384887 ] 
            
Scott M Stark commented on JBAS-4902:
-------------------------------------

Attach the jaxrpc/jbws128 test  ear or describe how to build it. The java module is an issue with java application client container not being started that being worked on. 

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 13:44:04 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Mon, 29 Oct 2007 13:44:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JGRP-613) Access to
 NAKACK#rebroadcast_digest field needs a lock
Message-ID: <8602308.1193679844347.JavaMail.jira@cloud.prod.atl2.jboss.com>

Access to NAKACK#rebroadcast_digest field needs a lock
------------------------------------------------------

                 Key: JGRP-613
                 URL: http://jira.jboss.com/jira/browse/JGRP-613
             Project: JGroups
          Issue Type: Bug
    Affects Versions: 2.6
            Reporter: Vladimir Blagojevic
         Assigned To: Bela Ban
            Priority: Minor
             Fix For: 2.6


It seems that rebroadcast_digest field of NAKACK  is accessed by multiple threads which step over each other leading to a consequences below.
This is very hard to reproduce and I have seen it only a few times so far.



-------------------------------------------------------
GMS: address is 127.0.0.1:2528
-------------------------------------------------------
11141 [INFO][main] ConcurrentStateTransferTest: - Thread for channel 127.0.0.1:2528[A] started
15250 [INFO][A] ConcurrentStateTransferTest: - channel.getState at A127.0.0.1:2518 returned false
15297 [INFO][Multiplexer,udp,127.0.0.1:2520] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2520)]: received 127.0.0.1:2518
15297 [INFO][Multiplexer,udp,127.0.0.1:2524] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2524)]: received 127.0.0.1:2518
15297 [INFO][Multiplexer,udp,127.0.0.1:2518] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2518)]: received 127.0.0.1:2518
15297 [INFO][Multiplexer,udp,127.0.0.1:2528] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2528)]: received 127.0.0.1:2518
15328 [ERROR][OOB,udp,127.0.0.1:2520] UDP: - failed handling incoming message
java.lang.NullPointerException
	at org.jgroups.protocols.pbcast.NAKACK.rebroadcastMessages(NAKACK.java:1036)
	at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:620)
	at org.jgroups.protocols.UNICAST.down(UNICAST.java:434)
	at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317)
	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:813)
	at org.jgroups.protocols.FC.down(FC.java:370)
	at org.jgroups.protocols.FRAG2.down(FRAG2.java:175)
	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:318)
	at org.jgroups.protocols.pbcast.FLUSH.handleFlushReconcile(FLUSH.java:455)
	at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:337)
	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:258)
	at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
	at org.jgroups.protocols.FC.up(FC.java:408)
	at org.jgroups.protocols.pbcast.GMS.up(GMS.java:742)
	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
	at org.jgroups.protocols.UNICAST.up(UNICAST.java:264)
	at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:798)
	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:662)
	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
	at org.jgroups.protocols.FD.up(FD.java:322)
	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308)
	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1461)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	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

        


From jira-events at lists.jboss.org  Mon Oct 29 14:17:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 14:17:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8338154.1193681821851.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

Brian Stansberry updated JBAS-4838:
-----------------------------------

    Attachment: updated-29-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section3+-+Clustered_Entity_EJBs.odt

My edits attached.

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt, updated-29-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section3+-+Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 14:17:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 14:17:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4838) TECH REVIEW:
 Clustering - Chapter1 - Section3 - Clustered Entity EJBs
In-Reply-To: <18719134.1192167304169.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1322352.1193681822065.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4838?page=all ]

Brian Stansberry reassigned JBAS-4838:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

> TECH REVIEW:  Clustering - Chapter1 - Section3 - Clustered Entity EJBs
> ----------------------------------------------------------------------
>
>                 Key: JBAS-4838
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4838
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter1 - Section3 - Clustered_Entity_EJBs.odt, updated-29-10-2007-JBAS-422+-+Clustering+-+Chapter1+-+Section3+-+Clustered_Entity_EJBs.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 14:19:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 14:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24742704.1193681941900.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry reassigned JBAS-4841:
--------------------------------------

    Assignee: Brian Stansberry  (was: Galder Zamarreno)

Assigning to myself, as Galder is on vacation.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 15:41:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Mon, 29 Oct 2007 15:41:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-3075) ClassLoading code
	out of sync.
Message-ID: <29991406.1193686861617.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3075?page=all ]

Dimitris Andreadis updated JBAS-3075:
-------------------------------------

    Fix Version/s: JBossAS-5.0.0.CR1
                       (was:  JBossAS-5.0.0.Beta3)

> ClassLoading code out of sync.
> ------------------------------
>
>                 Key: JBAS-3075
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3075
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>            Reporter: Adrian Brock
>             Fix For: JBossAS-5.0.0.CR1
>
>
> The classloading code is out-of-sync between jboss-4.0.x and jboss-head.
> Looks like all the changes/fixes have not been applied in head.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:01:02 2007
From: jira-events at lists.jboss.org (Adam Lewandowski (JIRA))
Date: Mon, 29 Oct 2007 16:01:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1308) getFactHandle with
 equality-based assert behavior
Message-ID: <3690771.1193688062726.JavaMail.jira@cloud.prod.atl2.jboss.com>

getFactHandle with equality-based assert behavior
-------------------------------------------------

                 Key: JBRULES-1308
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1308
             Project: JBoss Drools
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 4.0.3
            Reporter: Adam Lewandowski


If I set my rule base to use equality-based assert behavior, I'm expecting to be able to use the getFactHandle(object) method to retrieve a previously asserted fact by providing an equivalent (by equals() and hashCode()) object as an argument. This appears to not be the case, as AbstractWorkingMemory uses it's identityMap and associated IdentityAssertMapComparator to do the getFactHandle lookup instead of the assertMap and EqualityAssertMapComparator. This causes the lookup to be done with the system hashCode() method and not the overridden version supplied in my fact class. The lookup thus fails and returns null. 

See attached unit test.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:03:01 2007
From: jira-events at lists.jboss.org (Adam Lewandowski (JIRA))
Date: Mon, 29 Oct 2007 16:03:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBRULES-1308) getFactHandle with
 equality-based assert behavior
In-Reply-To: <3690771.1193688062726.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4829321.1193688181452.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1308?page=all ]

Adam Lewandowski updated JBRULES-1308:
--------------------------------------

    Attachment: GetFactHandleWithEqualityTest.java

Unit test demonstrating expected behavior

> getFactHandle with equality-based assert behavior
> -------------------------------------------------
>
>                 Key: JBRULES-1308
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1308
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>            Reporter: Adam Lewandowski
>         Attachments: GetFactHandleWithEqualityTest.java
>
>
> If I set my rule base to use equality-based assert behavior, I'm expecting to be able to use the getFactHandle(object) method to retrieve a previously asserted fact by providing an equivalent (by equals() and hashCode()) object as an argument. This appears to not be the case, as AbstractWorkingMemory uses it's identityMap and associated IdentityAssertMapComparator to do the getFactHandle lookup instead of the assertMap and EqualityAssertMapComparator. This causes the lookup to be done with the system hashCode() method and not the overridden version supplied in my fact class. The lookup thus fails and returns null. 
> See attached unit test.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:27:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8431331.1193689621820.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=comments#action_12384936 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1083:
-----------------------------------------------

EJB Tests Before Fixes:

Tests,Failures,Errors,Success rate
375,16,198,42.93%

After:

Tests,Failures,Errors,Success rate
375,31,98,65.60%

No parsing errors remain in EJB3 testsuite - 

* Start Server
shell> ./run.sh -c all > /tmp/jboss_xml_schema.txt

* Run EJB tests
shell> ./build.sh -f build-test.xml main no-start-jboss-ejb-tests

* Ensure no parse errors:
shell> grep 'but the target namespace of the schema' /tmp/jboss_xml_schema.txt


> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:37:02 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:37:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1083) Resolve
 testsuite issues introduced by metadata refactoring
In-Reply-To: <29125326.1193517015170.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5174663.1193690222138.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1083?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1083.
-------------------------------------------

    Resolution: Done

This issue addresses only parse errors related to new jboss.xml namespace

> Resolve testsuite issues introduced by metadata refactoring
> -----------------------------------------------------------
>
>                 Key: EJBTHREE-1083
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1083
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: HEAD
>
>
> This is a supertask used to track testsuite failures suspected to have arisen from the metamodel refactoring

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:37:03 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:37:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1084) Resolve Failure:
 org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
In-Reply-To: <8059247.1193517241440.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9565169.1193690223999.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1084?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1084.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
> -------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1084
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1084
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.circulardependency.unit.IgnoreDependencyTestCase
> JAR does not deploy due to error:
> Caused by: org.xml.sax.SAXException: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]
> @IgnoreDependency is not used in this test, but is defined in jboss.xml

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:37:04 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:37:04 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1085) Resolve Failure:
 org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
In-Reply-To: <26637097.1193517781512.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15409021.1193690224257.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1085?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1085.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1085
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1085
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.classloader.unit.ClassloaderUnitTestCase
> Error on JAR deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1086) Resolve Failure:
 org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
In-Reply-To: <12693205.1193518021659.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8814352.1193690341821.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1086?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1086.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
> -----------------------------------------------------------------------
>
>                 Key: EJBTHREE-1086
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1086
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase
> Error on JAR Deployment:
> Caused by: java.lang.RuntimeException: org.jboss.xb.binding.JBossXBException: Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1087) Resolve Failure:
 org.jboss.ejb3.test.container.unit.ContainerTestCase
In-Reply-To: <27563923.1193518201480.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32058624.1193690341966.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1087?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1087.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.container.unit.ContainerTestCase
> ---------------------------------------------------------------------
>
>                 Key: EJBTHREE-1087
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1087
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.container.unit.ContainerTestCase
> Error on JAR Deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:02 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1088) Resolve Failure:
 org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
In-Reply-To: <27878026.1193518561424.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27914710.1193690342119.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1088?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1088.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
> ----------------------------------------------------------------
>
>                 Key: EJBTHREE-1088
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1088
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell>  ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
> Error on Deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:39:03 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:39:03 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1089) Resolve Failure:
 org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
In-Reply-To: <3816689.1193518861438.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9043514.1193690343101.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1089?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1089.
-------------------------------------------

    Resolution: Done

Closed by parent issue EJBTHREE-1083

> Resolve Failure: org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
> ---------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1089
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1089
>             Project: EJB 3.0
>          Issue Type: Sub-task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> shell> ./build.sh -f build-test.xml one-test -Dtest=org.jboss.ejb3.test.dependency.unit.DependencyUnitTestCase
> Error on JAR Deployment:
> Failed to parse source: TargetNamespace.1: Expecting namespace 'http://java.sun.com/xml/ns/javaee', but the target namespace of the schema document is 'http://www.jboss.com/xml/ns/javaee'. @ http://www.jboss.org/j2ee/schema/jboss_5_0.xsd[9,27]

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:50:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 16:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12670497.1193691001628.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Brian Stansberry updated JBAS-4839:
-----------------------------------

    Attachment: updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part1.odt
                updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part2.odt

My edits attached.  OpenOffice kept crashing, so I tried to minimize this by breaking the document in half. Didn't help, but that's why there are two documents attached.

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part1.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part2.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:50:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 16:50:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4839) TECH REVIEW:
 Chapter1 - Section4 - Clustering HTTP Services
In-Reply-To: <18464381.1192167304422.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28646052.1193691002043.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4839?page=all ]

Brian Stansberry reassigned JBAS-4839:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

> TECH REVIEW:  Chapter1 - Section4 - Clustering HTTP Services
> ------------------------------------------------------------
>
>                 Key: JBAS-4839
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4839
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Chapter1 - Section4 - Clustering_HTTP_Services.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part1.odt, updated-29-10-2007-JBAS-422+-+Chapter1+-+Section4+-+Clustering_HTTP_Services-part2.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 16:54:35 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Mon, 29 Oct 2007 16:54:35 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1091) Ensure all
 metadata files are included in the Schema test case
Message-ID: <18825902.1193691275979.JavaMail.jira@cloud.prod.atl2.jboss.com>

Ensure all metadata files are included in the Schema test case
--------------------------------------------------------------

                 Key: EJBTHREE-1091
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1091
             Project: EJB 3.0
          Issue Type: Task
            Reporter: Andrew Lee Rubinger
         Assigned To: Andrew Lee Rubinger
             Fix For: HEAD


Be sure that all ejb-jar.xml, jboss.xml files in the EJB3 module are included in the tests of org.jboss.ejb3.test.schema.unit.SchemaTestCase

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 18:43:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Mon, 29 Oct 2007 18:43:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1712) Make producer
 tests go through the WS stack
In-Reply-To: <22960492.1190516351026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1760375.1193697781534.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=comments#action_12384961 ] 
            
Thomas Heute commented on JBPORTAL-1712:
----------------------------------------

Can we set that with a higher priority ? At the moment in the 2.6 testsuite, the 2 tests which are failing are related to this issue.
For that reason, we are getting used to ignore Hudson error reports which is not good.

> Make producer tests go through the WS stack
> -------------------------------------------
>
>                 Key: JBPORTAL-1712
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1712
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal WSRP
>    Affects Versions: 2.8 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>             Fix For: 2.8 Final, 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 18:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 18:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5998500.1193698741616.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry updated JBAS-4841:
-----------------------------------

    Attachment: updated-29.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt

My edits attached.  The items Galder mentioned in his last comment are done.

Note that the file attached to this JIRA did not include the JBoss Cache section.  I looked at it on-line and it looked pretty reasonable.  My only suggestion is that it include a reference or link to the main JBoss Cache 1.4.1.SP5 documentation, which of course is far more complete.  Same things goes for JGroups.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt, updated-29.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 18:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 18:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4841) TECH REVIEW:
 Chapter2 - JBossCache and JGroups Services
In-Reply-To: <26289179.1192167438493.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26863618.1193698741885.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4841?page=all ]

Brian Stansberry reassigned JBAS-4841:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assigning back to samson.

> TECH REVIEW: Chapter2 - JBossCache and JGroups Services
> -------------------------------------------------------
>
>                 Key: JBAS-4841
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4841
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering - Chapter2 - JBossCache_and_JGroups_Services.odt, updated-25.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt, updated-29.10.2007-JBAS-422+-+Clustering+-+Chapter2+-+JBossCache_and_JGroups_Services.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 19:53:01 2007
From: jira-events at lists.jboss.org (Jon Stevens (JIRA))
Date: Mon, 29 Oct 2007 19:53:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4918) for logging,
 server.xml references another variable than jboss-log4j.xml does
Message-ID: <20868859.1193701981886.JavaMail.jira@cloud.prod.atl2.jboss.com>

for logging, server.xml references another variable than jboss-log4j.xml does
-----------------------------------------------------------------------------

                 Key: JBAS-4918
                 URL: http://jira.jboss.com/jira/browse/JBAS-4918
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: JBossAS-4.2.0.GA
         Environment: all
            Reporter: Jon Stevens
         Assigned To: Scott M Stark


jboss-log4j.xml has this as default:

      <param name="File" value="${jboss.server.log.dir}/server.log"/>

jboss-web.deployer has this:

            <!-- Access logger -->
            <Valve className="org.apache.catalina.valves.AccessLogValve"
                prefix="localhost_access_log." suffix=".log"
                pattern="common" directory="${jboss.server.home.dir}/log" 
                resolveHosts="false" />

Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because

#1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir}
#2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value.

My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything.

jon

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 21:10:02 2007
From: jira-events at lists.jboss.org (John Gilbert (JIRA))
Date: Mon, 29 Oct 2007 21:10:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-615) NPE in Embedded
 Jboss when getCallerPrincipal method on SessionContext
Message-ID: <11451022.1193706602722.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-615?page=comments#action_12384972 ] 
            
John Gilbert commented on EJBTHREE-615:
---------------------------------------

What does "EJB 3 embedded is no longer supported." mean? 
Is something replacing it?

> NPE in Embedded Jboss when getCallerPrincipal method on SessionContext
> ----------------------------------------------------------------------
>
>                 Key: EJBTHREE-615
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-615
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC8 - FD
>            Reporter: Nicolai ?dum
>         Assigned To: Carlo de Wolf
>         Attachments: BugReportInterceptor.java
>
>
> The bug is pretty easy to create.
> Modify the CalculaterBean in the security example that is distributed with JBoss embedded like this
> import javax.annotation.Resource;
> import java.security.Principal;
> import javax.ejb.SessionContext;
> ..
> public class CalculatorBean implements Calculator
> {
> @Resource SessionContext ctx;	
> @RolesAllowed({"student"})
> public int subtract(int x, int y)
> {
> Principal caller = ctx.getCallerPrincipal(); //Nullpointer
> return x - y;
> }
> The exception
> full stacktrace: 
> javax.ejb.EJBException: java.lang.NullPointerException 
> at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) 
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) 
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:197) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:167) 
> at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:100) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:78) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) 
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) 
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:181) 
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79) 
> at $Proxy15.getSubscriberDetails(Unknown Source) 
> Another user has reported that is is possible to get the principal from org.jboss.security.SecurityAssociation.getPrincipal(), but not from the Session Context.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 21:13:01 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Mon, 29 Oct 2007 21:13:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1309) Gui refactoring
	and redesign
Message-ID: <2055807.1193706781420.JavaMail.jira@cloud.prod.atl2.jboss.com>

Gui refactoring and redesign 
-----------------------------

                 Key: JBRULES-1309
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1309
             Project: JBoss Drools
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Fernando Meyer
         Assigned To: Fernando Meyer




-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 23:11:21 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Mon, 29 Oct 2007 23:11:21 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (BPEL-282) Engine runs process
 instances in serie instead of in parallel
In-Reply-To: <7870750.1193112683491.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8980951.1193713881357.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/BPEL-282?page=comments#action_12384976 ] 
            
Alejandro Guizar commented on BPEL-282:
---------------------------------------

Currently, all start message listeners run on a single JMS session. Since JMS delivers messages one at a time per session, this feature may cause the perceived serial execution. I have made slight modifications which allow each start listener to run in a separate JMS session. This should enable parallel execution as far as the JMS connection and, ultimately, the available CPU cycles permit it.

Once I complete the QA procedure I will upload a new version of the jBPM BPEL binaries to the repository and mark the issue as resolved.

> Engine runs process instances in serie instead of in parallel
> -------------------------------------------------------------
>
>                 Key: BPEL-282
>                 URL: http://jira.jboss.com/jira/browse/BPEL-282
>             Project: JBoss jBPM BPEL
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>         Environment: RHEL
>            Reporter: Santiago Erquicia
>         Assigned To: Alejandro Guizar
>
> We are stress testing a BPEL process and we found out that the engine runs all the requests it receives in serie. That means that if there are two or more concurrent users of the system, one has to wait till the first process instance stops at some point (wait state) so the other request can be processed.
> On our test environment, we are calling a web service which is also calling another web service. The are connection problems with the second one, so from time to time the web service just times out. This means that a concurrent user has to wait for that time out, and whatever is left of that process instance, in order to be processed.
> On our JMeter test, the throughput keeps stable even if there number of request is bigger than the throughput of the BPEL engine. The result is that the time for response of each process request increases indefinitely if the usage is bigger than the throughput. This obviously doesn't scale at all for the processing requirement we are considering.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 23:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 23:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4919)
 HASingletonElectionPolicySimple
 does not handle heterogeneous topologies
Message-ID: <10465338.1193716621629.JavaMail.jira@cloud.prod.atl2.jboss.com>

HASingletonElectionPolicySimple does not handle heterogeneous topologies
------------------------------------------------------------------------

                 Key: JBAS-4919
                 URL: http://jira.jboss.com/jira/browse/JBAS-4919
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-5.0.0.Beta2
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


HASingletonElectionPolicySimple is just getting the current view from HAPartition and making a decision based on that, ignoring the fact that the service it's managing may not be running on all members of the cluster.

The HASingletonElectionPolicy API should be changed.  The isMasterReplica method should take (List<ClusterNode> newReplicants, int newViewID) rather than HAPartition.  The partition is provided via dependency injection at startup, no need to pass it in the method call. HASingletonElectionPolicySimple uses the provided replicants to make its decision, not the HAPartition view.

-- 
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

        


From jira-events at lists.jboss.org  Mon Oct 29 23:57:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Mon, 29 Oct 2007 23:57:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
In-Reply-To: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24674937.1193716621931.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4834?page=all ]

Brian Stansberry updated JBAS-4834:
-----------------------------------

    Attachment: JBAS-422+-+Clustering+-++Chapter1+-+Section4.5+-+HASingleton.odt

Attached is a new section that needs to be added. It should go just before the Clustered JMS section.

> TECH REVIEW: Clustering Guide - TRACKER
> ---------------------------------------
>
>                 Key: JBAS-4834
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422+-+Clustering+-++Chapter1+-+Section4.5+-+HASingleton.odt
>
>
> Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 00:01:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 00:01:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4920) Add section on
	HASingleton
Message-ID: <29549172.1193716861536.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add section on HASingleton
--------------------------

                 Key: JBAS-4920
                 URL: http://jira.jboss.com/jira/browse/JBAS-4920
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: Clustering
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Brian Stansberry
         Assigned To: samson kittoli


I've added a new section for a significant area that was missing, HASingleton; document is attached to the parent issue.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 00:27:01 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 30 Oct 2007 00:27:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18051090.1193718421511.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=all ]

Clebert Suconic closed JBMESSAGING-1099.
----------------------------------------

    Resolution: Done

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: 1.4.0.SP1, AS 5.0 Integration, EAP 4.3 Integration
>
>
> When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.
> HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 00:31:01 2007
From: jira-events at lists.jboss.org (Clebert Suconic (JIRA))
Date: Tue, 30 Oct 2007 00:31:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1099) Potential
 deadlock in shutting down server
In-Reply-To: <17284447.1191947480573.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22187280.1193718661750.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1099?page=comments#action_12384985 ] 
            
Clebert Suconic commented on JBMESSAGING-1099:
----------------------------------------------

The failure on ClusteredClientCrashTest is another case

> Potential deadlock in shutting down server
> ------------------------------------------
>
>                 Key: JBMESSAGING-1099
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1099
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Blocker
>             Fix For: AS 5.0 Integration, EAP 4.3 Integration, 1.4.0.SP1
>
>
> When the serverShutdown is happening on an MDB Container, handleClosing might be interrupted by an exception what will cause the ConnectionConsumer to hang.
> HandleClosing might fail because the ServerPeer is already is shutdown mode, or because the remote server was killed already.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 01:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 01:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9405442.1193723941696.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Brian Stansberry updated JBAS-4835:
-----------------------------------

    Attachment: updated-30-10-2007-JBAS-422+-+Clustering+-++Chapter1+-+Introduction.odt

My edits attached.

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: Brian Stansberry
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt, updated-30-10-2007-JBAS-422+-+Clustering+-++Chapter1+-+Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 01:59:01 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 01:59:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4835) TECH REVIEW:
 Clustering Guide - Chapter 1 - Introduction
In-Reply-To: <16547652.1192167303644.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12128236.1193723941902.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4835?page=all ]

Brian Stansberry reassigned JBAS-4835:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Assign back to samson.

> TECH REVIEW: Clustering Guide - Chapter 1 - Introduction
> --------------------------------------------------------
>
>                 Key: JBAS-4835
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4835
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422 - Clustering -  Chapter1 - Introduction.odt, updated-30-10-2007-JBAS-422+-+Clustering+-++Chapter1+-+Introduction.odt
>
>
> Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide
> 1. Open document in Open Office
> 2. Edit -> Changes -> Record
> 3. Edit the document
> 4. Save changes and reattach to this Jira
> It is important for track changes to be enabled so the re-write can be easily performed.
> http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 01:59:02 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 01:59:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4834) TECH REVIEW:
 Clustering Guide - TRACKER
In-Reply-To: <24150486.1192165863538.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14054570.1193723942106.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4834?page=all ]

Brian Stansberry reassigned JBAS-4834:
--------------------------------------

    Assignee: samson kittoli  (was: Brian Stansberry)

Done. :) Assigning back to samson.

> TECH REVIEW: Clustering Guide - TRACKER
> ---------------------------------------
>
>                 Key: JBAS-4834
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4834
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Clustering Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: samson kittoli
>         Assigned To: samson kittoli
>         Attachments: JBAS-422+-+Clustering+-++Chapter1+-+Section4.5+-+HASingleton.odt
>
>
> Issue tracker for the Clustering Guide

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:20:11 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:20:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-826) JBoss Remoting logs
 at ERROR and WARN in many places
Message-ID: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBoss Remoting logs at ERROR and WARN in many places
----------------------------------------------------

                 Key: JBREM-826
                 URL: http://jira.jboss.com/jira/browse/JBREM-826
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
            Reporter: Tim Fox
             Fix For: 2.4.0.Beta1 (Pinto)


In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

@main 08:01:30,648 INFO  [ServerManagement] Waiting for server to die
@main 08:01:30,953 INFO  [ServerManagement] server 1 killed and dead
@Timer-3 08:01:31,253 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,277 WARN  [ClientClusteredConnectionFactoryDelegate] org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:93)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 9 more
@Thread-9 08:01:31,299 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
SERVER 0 STDOUT: @Timer-4 08:01:31,301 ERROR [SocketClientInvoker] Got marshalling exception, exiting
SERVER 0 STDOUT: java.net.SocketException: end of file
SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
@Thread-9 08:01:31,320 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed sending disconnect for client lease for client with session ID 3j001-bj8ucn-f8e4sbxc-1-f8e4sbxd-2
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,345 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?cli

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:24:02 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:24:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-826) JBoss Remoting logs
 at ERROR and WARN in many places
In-Reply-To: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28680681.1193732642566.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-826?page=all ]

Tim Fox updated JBREM-826:
--------------------------

    Description: 
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

  was:
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

@main 08:01:30,648 INFO  [ServerManagement] Waiting for server to die
@main 08:01:30,953 INFO  [ServerManagement] server 1 killed and dead
@Timer-3 08:01:31,253 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,277 WARN  [ClientClusteredConnectionFactoryDelegate] org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:93)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 9 more
@Thread-9 08:01:31,299 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
SERVER 0 STDOUT: @Timer-4 08:01:31,301 ERROR [SocketClientInvoker] Got marshalling exception, exiting
SERVER 0 STDOUT: java.net.SocketException: end of file
SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
@Thread-9 08:01:31,320 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed sending disconnect for client lease for client with session ID 3j001-bj8ucn-f8e4sbxc-1-f8e4sbxd-2
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:01:31,345 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[c0f1ec, bisocket://localhost:2117](3j001-bj8ucn-f8e4sbxc-1-f8e4sby7-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2117/?cli

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.


> JBoss Remoting logs at ERROR and WARN in many places
> ----------------------------------------------------
>
>                 Key: JBREM-826
>                 URL: http://jira.jboss.com/jira/browse/JBREM-826
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tim Fox
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.
> JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.
> There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd
> Failover in JBoss Messaging is a good example.
> In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.
> However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:
> This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.
> If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.
> In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:36:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-826) JBoss Remoting logs
 at ERROR and WARN in many places
In-Reply-To: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32512115.1193733361749.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-826?page=all ]

Tim Fox updated JBREM-826:
--------------------------

    Description: 
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. 

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projects. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exception occurs.

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,571 INFO  [RMITestServer] kill() invoked - first deregistering from the rmi registry
SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,572 INFO  [RMITestServer] unregistered messaging_rmi_server_1 from registry
SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] unregistered naming_rmi_server_1 from registry
SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] Killing VM!!!!
@main 08:27:29,940 INFO  [ServerManagement] Waiting for server to die
SERVER 0 STDOUT: @Timer-4 08:27:30,084 ERROR [SocketClientInvoker] Got marshalling exception, exiting
SERVER 0 STDOUT: java.net.SocketException: end of file
SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
@main 08:27:30,241 INFO  [ServerManagement] server 1 killed and dead
@Timer-3 08:27:30,275 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
@Thread-9 08:27:30,318 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-9 08:27:30,338 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pqua-2
@Thread-9 08:27:30,360 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-10 08:27:30,532 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-10 08:27:30,551 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pss1-9
@Thread-10 08:27:30,570 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-9 08:27:30,600 ERROR [BisocketServerInvoker] unable to get secondary locator
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
        at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
        at org.jboss.remoting.Client.addListener(Client.java:921)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 14 more
@Thread-9 08:27:30,620 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-9 08:27:30,639 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5puat-k
@Thread-10 08:27:30,760 ERROR [BisocketServerInvoker] unable to get secondary locator
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
        at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
        at org.jboss.remoting.Client.addListener(Client.java:921)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
        at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
        ... 14 more
@Thread-10 08:27:30,780 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
@Thread-10 08:27:30,807 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pugn-p
@Thread-13 08:27:31,491 INFO  [FailoverCommandCenter] JBoss Messaging server failure detected - waiting for failover to complete...
@Thread-13 08:27:31,793 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
        at java.io.FilterInputStream.read(FilterInputStream.java:66)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
        at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
        at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:358)
        at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
        at org.jboss.remoting.Client.connect(Client.java:1525)
        at org.jboss.remoting.Client.connect(Client.java:462)
        at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:295)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:291)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
        at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
        at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
        at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
        at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:134)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
        at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
        at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
        at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
        at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
@Thread-13 08:27:31,801 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[682406, bisocket://localhost:2854](3j001-c12qds-f8e5pqu9-1-f8e5puj4-v)] failed to ping to server: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is:
        java.net.SocketException: Connection reset
@Thread-2 08:27:31,820 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
        at java.io.FilterInputStream.read(FilterInputStream.java:66)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.finalize(ClientClusteredConnectionFactoryDelegate.java:158)
        at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:418)
@Thread-2 08:27:31,839 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2854/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=fals

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

The customer says "Why was JBoss reporting errors when everything was ok?"

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

  was:
In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.

JBR is a toolkit and should not log errors it does not handle. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exeception occurs.

There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projectsd

Failover in JBoss Messaging is a good example.

In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.

However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:

This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.

If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.

In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.


> JBoss Remoting logs at ERROR and WARN in many places
> ----------------------------------------------------
>
>                 Key: JBREM-826
>                 URL: http://jira.jboss.com/jira/browse/JBREM-826
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tim Fox
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.
> JBR is a toolkit and should not log errors it does not handle. 
> There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projects. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exception occurs.
> Failover in JBoss Messaging is a good example.
> In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.
> However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,571 INFO  [RMITestServer] kill() invoked - first deregistering from the rmi registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,572 INFO  [RMITestServer] unregistered messaging_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] unregistered naming_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] Killing VM!!!!
> @main 08:27:29,940 INFO  [ServerManagement] Waiting for server to die
> SERVER 0 STDOUT: @Timer-4 08:27:30,084 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> SERVER 0 STDOUT: java.net.SocketException: end of file
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
> SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
> SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
> SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
> @main 08:27:30,241 INFO  [ServerManagement] server 1 killed and dead
> @Timer-3 08:27:30,275 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: end of file
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
>         at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> @Thread-9 08:27:30,318 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,338 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pqua-2
> @Thread-9 08:27:30,360 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,532 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,551 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pss1-9
> @Thread-10 08:27:30,570 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,600 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-9 08:27:30,620 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,639 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5puat-k
> @Thread-10 08:27:30,760 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-10 08:27:30,780 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,807 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pugn-p
> @Thread-13 08:27:31,491 INFO  [FailoverCommandCenter] JBoss Messaging server failure detected - waiting for failover to complete...
> @Thread-13 08:27:31,793 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
>         at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:358)
>         at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
>         at org.jboss.remoting.Client.connect(Client.java:1525)
>         at org.jboss.remoting.Client.connect(Client.java:462)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:295)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:291)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
>         at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:134)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
>         at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
>         at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> @Thread-13 08:27:31,801 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[682406, bisocket://localhost:2854](3j001-c12qds-f8e5pqu9-1-f8e5puj4-v)] failed to ping to server: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is:
>         java.net.SocketException: Connection reset
> @Thread-2 08:27:31,820 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.finalize(ClientClusteredConnectionFactoryDelegate.java:158)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:418)
> @Thread-2 08:27:31,839 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2854/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=fals
> This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.
> The customer says "Why was JBoss reporting errors when everything was ok?"
> If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.
> In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 04:54:01 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Tue, 30 Oct 2007 04:54:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-826) JBoss Remoting
 logs at ERROR and WARN in many places
In-Reply-To: <29575835.1193732411600.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17971820.1193734441899.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-826?page=comments#action_12385011 ] 
            
Tim Fox commented on JBREM-826:
-------------------------------

I can supress the error messages using the following log4j snippet:


   <category name="org.jboss.remoting.transport.socket.SocketClientInvoker">
      <priority value="FATAL"/>
   </category>

   <category name="org.jboss.remoting.transport.bisocket.BisocketServerInvoker">
      <priority value="FATAL"/>
   </category>

   <category name="org.jboss.remoting.Client">
      <priority value="FATAL"/>
   </category>

   <category name="org.jboss.remoting.LeasePinger">
      <priority value="FATAL"/>
   </category>

This works nicely - but it might hide valid error conditions

> JBoss Remoting logs at ERROR and WARN in many places
> ----------------------------------------------------
>
>                 Key: JBREM-826
>                 URL: http://jira.jboss.com/jira/browse/JBREM-826
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Tim Fox
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> In many places JBoss Remoting logs at ERROR or WARN which seem inappropriate.
> JBR is a toolkit and should not log errors it does not handle. 
> There is a general principle of you shouldn't log unless you handle the error. If you just pass it up, don't log. This principle is adhered to in JBoss AS for example, and IMHO should be used throughout all JBoss projects. If every toolkit being used in the chain logged the same error then you end up with a complete mess in the logs every time an exception occurs.
> Failover in JBoss Messaging is a good example.
> In JBM we detect failure of the remoting connection via the connection listener, and transparently reconnect on a different node. In this case, from the users POV *no error* has occurred - the process should be completely seamless.
> However JBoss Remoting spews a load of exceptions to the logs at ERROR and WARN, for example:
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,571 INFO  [RMITestServer] kill() invoked - first deregistering from the rmi registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,572 INFO  [RMITestServer] unregistered messaging_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] unregistered naming_rmi_server_1 from registry
> SERVER 1 STDOUT: @RMI TCP Connection(2)-127.0.0.1 08:27:29,573 INFO  [RMITestServer] Killing VM!!!!
> @main 08:27:29,940 INFO  [ServerManagement] Waiting for server to die
> SERVER 0 STDOUT: @Timer-4 08:27:30,084 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> SERVER 0 STDOUT: java.net.SocketException: end of file
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
> SERVER 0 STDOUT:        at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
> SERVER 0 STDOUT:        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
> SERVER 0 STDOUT:        at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
> SERVER 0 STDOUT:        at java.util.TimerThread.mainLoop(Timer.java:512)
> SERVER 0 STDOUT:        at java.util.TimerThread.run(Timer.java:462)
> @main 08:27:30,241 INFO  [ServerManagement] server 1 killed and dead
> @Timer-3 08:27:30,275 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: end of file
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:577)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.ConnectionValidator.doCheckConnection(ConnectionValidator.java:133)
>         at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:308)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> @Thread-9 08:27:30,318 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,338 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pqua-2
> @Thread-9 08:27:30,360 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,532 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,551 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pss1-9
> @Thread-10 08:27:30,570 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed to ping to server: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,600 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-9 08:27:30,620 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-9 08:27:30,639 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5puat-k
> @Thread-10 08:27:30,760 ERROR [BisocketServerInvoker] unable to get secondary locator
> org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.getSecondaryLocator(BisocketClientInvoker.java:538)
>         at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.createControlConnection(BisocketServerInvoker.java:228)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:402)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.addCallbackListener(Client.java:1703)
>         at org.jboss.remoting.Client.addListener(Client.java:921)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:237)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:312)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.establishCallback(ClientClusteredConnectionFactoryDelegate.java:99)
>         at org.jboss.jms.client.remoting.ConnectionFactoryCallbackHandler$CallbackConnectionListener.handleConnectionException(ConnectionFactoryCallbackHandler.java:105)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> Caused by: java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:519)
>         at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:420)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:815)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
>         ... 14 more
> @Thread-10 08:27:30,780 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2840/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
> @Thread-10 08:27:30,807 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[53ab04, bisocket://localhost:2840](3j001-c12qds-f8e5pqu9-1-f8e5pqwg-3)] failed sending disconnect for client lease for client with session ID 3j001-c12qds-f8e5pqu9-1-f8e5pugn-p
> @Thread-13 08:27:31,491 INFO  [FailoverCommandCenter] JBoss Messaging server failure detected - waiting for failover to complete...
> @Thread-13 08:27:31,793 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283)
>         at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:117)
>         at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:358)
>         at org.jboss.remoting.Client.setupClientLease(Client.java:1625)
>         at org.jboss.remoting.Client.connect(Client.java:1525)
>         at org.jboss.remoting.Client.connect(Client.java:462)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:295)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:291)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
>         at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:134)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
>         at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
>         at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
>         at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
>         at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:452)
> @Thread-13 08:27:31,801 WARN  [LeasePinger] LeasePinger[SocketClientInvoker[682406, bisocket://localhost:2854](3j001-c12qds-f8e5pqu9-1-f8e5puj4-v)] failed to ping to server: Failed to communicate.  Problem during marshalling/unmarshalling; nested exception is:
>         java.net.SocketException: Connection reset
> @Thread-2 08:27:31,820 ERROR [SocketClientInvoker] Got marshalling exception, exiting
> java.net.SocketException: Connection reset
>         at java.net.SocketInputStream.read(SocketInputStream.java:168)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:1000)
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:574)
>         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:413)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         at org.jboss.remoting.Client.invoke(Client.java:1634)
>         at org.jboss.remoting.Client.invoke(Client.java:548)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.removeCallback(ClientClusteredConnectionFactoryDelegate.java:152)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.closeCallback(ClientClusteredConnectionFactoryDelegate.java:168)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.finalize(ClientClusteredConnectionFactoryDelegate.java:158)
>         at org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$FinalizerShutdownHook.run(ClientClusteredConnectionFactoryDelegate.java:418)
> @Thread-2 08:27:31,839 WARN  [Client] unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://localhost:2854/?clientLeasePeriod=10000&clientMaxPoolSize=200&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=fals
> This completely messes up the logs and the customer believes something has gone wrong, phones support and they waste a lot of time trying to work out what the problem is, when actually there is no problem and this is perfectly successful failover from one node to another, but to the customer they have a flawed experience.
> The customer says "Why was JBoss reporting errors when everything was ok?"
> If anything is to be logged in these cases it should be at DEBUG level at the highest, so it can be easily supressed in the standard log4j config.
> In the mean-time if you could provide a log4j config which supresses these messages for the specific classes so they don't appear even on ERROR level that would be much appreciated.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 05:02:01 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 30 Oct 2007 05:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1707) New
 UserModule/RoleModule finders
In-Reply-To: <6276632.1190228243214.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9649873.1193734921906.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1707?page=all ]

Thomas Heute updated JBPORTAL-1707:
-----------------------------------

    Fix Version/s: 2.8 Final

> New UserModule/RoleModule finders
> ---------------------------------
>
>                 Key: JBPORTAL-1707
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1707
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Security
>    Affects Versions: 2.6.1 Final
>            Reporter: Andrew Oliver
>         Assigned To: Boleslaw Dawidowicz
>             Fix For: 2.8 Final
>
>
> While working with clients using the portal API some efficiency issues with regards to finders have become apparent:
> It is presently possible to find users having a role by calling MembershipModule.getUsers(role).  However it is not possible to get a list of users with a set of roles, a list of users who do NOT have a role or set of roles.  (there are ways in both HQL and LDAP to construct each type of query).  I suggest something similar to hibernate conditions.
> MembershipModule.getUsers().addCondition(
>    Condition.and(
>         Condition.not(roleSet), Condition.with(roleSet)
>    )
> )
> this would result in roughly:
> from Users where roles in (:roleSet) and roles not in (:roleSet2)
> and something like 
> (& (|(role=roleName)(role=roleName)  )
>      (&(!role=roleName)(!role=roleName) )
> )
> in LDAP
> the attribute name can be based on the type.  As it stands you have to do something like:
> 		try {			
> 			Role roleApproved = rolemodule.findRoleByName("approved");
> 			Role roleUsers = rolemodule.findRoleByName("User");
> 			//todo create transient wrapper set.
> 		    Set users = membership.getUsers(roleUsers);
> 		    dirtyStinkyHackToGetAroundPortalAPIBugACO(users);
> 		    System.err.println("Total number of users with User Role  : " + users.size() );
> 		    Set temp = new HashSet();
> 		    temp = dirtyStinkyHackToGetAroundPortalAPIBugACO(users); //because the hibernate set doesn't have removeall
> 		    users = temp;
> 			Set usersApproved = membership.getUsers(roleApproved);
> 			System.err.println("number of users with approved role: "+usersApproved.size());
> 			users.removeAll(usersApproved);
> 			System.err.println("Total number of users with User Role and NO approved role : " + users.size() );
> 			Map profiles = profiles(users);
> 			response.setRenderParameter("op", "new");
> 			request.getPortletSession().setAttribute("users", users);
> 			request.getPortletSession().setAttribute("profiles", profiles);
> 		} catch (IdentityException e) {
> 			//todo type this and catch it up higher to make a 
> 			//smarter error message
> 			throw new RuntimeException(e);
> 		}
> 	private Map profiles(Set users) throws IdentityException {
> 		Iterator i = users.iterator();
> 		Map retval = new HashMap();
> 		while(i.hasNext()) {
> 			User user = (User) i.next();
> 			retval.put(user, profileModule.getProperties(user));
> 		}
> 		return retval;
> 	}
> 	
> 	private Set dirtyStinkyHackToGetAroundPortalAPIBugACO(Set users) {
> 		Iterator i = users.iterator();
> 		Set retval = new HashSet();
> 		while(i.hasNext()) {
> 			User u = (User)i.next();
> 			u.getUserName();
> 			retval.add(u);
> 		}
> 		return retval;
> 	}
> Just to get the list of users who DONT have the "approved" role.  For our immediate needs:
> UserModule.getUsersWithout(role) would work...until next time.
> -Andy

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 05:02:02 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Tue, 30 Oct 2007 05:02:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1713) add proxy
 capabilities to the portal build
In-Reply-To: <12423891.1190660381147.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24203208.1193734922086.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1713?page=all ]

Thomas Heute updated JBPORTAL-1713:
-----------------------------------

        Fix Version/s: 2.6.3 Final
    Affects Version/s: 2.6.2 Final
                           (was: 2.6.3 Final)

> add proxy capabilities to the portal build
> ------------------------------------------
>
>                 Key: JBPORTAL-1713
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1713
>             Project: JBoss Portal
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.2 Final
>            Reporter: Andrew Oliver
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: build-proxy.patch
>
>
> This patch will add proxy settings to the build
> i.e. 
> C:\Users\oliveran\portal\JBoss_Portal_Branch_2_6\build>build.bat -Dproxy.host=localhost -Dproxy.port=5865 -Dproxy.username=xxx -Dproxy.password=xxx

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 05:24:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 05:24:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4918) for logging,
 server.xml references another variable than jboss-log4j.xml does
In-Reply-To: <20868859.1193701981886.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14039219.1193736241899.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4918?page=all ]

Dimitris Andreadis updated JBAS-4918:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA
         Assignee: Dimitris Andreadis  (was: Scott M Stark)

> for logging, server.xml references another variable than jboss-log4j.xml does
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-4918
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4918
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: all
>            Reporter: Jon Stevens
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.2.3.GA
>
>
> jboss-log4j.xml has this as default:
>       <param name="File" value="${jboss.server.log.dir}/server.log"/>
> jboss-web.deployer has this:
>             <!-- Access logger -->
>             <Valve className="org.apache.catalina.valves.AccessLogValve"
>                 prefix="localhost_access_log." suffix=".log"
>                 pattern="common" directory="${jboss.server.home.dir}/log" 
>                 resolveHosts="false" />
> Now, because those two variables are different, I can't easily setup logging to say /var/log/jboss because
> #1. there is two different variables to define: ${jboss.server.home.dir} and ${jboss.server.log.dir}
> #2. the access logger has /log hard coded to the end of the directory attribute which makes it impossible to set the two variables to the same value.
> My preference would be that the default is made to a single variable ${jboss.server.log.dir} which can control everything.
> jon

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:24:01 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 30 Oct 2007 06:24:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4921) Web service
 deployment: web.xml modified to web.xml.org - Subsequent runs fail
Message-ID: <12195707.1193739841403.JavaMail.jira@cloud.prod.atl2.jboss.com>

Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
------------------------------------------------------------------------------

                 Key: JBAS-4921
                 URL: http://jira.jboss.com/jira/browse/JBAS-4921
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Web Services
    Affects Versions: JBossAS-4.2.1.GA
            Reporter: Heiko Braun
         Assigned To: Heiko Braun


See associated JBossWS issue

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:26:01 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 30 Oct 2007 06:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4921) Web service
 deployment: web.xml modified to web.xml.org - Subsequent runs fail
In-Reply-To: <12195707.1193739841403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13918070.1193739961526.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4921?page=all ]

Heiko Braun updated JBAS-4921:
------------------------------

    Fix Version/s: JBossAS-4.2.3.GA

> Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4921
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4921
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Heiko Braun
>         Assigned To: Heiko Braun
>             Fix For: JBossAS-4.2.3.GA
>
>
> See associated JBossWS issue

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:26:01 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Tue, 30 Oct 2007 06:26:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4921) Web service
 deployment: web.xml modified to web.xml.org - Subsequent runs fail
In-Reply-To: <12195707.1193739841403.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20702312.1193739961673.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4921?page=all ]

Heiko Braun resolved JBAS-4921.
-------------------------------

    Resolution: Done

> Web service deployment: web.xml modified to web.xml.org - Subsequent runs fail
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-4921
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4921
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Heiko Braun
>         Assigned To: Heiko Braun
>             Fix For: JBossAS-4.2.3.GA
>
>
> See associated JBossWS issue

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:53:10 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 06:53:10 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4922) NPE in
	AssemblyDescriptorMetaData
Message-ID: <21462601.1193741590212.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE in AssemblyDescriptorMetaData
---------------------------------

                 Key: JBAS-4922
                 URL: http://jira.jboss.com/jira/browse/JBAS-4922
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 06:55:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 06:55:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4922) NPE in
	AssemblyDescriptorMetaData
In-Reply-To: <21462601.1193741590212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10882342.1193741701499.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4922?page=all ]

Thomas Diesler updated JBAS-4922:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test

11:47:39,226 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=ejb/ConfidentialSLSB,service=EJB state=Configured mode=Manual requiredState=Create
java.lang.NullPointerException
        at org.jboss.metadata.AssemblyDescriptorMetaData.getPrincipalVersusRolesMap(AssemblyDescriptorMetaData.java:126)
        at org.jboss.ejb.plugins.SecurityInterceptor.setContainer(SecurityInterceptor.java:132)
        at org.jboss.ejb.SessionContainer.createInterceptors(SessionContainer.java:374)
        at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:182)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:267)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
        at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)

         Assignee: Scott M Stark

> NPE in AssemblyDescriptorMetaData
> ---------------------------------
>
>                 Key: JBAS-4922
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4922
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> 11:47:39,226 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=ejb/ConfidentialSLSB,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at org.jboss.metadata.AssemblyDescriptorMetaData.getPrincipalVersusRolesMap(AssemblyDescriptorMetaData.java:126)
>         at org.jboss.ejb.plugins.SecurityInterceptor.setContainer(SecurityInterceptor.java:132)
>         at org.jboss.ejb.SessionContainer.createInterceptors(SessionContainer.java:374)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:182)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:267)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
>         at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:02:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4856) Web Services
 regression after update to new metadata model
In-Reply-To: <28485098.1192452063304.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15999708.1193742121464.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4856?page=all ]

Thomas Diesler updated JBAS-4856:
---------------------------------

    Summary: Web Services regression after update to new metadata model  (was: Issues related to the new metadata model)

> Web Services regression after update to new metadata model
> ----------------------------------------------------------
>
>                 Key: JBAS-4856
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4856
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:02:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:02:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4923) No valid security
 context for the caller identity
Message-ID: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>

No valid security context for the caller identity
-------------------------------------------------

                 Key: JBAS-4923
                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:04:12 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:04:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9843317.1193742252481.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4923?page=all ]

Thomas Diesler updated JBAS-4923:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test

Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
        at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
        at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
        at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
        at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)


> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:04:12 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:04:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6588545.1193742252684.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4923?page=all ]

Thomas Diesler reassigned JBAS-4923:
------------------------------------

    Assignee: Anil Saldhana

> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:19:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:19:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4924) NPE caused by
 SessionContainer.createService
Message-ID: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE caused by SessionContainer.createService
--------------------------------------------

                 Key: JBAS-4924
                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:21:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:21:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28581936.1193743261405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler updated JBAS-4924:
---------------------------------

    Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test

12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
java.lang.NullPointerException
        at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
        at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
        at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
        at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
        at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.jboss.ejb.Container.createService(Container.java:854)
        at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)


> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:23:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18912757.1193743381680.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler updated JBAS-4924:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:23:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:23:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12077261.1193743381813.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler reassigned JBAS-4924:
------------------------------------

    Assignee: Thomas Diesler

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:27:19 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 07:27:19 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-613) Access to
 NAKACK#rebroadcast_digest field needs a lock
In-Reply-To: <8602308.1193679844347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26290239.1193743639837.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-613?page=comments#action_12385024 ] 
            
Bela Ban commented on JGRP-613:
-------------------------------

This is caused by FLUSH handling the FLUSH_RECONCILE message. I thought that is sent out by the FLUSH coordinator, so it should not get invoked concurrently ?

I'll fix the NPE, but why is this code invoked by multiple threads ?

> Access to NAKACK#rebroadcast_digest field needs a lock
> ------------------------------------------------------
>
>                 Key: JGRP-613
>                 URL: http://jira.jboss.com/jira/browse/JGRP-613
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Vladimir Blagojevic
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.6
>
>
> It seems that rebroadcast_digest field of NAKACK  is accessed by multiple threads which step over each other leading to a consequences below.
> This is very hard to reproduce and I have seen it only a few times so far.
> -------------------------------------------------------
> GMS: address is 127.0.0.1:2528
> -------------------------------------------------------
> 11141 [INFO][main] ConcurrentStateTransferTest: - Thread for channel 127.0.0.1:2528[A] started
> 15250 [INFO][A] ConcurrentStateTransferTest: - channel.getState at A127.0.0.1:2518 returned false
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2520] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2520)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2524] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2524)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2518] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2518)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2528] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2528)]: received 127.0.0.1:2518
> 15328 [ERROR][OOB,udp,127.0.0.1:2520] UDP: - failed handling incoming message
> java.lang.NullPointerException
> 	at org.jgroups.protocols.pbcast.NAKACK.rebroadcastMessages(NAKACK.java:1036)
> 	at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:620)
> 	at org.jgroups.protocols.UNICAST.down(UNICAST.java:434)
> 	at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317)
> 	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:813)
> 	at org.jgroups.protocols.FC.down(FC.java:370)
> 	at org.jgroups.protocols.FRAG2.down(FRAG2.java:175)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:318)
> 	at org.jgroups.protocols.pbcast.FLUSH.handleFlushReconcile(FLUSH.java:455)
> 	at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:337)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:258)
> 	at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
> 	at org.jgroups.protocols.FC.up(FC.java:408)
> 	at org.jgroups.protocols.pbcast.GMS.up(GMS.java:742)
> 	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:264)
> 	at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:798)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:662)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1461)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:42:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 07:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-613) Access to
 NAKACK#rebroadcast_digest field needs a lock
In-Reply-To: <8602308.1193679844347.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7789445.1193744521693.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-613?page=all ]

Bela Ban resolved JGRP-613.
---------------------------

    Resolution: Done

> Access to NAKACK#rebroadcast_digest field needs a lock
> ------------------------------------------------------
>
>                 Key: JGRP-613
>                 URL: http://jira.jboss.com/jira/browse/JGRP-613
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Vladimir Blagojevic
>         Assigned To: Bela Ban
>            Priority: Minor
>             Fix For: 2.6
>
>
> It seems that rebroadcast_digest field of NAKACK  is accessed by multiple threads which step over each other leading to a consequences below.
> This is very hard to reproduce and I have seen it only a few times so far.
> -------------------------------------------------------
> GMS: address is 127.0.0.1:2528
> -------------------------------------------------------
> 11141 [INFO][main] ConcurrentStateTransferTest: - Thread for channel 127.0.0.1:2528[A] started
> 15250 [INFO][A] ConcurrentStateTransferTest: - channel.getState at A127.0.0.1:2518 returned false
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2520] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2520)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2524] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2524)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2518] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2518)]: received 127.0.0.1:2518
> 15297 [INFO][Multiplexer,udp,127.0.0.1:2528] ConcurrentStateTransferTest: - -- [#A (127.0.0.1:2528)]: received 127.0.0.1:2518
> 15328 [ERROR][OOB,udp,127.0.0.1:2520] UDP: - failed handling incoming message
> java.lang.NullPointerException
> 	at org.jgroups.protocols.pbcast.NAKACK.rebroadcastMessages(NAKACK.java:1036)
> 	at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:620)
> 	at org.jgroups.protocols.UNICAST.down(UNICAST.java:434)
> 	at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:317)
> 	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:813)
> 	at org.jgroups.protocols.FC.down(FC.java:370)
> 	at org.jgroups.protocols.FRAG2.down(FRAG2.java:175)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:318)
> 	at org.jgroups.protocols.pbcast.FLUSH.handleFlushReconcile(FLUSH.java:455)
> 	at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:337)
> 	at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.up(STREAMING_STATE_TRANSFER.java:258)
> 	at org.jgroups.protocols.FRAG2.up(FRAG2.java:205)
> 	at org.jgroups.protocols.FC.up(FC.java:408)
> 	at org.jgroups.protocols.pbcast.GMS.up(GMS.java:742)
> 	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234)
> 	at org.jgroups.protocols.UNICAST.up(UNICAST.java:264)
> 	at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:798)
> 	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:662)
> 	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
> 	at org.jgroups.protocols.FD.up(FD.java:322)
> 	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:308)
> 	at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
> 	at org.jgroups.protocols.Discovery.up(Discovery.java:250)
> 	at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
> 	at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1461)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	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

        


From jira-events at lists.jboss.org  Tue Oct 30 07:42:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 07:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31026780.1193744521867.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12385028 ] 
            
Thomas Diesler commented on JBAS-4902:
--------------------------------------

To run any of the tests you do:

svn co https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2
cd jbossws-native-2.0.2
cp ant.properties.example ant.properties
vi ant.properties
ant deploy-jboss500
ant tests-main

ant -Dtest=jaxrpc/jbws128 test 

This is also described here

http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source


> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 08:43:13 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 08:43:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-611) MergeTask GMS
 ConcurrentModificationException
In-Reply-To: <32335654.1193392021705.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33531090.1193748193011.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-611?page=all ]

Bela Ban resolved JGRP-611.
---------------------------

    Resolution: Done

fixed in 2.6 (CVS head) and 2.5 branch

> MergeTask GMS ConcurrentModificationException
> ---------------------------------------------
>
>                 Key: JGRP-611
>                 URL: http://jira.jboss.com/jira/browse/JGRP-611
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.5.2, 2.6
>
>
> [Vivek Sar]
> I'm using JGroups 2.5 GA and have 3 members in the group using udp
> gossip router (stack below). Occasionally, we have seen the following
> exception if a node goes down and comes up again. This happens over
> and over, only way to recover would then be to stop all the members
> and start them again.
>  2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - exception while merging
> java.util.ConcurrentModificationException
> 	at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
> 	at java.util.AbstractList$Itr.next(Unknown Source)
> 	at org.jgroups.protocols.pbcast.CoordGmsImpl.removeRejectedMergeRequests(CoordGmsImpl.java:749)
> 	at org.jgroups.protocols.pbcast.CoordGmsImpl.access$500(CoordGmsImpl.java:26)
> 	at org.jgroups.protocols.pbcast.CoordGmsImpl$MergeTask.run(CoordGmsImpl.java:817)
> 	at java.lang.Thread.run(Unknown Source)
> 2007-10-25 12:08:32,717 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 12:08:51,443 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:27,237 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:39,934 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
> 2007-10-25 13:09:55,013 ERROR [MergeTask] GMS - coords or merge_id == null
> ...
> ...
> Protocol Stack,
> <config>
>     <UDP
> 		 ip_mcast="false"
> 		 mcast_addr="228.10.10.10"
> 		 mcast_port="3092"
> 		 bind_addr="${jgroups.bindaddress.ip:jgroupshost}"
> 		 bind_port="${jgroups.bindaddress.port:3092}"		 		
>          tos="16"
>          ucast_recv_buf_size="200000"
>          ucast_send_buf_size="640000"
>          mcast_recv_buf_size="250000"
>          mcast_send_buf_size="640000"
>          loopback="true"
>          discard_incompatible_packets="true"
>          max_bundle_size="64000"
>          max_bundle_timeout="30"
>          use_incoming_packet_handler="true"
>          use_outgoing_packet_handler="false"
>          ip_ttl="32"
>          enable_bundling="true"
> 		 use_concurrent_stack="true"
> 		 thread_pool.enabled="true"
> 		 thread_pool.min_threads="1"
> 		 thread_pool.max_threads="100"
> 		 thread_pool.keep_alive_time="20000"
> 		 thread_pool.queue_enabled="false"
> 		 thread_pool.queue_max_size="10"
> 		 thread_pool.rejection_policy="Run"
> 		 oob_thread_pool.enabled="true"
> 		 oob_thread_pool.min_threads="1"
> 		 oob_thread_pool.max_threads="4"
> 		 oob_thread_pool.keep_alive_time="30000"
> 		 oob_thread_pool.queue_enabled="true"
> 		 oob_thread_pool.queue_max_size="10"
> 		 oob_thread_pool.rejection_policy="Run"/>
>     <PING gossip_host="${jgroups.gossiprouter.ip:jgroupshost}"
> gossip_port="${jgroups.gossiprouter.port:3091}"
> 		    gossip_refresh="15000"
> 		    timeout="3000"
>             num_initial_members="3"/>
> 	
> 	<MERGE2 min_interval="5000" max_interval="10000"
> 		down_thread="false" up_thread="false"/>
> 	
> 	<FD_SOCK up_thread="false" down_thread="false"/>
> 	
>     <FD timeout="10000" max_tries="5" shun="true"/>
>     <VERIFY_SUSPECT timeout="1500"/>
> 	
>     <pbcast.NAKACK max_xmit_size="60000"
>                    use_mcast_xmit="false" gc_lag="0"
>                    retransmit_timeout="100,200,300,600,1200,2400,4800"
>                    discard_delivered_msgs="true"/>
> 	
>     <UNICAST timeout="300,600,1200,2400,3600"/>
> 	
>     <ENCRYPT key_store_name="keystore" store_password="xxx"
> key_password="xxx" alias="xxx"/>
> 	
>     <pbcast.STABLE stability_delay="1000" desired_avg_gossip="50000"
>                    max_bytes="400000"/>
> 	
>     <VIEW_SYNC avg_send_interval="60000"/>
> 	
> 	
> 	<AUTH auth_class="org.jgroups.auth.MD5Token"
>         auth_value="xxx"
>         token_hash="MD5"/>
> 		
>     <pbcast.GMS print_local_addr="true" join_timeout="5000"
>                 join_retry_timeout="2000" shun="true"/>
> 	
>      <FC max_credits="2000000"
>          min_threshold="0.10"/>
> 	
> 	<FRAG2 frag_size="60000"/>
> 	
>     <pbcast.STATE_TRANSFER  />
> </config>

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:36:01 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 30 Oct 2007 09:36:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-608) FLUSH not safe in
 simultaneous flush situation
In-Reply-To: <31645000.1193153881545.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6328052.1193751361682.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-608?page=all ]

Vladimir Blagojevic resolved JGRP-608.
--------------------------------------

    Resolution: Done

Smaller lock scope. Commit set:
protocols/pbcast/FLUSH.java 1.77

> FLUSH not safe in simultaneous flush situation
> ----------------------------------------------
>
>                 Key: JGRP-608
>                 URL: http://jira.jboss.com/jira/browse/JGRP-608
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.6
>            Reporter: Michael Newcomb
>         Assigned To: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 2.6
>
>
> I'm running into a few problems when multiple members request a FLUSH at the same time.
> I am still in the process of analyzing the situation, but here are a few problems:
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   byte oldPhase = flushPhase.transitionToFirstPhase();
>   if(oldPhase == FlushPhase.START_PHASE){
>     sendBlockUpToChannel();
>     onStartFlush(msg.getSrc(), fh);
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     Address flushRequester = msg.getSrc();
>     Address coordinator = null;
>     synchronized(sharedLock){
>       if(flushCoordinator != null)
>         coordinator = flushCoordinator;
>       else
>         coordinator = flushRequester;
>     }
> After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase().
> IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase().
> The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem.
> Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here.
> If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight.
> So the following code handles that situation...
> private void handleStartFlush(Message msg, FlushHeader fh) {
>   ...
>   }else if(oldPhase == FlushPhase.FIRST_PHASE){
>     ...
>     if(flushRequester.compareTo(coordinator) < 0){
>       rejectFlush(fh.viewID, coordinator);
>       ...
>       synchronized(sharedLock){
>         flushCoordinator = flushRequester;
>       }
>     }
> If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well.
> I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed.
> I will be testing a patch this afternoon and hope to report back.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:42:01 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Tue, 30 Oct 2007 09:42:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28564576.1193751721462.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12385051 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

The problem is that, when a synchronous call is received via UNICAST, the thread acquires a caller-based lock in UNICAST and then dispatches the request up the stack.

When the same thread is used to send a large return value, FRAG2 splits the response message into many smaller messages, which then get sent to the sender (self in RpcDispatcher.testLargeReturnValue()), thus blocking FC.

The thread pool for regular threads is blocked and all other messages (even OOB ones !) are sitting in the IP buffers and don't even make it to the transport. This means, credits (sent via OOB messages) are not received and we just block.

Solution (pick one or more):

- In the regular thread pool:
    - Use a queue
    - Increase the max thread
    - Set rejection policy to "discard" rather than "run"
- Increase FC.max_credits to a value greater than the largest return value. Dangerous, as this increases time without blocks


I'll keep looking for a better solution

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:47:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 09:47:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4874) Track JBoss and
 thirdparty dependencies for JBossAS 4.2.3
In-Reply-To: <29949338.1192721463216.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14806801.1193752021721.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4874?page=all ]

Dimitris Andreadis updated JBAS-4874:
-------------------------------------

    Assignee: Dimitris Andreadis
    Priority: Critical  (was: Major)

> Track JBoss and thirdparty dependencies for JBossAS 4.2.3
> ---------------------------------------------------------
>
>                 Key: JBAS-4874
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4874
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>            Priority: Critical
>             Fix For: JBossAS-4.2.3.GA
>
>
> Use subtasks to track component updates in AS 4.2.3.GA

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:51:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 09:51:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4925) Upgrade jboss cache
 to 1.4.1.SP6 (from 1.4.1.SP5)
Message-ID: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
-------------------------------------------------

                 Key: JBAS-4925
                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: JBoss Cache
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Dimitris Andreadis
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 09:53:02 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 09:53:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4925) Upgrade jboss
 cache to 1.4.1.SP6 (from 1.4.1.SP5)
In-Reply-To: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27215690.1193752382562.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4925?page=comments#action_12385056 ] 
            
Dimitris Andreadis commented on JBAS-4925:
------------------------------------------

Flipped the build to SP6; leave this open until we verify it's ok.

> Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
> -------------------------------------------------
>
>                 Key: JBAS-4925
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.3.GA
>
>
> Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:13:02 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 10:13:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
Message-ID: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>

IncompleteDeploymentException prevents further deployments
----------------------------------------------------------

                 Key: JBAS-4926
                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:15:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 10:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13123589.1193753701492.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4926?page=all ]

Thomas Diesler updated JBAS-4926:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
It seems that an incomplete deployment prevents any further deployment

    [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
    [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
    [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
    [junit]     ... 45 more
    [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

    [junit] *** CONTEXTS IN ERROR: Name -> Error

    [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started


    [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
    [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
    [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

         Assignee: Scott M Stark

> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:55:14 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 10:55:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7176652.1193756114311.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Lee Rubinger reopened EJBTHREE-1062:
-------------------------------------------

             
Reopened to merge w/ Branch_4_2

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 10:55:14 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 10:55:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29076030.1193756114634.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Lee Rubinger updated EJBTHREE-1062:
------------------------------------------

    Fix Version/s: Branch_4_2

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:28:13 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Tue, 30 Oct 2007 11:28:13 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4925) Upgrade jboss
 cache to 1.4.1.SP6 (from 1.4.1.SP5)
In-Reply-To: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16546479.1193758093602.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4925?page=comments#action_12385086 ] 
            
Brian Stansberry commented on JBAS-4925:
----------------------------------------

Guys, 1.4.1.SP6 isn't even released yet. Until it is, and the brew build is redone from the QE approved src, the current integration is equivalent to a snapshot.

> Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
> -------------------------------------------------
>
>                 Key: JBAS-4925
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.3.GA
>
>
> Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:32:01 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 11:32:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4925) Upgrade jboss
 cache to 1.4.1.SP6 (from 1.4.1.SP5)
In-Reply-To: <5469541.1193752261482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32963594.1193758321784.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4925?page=comments#action_12385090 ] 
            
Dimitris Andreadis commented on JBAS-4925:
------------------------------------------

That's cool, we are on the bleeding edge :-)

> Upgrade jboss cache to 1.4.1.SP6 (from 1.4.1.SP5)
> -------------------------------------------------
>
>                 Key: JBAS-4925
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4925
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: JBoss Cache
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.3.GA
>
>
> Upgrade JBossCache to the latest SP6.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:48:01 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Tue, 30 Oct 2007 11:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1712) Make producer
 tests go through the WS stack
In-Reply-To: <22960492.1190516351026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4131704.1193759281405.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=comments#action_12385100 ] 
            
Chris Laprun commented on JBPORTAL-1712:
----------------------------------------

Gonna see what I can do... It's tricky because I would like to switch to the new test framework as well as I would like to touching the test infrastructure too many times.

> Make producer tests go through the WS stack
> -------------------------------------------
>
>                 Key: JBPORTAL-1712
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1712
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal WSRP
>    Affects Versions: 2.8 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>             Fix For: 2.8 Final, 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 11:50:06 2007
From: jira-events at lists.jboss.org (Greg Bridges (JIRA))
Date: Tue, 30 Oct 2007 11:50:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4927) Code added in 4.2.1
 breaks web app that works in 4.2.0
Message-ID: <22925434.1193759406449.JavaMail.jira@cloud.prod.atl2.jboss.com>

Code added in 4.2.1 breaks web app that works in 4.2.0
------------------------------------------------------

                 Key: JBAS-4927
                 URL: http://jira.jboss.com/jira/browse/JBAS-4927
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
    Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
         Environment: linux, java5
            Reporter: Greg Bridges
         Assigned To: Remy Maucherat


Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.

I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.

At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.

If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:05:01 2007
From: jira-events at lists.jboss.org (Remy Maucherat (JIRA))
Date: Tue, 30 Oct 2007 12:05:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4927) Code added in
 4.2.1 breaks web app that works in 4.2.0
In-Reply-To: <22925434.1193759406449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5785654.1193760301634.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4927?page=comments#action_12385109 ] 
            
Remy Maucherat commented on JBAS-4927:
--------------------------------------

Caused by fixing JBCTS-609.

> Code added in 4.2.1 breaks web app that works in 4.2.0
> ------------------------------------------------------
>
>                 Key: JBAS-4927
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4927
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
>         Environment: linux, java5
>            Reporter: Greg Bridges
>         Assigned To: Remy Maucherat
>
> Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.
> I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.
> At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.
> If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:11:02 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Tue, 30 Oct 2007 12:11:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-255) Arrows in admin
 page are displayed wrongly
Message-ID: <22269073.1193760662165.JavaMail.jira@cloud.prod.atl2.jboss.com>

Arrows in admin page are displayed wrongly
------------------------------------------

                 Key: JBFORUMS-255
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-255
             Project: JBoss Forums
          Issue Type: Bug
          Components: Forum View Layer
            Reporter: Ryszard Kozmik
            Priority: Minor
             Fix For: 1.0.1 RC, 1.1.0 Alpha


Arrows for changing order of forums and categories are messed up after admin panel view refactoring.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:13:11 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 12:13:11 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4927) Code added in 4.2.1
 breaks web app that works in 4.2.0
In-Reply-To: <22925434.1193759406449.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22969989.1193760791809.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4927?page=all ]

Dimitris Andreadis updated JBAS-4927:
-------------------------------------

    Fix Version/s: JBossAS-4.2.3.GA

Schedule for 4.2.3.GA. Maybe we should look at it in trunk, too.

> Code added in 4.2.1 breaks web app that works in 4.2.0
> ------------------------------------------------------
>
>                 Key: JBAS-4927
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4927
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
>         Environment: linux, java5
>            Reporter: Greg Bridges
>         Assigned To: Remy Maucherat
>             Fix For: JBossAS-4.2.3.GA
>
>
> Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.
> I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.
> At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.
> If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:13:12 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 30 Oct 2007 12:13:12 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9205571.1193760792698.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/GPD-169?page=all ]

Koen Aers closed GPD-169.
-------------------------

    Resolution: Done

The issue was fixed on HEAD. It would be nice if someone could verify if the problem is gone.

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:15:01 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Tue, 30 Oct 2007 12:15:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-256) Update build
	script
Message-ID: <14140527.1193760901691.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update build script
-------------------

                 Key: JBFORUMS-256
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-256
             Project: JBoss Forums
          Issue Type: Task
          Components: Portlet Productization
            Reporter: Ryszard Kozmik
         Assigned To: Przemyslaw Dej
            Priority: Critical
             Fix For: 1.0.1 RC, 1.1.0 Alpha, 1.0.0 GA


A package for JBoss Portal 2.6.1 was made and is available in project's downloads but build script was not updated to build such a package. Mostly the change is bundling more jars and an xml with defined scoped classloader repo.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 12:40:02 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Tue, 30 Oct 2007 12:40:02 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBFORUMS-257) Not efficient
	admin view
Message-ID: <13466011.1193762402854.JavaMail.jira@cloud.prod.atl2.jboss.com>

Not efficient admin view
------------------------

                 Key: JBFORUMS-257
                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-257
             Project: JBoss Forums
          Issue Type: Bug
          Components: Forum Model Layer, Forum View Layer
            Reporter: Ryszard Kozmik
             Fix For: 1.0.1 RC, 1.1.0 Alpha


When having lots of forums/categories in database, admin view breaks due to model layer problems. Probably something was messed up while doing view refactoring.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:37:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 13:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1091) Ensure all
 metadata files are included in the Schema test case
In-Reply-To: <18825902.1193691275979.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22800996.1193765821542.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1091?page=comments#action_12385145 ] 
            
Andrew Lee Rubinger commented on EJBTHREE-1091:
-----------------------------------------------

Included all ejb-jar.xml and jboss*.xml files (excluding jboss-service.xml, jboss-app.xml, etc)

> Ensure all metadata files are included in the Schema test case
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-1091
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1091
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> Be sure that all ejb-jar.xml, jboss.xml files in the EJB3 module are included in the tests of org.jboss.ejb3.test.schema.unit.SchemaTestCase

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:37:01 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 13:37:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1091) Ensure all
 metadata files are included in the Schema test case
In-Reply-To: <18825902.1193691275979.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12532390.1193765821854.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1091?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1091.
-------------------------------------------

    Resolution: Done

> Ensure all metadata files are included in the Schema test case
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-1091
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1091
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Andrew Lee Rubinger
>         Assigned To: Andrew Lee Rubinger
>             Fix For: HEAD
>
>
> Be sure that all ejb-jar.xml, jboss.xml files in the EJB3 module are included in the tests of org.jboss.ejb3.test.schema.unit.SchemaTestCase

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:44:01 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 13:44:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBXB-112) Failed to create a
	new SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6535534.1193766241623.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Thomas Diesler reopened JBXB-112:
---------------------------------

             
Could you please update the repository snapshot?

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 13:48:01 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 30 Oct 2007 13:48:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1092)
 <load-balance-policy> does not override annotation
Message-ID: <17076593.1193766481412.JavaMail.jira@cloud.prod.atl2.jboss.com>

<load-balance-policy> does not override annotation
--------------------------------------------------

                 Key: EJBTHREE-1092
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1092
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            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

        


From jira-events at lists.jboss.org  Tue Oct 30 14:24:06 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Tue, 30 Oct 2007 14:24:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JGRP-570) Complete thread
 naming for all channel threads
In-Reply-To: <23416128.1186496749399.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12136184.1193768646538.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JGRP-570?page=all ]

Vladimir Blagojevic resolved JGRP-570.
--------------------------------------

    Resolution: Done

Resolved by introducing ThreadFactory as a field of ProtocolStack. Thus we removed all proliferated ThreadNamingPattern references as well as resolved the problem of thread renaming for short lived threads (ViewHandler, MergeTask and so on).

Commit set:

Revision  Path
1.1             JGroups/src/org/jgroups/ThreadFactory.java
1.54          JGroups/src/org/jgroups/stack/ProtocolStack.java

All other changes are trivial string replacement.

> Complete thread naming for all channel threads
> ----------------------------------------------
>
>                 Key: JGRP-570
>                 URL: http://jira.jboss.com/jira/browse/JGRP-570
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Vladimir Blagojevic
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.6
>
>
> We have improved thread naming in Jgroups 2.5 release. However, we still have threads in protocols above TP that are named independently of TP threads - they follow different naming pattern. We should investigate how to consistently name all threads that belong to one channel. Should we pass ThreadNamingPattern as and event through the stack?

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:11:39 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Tue, 30 Oct 2007 15:11:39 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4928) Compare AS library
 names between 4.2.x & 5.0.x
Message-ID: <17641383.1193771499144.JavaMail.jira@cloud.prod.atl2.jboss.com>

Compare AS library names between 4.2.x & 5.0.x 
-----------------------------------------------

                 Key: JBAS-4928
                 URL: http://jira.jboss.com/jira/browse/JBAS-4928
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Build System
            Reporter: Dimitris Andreadis
         Assigned To: Rajesh Rajasekaran
             Fix For: JBossAS-5.0.0.CR1


Check how similar libraries are deployed under different names in server/xxx/lib between 4.2.x & 5.0.x

The names shouldn't change, unless there is a good reason for that.

E.g.
lib/servlet-api.jar in 4.2.x
lib/javax.servlet.jar in 5.0.x

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:19:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:19:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6103051.1193771984729.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385160 ] 
            
Thomas Diesler commented on JBAS-4926:
--------------------------------------

I reverted the change that caused this

[tdiesler at tdvaio trunk]$ svn diff -rPREV system-jmx/src/main/org/jboss/deployment/MainDeployer.java
Index: system-jmx/src/main/org/jboss/deployment/MainDeployer.java
===================================================================
--- system-jmx/src/main/org/jboss/deployment/MainDeployer.java  (revision 66567)
+++ system-jmx/src/main/org/jboss/deployment/MainDeployer.java  (working copy)
@@ -811,7 +811,7 @@
             deploymentName = deployment.getName();
             delegate.process();
             // TODO: JBAS-4292
-            delegate.checkComplete();
+            delegate.checkComplete(deployment);
             contextMap.put(url, deploymentName);
          }
          catch(Exception e)


> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:27:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:27:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26857238.1193772464806.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4926?page=all ]

Thomas Diesler resolved JBAS-4926.
----------------------------------

    Resolution: Done

> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:29:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:29:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5219507.1193772585155.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4901?page=all ]

Thomas Diesler reassigned JBAS-4901:
------------------------------------

    Assignee: Ales Justin  (was: Thomas Diesler)

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Ales Justin
>             Fix For: JBossAS-5.0.0.CR1
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:33:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4929) mapped-name is
 required for jdbc/juddiDB of deployment juddi.war
Message-ID: <548500.1193772824675.JavaMail.jira@cloud.prod.atl2.jboss.com>

mapped-name is required for jdbc/juddiDB of deployment juddi.war
----------------------------------------------------------------

                 Key: JBAS-4929
                 URL: http://jira.jboss.com/jira/browse/JBAS-4929
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:37:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:37:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4929) mapped-name is
 required for jdbc/juddiDB of deployment juddi.war
In-Reply-To: <548500.1193772824675.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24618239.1193773064754.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4929?page=all ]

Thomas Diesler updated JBAS-4929:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
When you deploy

http://repository.jboss.com/jboss/jaxr/1.2.0.GA/lib/juddi-service.sar

you get

20:22:46,758 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
20:22:46,779 ERROR [BaseModelMBean] Exception invoking method addChild
java.lang.RuntimeException: mapped-name is required for jdbc/juddiDB of deployment juddi.war
        at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:130)
        at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:212)
        at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:343)

         Assignee: Carlo de Wolf

> mapped-name is required for jdbc/juddiDB of deployment juddi.war
> ----------------------------------------------------------------
>
>                 Key: JBAS-4929
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4929
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> When you deploy
> http://repository.jboss.com/jboss/jaxr/1.2.0.GA/lib/juddi-service.sar
> you get
> 20:22:46,758 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
> 20:22:46,779 ERROR [BaseModelMBean] Exception invoking method addChild
> java.lang.RuntimeException: mapped-name is required for jdbc/juddiDB of deployment juddi.war
>         at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:130)
>         at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:212)
>         at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:343)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:36:09 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 15:36:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28905516.1193772969221.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4926?page=all ]

Scott M Stark reopened JBAS-4926:
---------------------------------

             
This fails to identify deployments that should fail as failing. What is the real issue with this exception? Why shouldn't the ear deployment be failing?


> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:46:09 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Tue, 30 Oct 2007 15:46:09 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <597914.1193773569491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385164 ] 
            
Thomas Diesler commented on JBAS-4926:
--------------------------------------

If I do not have the juddi-service.sar deployed i.e. there is no failed deployment because of [JBAS-4929]
then the ear deployment does not fail either.

Also, the junit output contains a list of all failed deployments for every test. This prevents junit-reports because of the xml volume to process.
Is it not enough to list the deployment as failed when it actually is deployed for the first time?





> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 15:55:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 15:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25464925.1193774144718.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385166 ] 
            
Scott M Stark commented on JBAS-4926:
-------------------------------------

Ok, then the real problem for this issue is that the checkIncomplete(Deployment) call is not working.


> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 16:16:45 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 30 Oct 2007 16:16:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1092)
 <load-balance-policy> does not override annotation
In-Reply-To: <17076593.1193766481412.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23067018.1193775405296.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1092?page=all ]

William DeCoste closed EJBTHREE-1092.
-------------------------------------

    Resolution: Rejected

Works fine - user's jboss.xml was invalid and did not reference the schema.

> <load-balance-policy> does not override annotation
> --------------------------------------------------
>
>                 Key: EJBTHREE-1092
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1092
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            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

        


From jira-events at lists.jboss.org  Tue Oct 30 16:20:44 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Tue, 30 Oct 2007 16:20:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1093) create tutorial
 for validating jboss.xml
Message-ID: <29220382.1193775644586.JavaMail.jira@cloud.prod.atl2.jboss.com>

create tutorial for validating jboss.xml
----------------------------------------

                 Key: EJBTHREE-1093
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1093
             Project: EJB 3.0
          Issue Type: Task
          Components: Documentation
            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

        


From jira-events at lists.jboss.org  Tue Oct 30 17:06:45 2007
From: jira-events at lists.jboss.org (Mike Clark (JIRA))
Date: Tue, 30 Oct 2007 17:06:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1128) Message not
 routed from one node to node with only consumer.
Message-ID: <15994322.1193778405017.JavaMail.jira@cloud.prod.atl2.jboss.com>

Message not routed from one node to node with only consumer.
------------------------------------------------------------

                 Key: JBMESSAGING-1128
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
             Project: JBoss Messaging
          Issue Type: Bug
          Components: JMS Clustering
    Affects Versions: 1.4.0.GA
         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
            Reporter: Mike Clark
         Assigned To: Tim Fox


In trying to reproduce behavior described in case 18885, I can reproduce the following:

Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.

Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)

Both instances were created from a clean "all" instance.


-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 18:44:44 2007
From: jira-events at lists.jboss.org (Andrew Lee Rubinger (JIRA))
Date: Tue, 30 Oct 2007 18:44:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1062) Finding the
 default local
 business interface on a bean with a superclass that implements interfaces
 doesn't work
In-Reply-To: <12225669.1191953763549.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22150810.1193784284685.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1062?page=all ]

Andrew Lee Rubinger resolved EJBTHREE-1062.
-------------------------------------------

    Resolution: Done

Merged tests and fix w/ Branch_4_2

> Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1062
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, Branch_4_2
>
>
> The following doesn't work:
> @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {}
> interface ExpectedLocalInterface {}
> class SuperBean implements OtherInterface {}
> interface OtherInterface {}
> Based on the spec ExpectedLocalInterface is expected to become the local business interface.
> EJB 3 4.6.6:
> If bean class implements a single interface, that interface is assumed to be the busi-
> ness interface of the bean. This business interface will be a local interface unless the
> interface is designated as a remote business interface by use of the Remote annota-
> tion on the bean class or interface or by means of the deployment descriptor.

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 19:04:01 2007
From: jira-events at lists.jboss.org (Ronald van Kuijk (JIRA))
Date: Tue, 30 Oct 2007 19:04:01 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10951676.1193785441337.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12385176 ] 
            
Ronald van Kuijk commented on GPD-169:
--------------------------------------

is the head used in the nightly builds of jbosstools? 

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 19:28:44 2007
From: jira-events at lists.jboss.org (Koen Aers (JIRA))
Date: Tue, 30 Oct 2007 19:28:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (GPD-169) GPD Diagram node and
 text positioning not saving.
In-Reply-To: <20962546.1190963021672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14699049.1193786924767.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/GPD-169?page=comments#action_12385178 ] 
            
Koen Aers commented on GPD-169:
-------------------------------

i am not sure, i will ping marshall about it

> GPD Diagram node and text positioning not saving.
> -------------------------------------------------
>
>                 Key: GPD-169
>                 URL: http://jira.jboss.com/jira/browse/GPD-169
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM JPDL Designer 3.1.0.GA
>         Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1
>            Reporter: David Roberts
>         Assigned To: Koen Aers
>             Fix For: jBPM jPDL Designer 3.1.1
>
>         Attachments: Before and After.jpg, gpd.xml, processdefinition.xml
>
>
> Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem:
> When re-opening a process definition with the GPD, my nodes are jumbled up and placed at random locations. So there is this web of transition lines running everywhere to reach the nodes. You can't see what's going on. Each time I open my process definition in the GPD to work with it, I have to spend 10 to 15 minutes re-aligning everything.
> Transition text also has a problem:
> All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. 
> I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. 

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 19:39:44 2007
From: jira-events at lists.jboss.org (Ales Justin (JIRA))
Date: Tue, 30 Oct 2007 19:39:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMICROCONT-187) Complete the
 single deployment api
In-Reply-To: <3044720.1183400757621.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9612966.1193787584681.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-187?page=all ]

Ales Justin reassigned JBMICROCONT-187:
---------------------------------------

    Assignee: Ales Justin  (was: Adrian Brock)

> Complete the single deployment api
> ----------------------------------
>
>                 Key: JBMICROCONT-187
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-187
>             Project: JBoss MicroContainer
>          Issue Type: Task
>          Components: Deployment
>            Reporter: Adrian Brock
>         Assigned To: Ales Justin
>             Fix For: JBossMC-2.0.0.GA
>
>
> The single deployment api needs finishing.
> 1) deploy()/undeploy() on the DeployerClient/MainDeployer need making threadsafe such
> that they only do work on the deployment passed a parameter
> 2) The incomplete checking for a single deployment needs to "know" look at only those microcontainer
> contexts that it created (+ those contexts/deployments referenced as dependencies).

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 22:25:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 22:25:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4929) mapped-name is
 required for jdbc/juddiDB of deployment juddi.war
In-Reply-To: <548500.1193772824675.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19082183.1193797544630.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4929?page=all ]

Scott M Stark resolved JBAS-4929.
---------------------------------

    Resolution: Done

> mapped-name is required for jdbc/juddiDB of deployment juddi.war
> ----------------------------------------------------------------
>
>                 Key: JBAS-4929
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4929
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> When you deploy
> http://repository.jboss.com/jboss/jaxr/1.2.0.GA/lib/juddi-service.sar
> you get
> 20:22:46,758 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, vfsUrl=juddi-service.sar/juddi.war
> 20:22:46,779 ERROR [BaseModelMBean] Exception invoking method addChild
> java.lang.RuntimeException: mapped-name is required for jdbc/juddiDB of deployment juddi.war
>         at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:130)
>         at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:212)
>         at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:343)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 22:50:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 22:50:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4922) NPE in
 AssemblyDescriptorMetaData
In-Reply-To: <21462601.1193741590212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15004566.1193799044658.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4922?page=all ]

Scott M Stark resolved JBAS-4922.
---------------------------------

    Resolution: Done

Fixed in jboss-metadata.jar snapshot rev 1721

> NPE in AssemblyDescriptorMetaData
> ---------------------------------
>
>                 Key: JBAS-4922
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4922
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> 11:47:39,226 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=ejb/ConfidentialSLSB,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at org.jboss.metadata.AssemblyDescriptorMetaData.getPrincipalVersusRolesMap(AssemblyDescriptorMetaData.java:126)
>         at org.jboss.ejb.plugins.SecurityInterceptor.setContainer(SecurityInterceptor.java:132)
>         at org.jboss.ejb.SessionContainer.createInterceptors(SessionContainer.java:374)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:182)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:267)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
>         at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 23:43:45 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 23:43:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4915) service-ref merge
	looses data
In-Reply-To: <10418750.1193657594185.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28915121.1193802225374.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4915?page=all ]

Scott M Stark resolved JBAS-4915.
---------------------------------

    Resolution: Done

Resolved by jboss-metadata.jar snapshot rev 1722

> service-ref merge looses data
> -----------------------------
>
>                 Key: JBAS-4915
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4915
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> In the following scenario only jboss-client.xml contains <service-ref> elements
> <application-client version="5" xmlns="http://java.sun.com/xml/ns/javaee" 
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application-client_5.xsd">
>   
>   <display-name>TestEndpointService</display-name>
>   
> </application-client>
> <jboss-client>
>   <jndi-name>jbossws-client</jndi-name>
>   
>   <!-- 
>   @WebServiceRef(name = "Service1")
>   -->
>   <service-ref>
>     <service-ref-name>Service1</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service2")
>   -->
>   <service-ref>
>     <service-ref-name>Service2</service-ref-name>
>     <config-name>Custom Client</config-name>
>     <config-file>META-INF/jbossws-client-config.xml</config-file>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service3")
>   -->
>   <service-ref>
>     <service-ref-name>Service3</service-ref-name>
>     <service-impl-class>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpointService</service-impl-class>
>     <service-qname>{http://org.jboss.ws/wsref}TestEndpointService</service-qname>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Service4")
>   -->
>   <service-ref>
>     <service-ref-name>Service4</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port1", type = TestEndpoint.class)
>   -->
>   <service-ref>
>     <service-ref-name>Port1</service-ref-name>
>     <port-component-ref>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port2")
>   -->
>   <service-ref>
>     <service-ref-name>Port2</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <config-name>Custom Client</config-name>
>       <config-file>META-INF/jbossws-client-config.xml</config-file>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
>   <!-- 
>   @WebServiceRef(name = "Port3")
>   -->
>   <service-ref>
>     <service-ref-name>Port3</service-ref-name>
>     <port-component-ref>
>       <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.webserviceref.TestEndpoint</service-endpoint-interface>
>       <port-qname>{http://org.jboss.ws/wsref}TestEndpointPort</port-qname>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.username</prop-name>
>         <prop-value>kermit</prop-value>
>       </stub-property>
>       <stub-property>
>         <prop-name>javax.xml.ws.security.auth.password</prop-name>
>         <prop-value>thefrog</prop-value>
>       </stub-property>
>     </port-component-ref>
>     <wsdl-override>META-INF/wsdl/TestEndpoint.wsdl</wsdl-override>
>   </service-ref>
>   
> </jboss-client>
> These are lost by
>    public static JBossServiceReferencesMetaData merge(ServiceReferencesMetaData override,
>          ServiceReferencesMetaData overriden,
>          String overridenFile, String overrideFile)
>    {
>       if (override == null && overriden == null)
>          return null;
>       JBossServiceReferencesMetaData merged = new JBossServiceReferencesMetaData();
>       JavaEEMetaDataUtil.merge(merged, overriden, override, "service-ref", overridenFile, overrideFile, false);
>       return merged;
>    }
> because JavaEEMetaDataUtil.merge does nothing with merged if overridden is empty

-- 
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

        


From jira-events at lists.jboss.org  Tue Oct 30 23:49:48 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Tue, 30 Oct 2007 23:49:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12150656.1193802588046.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385194 ] 
            
Scott M Stark commented on JBAS-4914:
-------------------------------------

When I run the test, it does not try to deploy anything or run any test:

[starksm at succubus jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase

...

bs/jaxrpc-samples-jsr109ejb-rpc-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109ejb-doc.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109ejb-doc-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-rpc.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-rpc-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-doc.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-jsr109pojo-doc-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-message.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-message-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-mtom.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-mtom-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-oneway.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-oneway-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-rpcstyle.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-rpcstyle-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-secureejb.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-secureejb-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-swa.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-swa-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-store-pass-encrypt.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-store-pass-encrypt-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wsbpel-hello.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wsbpel-hello-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-sign.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-sign-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-encrypt.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxrpc-samples-wssecurity-encrypt-client.jar

build-jars-jaxws:
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-benchmark-doclit.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/ri-benchmark-doclit.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-complex.war
    [unjar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.jar into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.jar
    [unwar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.war into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.war
    [unwar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.war into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.sar/jaxws-jbws1762-exploded.war
    [unwar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.war into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.ear/jaxws-jbws1762-exploded.war
    [unjar] Expanding: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-packaged.jar into /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1762-exploded.ear/jaxws-jbws1762-exploded.jar

build-interop-jars:
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop-BaseDataTypesDocLitB.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop-BaseDataTypesDocLitW.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop-BaseDataTypesRpcLit.war
      [ear] Building ear: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jbossws-interop.ear

build-samples-jaxws:
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-secure-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-override-client.jar
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecurity-encrypt.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecurity-sign.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecurityAnnotatedpolicy-encrypt.war
      [war] Building war: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-wssecuritypolicy-encrypt.war
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-secure-client.jar
      [jar] Building jar: /home/svn/JBossWS/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-override-client.jar

build-jars-jaxws:

tests-main:

most:

main:

BUILD SUCCESSFUL
Total time: 23 seconds
[starksm at succubus jbossws-native-2.0.2]$



> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 01:13:44 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 31 Oct 2007 01:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <11053624.1193807624765.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385200 ] 
            
Anil Saldhana commented on JBAS-4914:
-------------------------------------

Scott, I have seen this.  You need to add "one-test" at the end.

This has worked last time I did:
a)  ant deploy-jboss500
b) Start JBoss
c) ant -Dtest=fqn one-test


> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 02:57:06 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 02:57:06 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17084263.1193813826663.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385205 ] 
            
Scott M Stark commented on JBAS-4914:
-------------------------------------

Ok, I get further, but something is still not built correctly as the reports output shows the test class is not found. This is after I have run ant and ant tests-compile.

Testsuite: org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec

   Caused an ERROR
org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.samples.context.WebSer
viceContextJSETestCase
   at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
   at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Class.java:164)


> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 03:19:54 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 03:19:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-713) Check if jbossweb
 can replace tomcat jars for the http server invoker
In-Reply-To: <28749862.1172479535523.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19158649.1193815194791.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-713?page=comments#action_12385207 ] 
            
Ron Sigal commented on JBREM-713:
---------------------------------

CoyoteInvoker.event() is defined:

   public boolean event(Request arg0, Response arg1, SocketStatus arg2) throws Exception;

but org.apache.tomcat.util.net.SocketStatus is an enum that does not exist in tomcat.  To get around the problem, I've created an interface org.apache.tomcat.util.net.SocketStatus, put it in tomcat-addenda.jar, and put tomcat-addenda.jar in .../lib/apache-tomcat.  This way, a SocketStatus will be available if apache-tomcat/*.jar's are on the classpath.

Also, I've changed the definition of the classpaths in build.xml so that the tomcat jars are included if jdk is 1.4, and jbossweb.jar is included if jdk is 1.5.

Note:  test in build.xml should be jdk 1.5 or greater.

> Check if jbossweb can replace tomcat jars for the http server invoker
> ---------------------------------------------------------------------
>
>                 Key: JBREM-713
>                 URL: http://jira.jboss.com/jira/browse/JBREM-713
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker.
> See JBREM-705.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 03:41:54 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 03:41:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1094) Update wiki page
 "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
Message-ID: <816416.1193816514805.JavaMail.jira@cloud.prod.atl2.jboss.com>

Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
---------------------------------------------------------------------

                 Key: EJBTHREE-1094
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1094
             Project: EJB 3.0
          Issue Type: Task
          Components: Documentation
            Reporter: Ron Sigal


1. As of Remoting 2.2.x, the Object Name of the org.jboss.remoting.transport.servlet.ServerServletInvoker is hard coded as "jboss.remoting:service=invoker,transport=servlet", which means that only a single instance of ServerServletInvoker can be created.  That would be a problem if, say, EJB3 and JBossMessaging both wanted to use the servlet transport.

As of Remoting 2.4.0, the Object Name will be generated by org.jboss.remoting.ServerInvoker.getMBeanObjectName(), which adds values for "host", "port", and any other parameters on the InvokerLocator.  For example, the Object Name for the ServerServletInvoker in the example is now

   jboss.remoting:service=invoker,transport=servlet,host=127.0.0.1,port=8080

2. While the https example works for org.apache.coyote.http11.Http11Protocol (the non-native version), it doesn't seem to work with org.apache.coyote.http11.Http11AprProtocol.  It seems that jbossweb wants keystores in openssl PEM format.  I must be missing something, though, because I couldn't get it to work with APR.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 03:58:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 03:58:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29584948.1193817524668.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385210 ] 
            
Ron Sigal commented on JBREM-675:
---------------------------------

There seem to be three changes in the attached ServletServerInvoker:

1. The MBean Object Name is no longer hard coded.
2. Leasing information is added to responses.
3. Response code 200 is used instead of 204 to avoid a null response.

ServletServerInvoker has been updated as follows:

1. The ServletServerInvoker.getMBeanObjectName() method is deleted, so that org.jboss.remoting.ServerInvoker.getMBeanObjectName() is called instead.  The latter adds values for "port", "host", and all parameters that appear in the InvokerLocator. 

2. Leasing is handled by ServerInvoker and doesn't need to be handled by ServletServerInvoker.

3. The response code issue has been fixed along the lines of the treatment in org.jboss.remoting.transport.coyote.CoyoteInvoker.  That is, if the request did not come from org.jboss.remoting.transport.http.HTTPClientInvoker or the request method was PUT, then 204 is used for a null response.  Otherwise, 200 is used.

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:08:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 04:08:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1052) When running
 stress tests wrong log4j.xml is picked up
In-Reply-To: <10580807.1187882838240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19049657.1193818124743.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1052?page=all ]

Tim Fox reopened JBMESSAGING-1052:
----------------------------------

             
It's still picking up the wrong one from tests/etc

> When running stress tests wrong log4j.xml is picked up
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-1052
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used.
> This means stress tests are being run on trace logging, which is incorrect (makes them take ages)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:08:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 04:08:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBMESSAGING-1052) When running
 stress tests wrong log4j.xml is picked up
In-Reply-To: <10580807.1187882838240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31407497.1193818124920.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1052?page=all ]

Tim Fox reassigned JBMESSAGING-1052:
------------------------------------

    Assignee: Clebert Suconic  (was: Tim Fox)

> When running stress tests wrong log4j.xml is picked up
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-1052
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>             Fix For: EAP 4.3 Integration
>
>
> When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used.
> This means stress tests are being run on trace logging, which is incorrect (makes them take ages)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:08:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 04:08:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1052) When running
 stress tests wrong log4j.xml is picked up
In-Reply-To: <10580807.1187882838240.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8595723.1193818125106.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1052?page=all ]

Tim Fox updated JBMESSAGING-1052:
---------------------------------

    Fix Version/s: EAP 4.3 Integration
                       (was: 1.4.0.CR2)
         Priority: Minor  (was: Major)

> When running stress tests wrong log4j.xml is picked up
> ------------------------------------------------------
>
>                 Key: JBMESSAGING-1052
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1052
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Tim Fox
>         Assigned To: Clebert Suconic
>            Priority: Minor
>             Fix For: EAP 4.3 Integration
>
>
> When running stress tests, the log4j.xml from tests/etc, but the log4j.xml from tests/etc/stress isn't being used.
> This means stress tests are being run on trace logging, which is incorrect (makes them take ages)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:26:49 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 04:26:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27762249.1193819209668.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385215 ] 
            
Thomas Diesler commented on JBAS-4914:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers

You will need to comment this

# [JBAS-4890] EJBAccessException: Caller unauthorized
org/jboss/test/ws/jaxws/samples/context/**


> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:28:44 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 04:28:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7984447.1193819324604.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

Updated the snapshot.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:33:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 04:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4914) NPE in
	JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27553144.1193819624736.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4914?page=comments#action_12385217 ] 
            
Thomas Diesler commented on JBAS-4914:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers

You will need to comment this

# [JBAS-4890] EJBAccessException: Caller unauthorized
org/jboss/test/ws/jaxws/samples/context/**

before you run tests-main

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 04:33:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 04:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18247574.1193819624920.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Thomas Diesler updated JBAS-4914:
---------------------------------

    Comment: was deleted

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:06:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 05:06:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1773) Unable to
 destroy instance customization
In-Reply-To: <28539289.1193307421819.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22866124.1193821604724.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1773?page=all ]

Thomas Heute updated JBPORTAL-1773:
-----------------------------------

    Assignee: Julien Viet  (was: Thomas Heute)

> Unable to destroy instance customization
> ----------------------------------------
>
>                 Key: JBPORTAL-1773
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1773
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.6.1 Final
>         Environment: Fedora Core 7
> JVM 1.5.0_12
> JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) (installed with jems-installer 1.2.0.GA with 'ejb3' profile)
> JBoss Potal 2.6.1.GA
>            Reporter: Ovidiu Nichifor
>         Assigned To: Julien Viet
>             Fix For: 2.6.3 Final
>
>         Attachments: sample-portlet.war
>
>
> Create & place a window on a region of an ordinary page of your personal dashboard.
> Make sure it is visible on your dashboard.
> Destroy that window.
> Recreate the window with the same name, content type, instance, page parent, region and order as before.
> An error will appear in the console:
> 12:17:12,694 ERROR [AbstractInstance] Was not able to destroy local._4 for customization dashboard:/admin/sample/P, reason is : null
> 12:17:57,309 ERROR [AbstractInstance] Was not able to destroy local._3 for customization dashboard:/admin/sample/Preferences, reason is : null
> It seems that when a window is destroyed the entries from 'JBP_PORTLET_STATE' table are deleted but the customization entry from 'JBP_INSTANCE_PER_USER' is not; this entry references an invalid portlet ref in the previous table.
> Sample:
> `JBP_PORTLET_STATE`
> PK 	PORTLET_ID                    REGISTRATION_ID 	REGISTRATION_TIME 	TERMINATION_TIME 	PARENT_PK
> 1 	/portal-news-samples.NewsPortlet 	NULL 	2007-10-25 11:57:28 	NULL 	NULL
> `JBP_INSTANCE_PER_USER`
> PK 	INSTANCE_PK 	SER_STATE 	USER_ID 	PORTLET_REF
> 1 	16 	[BLOB - NULL] 	dashboard:/admin/default/Preferences 	local._2
> 2 	16 	[BLOB - NULL] 	dashboard:/admin/sample/Preferences 	local._3
> 3 	16 	[BLOB - NULL] 	dashboard:/admin/sample/P 	local._4
> Your newly created window does exist in the 'OBJECT_NODE' table but the portal will NOT render it anymore, especially if you restart the AS. Done some more debug and ended up with a NoSuchPortletException which is as expected since the persistent state (local._X) is no longer valid.
> Also, org.jboss.portal.core.impl.model.instance.AbstarctInstance#destroyCustomization does remove the customization state but does not delete the entry from 'JBP_INSTANCE_PER_USER'.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:13:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4930) Cannot lookup ejb3
	remote proxy
Message-ID: <16096432.1193822024649.JavaMail.jira@cloud.prod.atl2.jboss.com>

Cannot lookup ejb3 remote proxy
-------------------------------

                 Key: JBAS-4930
                 URL: http://jira.jboss.com/jira/browse/JBAS-4930
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:15:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:15:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4930) Cannot lookup ejb3
	remote proxy
In-Reply-To: <16096432.1193822024649.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5192444.1193822144652.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4930?page=all ]

Thomas Diesler updated JBAS-4930:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test

one-test:
    [mkdir] Created dir: /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/reports
    [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 3.901 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED

Testcase: testEJBClient took 0.023 sec
        Caused an ERROR
ejb not bound
javax.naming.NameNotFoundException: ejb not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
        at sun.rmi.transport.Transport$1.run(Transport.java:153)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
        at java.lang.Thread.run(Thread.java:595)
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
        at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
        at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
        at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
        at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
        at $Proxy0.lookup(Unknown Source)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
        at javax.naming.InitialContext.lookup(InitialContext.java:351)
        at org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.testEJBClient(ServiceRefEJBTestCase.java:86)


@Remote(EJBRemote.class)
@RemoteBinding(jndiBinding = "/ejb/EJBClient")
@Stateless

public class EJBClient 
{
   ...
}

   public void testEJBClient() throws Exception
   {      
      // JAXWS <service-ref> is only supported in EE5 
      if (isTargetJBoss50())
      {
         InitialContext iniCtx = getInitialContext();
         EJBRemote ejbRemote = (EJBRemote)iniCtx.lookup("/ejb/EJBClient");

         String helloWorld = "Hello World!";
         Object retObj = ejbRemote.echo(helloWorld);
         assertEquals(helloWorld, retObj);
      }
   }


         Assignee: Carlo de Wolf

> Cannot lookup ejb3 remote proxy
> -------------------------------
>
>                 Key: JBAS-4930
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4930
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
> one-test:
>     [mkdir] Created dir: /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/reports
>     [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 3.901 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
> Testcase: testEJBClient took 0.023 sec
>         Caused an ERROR
> ejb not bound
> javax.naming.NameNotFoundException: ejb not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
>         at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
>         at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
>         at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
>         at $Proxy0.lookup(Unknown Source)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.testEJBClient(ServiceRefEJBTestCase.java:86)
> @Remote(EJBRemote.class)
> @RemoteBinding(jndiBinding = "/ejb/EJBClient")
> @Stateless
> public class EJBClient 
> {
>    ...
> }
>    public void testEJBClient() throws Exception
>    {      
>       // JAXWS <service-ref> is only supported in EE5 
>       if (isTargetJBoss50())
>       {
>          InitialContext iniCtx = getInitialContext();
>          EJBRemote ejbRemote = (EJBRemote)iniCtx.lookup("/ejb/EJBClient");
>          String helloWorld = "Hello World!";
>          Object retObj = ejbRemote.echo(helloWorld);
>          assertEquals(helloWorld, retObj);
>       }
>    }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:29:44 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Wed, 31 Oct 2007 05:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4823) TECH REVIEW:
 Getting Started Guide - TRACKER
In-Reply-To: <7242681.1192163283251.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18058595.1193822984596.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4823?page=comments#action_12385220 ] 
            
Luc Texier commented on JBAS-4823:
----------------------------------

The JBoss Frontline Team has now completed the review of this manual



> TECH REVIEW: Getting Started Guide - TRACKER
> --------------------------------------------
>
>                 Key: JBAS-4823
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4823
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tech Review Tracker Issue

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:32:42 2007
From: jira-events at lists.jboss.org (Luc Texier (JIRA))
Date: Wed, 31 Oct 2007 05:32:42 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4819) TECH REVIEW:
 Installation Guide - TRACKER
In-Reply-To: <31236397.1192161963223.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25985015.1193823162744.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4819?page=comments#action_12385221 ] 
            
Luc Texier commented on JBAS-4819:
----------------------------------

The JBoss Frontline Team has now completed the review of this manual

> TECH REVIEW: Installation Guide - TRACKER
> -----------------------------------------
>
>                 Key: JBAS-4819
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4819
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Installation Guide
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Michael Smith
>
> Tracker for Chapter Edits of the Installation Guide

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:38:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:38:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBXB-112) Failed to create a
	new SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13375090.1193823524658.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Thomas Diesler reopened JBXB-112:
---------------------------------

             
Did you update repository.jboss.org/jboss/jbossxb/snapshot as well?

[tdiesler at tddell snapshot]$ svn info
Path: .
URL: https://svn.jboss.org/repos/repository.jboss.org/jboss/jbossxb/snapshot
Repository Root: https://svn.jboss.org/repos/repository.jboss.org
Repository UUID: 51ec34b3-9f2d-0410-9c14-dfb4b5b5928d
Revision: 1724
Node Kind: directory
Schedule: normal
Last Changed Author: scott.stark at jboss.org
Last Changed Rev: 1654
Last Changed Date: 2007-10-25 07:06:07 +0200 (Thu, 25 Oct 2007)


> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:46:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:46:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4931) Fix ejb3
	ClientLaucher
Message-ID: <32592692.1193824004672.JavaMail.jira@cloud.prod.atl2.jboss.com>

Fix ejb3 ClientLaucher
----------------------

                 Key: JBAS-4931
                 URL: http://jira.jboss.com/jira/browse/JBAS-4931
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:48:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:48:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4931) Fix ejb3
	ClientLaucher
In-Reply-To: <32592692.1193824004672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7321225.1193824124814.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4931?page=all ]

Thomas Diesler updated JBAS-4931:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
      Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase 

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.82 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED

java.lang.RuntimeException: NYI
        at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:116)
        at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:99)
        at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:186)
        at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)

         Assignee: Carlo de Wolf

> Fix ejb3 ClientLaucher
> ----------------------
>
>                 Key: JBAS-4931
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4931
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.82 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED
> java.lang.RuntimeException: NYI
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:116)
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:99)
>         at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:186)
>         at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:54:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:54:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6150444.1193824485163.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Thomas Diesler updated JBAS-4924:
---------------------------------

    Assignee: Carlo de Wolf  (was: Thomas Diesler)

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4900) cannot redeploy
 after deployment error
In-Reply-To: <25923109.1193155741397.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <29316220.1193824605489.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4900?page=comments#action_12385229 ] 
            
Thomas Diesler commented on JBAS-4900:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> cannot redeploy after deployment error
> --------------------------------------
>
>                 Key: JBAS-4900
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4900
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>            Reporter: Thomas Diesler
>         Assigned To: Adrian Brock
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> If a deployment fails for any reason. The deployment cannot be redeployed because it "is already installed"
> This forces a restart of the appserver between debugging sessions.
> Caused by: java.lang.IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
>         at org.jboss.virtual.plugins.vfs.helpers.PathTokenizer.getTokens(PathTokenizer.java:67)
>         at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:266)
>         at org.jboss.virtual.plugins.context.jar.AbstractJarHandler.findChild(AbstractJarHandler.java:340)
>         at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:383)
>         at org.jboss.wsf.container.jboss50.VirtualFileAdaptor.findChild(VirtualFileAdaptor.java:62)
>         at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:239)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:254)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:260)
>         at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:129)
>         at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
>         at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
>         at org.jboss.wsf.container.jboss50.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:94)
>         at org.jboss.wsf.container.jboss50.AbstractWebServiceDeployer.deploy(AbstractWebServiceDeployer.java:63)
>         at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>         ... 62 more
> 18:00:22,664 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> ...
> 18:02:58,892 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> 18:02:58,897 WARN  [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS MISSING DEPLOYERS: Name
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war -> java.lang.IllegalStateException: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1798.war is already installed.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4901) Reverse paths are
 not allowed (containing a . or ..)
In-Reply-To: <29172279.1193157121519.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2759577.1193824605846.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4901?page=comments#action_12385230 ] 
            
Thomas Diesler commented on JBAS-4901:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> Reverse paths are not allowed (containing a . or ..)
> ----------------------------------------------------
>
>                 Key: JBAS-4901
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4901
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Ales Justin
>             Fix For: JBossAS-5.0.0.CR1
>
>
> This change breaks backward compatibility
> IllegalArgumentException: Reverse paths are not allowed (containing a . or ..), use getParent(): WEB-INF/wsdl//imported/my-service/1.0-SNAPSHOT/../../../common/1.0-SNAPSHOT/CoreComponentTypes.xsd
> To be lees strict, this should be valid
> vf.findChild("foo/bar/../file.txt")
> and this not
> vf.findChild("foo/bar/../../../file.txt")

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4902) nested jar not
	deployed
In-Reply-To: <22677462.1193157841505.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <1180764.1193824606020.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4902?page=comments#action_12385231 ] 
            
Thomas Diesler commented on JBAS-4902:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> nested jar not deployed
> -----------------------
>
>                 Key: JBAS-4902
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4902
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>            Priority: Critical
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> A nested jar inside an ear is not deployed 
> 2007-10-23 18:34:10,954 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,956 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,957 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at ee993e, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,963 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:10,964 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:10,965 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsing file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] for deploymentType: class org.jboss.metadata.ear.spec.EarMetaData
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,967 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true
> 2007-10-23 18:34:10,968 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl at 1ee5bba, isNamespaceAware: true, isValidating: true, isXIncludeAware: true
> 2007-10-23 18:34:10,973 DEBUG [org.jboss.deployment.AppParsingDeployer] Parsed file: JarEntryHandler at 12785233[path=META-INF/application.xml context=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear real=jar:file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear!/META-INF/application.xml] to: org.jboss.metadata.ear.spec.Ear14MetaData at 1f
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3 at 16f8834, cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,977 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=0}
> 2007-10-23 18:34:10,978 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Multiple class loaders found for pkg: 
> 2007-10-23 18:34:10,984 DEBUG [org.jboss.ejb3.deployers.EJBRegistrationDeployer] ********* EJBRegistrationDepoyer Begin Unit: jaxws-jbws1813.ear jar: jaxws-jbws1813.ear
> 2007-10-23 18:34:10,987 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 2
> 2007-10-23 18:34:10,992 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove deployment context: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling undeployment: vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear parent=null
> 2007-10-23 18:34:11,384 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Undeploying vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,387 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3 at 1e0025d{ url=vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear ,addedOrder=52}
> 2007-10-23 18:34:11,389 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Undeployed vfsfile:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws1813.ear
> [tdiesler at tddell jbossws-native-2.0.2]$ jar -ft output/tests/libs/jaxws-jbws1813.ear 
> META-INF/
> META-INF/MANIFEST.MF
> jaxws-jbws1813.jar
> META-INF/application.xml
> <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4">
>   
>   <module>
>     <java>jaxws-jbws1813.jar</java>
>   </module>
>   
> </application>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws1813  test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.016 sec
>     [junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4903) EJB 2.1 view
	cannot be realized
In-Reply-To: <30214185.1193159761504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3163056.1193824606199.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4903?page=comments#action_12385232 ] 
            
Thomas Diesler commented on JBAS-4903:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> EJB 2.1 view cannot be realized
> -------------------------------
>
>                 Key: JBAS-4903
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4903
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Andrew Lee Rubinger
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/jbws944  test
> 19:09:36,857 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-jbws944.jar
> 19:09:38,246 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 with dependencies:
> 19:09:38,246 INFO  [MCKernelAbstraction]   and supplies:
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteHome
> 19:09:38,247 INFO  [MCKernelAbstraction]        Class:org.jboss.test.ws.jaxws.jbws944.EJB3RemoteInterface
> 19:09:40,992 INFO  [EJBContainer] STARTED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,107 INFO  [EJBContainer] STOPPED EJB: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 ejbName: FooBean01
> 19:09:41,114 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:jar=jaxws-jbws944.jar,name=FooBean01,service=EJB3 state=Create
> java.lang.RuntimeException: org.jboss.test.ws.jaxws.jbws944.EJB3Bean01 defines home but provides no local/remote interfaces extending javax.ejb.EJBLocalObject/javax.ejb.EJBObject; EJB 2.1 view cannot be realized
>         at org.jboss.ejb3.session.BaseSessionProxyFactory.ensureEjb21ViewComplete(BaseSessionProxyFactory.java:139)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:82)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:179)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:114)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:228)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:121)
>         at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:82)
>         at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:124)
> @WebService(name = "EJB3Bean", serviceName = "EJB3BeanService", targetNamespace = "http://org.jboss.ws/jbws944")
> @WebContext(contextRoot = "/jaxws-jbws944", urlPattern = "/FooBean01")
> @SOAPBinding(style = SOAPBinding.Style.RPC)
> @Remote(EJB3RemoteInterface.class)
> @RemoteHome(EJB3RemoteHome.class)
> @RemoteBinding(jndiBinding = "/ejb3/EJB3EndpointInterface")
> @Stateless(name = "FooBean01")
> public class EJB3Bean01 implements EJB3RemoteInterface
> {
>    @WebMethod
>    public String echo(String input)
>    {
>       return input;
>    }
> }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14669290.1193824606353.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4923?page=comments#action_12385233 ] 
            
Thomas Diesler commented on JBAS-4923:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:56:46 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:56:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23805245.1193824606523.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4924?page=comments#action_12385234 ] 
            
Thomas Diesler commented on JBAS-4924:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:58:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:58:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4926)
 IncompleteDeploymentException prevents further deployments
In-Reply-To: <6697075.1193753582504.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15224889.1193824724789.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4926?page=comments#action_12385235 ] 
            
Thomas Diesler commented on JBAS-4926:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> IncompleteDeploymentException prevents further deployments
> ----------------------------------------------------------
>
>                 Key: JBAS-4926
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4926
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> It seems that an incomplete deployment prevents any further deployment
>     [junit] Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxrpc-jbws626.ear
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:820)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     [junit]     at java.lang.reflect.Method.invoke(Method.java:585)
>     [junit]     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>     [junit]     ... 45 more
>     [junit] Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
>     [junit] *** CONTEXTS IN ERROR: Name -> Error
>     [junit] vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/juddi-service.sar/ -> LifecycleException:  Pipeline has not been started
>     [junit]     at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:620)
>     [junit]     at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:393)
>     [junit]     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:58:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4930) Cannot lookup ejb3
	remote proxy
In-Reply-To: <16096432.1193822024649.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13109645.1193824725202.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4930?page=comments#action_12385236 ] 
            
Thomas Diesler commented on JBAS-4930:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> Cannot lookup ejb3 remote proxy
> -------------------------------
>
>                 Key: JBAS-4930
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4930
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test
> one-test:
>     [mkdir] Created dir: /home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/reports
>     [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 3.901 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED
> Testcase: testEJBClient took 0.023 sec
>         Caused an ERROR
> ejb not bound
> javax.naming.NameNotFoundException: ejb not bound
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
>         at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
>         at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
>         at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
>         at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
>         at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
>         at $Proxy0.lookup(Unknown Source)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
>         at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
>         at javax.naming.InitialContext.lookup(InitialContext.java:351)
>         at org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.testEJBClient(ServiceRefEJBTestCase.java:86)
> @Remote(EJBRemote.class)
> @RemoteBinding(jndiBinding = "/ejb/EJBClient")
> @Stateless
> public class EJBClient 
> {
>    ...
> }
>    public void testEJBClient() throws Exception
>    {      
>       // JAXWS <service-ref> is only supported in EE5 
>       if (isTargetJBoss50())
>       {
>          InitialContext iniCtx = getInitialContext();
>          EJBRemote ejbRemote = (EJBRemote)iniCtx.lookup("/ejb/EJBClient");
>          String helloWorld = "Hello World!";
>          Object retObj = ejbRemote.echo(helloWorld);
>          assertEquals(helloWorld, retObj);
>       }
>    }

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 05:58:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 05:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4931) Fix ejb3
	ClientLaucher
In-Reply-To: <32592692.1193824004672.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7809336.1193824725370.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4931?page=comments#action_12385237 ] 
            
Thomas Diesler commented on JBAS-4931:
--------------------------------------

Tests may be excluded from the compile target by the exclude file

https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt

This allows us to detect regression and have a unified testsuite across all supported containers
You will need to comment the exclude before you run tests-main

> Fix ejb3 ClientLaucher
> ----------------------
>
>                 Key: JBAS-4931
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4931
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.82 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED
> java.lang.RuntimeException: NYI
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:116)
>         at org.jboss.ejb3.client.ClientLauncher.loadXML(ClientLauncher.java:99)
>         at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:186)
>         at org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase.testApplicationClient(WebServiceRefClientTestCase.java:80)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:20:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:20:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4932) Failed
 testRoleSecuredServiceAccess
Message-ID: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>

Failed testRoleSecuredServiceAccess
-----------------------------------

                 Key: JBAS-4932
                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
            Reporter: Thomas Diesler




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:22:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:22:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4932) Failed
 testRoleSecuredServiceAccess
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21842646.1193826164662.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler updated JBAS-4932:
---------------------------------

    Description: 
[tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
    [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
    [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
    [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED

11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
java.rmi.AccessException: SecurityException; nested exception is: 
        java.lang.SecurityException: Denied: caller with subject=Subject:
        Principal: anonymous
        Principal: Roles(members)
 and security context post-mapping roles=Roles(members)
        at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
        at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
        at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
        at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
        at org.jboss.ejb.Container.invoke(Container.java:1013)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
        at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)


> Failed testRoleSecuredServiceAccess
> -----------------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:22:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:22:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4932) Failed
 testRoleSecuredServiceAccess
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10748819.1193826164842.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler updated JBAS-4932:
---------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
         Assignee: Scott M Stark

> Failed testRoleSecuredServiceAccess
> -----------------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:34:44 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:34:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4932) Invalid principal:
	anonymous
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <33118710.1193826884820.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler updated JBAS-4932:
---------------------------------

    Summary: Invalid principal: anonymous  (was: Failed testRoleSecuredServiceAccess)

> Invalid principal: anonymous
> ----------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:38:45 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 06:38:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-486) Optimize
	activations
Message-ID: <26176923.1193827125055.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-486?page=all ]

Manik Surtani updated JBCACHE-486:
----------------------------------

    Fix Version/s:     (was: 2.1.0.CR1)

> Optimize activations
> --------------------
>
>                 Key: JBCACHE-486
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-486
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.3.0.GA
>            Reporter: Jerry Gauthier
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.1.0.GA
>
>
> JBCACHE-420 notes that activation processing is performed excessively.  The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue.
> The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor.  Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated.  This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination.  This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader).
> It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance.  One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__
> to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when
> activated.  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:41:44 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 06:41:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-474) Compatibility fwk
 for all classes passed on the wire
Message-ID: <15960100.1193827304970.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-474?page=all ]

Manik Surtani updated JBCACHE-474:
----------------------------------

    Fix Version/s: 2.2.0.GA
                       (was: 2.1.0.GA)

> Compatibility fwk for all classes passed on the wire
> ----------------------------------------------------
>
>                 Key: JBCACHE-474
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-474
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.4SP1
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.2.0.GA
>
>
> Classes that are serialized:
> Fqn
> MethodCall (JG?)
> *Exception
> GlobalTransaction
> State transfers
> 1) Lets use JGroups Streamable where possible (dependency?  Externalizable instead?)
> 2) Provide a header short containing version
> 3) Use a MarshallingFactory for each version so we can understand messages from older installations
> 4) Provide MarshallingFactories as plugins so old versions can talk to newer versions (fwd compat)
> Object unmarshal(short version, Class type, InputStream is)
> {
> 	// if plugin directory empty or unset || version == currentVersion, revert back to existing mechanism
> 	// else
> 	// Look up UnmarshallerPlugin in the compat table (populated at startup with the contents of the plugin dir)
> 	// Lookup based on version and class type.  Unmarshaller then extracts and regenerates the relevant object.
> }
> Unit test as well.
> Standalone fwk?  jboss-compat.jar + plugins.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:45:45 2007
From: jira-events at lists.jboss.org (Thomas Diesler (JIRA))
Date: Wed, 31 Oct 2007 06:45:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBAS-4932) Invalid principal:
	anonymous
In-Reply-To: <10372480.1193826044582.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18435992.1193827545039.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4932?page=all ]

Thomas Diesler reassigned JBAS-4932:
------------------------------------

    Assignee: Anil Saldhana  (was: Scott M Stark)

> Invalid principal: anonymous
> ----------------------------
>
>                 Key: JBAS-4932
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4932
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/jbws723 test
> tests-run-internal:
>     [junit] Running org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase
>     [junit] FIXME: [JBAS-3595] - Tomcat allows http access with transport guarantie CONFIDENTIAL
>     [junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 44.363 sec
>     [junit] Test org.jboss.test.ws.jaxrpc.jbws723.JBWS723TestCase FAILED
> 11:13:23,483 INFO  [MCKernelAbstraction] installing bean: jboss.j2ee:jar=jaxrpc-jbws723-client.jar,name=jbossws-client,service=EJB3 with dependencies:
> 11:13:23,483 INFO  [MCKernelAbstraction]   and supplies:
> 11:13:23,761 INFO  [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: jbossws-client
> 11:13:33,532 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
> java.rmi.AccessException: SecurityException; nested exception is: 
>         java.lang.SecurityException: Denied: caller with subject=Subject:
>         Principal: anonymous
>         Principal: Roles(members)
>  and security context post-mapping roles=Roles(members)
>         at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388)
>         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:209)
>         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:138)
>         at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:651)
>         at org.jboss.ejb.Container.invoke(Container.java:1013)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.wsf.container.jboss50.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
>         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 06:52:44 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 06:52:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1207) Investigate
 failures in StateTransferUnderLoadTest
Message-ID: <31639318.1193827964640.JavaMail.jira@cloud.prod.atl2.jboss.com>

Investigate failures in StateTransferUnderLoadTest
--------------------------------------------------

                 Key: JBCACHE-1207
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1207
             Project: JBoss Cache
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: Manik Surtani
         Assigned To: Vladimir Blagojevic
             Fix For: 2.1.0.GA


This involves attempting to transfer state while having several concurrent put operations that *seem* to result in:

1) A block being issued
2) The put operation holding locks on the state generator
3) The put not being able to complete because of the block
4) The state transfer not being able to generate state because of the put operation
5) Deadlock!


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 07:58:45 2007
From: jira-events at lists.jboss.org (Shiva Shankar Reddy (JIRA))
Date: Wed, 31 Oct 2007 07:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1310)
 java.lang.NullPointerException at
 org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
Message-ID: <14615917.1193831925460.JavaMail.jira@cloud.prod.atl2.jboss.com>

java.lang.NullPointerException at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
-----------------------------------------------------------------------------------------------------------------------------------

                 Key: JBRULES-1310
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1310
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder
    Affects Versions: 4.0.3
         Environment: OS: Windows
hardware : Pentium Duo Core2,
Server: JBOSS4.X
Drools: 4.0.3
            Reporter: Shiva Shankar Reddy


when i am using  drools 3.x jars then rules are getting fired in a proper manner and working perfectly.
I have tried to migrate from 3.x to 4.0.3 then i am getting the following error.
I have tried changing jars and so on....  
2007-10-31 16:20:48,120 ERROR [STDERR] java.lang.NullPointerException
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)
2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.remote.rules.RulesEngineInvoker.readRule(RulesEngineInvoker.java :103)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.RuleService.doProcess(RuleService.java:318)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.invokeRuleService (FetchFSSData.java:140)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.triggerData(FetchFSSData.java:68)
2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData$1.run (FetchFSSData.java:84)
2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:00:44 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 08:00:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-112) Failed to create a new
	SAX parser
In-Reply-To: <23480384.1192442583823.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21454106.1193832044584.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-112?page=all ]

Alexey Loubyansky closed JBXB-112.
----------------------------------

    Resolution: Done

Now I did. Sorry, I didn't know you meant that one.

> Failed to create a new SAX parser
> ---------------------------------
>
>                 Key: JBXB-112
>                 URL: http://jira.jboss.com/jira/browse/JBXB-112
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Bug
>    Affects Versions: JBossXB-2.0.0.CR4
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-2.0.0.CR5
>
>
> package org.jboss.xb.binding.parser.sax;
> public class SaxJBossXBParser
>    public SaxJBossXBParser()
>       throws JBossXBException
>    {
> ...
>  parser = saxFactory.newSAXParser();
>          log.debug("Created parser: "+parser
>                + ", isNamespaceAware: "+parser.isNamespaceAware()
>                + ", isValidating: "+parser.isValidating()
>                + ", isXIncludeAware: "+parser.isXIncludeAware()
>                );
> This is the javadoc for isXIncludeAware:
> boolean javax.xml.parsers.SAXParser.isXIncludeAware()
> Get the XInclude processing mode for this parser.
> See Also:
> SAXParserFactory.setXIncludeAware(boolean)
> Returns:
> the return value of the SAXParserFactory.isXIncludeAware() when this parser was created from factory.
> Throws:
> UnsupportedOperationException For backward compatibility, when implementations for earlier versions of JAXP is used, this exception will be thrown.
> Since:
> 1.5
> Either we should not log it or catch and ignore the exception in XB.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:27:58 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 31 Oct 2007 08:27:58 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-107) The different types
 of classloader
 integration for AOP belong in the related release not jboss-head
Message-ID: <20303922.1193833678405.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ]

Kabir Khan closed JBAOP-107.
----------------------------

    Resolution: Done

Done for JBoss 5, AS 4 will remain as-is

> The different types of classloader integration for AOP belong in the related release not jboss-head
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JBAOP-107
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-107
>             Project: JBoss AOP
>          Issue Type: Task
>    Affects Versions: 2.0.0.alpha4
>            Reporter: Adrian Brock
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.CR1
>
>
> The JBoss classloading integration with JBossAOP should be managed by JBoss release,
> not by the aop/aspects modules in jboss-head.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:29:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 08:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1730)
 IdentityServiceControllerImpl : unregister existing MBean service before to
 re register them
In-Reply-To: <4337065.1191178121268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31028698.1193833784966.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=all ]

Thomas Heute resolved JBPORTAL-1730.
------------------------------------

    Resolution: Done

> IdentityServiceControllerImpl : unregister existing MBean service before to re register them
> --------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1730
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
> the Identity Beans are registered as JMX MBeans.
> When redeploying the service, an exception is thrown, as the services are yet deployed.
> javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
> Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
> // Unregister the former service is if it is yet there.
> // This to avoid the exception when redeploying this service
> if (getServer().isRegistered(
> 		new ObjectName(module.getServiceName()))) {
> 	getServer().unregisterMBean(
> 			new ObjectName(module.getServiceName()));
> }
> Thanks,

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 08:31:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 08:31:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1730)
 IdentityServiceControllerImpl : unregister existing MBean service before to
 re register them
In-Reply-To: <4337065.1191178121268.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7636610.1193833904647.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=comments#action_12385252 ] 
            
Thomas Heute commented on JBPORTAL-1730:
----------------------------------------

Thanks

> IdentityServiceControllerImpl : unregister existing MBean service before to re register them
> --------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-1730
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1730
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.1 Final
>            Reporter: Antoine Herzog
>         Assigned To: Thomas Heute
>            Priority: Optional
>             Fix For: 2.6.3 Final
>
>
> In IdentityServiceControllerImpl (service name="portal:service=Module,type=IdentityServiceController")
> the Identity Beans are registered as JMX MBeans.
> When redeploying the service, an exception is thrown, as the services are yet deployed.
> javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already registered.
> Let's put this code before to register the bean, at line 378 of IdentityServiceControllerImpl.java
> // Unregister the former service is if it is yet there.
> // This to avoid the exception when redeploying this service
> if (getServer().isRegistered(
> 		new ObjectName(module.getServiceName()))) {
> 	getServer().unregisterMBean(
> 			new ObjectName(module.getServiceName()));
> }
> Thanks,

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:13:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 09:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1597) i18n display
 name for portlet instances
In-Reply-To: <18247414.1184788607107.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31188280.1193836424641.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1597?page=all ]

Thomas Heute resolved JBPORTAL-1597.
------------------------------------

    Resolution: Done

> i18n display name for portlet instances
> ---------------------------------------
>
>                 Key: JBPORTAL-1597
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1597
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:19:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 09:19:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1736) Site structure
	i18n
In-Reply-To: <11410482.1191924963437.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17337815.1193836784886.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1736?page=all ]

Thomas Heute updated JBPORTAL-1736:
-----------------------------------

    Assignee: Thomas Heute  (was: Julien Viet)

> Site structure i18n
> -------------------
>
>                 Key: JBPORTAL-1736
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1736
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Portals, pages and windows (portal objects) should be i18nable. (So far only pages are, and not in a good manner)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:52:48 2007
From: jira-events at lists.jboss.org (Martin Trummer (JIRA))
Date: Wed, 31 Oct 2007 09:52:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4426) ADF integration!
In-Reply-To: <26955948.1179389152212.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2347994.1193838768491.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4426?page=comments#action_12385281 ] 
            
Martin Trummer commented on JBAS-4426:
--------------------------------------

make sure that you do not have the same library twice.
I got the same error, because I had 2 different versions of the same library (jsf-impl.jar):
* one in my .war archive under WEB-INF/lib
* the other one in jboss-4.2.0.GA\server\default\deploy\jboss-web.deployer\jsf-libs

removing the library from my .war archive fixed it

> ADF integration!
> ----------------
>
>                 Key: JBAS-4426
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4426
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.0.GA
>         Environment: ADF components from Oracle!
>            Reporter: Cristian Olaru
>
> When I deploy an application with ADF components inside I get this exception:
> 10:51:34,213 ERROR [[/aplicatie_test]] Exception thrown by attributes event listener
> java.lang.ClassCastException: com.sun.faces.application.ApplicationAssociate cannot be cast to com.sun.faces.application.ApplicationAssociate
>         at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:180)
>         at com.sun.faces.application.WebappLifecycleListener.getAssociate(WebappLifecycleListener.java:289)
>         at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:225)
>         at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:144)
>         at org.apache.catalina.connector.Request.setAttribute(Request.java:1435)
>         at org.apache.catalina.connector.RequestFacade.setAttribute(RequestFacade.java:503)
>         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:193)
>         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
>         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
>         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
>         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
>         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:619)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:58:45 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 31 Oct 2007 09:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1303) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <7852123.1193582641743.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <9329218.1193839125333.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1303?page=all ]

Fernando Meyer closed JBRULES-1303.
-----------------------------------

    Resolution: Duplicate Issue

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1303
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1303
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook running Leopard, Eclipse Europa, Java 1.5 (Mac OSX), Drools 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:58:45 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 31 Oct 2007 09:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1304) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <15904136.1193582881635.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27958853.1193839125470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1304?page=all ]

Fernando Meyer closed JBRULES-1304.
-----------------------------------

    Resolution: Duplicate Issue

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1304
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1304
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306 
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306 
> browser problems when submitting :( 

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 09:58:45 2007
From: jira-events at lists.jboss.org (Fernando Meyer (JIRA))
Date: Wed, 31 Oct 2007 09:58:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1305) Memory Leak when
 reusing cached RuleBase and retracting Facts
In-Reply-To: <13001809.1193583241581.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16533027.1193839125600.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1305?page=all ]

Fernando Meyer closed JBRULES-1305.
-----------------------------------

    Resolution: Duplicate Issue

> Memory Leak when reusing cached RuleBase and retracting Facts
> -------------------------------------------------------------
>
>                 Key: JBRULES-1305
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1305
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>         Environment: MacBook, Leopard, Java 1.5 for Mac OSX, Europa, Drools 4.0.2 and 4.0.3
>            Reporter: John Dunning
>
> THIS BUG IS RAISED IN 
> Key: JBRULES-1306
> URL: http://jira.jboss.com/jira/browse/JBRULES-1306
> browser problems when submitting :(

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:09:44 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 10:09:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1308) getFactHandle
 with equality-based assert behavior
In-Reply-To: <3690771.1193688062726.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18627585.1193839784820.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1308?page=all ]

Edson Tirelli reassigned JBRULES-1308:
--------------------------------------

    Assignee: Edson Tirelli

> getFactHandle with equality-based assert behavior
> -------------------------------------------------
>
>                 Key: JBRULES-1308
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1308
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.3
>            Reporter: Adam Lewandowski
>         Assigned To: Edson Tirelli
>         Attachments: GetFactHandleWithEqualityTest.java
>
>
> If I set my rule base to use equality-based assert behavior, I'm expecting to be able to use the getFactHandle(object) method to retrieve a previously asserted fact by providing an equivalent (by equals() and hashCode()) object as an argument. This appears to not be the case, as AbstractWorkingMemory uses it's identityMap and associated IdentityAssertMapComparator to do the getFactHandle lookup instead of the assertMap and EqualityAssertMapComparator. This causes the lookup to be done with the system hashCode() method and not the overridden version supplied in my fact class. The lookup thus fails and returns null. 
> See attached unit test.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:09:45 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 10:09:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBRULES-1310)
 java.lang.NullPointerException at
 org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
In-Reply-To: <14615917.1193831925460.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <26786757.1193839785978.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1310?page=all ]

Edson Tirelli reassigned JBRULES-1310:
--------------------------------------

    Assignee: Edson Tirelli

> java.lang.NullPointerException at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1310
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1310
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Drl Parser/Builder
>    Affects Versions: 4.0.3
>         Environment: OS: Windows
> hardware : Pentium Duo Core2,
> Server: JBOSS4.X
> Drools: 4.0.3
>            Reporter: Shiva Shankar Reddy
>         Assigned To: Edson Tirelli
>
> when i am using  drools 3.x jars then rules are getting fired in a proper manner and working perfectly.
> I have tried to migrate from 3.x to 4.0.3 then i am getting the following error.
> I have tried changing jars and so on....  
> 2007-10-31 16:20:48,120 ERROR [STDERR] java.lang.NullPointerException
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.remote.rules.RulesEngineInvoker.readRule(RulesEngineInvoker.java :103)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.RuleService.doProcess(RuleService.java:318)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.invokeRuleService (FetchFSSData.java:140)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData.triggerData(FetchFSSData.java:68)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at com.ess.framework.service.FetchFSSData$1.run (FetchFSSData.java:84)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 2007-10-31 16:20:48,120 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:09:46 2007
From: jira-events at lists.jboss.org (chris effenberger (JIRA))
Date: Wed, 31 Oct 2007 10:09:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (HIBERNATE-72) Use oracle to
 generate the id with the orcle seqence table
In-Reply-To: <13799401.1190037869830.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13603888.1193839786584.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/HIBERNATE-72?page=comments#action_12385285 ] 
            
chris effenberger commented on HIBERNATE-72:
--------------------------------------------

see the TopLink solution for the problem. there is a explanation int his blog:
http://www.it-eye.nl/weblog/2007/06/12/what-i-would-like-to-see-in-jpa-2/


> Use oracle to generate the id with the orcle seqence table
> ----------------------------------------------------------
>
>                 Key: HIBERNATE-72
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-72
>             Project: Hibernate
>          Issue Type: Bug
>         Environment: jboss-4.2.1
>            Reporter: chris effenberger
>         Assigned To: Steve Ebersole
>
> I want to use the ejb3 entity model.
> the PK should generated by the orcle sequence table not by hibernate.
> So I configure me bean with:
>     @GeneratedValue(generator="select")
>     @GenericGenerator(name="select", strategy="select",
>     		parameters = 
>     		{
>     		  @Parameter(name = "key", value = "idstoerung")
>             })
> The following error occurs:
> javax.ejb.EJBException: javax.persistence.PersistenceException: org.hibernate.HibernateException: Unable to resolve property: idstoerung
> 	at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
> 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> Caused by: javax.persistence.PersistenceException: org.hibernate.HibernateException: Unable to resolve property: idstoerung
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:629)
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:218)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:182)
> 	at de.dillinger.ww.stoerzeit.session.StoerzeitFacadeBean.aktiviereStoerungAn(StoerzeitFacadeBean.java:98)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
> 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
> 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
> 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
> 	at org.jboss.remoting.Client.invoke(Client.java:1550)
> 	at org.jboss.remoting.Client.invoke(Client.java:530)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy5.aktiviereStoerungAn(Unknown Source)
> 	at de.dillinger.ww.stoerzeit.test.TestClient.aktiviereStoerungAn(TestClient.java:90)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> 	at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> 	at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> 	at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71)
> 	at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
> 	at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
> 	at $Proxy5.aktiviereStoerungAn(Unknown Source)
> 	at de.dillinger.ww.stoerzeit.test.TestClient.aktiviereStoerungAn(TestClient.java:90)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
> 	at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
> 	at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
> 	at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71)
> 	at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
> 	at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
> 	at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
> 	at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: org.hibernate.HibernateException: Unable to resolve property: idstoerung
> 	at org.hibernate.tuple.entity.EntityMetamodel.getPropertyIndex(EntityMetamodel.java:439)
> 	at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValue(AbstractEntityTuplizer.java:286)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValue(AbstractEntityPersister.java:3586)
> 	at org.hibernate.id.SelectGenerator$SelectGeneratorDelegate.bindParameters(SelectGenerator.java:116)
> 	at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:54)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2158)
> 	at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2638)
> 	at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:48)
> 	at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250)
> 	at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:298)
> 	at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181)
> 	at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:107)
> 	at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:131)
> 	at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:87)
> 	at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38)
> 	at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:618)
> 	at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:592)
> 	at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:596)
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:212)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:182)
> 	at de.mycompany.StoerzeitFacadeBean.aktiviereStoerungAn(StoerzeitFacadeBean.java:98)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
> 	at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
> 	at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
> 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
> 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278)
> 	at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
> 	at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
> 	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:560)
> 	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
> 	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
> This happens when there is no property in the EntityMetamodel. 
> In ejb2.x we have our own class 
> @jboss.entity-command
>    class = "de.mycompany.OracleCreateCommand"
>    name = "oracle-sequence"
> so we become the generated id with the RETURNING
> Is such a configuration possible in EJB3?

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:36:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 10:36:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1737) Themes should
 be able to display text with the correct locale
In-Reply-To: <16743422.1191925098787.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24390644.1193841404690.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1737?page=all ]

Thomas Heute resolved JBPORTAL-1737.
------------------------------------

    Resolution: Won't Fix

> Themes should be able to display text with the correct locale
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1737
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1737
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core, Portal Theme
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Not sure what's the current state 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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:36:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 10:36:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1737) Themes should
 be able to display text with the correct locale
In-Reply-To: <16743422.1191925098787.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13714789.1193841404914.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1737?page=comments#action_12385297 ] 
            
Thomas Heute commented on JBPORTAL-1737:
----------------------------------------

It was actually already the case. The correct locale is passed in the HTTPRequest.

> Themes should be able to display text with the correct locale
> -------------------------------------------------------------
>
>                 Key: JBPORTAL-1737
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1737
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core, Portal Theme
>            Reporter: Thomas Heute
>         Assigned To: Thomas Heute
>             Fix For: 2.6.3 Final
>
>
> Not sure what's the current state 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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:42:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 10:42:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1129) Change
 default data stack to TCP
Message-ID: <15869414.1193841765690.JavaMail.jira@cloud.prod.atl2.jboss.com>

Change default data stack to TCP
--------------------------------

                 Key: JBMESSAGING-1129
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1129
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: 1.4.0.SP1


Default data stack is now TCP for better performance in smaller clusters

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:42:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 10:42:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1129) Change default
 data stack to TCP
In-Reply-To: <15869414.1193841765690.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <815780.1193841765975.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1129?page=all ]

Tim Fox closed JBMESSAGING-1129.
--------------------------------

    Resolution: Done

> Change default data stack to TCP
> --------------------------------
>
>                 Key: JBMESSAGING-1129
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1129
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 1.4.0.SP1
>
>
> Default data stack is now TCP for better performance in smaller clusters

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 10:44:45 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 10:44:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1115)
 java.net.SocketException: Too many open files
In-Reply-To: <24292710.1192769894777.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17387060.1193841885301.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1115?page=all ]

Tim Fox closed JBMESSAGING-1115.
--------------------------------

    Resolution: Won't Fix

Apparently this is because the user is using Spring JMS Template, which creates huge numbers of connections.


> java.net.SocketException: Too many open files
> ---------------------------------------------
>
>                 Key: JBMESSAGING-1115
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1115
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.4.0.SP1
>
>
> When loading large messages into a queue, the JBM server can not handle the request of open files and starts unloading. This occurred at sending approximately 5000 emails to the queue.
> 2007-10-03 18:10:20,677 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[10.152.1.72:4457] failed to handle socket
> java.net.SocketException: Too many open files
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
>         at java.net.ServerSocket.implAccept(ServerSocket.java:450)
>         at java.net.ServerSocket.accept(ServerSocket.java:421)
>         at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:520)
>         at java.lang.Thread.run(Thread.java:595)
> 2007-10-03 18:10:24,171 WARN  [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/opt/jboss-eap-4.2/server/production/deploy', reason unknown

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:06:45 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 31 Oct 2007 11:06:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (EJBTHREE-1094) Update wiki page
 "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
In-Reply-To: <816416.1193816514805.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19528888.1193843205275.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1094?page=all ]

William DeCoste reassigned EJBTHREE-1094:
-----------------------------------------

    Assignee: William DeCoste

> Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0
> ---------------------------------------------------------------------
>
>                 Key: EJBTHREE-1094
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1094
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Ron Sigal
>         Assigned To: William DeCoste
>
> 1. As of Remoting 2.2.x, the Object Name of the org.jboss.remoting.transport.servlet.ServerServletInvoker is hard coded as "jboss.remoting:service=invoker,transport=servlet", which means that only a single instance of ServerServletInvoker can be created.  That would be a problem if, say, EJB3 and JBossMessaging both wanted to use the servlet transport.
> As of Remoting 2.4.0, the Object Name will be generated by org.jboss.remoting.ServerInvoker.getMBeanObjectName(), which adds values for "host", "port", and any other parameters on the InvokerLocator.  For example, the Object Name for the ServerServletInvoker in the example is now
>    jboss.remoting:service=invoker,transport=servlet,host=127.0.0.1,port=8080
> 2. While the https example works for org.apache.coyote.http11.Http11Protocol (the non-native version), it doesn't seem to work with org.apache.coyote.http11.Http11AprProtocol.  It seems that jbossweb wants keystores in openssl PEM format.  I must be missing something, though, because I couldn't get it to work with APR.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:13:44 2007
From: jira-events at lists.jboss.org (Thomas Heute (JIRA))
Date: Wed, 31 Oct 2007 11:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1775) Let a user
 define multiple
 display-name for a portlet-instance in the admin portlet
Message-ID: <27848379.1193843624923.JavaMail.jira@cloud.prod.atl2.jboss.com>

Let a user define multiple display-name for a portlet-instance in the admin portlet
-----------------------------------------------------------------------------------

                 Key: JBPORTAL-1775
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1775
             Project: JBoss Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Portal Core Admin
            Reporter: Thomas Heute
         Assigned To: Wesley Hales
             Fix For: 2.6.3 Final


When an administrator creates a new portlet-instance, he should be able to define (and edit) different display-names for a single instance.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:15:44 2007
From: jira-events at lists.jboss.org (Alejandro Guizar (JIRA))
Date: Wed, 31 Oct 2007 11:15:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (BPEL-282) Engine runs process
 instances in serie instead of in parallel
In-Reply-To: <7870750.1193112683491.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12161805.1193843744898.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/BPEL-282?page=all ]

Alejandro Guizar updated BPEL-282:
----------------------------------

       Issue Type: Feature Request  (was: Bug)
    Fix Version/s: jBPM BPEL 1.1 GA

> Engine runs process instances in serie instead of in parallel
> -------------------------------------------------------------
>
>                 Key: BPEL-282
>                 URL: http://jira.jboss.com/jira/browse/BPEL-282
>             Project: JBoss jBPM BPEL
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>         Environment: RHEL
>            Reporter: Santiago Erquicia
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> We are stress testing a BPEL process and we found out that the engine runs all the requests it receives in serie. That means that if there are two or more concurrent users of the system, one has to wait till the first process instance stops at some point (wait state) so the other request can be processed.
> On our test environment, we are calling a web service which is also calling another web service. The are connection problems with the second one, so from time to time the web service just times out. This means that a concurrent user has to wait for that time out, and whatever is left of that process instance, in order to be processed.
> On our JMeter test, the throughput keeps stable even if there number of request is bigger than the throughput of the BPEL engine. The result is that the time for response of each process request increases indefinitely if the usage is bigger than the throughput. This obviously doesn't scale at all for the processing requirement we are considering.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:23:58 2007
From: jira-events at lists.jboss.org (Mircea Markus (JIRA))
Date: Wed, 31 Oct 2007 11:23:58 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1153) Introduce a
 concept of structural nodes
In-Reply-To: <6252571.1185539387065.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8166264.1193844238855.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1153?page=all ]

Mircea Markus resolved JBCACHE-1153.
------------------------------------

    Resolution: Won't Fix

as per foru, discussion decided to allow the user to to mark nodes as 'structural' using the resident flag.

> Introduce a concept of structural nodes
> ---------------------------------------
>
>                 Key: JBCACHE-1153
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1153
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Manik Surtani
>         Assigned To: Mircea Markus
>             Fix For: 2.2.0.GA
>
>
> Structural nodes should not be taken into consideration when processing regions for eviction.
> Typically are nodes that do not contain data (and are not intended to contain data), but are used to build tree structure.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:27:45 2007
From: jira-events at lists.jboss.org (Shane Preater (JIRA))
Date: Wed, 31 Oct 2007 11:27:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-933) NPE when
 deploying web service beans
In-Reply-To: <16564123.1175251646383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20738161.1193844465152.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-933?page=comments#action_12385317 ] 
            
Shane Preater commented on EJBTHREE-933:
----------------------------------------

I am getting this exact error when attempting to deploy a local ejb 2.x session bean which is being referenced by an Ejb 3 session bean.

I am using 4.2.1.GA and the stack is thus:

15:22:07,875 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=migrationTesting.jar,na
me=EJB3BusinessInterfaceImplementation,service=EJB3 is not registered
15:22:07,875 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=migrationTesting.jar,na
me=RemoteHomeTest,service=EJB3 is not registered
15:22:07,875 WARN  [JmxKernelAbstraction] jboss.j2ee:jar=migrationTesting.jar,na
me=LocalHomeTest,service=EJB3 is not registered
15:22:08,296 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jbo
ss.ejb3.stateless.StatelessContainer
15:22:08,296 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=migra
tionTesting.jar,name=EJB3BusinessInterfaceImplementation,service=EJB3 with depen
dencies:
15:22:08,296 INFO  [JmxKernelAbstraction]       jboss.j2ee:jar=migrationTesting.
jar,name=LocalHomeTest,service=EJB3
15:22:08,312 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jbo
ss.ejb3.stateless.StatelessContainer
15:22:08,312 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=migra
tionTesting.jar,name=RemoteHomeTest,service=EJB3 with dependencies:
15:22:08,312 INFO  [JmxKernelAbstraction]       jboss.j2ee:jar=migrationTesting.
jar,name=LocalHomeTest,service=EJB3
15:22:08,312 INFO  [JmxKernelAbstraction] creating wrapper delegate for: org.jbo
ss.ejb3.stateless.StatelessContainer
15:22:08,312 INFO  [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=migra
tionTesting.jar,name=LocalHomeTest,service=EJB3 with dependencies:
15:22:08,343 INFO  [EJBContainer] STARTED EJB: com.aeroint.ejbtest.server.sessio
n.LocalHomeTestEJB ejbName: LocalHomeTest
15:22:08,343 INFO  [EJBContainer] STOPPED EJB: com.aeroint.ejbtest.server.sessio
n.LocalHomeTestEJB ejbName: LocalHomeTest
15:22:08,359 WARN  [ServiceController] Problem starting service jboss.j2ee:jar=m
igrationTesting.jar,name=LocalHomeTest,service=EJB3
java.lang.NullPointerException
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(St
atelessRemoteProxyFactory.java:75)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStateless
ProxyFactory.java:172)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRe
moteProxyFactory.java:100)
        at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStateles
sProxyFactory.java:221)
        at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessR
emoteProxyFactory.java:107)
        at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
        at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:128)
        at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.
java:94)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWra
pper.java:103)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy66.start(Unknown Source)
        at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java
:120)
        at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.jav
a:301)
        at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:362)
        at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy32.start(Unknown Source)
        at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
        at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
rServiceMBeanSupport.java:238)
        at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerIn
terceptor.java:93)
        at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
start(SubDeployerInterceptorSupport.java:188)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:95)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy33.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy9.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:610)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:274)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:225)
15:22:08,453 INFO  [EJB3Deployer] Deployed: file:/C:/sapphire_system/jboss-4.2.1
.GA/server/default/deploy/migrationTesting.jar
15:22:08,468 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

> NPE when deploying web service beans
> ------------------------------------
>
>                 Key: EJBTHREE-933
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-933
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Heiko Braun
>
> The exception:
> java.lang.NullPointerException
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:74)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:172)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:100)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:221)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107)
>         at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
>         at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94)
> The bean that get's deployed:
> package com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest;
> import javax.ejb.Stateless;
> import javax.jws.WebService;
> @WebService(
>     portName="Hello", 
>     serviceName="HelloService", 
>     targetNamespace="http://Hello.org",
>     wsdlLocation="META-INF/wsdl/HelloService.wsdl",
>     endpointInterface="com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest.Hello")
> @Stateless(name="WSEjbPortFieldInjectionTest")
> public class HelloBean {
>    public String hello(String str)
>    {
>       return "WebSvcTest-Hello " + str;
>    }
>    public String bye(String str)
>    {
>       return "WebSvcTest-Bye and take care " + str;
>    }
> }
> The spec:
> Session bean's business interface(s), if the session bean provides an EJB 3.0 local or remote
> client view.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:31:44 2007
From: jira-events at lists.jboss.org (Heiko Braun (JIRA))
Date: Wed, 31 Oct 2007 11:31:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-933) NPE when
 deploying web service beans
In-Reply-To: <16564123.1175251646383.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <3125750.1193844704570.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-933?page=comments#action_12385319 ] 
            
Heiko Braun commented on EJBTHREE-933:
--------------------------------------

Shane, the error you see was fixed upstream. 4.2.1 probably uses an EJB3 version that doesn't contain the fix. However you could workaround by implementing a remote interface on that bean.

> NPE when deploying web service beans
> ------------------------------------
>
>                 Key: EJBTHREE-933
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-933
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Heiko Braun
>
> The exception:
> java.lang.NullPointerException
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:74)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:172)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:100)
>         at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:221)
>         at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107)
>         at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83)
>         at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124)
>         at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94)
> The bean that get's deployed:
> package com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest;
> import javax.ejb.Stateless;
> import javax.jws.WebService;
> @WebService(
>     portName="Hello", 
>     serviceName="HelloService", 
>     targetNamespace="http://Hello.org",
>     wsdlLocation="META-INF/wsdl/HelloService.wsdl",
>     endpointInterface="com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest.Hello")
> @Stateless(name="WSEjbPortFieldInjectionTest")
> public class HelloBean {
>    public String hello(String str)
>    {
>       return "WebSvcTest-Hello " + str;
>    }
>    public String bye(String str)
>    {
>       return "WebSvcTest-Bye and take care " + str;
>    }
> }
> The spec:
> Session bean's business interface(s), if the session bean provides an EJB 3.0 local or remote
> client view.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:46:14 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 11:46:14 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4914) NPE in JBossWebRealm
In-Reply-To: <319962.1193403961627.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28929124.1193845574382.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4914?page=all ]

Scott M Stark resolved JBAS-4914.
---------------------------------

    Resolution: Done

one-test:
    [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSE
TestCase
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 17.609 sec

BUILD SUCCESSFUL
Total time: 19 seconds
[starksm at valkyrie jbossws-native-2.0.2]$

> NPE in JBossWebRealm
> --------------------
>
>                 Key: JBAS-4914
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4914
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Scott M Stark
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase 
> one-test:
>     [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase
>     [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 4.809 sec
>     [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase FAILED
> java.lang.NullPointerException
>         at org.jboss.web.tomcat.security.JBossWebRealm.hasRole(JBossWebRealm.java:536)
>         at org.apache.catalina.connector.Request.isUserInRole(Request.java:2184)
>         at org.apache.catalina.connector.RequestFacade.isUserInRole(RequestFacade.java:763)
>         at org.jboss.wsf.spi.invocation.WebServiceContextJSE.isUserInRole(WebServiceContextJSE.java:61)
>         at org.jboss.test.ws.jaxws.samples.context.EndpointJSE.testIsUserInRole(EndpointJSE.java:60)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 11:55:44 2007
From: jira-events at lists.jboss.org (Bela Ban (JIRA))
Date: Wed, 31 Oct 2007 11:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-610) Problems with large
 return value and FC
In-Reply-To: <29012914.1193384701402.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25464989.1193846144842.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-610?page=comments#action_12385326 ] 
            
Bela Ban commented on JGRP-610:
-------------------------------

Detailed explanation:
- A unicast is received. This acquires a (sender-based) lockin UNICAST on its way up
- When the message is received, the RpcDispatcher sends the large return value back *on the same thread* (the lock in UNICAST is not released)
- FRAG2 splits the return message into many smaller messages
- All messages are sent down, but when max_credits is exceeded, FC.down() blocks. This means the lock in UNICAST is *still* not released
- On the receiver side (sender == receiver), incoming calls cannot reach FC due to the lock in UNICAST (because FC is somewhere above 
  UNICAST), therefore FC will not send new credits (via OOB) to unblock the sender
- The only way credits will be received is for the sender to periodically (max_block_time ms) send an OOB credit request and unblock when it 
  receives the credit response
- However, even OOB messages will not get processed when the default thread pool in TP has the queue *disabled* and all threads are *busy* !

> Problems with large return value and FC
> ---------------------------------------
>
>                 Key: JGRP-610
>                 URL: http://jira.jboss.com/jira/browse/JGRP-610
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.6
>
>
> When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:01:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:01:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1095)
 ConsumerContainer throws NoInitialContextException on stop
Message-ID: <3234104.1193846504671.JavaMail.jira@cloud.prod.atl2.jboss.com>

ConsumerContainer throws NoInitialContextException on stop
----------------------------------------------------------

                 Key: EJBTHREE-1095
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1095
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf
         Assigned To: Carlo de Wolf
            Priority: Critical
             Fix For: AS 4.2.3.GA


2007-10-31 16:22:11,905 WARN  [org.jboss.ejb3.ServiceDelegateWrapper] Stopping failed jboss.j2ee:jar=consumer-test.jar,name=QueueTestConsumer,service=EJB3
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
	at javax.naming.InitialContext.getNameParser(InitialContext.java:439)
	at org.jboss.util.naming.Util.unbind(Util.java:135)
	at org.jboss.ejb3.mdb.ProducerFactory.stop(ProducerFactory.java:150)
	at org.jboss.ejb3.mdb.RemoteProducerFactory.stop(RemoteProducerFactory.java:99)
	at org.jboss.ejb3.mdb.ConsumerContainer.unregisterProducers(ConsumerContainer.java:286)
	at org.jboss.ejb3.mdb.ConsumerContainer.stop(ConsumerContainer.java:304)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.stop(Unknown Source)
	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy69.stop(Unknown Source)
	at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
	at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
	at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
	at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.stop(Unknown Source)
	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy33.stop(Unknown Source)
	at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
	at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy34.stop(Unknown Source)
	at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
	at sun.rmi.transport.Transport$1.run(Transport.java:153)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
	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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:01:44 2007
From: jira-events at lists.jboss.org (Jason Long (JIRA))
Date: Wed, 31 Oct 2007 12:01:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
Message-ID: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>

Make SLSB and SFSB hot deployable for RAD
-----------------------------------------

                 Key: EJBTHREE-1096
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
             Project: EJB 3.0
          Issue Type: Feature Request
    Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA, AS 5.0.0.Beta3, AS 4.2.3.GA, Branch_4_2, Branch_4_4, HEAD
            Reporter: Jason Long
             Fix For: AS 4.2.3.GA


Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:03:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:03:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1095)
 ConsumerContainer throws NoInitialContextException on stop
In-Reply-To: <3234104.1193846504671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18712043.1193846624608.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1095?page=comments#action_12385333 ] 
            
Carlo de Wolf commented on EJBTHREE-1095:
-----------------------------------------

MessagingContainer.getJMSProviderAdapter closes the context associated with the EJBContainer.

> ConsumerContainer throws NoInitialContextException on stop
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1095
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1095
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 4.2.3.GA
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> 2007-10-31 16:22:11,905 WARN  [org.jboss.ejb3.ServiceDelegateWrapper] Stopping failed jboss.j2ee:jar=consumer-test.jar,name=QueueTestConsumer,service=EJB3
> javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> 	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
> 	at javax.naming.InitialContext.getNameParser(InitialContext.java:439)
> 	at org.jboss.util.naming.Util.unbind(Util.java:135)
> 	at org.jboss.ejb3.mdb.ProducerFactory.stop(ProducerFactory.java:150)
> 	at org.jboss.ejb3.mdb.RemoteProducerFactory.stop(RemoteProducerFactory.java:99)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.unregisterProducers(ConsumerContainer.java:286)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.stop(ConsumerContainer.java:304)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy69.stop(Unknown Source)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
> 	at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
> 	at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy33.stop(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy34.stop(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:05:45 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:05:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1097)
 InitialContextFactory doesn't always create a new InitialContext
Message-ID: <25475823.1193846745189.JavaMail.jira@cloud.prod.atl2.jboss.com>

InitialContextFactory doesn't always create a new InitialContext
----------------------------------------------------------------

                 Key: EJBTHREE-1097
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097
             Project: EJB 3.0
          Issue Type: Bug
    Affects Versions: AS 4.2.2.GA
            Reporter: Carlo de Wolf


InitialContextFactory is not really a factory, it doesn't always create a new InitialContext.
This can lead to interesting situations if someone closes an InitialContext which doesn't have any properties and then tries to reuse it.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:11:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 12:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
In-Reply-To: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31106516.1193847104987.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=all ]

Carlo de Wolf updated EJBTHREE-1096:
------------------------------------

        Fix Version/s:     (was: AS 4.2.3.GA)
    Affects Version/s:     (was: AS 5.0.0.Beta3)
                           (was: AS 4.2.0 GA)
                           (was: AS 4.2.1.GA)
                           (was: Branch_4_2)
                           (was: Branch_4_4)
                           (was: HEAD)
                           (was: AS 4.2.3.GA)

> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
>                 Key: EJBTHREE-1096
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:29:48 2007
From: jira-events at lists.jboss.org (Vladimir Blagojevic (JIRA))
Date: Wed, 31 Oct 2007 12:29:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JGRP-609) Javadoc
	JChannelFactory
In-Reply-To: <12343365.1193244781608.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12962568.1193848188929.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JGRP-609?page=comments#action_12385341 ] 
            
Vladimir Blagojevic commented on JGRP-609:
------------------------------------------

Let me know of any further changes you may suggest.

Vladimir


    /**
     * Creates an implementation of the Channel using a given stack name and
     * registering it under a given identity.
     * <p>
     *
     * Channel has to be created with a unique application id per stack name.
     *
     * <p>
     * Provided stack name has to be one of the stacks defined in a property
     * file that was passed to setMultiplexerConfig (e.g conf/stacks.xml). If
     * clients attempt to create a Channel for an undefined stack name or
     * they attempt to register a duplicate Channel per stack an Exception will be
     * thrown.
     *
     *
     * <p>
     * Rather than having each multiplexed channel do a separate state transfer
     * clients can bundle state transfers for all channels created with the same
     * ChannelFactory. First of all, clients have to create Channels with
     * register_for_state_transfer set to true. After the last Channel that was
     * created with register_for_state_transfer set to true connects and
     * initiates state transfer the actual state transfer for all such channels
     * from this ChannelFactory is executed.
     *
     * <p>
     * Using bundled state transfers is especially useful with the FLUSH
     * protocol in a stack. Recall that each state transfer triggers a flush and
     * thus instead of doing a separate flush for each Channel created with this
     * ChannelFactory we execute only one flush for all state transfers.
     *
     * <p>
     * However, be aware of the implication of asynchronous nature of bundled
     * state transfer with the respect of channel connect. Recall that each
     * Channel after it returns from successful getState method can assume that
     * state is available. In case of bundled state transfer, state will be set
     * only <strong>after</strong> the last Channel registered for the bundled
     * state transfer connects and executes getState.
     *
     *
     *
     *
     * @param stack_name
     *            The name of the stack to be used. All stacks are defined in
     *            the configuration with which the factory is configured (see
     *            {@link #setMultiplexerConfig(Object)} for example.
     * @param id
     *            The identifier used for multiplexing and demultiplexing
     *            (dispatching requests to one of possibly multiple receivers).
     *            Note that id needs to be a string since it will be shipped
     *            with each message. Try to pick a short string, because this is
     *            shipped with every message (overhead).
     * @param register_for_state_transfer
     *            If set to true, after all registered listeners called
     *            connect() on the returned Channel, the state for all
     *            registered listeners will be fetched and set in all listeners
     * @param substate_id
     *            The ID of the substate to be retrieved. Set this to null if
     *            the entire state should be retrieved. If
     *            register_for_state_transfer is false, substate_id will be
     *            ignored
     *            
     *            
     * @return An implementation of Channel which keeps track of the id, so that
     *         it can be attached to each message and be properly dispatched at
     *         the receiver.
     *         
     * @see Multiplexer
     * @see MuxChannel
     *         
     * @throws ChannelException
     */

> Javadoc JChannelFactory
> -----------------------
>
>                 Key: JGRP-609
>                 URL: http://jira.jboss.com/jira/browse/JGRP-609
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.5.1
>            Reporter: Brian Stansberry
>         Assigned To: Vladimir Blagojevic
>             Fix For: 2.5.2, 2.6
>
>
> org.jgroups.JChannelFactory and org.jgroups.jmx.JChannelFactory need javadoc, particularly createMultiplexerChannel(String, String, boolean, String).  See JBMESSAGING-1120 for an example of the cost of misunderstanding this API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:29:49 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 12:29:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBXB-115) remove use of
 System.out from XsdBinder
Message-ID: <2329678.1193848189064.JavaMail.jira@cloud.prod.atl2.jboss.com>

remove use of System.out from XsdBinder
---------------------------------------

                 Key: JBXB-115
                 URL: http://jira.jboss.com/jira/browse/JBXB-115
             Project: JBoss XML Binding (JBossXB)
          Issue Type: Task
    Affects Versions: JBossXB-1.0.0.SP1
            Reporter: Alexey Loubyansky
         Assigned To: Alexey Loubyansky
             Fix For: JBossXB-1.0.0.SP2


$ svn diff
Index: main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java
===================================================================
--- main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (revision 2639)
+++ main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (working copy)
@@ -852,7 +852,7 @@
             ctx.simpleContentWithIdAsSimpleType &&
             particle == null && hasOnlyIdAttrs)
       {
-         binding.setStartElementCreatesObject(false);System.out.println("no object for " + binding.getQName());
+         binding.setStartElementCreatesObject(false);
       }
       else

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:33:44 2007
From: jira-events at lists.jboss.org (Alexey Loubyansky (JIRA))
Date: Wed, 31 Oct 2007 12:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBXB-115) remove use of
 System.out from XsdBinder
In-Reply-To: <2329678.1193848189064.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27831143.1193848424577.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBXB-115?page=all ]

Alexey Loubyansky closed JBXB-115.
----------------------------------

    Resolution: Done

Fixed.

> remove use of System.out from XsdBinder
> ---------------------------------------
>
>                 Key: JBXB-115
>                 URL: http://jira.jboss.com/jira/browse/JBXB-115
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Task
>    Affects Versions: JBossXB-1.0.0.SP1
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: JBossXB-1.0.0.SP2
>
>
> $ svn diff
> Index: main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java
> ===================================================================
> --- main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (revision 2639)
> +++ main/java/org/jboss/xb/binding/sunday/unmarshalling/XsdBinder.java  (working copy)
> @@ -852,7 +852,7 @@
>              ctx.simpleContentWithIdAsSimpleType &&
>              particle == null && hasOnlyIdAttrs)
>        {
> -         binding.setStartElementCreatesObject(false);System.out.println("no object for " + binding.getQName());
> +         binding.setStartElementCreatesObject(false);
>        }
>        else

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:37:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 12:37:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1130) Remove unused
 column INST_TIME
Message-ID: <11935598.1193848664775.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remove unused column INST_TIME
------------------------------

                 Key: JBMESSAGING-1130
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1130
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Tim Fox
         Assigned To: Tim Fox
             Fix For: EAP 4.3 Integration




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:48:49 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 12:48:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <20674535.1193849329490.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-3885?page=comments#action_12385358 ] 
            
Dimitris Andreadis commented on JBAS-3885:
------------------------------------------

Actually, the problem is that the RMI registry that is created to store the remote object reference for the JMXConnectorServer, binds to all interfaces by default. 

Then the same registry is seen by both servers, and the second registration fails, because the same name is used. 


> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:50:45 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 12:50:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1208) CacheFactory to
 allow creation from InputStreams
Message-ID: <6022219.1193849445024.JavaMail.jira@cloud.prod.atl2.jboss.com>

CacheFactory to allow creation from InputStreams 
-------------------------------------------------

                 Key: JBCACHE-1208
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1208
             Project: JBoss Cache
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
    Affects Versions: 2.0.0.GA
            Reporter: Manik Surtani
         Assigned To: Manik Surtani
             Fix For: 2.1.0.GA




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:50:45 2007
From: jira-events at lists.jboss.org (Manik Surtani (JIRA))
Date: Wed, 31 Oct 2007 12:50:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-1208) CacheFactory to
 allow creation from InputStreams
In-Reply-To: <6022219.1193849445024.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23496907.1193849445318.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1208?page=all ]

Manik Surtani resolved JBCACHE-1208.
------------------------------------

    Resolution: Done

> CacheFactory to allow creation from InputStreams 
> -------------------------------------------------
>
>                 Key: JBCACHE-1208
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1208
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA
>            Reporter: Manik Surtani
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:55:44 2007
From: jira-events at lists.jboss.org (Emmanuel Bernard (JIRA))
Date: Wed, 31 Oct 2007 12:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
In-Reply-To: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4216294.1193849744708.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_12385363 ] 
            
Emmanuel Bernard commented on EJBTHREE-1096:
--------------------------------------------

+1

> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
>                 Key: EJBTHREE-1096
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 12:55:44 2007
From: jira-events at lists.jboss.org (Tim Fox (JIRA))
Date: Wed, 31 Oct 2007 12:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1128) Message not
 routed from one node to node with only consumer.
In-Reply-To: <15994322.1193778405017.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23844085.1193849744953.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1128?page=all ]

Tim Fox updated JBMESSAGING-1128:
---------------------------------

    Fix Version/s: EAP 4.3 Integration

> Message not routed from one node to node with only consumer.
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1128
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
>            Reporter: Mike Clark
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> In trying to reproduce behavior described in case 18885, I can reproduce the following:
> Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.
> Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)
> Both instances were created from a clean "all" instance.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:01:44 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 13:01:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBRULES-1311) NPE when
 compiling rule consequences
Message-ID: <32316553.1193850104902.JavaMail.jira@cloud.prod.atl2.jboss.com>

NPE when compiling rule consequences
------------------------------------

                 Key: JBRULES-1311
                 URL: http://jira.jboss.com/jira/browse/JBRULES-1311
             Project: JBoss Drools
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Drl Parser/Builder, Rule Assemply/SPI
    Affects Versions: 4.0.3, 4.0.2, 4.0.1,  4.0.0.GA
            Reporter: Edson Tirelli
         Assigned To: Edson Tirelli
             Fix For: 4.1.0


I have the following code: (note String[] ruleFiles contains only one string)

 

public class Engine {

    private static RuleBase ruleBase;

 

    public void start(String[] ruleFiles) throws Exception {

        PackageBuilderConfiguration cfg = new PackageBuilderConfiguration();

        JavaDialectConfiguration javaConf = (JavaDialectConfiguration) cfg.getDialectConfiguration("java");

        javaConf.setCompiler(JavaDialectConfiguration.ECLIPSE);

        PackageBuilder builder = new PackageBuilder(cfg);

        for (String file : ruleFiles) {

            builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file)));

        }

        Package pkg = builder.getPackage();

 

        PackageBuilderErrors errors = builder.getErrors();

        if (errors.getErrors().length != 0) {

            // do something

        }

 

        RuleBaseConfiguration conf = new RuleBaseConfiguration();

        conf.setAssertBehaviour(RuleBaseConfiguration.AssertBehaviour.EQUALITY);

 

        ruleBase = RuleBaseFactory.newRuleBase();

        ruleBase.addPackage(pkg);

        ruleBase.newStatefulSession(false);

 

    }

}

 

At the builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file))); line I'm getting the following exception:

java.lang.NullPointerException

            at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)

            at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)

            at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)

            at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)

            at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:167)

            at myPackage.rivoli.service.rules.Engine.start(Engine.java:33)

            at myPackage.rivoli.rules.LeaderKingAndHeirTest.setUp(LeaderKingAndHeirTest.java:26)

            at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

            at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)

 

I am using Drools 4.0.3

I have the following jars in my class path:

antlr-runtime-3.0.jar

core-3.2.3.v_686_R32x.jar

drools-compiler-4.0.3.jar

drools-core-4.0.3.jar

mvel14-1.2.10.jar

 

Any ideas would be helpful. Thanks.

 
rule "leaders in same location"

salience 10

when

    $result : RuleResult(rulesPassed not contains "leaders in same location")

    $loc : LocationImpl()

    $leaderName : String()

    $leader1 : LeaderImpl(name == $leaderName, location == $loc)

    $leader2 : LeaderImpl(name != $leaderName, this != $leader1, location == $loc)

then

    $result.addPassedRule(leaders in same location);

    update($result);

end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:03:55 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:03:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4933) Upgrade to jbossxb
 1.0.0.SP2 (from 1.0.0.SP1)
Message-ID: <33091523.1193850235177.JavaMail.jira@cloud.prod.atl2.jboss.com>

Upgrade to jbossxb 1.0.0.SP2 (from 1.0.0.SP1)
---------------------------------------------

                 Key: JBAS-4933
                 URL: http://jira.jboss.com/jira/browse/JBAS-4933
             Project: JBoss Application Server
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
          Components: XML services
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Dimitris Andreadis
         Assigned To: Dimitris Andreadis
             Fix For: JBossAS-4.2.3.GA


Needed for fixing JBXB-115 (and anything else that pops up).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:17:44 2007
From: jira-events at lists.jboss.org (Edson Tirelli (JIRA))
Date: Wed, 31 Oct 2007 13:17:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBRULES-1311) NPE when compiling
 rule consequences
In-Reply-To: <32316553.1193850104902.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32852680.1193851064866.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBRULES-1311?page=all ]

Edson Tirelli closed JBRULES-1311.
----------------------------------

    Fix Version/s: 4.0.4
       Resolution: Done

Fixed.

> NPE when compiling rule consequences
> ------------------------------------
>
>                 Key: JBRULES-1311
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1311
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rule Assemply/SPI, Drl Parser/Builder
>    Affects Versions:  4.0.0.GA, 4.0.1, 4.0.2, 4.0.3
>            Reporter: Edson Tirelli
>         Assigned To: Edson Tirelli
>             Fix For: 4.0.4, 4.1.0
>
>
> I have the following code: (note String[] ruleFiles contains only one string)
>  
> public class Engine {
>     private static RuleBase ruleBase;
>  
>     public void start(String[] ruleFiles) throws Exception {
>         PackageBuilderConfiguration cfg = new PackageBuilderConfiguration();
>         JavaDialectConfiguration javaConf = (JavaDialectConfiguration) cfg.getDialectConfiguration("java");
>         javaConf.setCompiler(JavaDialectConfiguration.ECLIPSE);
>         PackageBuilder builder = new PackageBuilder(cfg);
>         for (String file : ruleFiles) {
>             builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file)));
>         }
>         Package pkg = builder.getPackage();
>  
>         PackageBuilderErrors errors = builder.getErrors();
>         if (errors.getErrors().length != 0) {
>             // do something
>         }
>  
>         RuleBaseConfiguration conf = new RuleBaseConfiguration();
>         conf.setAssertBehaviour(RuleBaseConfiguration.AssertBehaviour.EQUALITY);
>  
>         ruleBase = RuleBaseFactory.newRuleBase();
>         ruleBase.addPackage(pkg);
>         ruleBase.newStatefulSession(false);
>  
>     }
> }
>  
> At the builder.addPackageFromDrl(new InputStreamReader(ClassLoader.getSystemResourceAsStream(file))); line I'm getting the following exception:
> java.lang.NullPointerException
>             at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:54)
>             at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:67)
>             at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:446)
>             at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:304)
>             at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:167)
>             at myPackage.rivoli.service.rules.Engine.start(Engine.java:33)
>             at myPackage.rivoli.rules.LeaderKingAndHeirTest.setUp(LeaderKingAndHeirTest.java:26)
>             at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40)
>             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>             at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
>  
> I am using Drools 4.0.3
> I have the following jars in my class path:
> antlr-runtime-3.0.jar
> core-3.2.3.v_686_R32x.jar
> drools-compiler-4.0.3.jar
> drools-core-4.0.3.jar
> mvel14-1.2.10.jar
>  
> Any ideas would be helpful. Thanks.
>  
> rule "leaders in same location"
> salience 10
> when
>     $result : RuleResult(rulesPassed not contains "leaders in same location")
>     $loc : LocationImpl()
>     $leaderName : String()
>     $leader1 : LeaderImpl(name == $leaderName, location == $loc)
>     $leader2 : LeaderImpl(name != $leaderName, this != $leader1, location == $loc)
> then
>     $result.addPassedRule(leaders in same location);
>     update($result);
> end

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:49:44 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:49:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-3885) JMXConnectorServer
 not respecting the -b value
In-Reply-To: <12415211.1164646422070.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16126743.1193852984635.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-3885?page=all ]

Dimitris Andreadis closed JBAS-3885.
------------------------------------

    Resolution: Done

Fixed. I can now create 2 servers (e.g. copy the default configuration) and start them up on different ports (-b xx.xx.xx.xx) without them conflicting with each other.

The JMXServiceURL is also printed upon startup. You can point directly a jconsole to it, e.g.:

19:38:03,281 INFO  [JMXConnectorServerService] JMX Connector server:
service:jmx:rmi://192.168.0.22/jndi/rmi://192.168.0.22:1090/jmxconnector

The underlying problem was the the rmi registry was binding all local addresses by default. It required a custom ServerSocketFactory to overcome the limitation.

> JMXConnectorServer not respecting the -b value
> ----------------------------------------------
>
>                 Key: JBAS-3885
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3885
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>    Affects Versions: JBossAS-5.0.0.Beta1
>            Reporter: Javid Jamae
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:
> ./run.sh -b 192.168.1.140 -c node1
> ./run.sh -b 192.168.1.141 -c node2
> I can bring up the first node, but when I try to bring up the second node, I get the following exception. I've started the nodes in different orders, and it is always the second node that throws this exception.
> 19:12:28,656 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
> 19:12:28,828 INFO  [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console] has already been started
> 19:12:29,109 ERROR [AbstractKernelController] Error installing to Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL [rmi://192.168.1.140:1090/jmxconnector]: javax.naming.NameAlreadyBoundException:
>  jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>         at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>         at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>         at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>         at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
>         at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
>         at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
>         at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
>         at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
>         at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
>         at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
>         at org.jboss.system.ServiceController.start(ServiceController.java:431)
>         at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
>         at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
>         at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53)
>         at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
>         at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
>         at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
>         at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
>         at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>         at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
>         at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
>         at org.jboss.Main.boot(Main.java:210)
>         at org.jboss.Main$1.run(Main.java:508)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxconnector]
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
>         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
>         at javax.naming.InitialContext.bind(InitialContext.java:359)
>         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
>         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
>         ... 42 more
> Caused by: java.rmi.AlreadyBoundException: jmxconnector
>         at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
>         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>         at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
>         at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>         at sun.rmi.transport.Transport$1.run(Transport.java:153)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>         at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>         at java.lang.Thread.run(Thread.java:595)
>         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
>         at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
>         ... 46 more
> 19:12:29,187 INFO  [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/	

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:53:44 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4486) Binding the
 JMXConnector on a multihomed machine
In-Reply-To: <3535628.1181902331660.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23913666.1193853224835.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4486?page=comments#action_12385377 ] 
            
Dimitris Andreadis commented on JBAS-4486:
------------------------------------------

The rmi registry was actually causing the problem. It's fixed at JBAS-3885.

> Binding the JMXConnector on a multihomed machine
> ------------------------------------------------
>
>                 Key: JBAS-4486
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4486
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>            Reporter: Thomas Diesler
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I am having trouble with a multihome setup.
> Event though I am using dedicated bind addresses the JXMConnector fails
> to start on the second instance. It looks to like as if the bind address
> is just disregarded and instead binds to 0.0.0.0:
> (1) Instance A  (-b 192.168.0.101) started successfully
> (2) Instance B (-b 192.168.0.102) logs:
> 17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL
> [rmi://192.168.0.102:1090/jmxconnector]:
> javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
> java.rmi.AlreadyBoundException: jmxconnector]
>         at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at
> org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
> (3) [tdiesler at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
>                 
>         tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     
> The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:55:44 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBAS-4485) JMXConnector always
 binds to the loopback device, regardless of the actual bind address
In-Reply-To: <33166904.1181814258577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15681299.1193853344843.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4485?page=all ]

Dimitris Andreadis updated JBAS-4485:
-------------------------------------

    Component/s: JMX
       Assignee: Dimitris Andreadis

> JMXConnector always binds to the loopback device, regardless of the actual bind address
> ---------------------------------------------------------------------------------------
>
>                 Key: JBAS-4485
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4485
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: URL: https://svn.jboss.org/repos/jbossas/trunk
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 63502
> java version "1.5.0_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
> Linux jbws 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686 i686 i386 GNU/Linux
>            Reporter: Heiko Braun
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I am having trouble with a multihome setup.
> Event though I am using dedicated bind addresses the JXMConnector fails
> to start on the second instance. It looks to like as if the bind address
> is just disregarded and instead binds to to the loopback device
> (1) Instance A  (-b 192.168.0.101) started successfully
> (2) Instance B (-b 192.168.0.102) logs:
> 17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL
> [rmi://192.168.0.102:1090/jmxconnector]:
> javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
> java.rmi.AlreadyBoundException: jmxconnector]
>         at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at
> org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
> (3) [hbraun at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
>                 
>         tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     
> The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.
> As far as i can tell, it pulls the jdk 1.5 JMX implementation.  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:55:45 2007
From: jira-events at lists.jboss.org (Dimitris Andreadis (JIRA))
Date: Wed, 31 Oct 2007 13:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAS-4485) JMXConnector always
 binds to the loopback device, regardless of the actual bind address
In-Reply-To: <33166904.1181814258577.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <24840333.1193853345044.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4485?page=all ]

Dimitris Andreadis closed JBAS-4485.
------------------------------------

    Fix Version/s:  JBossAS-5.0.0.Beta3
       Resolution: Done

Should be fixed.

> JMXConnector always binds to the loopback device, regardless of the actual bind address
> ---------------------------------------------------------------------------------------
>
>                 Key: JBAS-4485
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4485
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: JBossAS-5.0.0.Beta2
>         Environment: URL: https://svn.jboss.org/repos/jbossas/trunk
> Repository Root: https://svn.jboss.org/repos/jbossas
> Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
> Revision: 63502
> java version "1.5.0_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
> Linux jbws 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686 i686 i386 GNU/Linux
>            Reporter: Heiko Braun
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> I am having trouble with a multihome setup.
> Event though I am using dedicated bind addresses the JXMConnector fails
> to start on the second instance. It looks to like as if the bind address
> is just disregarded and instead binds to to the loopback device
> (1) Instance A  (-b 192.168.0.101) started successfully
> (2) Instance B (-b 192.168.0.102) logs:
> 17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> java.io.IOException: Cannot bind to URL
> [rmi://192.168.0.102:1090/jmxconnector]:
> javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
> java.rmi.AlreadyBoundException: jmxconnector]
>         at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
>         at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
>         at
> org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)
> (3) [hbraun at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
>                 
>         tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     
> The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.
> As far as i can tell, it pulls the jdk 1.5 JMX implementation.  

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 13:59:44 2007
From: jira-events at lists.jboss.org (Mike Clark (JIRA))
Date: Wed, 31 Oct 2007 13:59:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1128) Message not
 routed from one node to node with only consumer.
In-Reply-To: <15994322.1193778405017.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12138935.1193853584726.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1128?page=all ]

Mike Clark closed JBMESSAGING-1128.
-----------------------------------

    Resolution: Done

No bug here:  jgroups configuration was the root cause of the behavior I was seeing.

> Message not routed from one node to node with only consumer.
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1128
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1128
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Clustering
>    Affects Versions: 1.4.0.GA
>         Environment: Sun JDK 1.5.0_12, JBoss EAP 4.2.0, JBoss Messaging 1.4.GA installed against the "all" configuration running on RHEL5 (CSB), MySQL 5 used as backing database.
>            Reporter: Mike Clark
>         Assigned To: Tim Fox
>             Fix For: EAP 4.3 Integration
>
>
> In trying to reproduce behavior described in case 18885, I can reproduce the following:
> Start two instances of JBoss (ports-01 and ports-02 using the usual binding manager approach).  Deployed a simple MDB to ports-02; simply logs messages with INFO priority.  Deployed a simple MBean to both ports-01 and ports-02 that allows me to send TextMessage messages to the respective boxes from the JMX console.
> Messages sent to ports-02 are consumed by the MDB as expected.  Messages sent to ports-01 are not consumed unless ports-02 is shutdown (normal shutdown) and restarted.  The MDB on ports-02 will consume the messages queued to ports-01 regardless of whether ports-01 is up or not (ports-01 shutdown cleanly).  Messages sent to ports-01 are, of course, seen in the database as soon as they are submitted (I'm using PERSISTENT delivery mode.)
> Both instances were created from a clean "all" instance.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 14:13:44 2007
From: jira-events at lists.jboss.org (Carlo de Wolf (JIRA))
Date: Wed, 31 Oct 2007 14:13:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1095)
 ConsumerContainer throws NoInitialContextException on stop
In-Reply-To: <3234104.1193846504671.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <6626244.1193854424607.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/EJBTHREE-1095?page=all ]

Carlo de Wolf resolved EJBTHREE-1095.
-------------------------------------

    Fix Version/s: AS 5.0.0.Beta3
       Resolution: Done

> ConsumerContainer throws NoInitialContextException on stop
> ----------------------------------------------------------
>
>                 Key: EJBTHREE-1095
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1095
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Carlo de Wolf
>         Assigned To: Carlo de Wolf
>            Priority: Critical
>             Fix For: AS 5.0.0.Beta3, AS 4.2.3.GA
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> 2007-10-31 16:22:11,905 WARN  [org.jboss.ejb3.ServiceDelegateWrapper] Stopping failed jboss.j2ee:jar=consumer-test.jar,name=QueueTestConsumer,service=EJB3
> javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> 	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
> 	at javax.naming.InitialContext.getNameParser(InitialContext.java:439)
> 	at org.jboss.util.naming.Util.unbind(Util.java:135)
> 	at org.jboss.ejb3.mdb.ProducerFactory.stop(ProducerFactory.java:150)
> 	at org.jboss.ejb3.mdb.RemoteProducerFactory.stop(RemoteProducerFactory.java:99)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.unregisterProducers(ConsumerContainer.java:286)
> 	at org.jboss.ejb3.mdb.ConsumerContainer.stop(ConsumerContainer.java:304)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy69.stop(Unknown Source)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
> 	at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
> 	at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
> 	at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
> 	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
> 	at $Proxy0.stop(Unknown Source)
> 	at org.jboss.system.ServiceController.stop(ServiceController.java:508)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy33.stop(Unknown Source)
> 	at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
> 	at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
> 	at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
> 	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
> 	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> 	at $Proxy34.stop(Unknown Source)
> 	at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
> 	at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
> 	at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
> 	at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
> 	at sun.rmi.transport.Transport$1.run(Transport.java:153)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> 	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
> 	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
> 	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

        


From jira-events at lists.jboss.org  Wed Oct 31 14:29:44 2007
From: jira-events at lists.jboss.org (Jon Whitmore (JIRA))
Date: Wed, 31 Oct 2007 14:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBPORTAL-1776)
 User.updatePassword() fails silently
Message-ID: <28848557.1193855384823.JavaMail.jira@cloud.prod.atl2.jboss.com>

User.updatePassword() fails silently
------------------------------------

                 Key: JBPORTAL-1776
                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1776
             Project: JBoss Portal
          Issue Type: Feature Request
      Security Level: Public (Everyone can see)
          Components: Portal Identity, Portal Security
    Affects Versions: 2.6.2 Final
         Environment: XP, portal 2.6.2, AS 4.2.2.GA, authenticating against LDAP with org.jboss.security.auth.spi.LdapExtLoginModule
            Reporter: Jon Whitmore


The method updatePassword() on org.jboss.portal.identity.User offers the user no information as to the success or failure of the operation.  The method can fail if the password offered is not strong enough for the authenticating authority behind the LoginModule.  

I'm requesting that the method at least return a boolean to indicate success or failure.  A more descriptive return code would be even better.

My work around to is call verifyPassword() after calling updatePassword() to see if in fact the password has been changed.  This trick works for me only because I am not caching passwords - installations caching passwords for only a couple seconds will not be able to use my work around.


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 14:34:44 2007
From: jira-events at lists.jboss.org (Anil Saldhana (JIRA))
Date: Wed, 31 Oct 2007 14:34:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2076859.1193855684739.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4923?page=comments#action_12385385 ] 
            
Anil Saldhana commented on JBAS-4923:
-------------------------------------

The issue is that the unauthenticatedPrincipal from the ApplicationMetaData is null.

====================================
org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal

// Check for an unauthenticated principal value
               else
               {
                  ApplicationMetaData appMetaData = con.getBeanMetaData().getApplicationMetaData();
                  String name = appMetaData.getUnauthenticatedPrincipal();
                  if (name != null)
                     caller = new SimplePrincipal(name);
               }
===================================

> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:18:45 2007
From: jira-events at lists.jboss.org (Jason Long (JIRA))
Date: Wed, 31 Oct 2007 15:18:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1096) Make SLSB and
 SFSB hot deployable for RAD
In-Reply-To: <11025823.1193846504983.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23716652.1193858325251.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/EJBTHREE-1096?page=comments#action_12385396 ] 
            
Jason Long commented on EJBTHREE-1096:
--------------------------------------

What changes to JBoss AS or the EJB3 spec are required  to achieve this?

Please also comment on the difficulty and likely time frame for these changes.

> Make SLSB and SFSB hot deployable for RAD
> -----------------------------------------
>
>                 Key: EJBTHREE-1096
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1096
>             Project: EJB 3.0
>          Issue Type: Feature Request
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Jason Long
>
> Seam POJO components are hot deployable for RAD.  It would be great if SFSB and SLSB could be used in the same manner.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:42:44 2007
From: jira-events at lists.jboss.org (William DeCoste (JIRA))
Date: Wed, 31 Oct 2007 15:42:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1098) create base ejb3
 and session domains in ejb3-interceptors-aop.xml
Message-ID: <16662887.1193859764851.JavaMail.jira@cloud.prod.atl2.jboss.com>

create base ejb3 and session domains in ejb3-interceptors-aop.xml
-----------------------------------------------------------------

                 Key: EJBTHREE-1098
                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1098
             Project: EJB 3.0
          Issue Type: Feature Request
    Affects Versions: AS 4.2.2.GA
            Reporter: William DeCoste
         Assigned To: William DeCoste
            Priority: Minor


Extent applicable domains from base domains so easier to add defaults to all domains

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:46:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 15:46:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBAS-4934) JBossCacheWrapper
 should not re-use data gravitation option
Message-ID: <6732877.1193860004854.JavaMail.jira@cloud.prod.atl2.jboss.com>

JBossCacheWrapper should not re-use data gravitation option
-----------------------------------------------------------

                 Key: JBAS-4934
                 URL: http://jira.jboss.com/jira/browse/JBAS-4934
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Clustering, Web (Tomcat) service
    Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.0.5.GA
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-4.2.3.GA


JBossCacheWrapper has a minor optimization where it creates an instance of Option, sets it to forceDataGravitation=true and then tries to re-use it across all invocations where we need to gravitate.  This is invalid usage; JBC does not promise an Option will be in its original state when an invocation returns.

Just need to create an Option for each call; no big deal.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 15:50:45 2007
From: jira-events at lists.jboss.org (Stefan Guilhen (JIRA))
Date: Wed, 31 Oct 2007 15:50:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBAS-4424)
 WebAuthentication:Generate a SSOID
In-Reply-To: <20618100.1179337252975.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10892089.1193860245148.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBAS-4424?page=comments#action_12385404 ] 
            
Stefan Guilhen commented on JBAS-4424:
--------------------------------------

The SSO cookie is now generated by the WebAuthentication class as part of the login process when a SSO valve has been set in the jboss-web.deployer/server.xml. On Branch_4_2, the org.jboss.web.tomcat.security.ExtendedSingleSignOn valve has to be used instead of the standard SingleSignOn valve, because the ExtendedSSO valve exposes some of the SSO methods as public, allowing the WebAuthentication to delegate sso behaviour to the proper valve. As no upgrade of the jbossweb is planned for Branch_4_2, we had to come up with this workaround. The SSO behaviour of the WebAuthentication has been tested on Branch_4_2, and the code has already been commited.

This new valve is not necessary on Trunk, as Remy is setting the necessary methods to public on SingleSignOn valve. Version 2.1.0.CR7 of jbossweb already sets some of the methods to public but one of them (update) still needs to be changed. As soon as we have the changes we need, I'll test this implementation on Trunk using the standard SSO valve, commit, and resolve the issue.

> WebAuthentication:Generate a SSOID
> ----------------------------------
>
>                 Key: JBAS-4424
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4424
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Security
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Anil Saldhana
>         Assigned To: Stefan Guilhen
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication
> The feature needs to implement the sso stuff if it is desired by the user.  At the least, ssoid needs to be generated and set on the session.
> The ssoid generation logic exists in AuthenticatorBase.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 16:20:45 2007
From: jira-events at lists.jboss.org (Kabir Khan (JIRA))
Date: Wed, 31 Oct 2007 16:20:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBAOP-366) Ability to attach a
 .aop deployment to a particular scoped classloader
In-Reply-To: <7683783.1172254777318.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <2741448.1193862045388.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAOP-366?page=all ]

Kabir Khan closed JBAOP-366.
----------------------------

    Resolution: Done

> Ability to attach a .aop deployment to a particular scoped classloader
> ----------------------------------------------------------------------
>
>                 Key: JBAOP-366
>                 URL: http://jira.jboss.com/jira/browse/JBAOP-366
>             Project: JBoss AOP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.alpha3
>            Reporter: Kabir Khan
>         Assigned To: Kabir Khan
>             Fix For: 2.0.0.CR1
>
>
> e.g. if an .ear file has been scoped with:
> <jboss-app>
>   <loader-repository>
>       dot.com:loader=ear1test
>   </loader-repository>
> </jboss-app>
> It should be possible to deploy at a later time a .aop file like:
> <aop>
>    <attach-scoped-loader>dot.com:loader=ear1test</attach-scoped-loader>
>     <!-- aspects, bindings etc. -->
> </aop>
> The classloader for the scoped repository "dot.com:loader=ear1test" should be used to deploy the contents of the .aop file in the same way as if the .aop file had been deployed as part of the .ear.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 16:35:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 16:35:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBCACHE-1192) Cannot gravitate
 data only stored in cache loader
In-Reply-To: <30559437.1191346143578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <13498577.1193862944959.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1192?page=all ]

Brian Stansberry reopened JBCACHE-1192:
---------------------------------------

             
Reopening because fix has introduced regressions in AS test suite; will create subtask for that issue.

> Cannot gravitate data only stored in cache loader
> -------------------------------------------------
>
>                 Key: JBCACHE-1192
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1192
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Eviction, Replication
>    Affects Versions: 1.4.1.SP4, 1.4.1.SP3, 1.4.1.SP2, 1.4.1.SP1, 2.0.0.GA, 1.4.1.GA, 1.4.0.SP1, 1.4.0.GA
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Critical
>             Fix For: 1.4.1.SP6, 2.1.0.GA, 2.1.0.CR1
>
>
> If data has been evicted and is only available via a cacheloader, data gravitation fails to find it.  The CacheImpl.gravitateData method only searches the in-memory state.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 16:48:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 16:48:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBCACHE-1209) Restore existing
 Option to InvocationContext in TreeCache._gravitateData
Message-ID: <10112660.1193863724684.JavaMail.jira@cloud.prod.atl2.jboss.com>

Restore existing Option to InvocationContext in TreeCache._gravitateData
------------------------------------------------------------------------

                 Key: JBCACHE-1209
                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1209
             Project: JBoss Cache
          Issue Type: Sub-task
      Security Level: Public (Everyone can see)
    Affects Versions: 1.4.1.SP6
            Reporter: Brian Stansberry
         Assigned To: Manik Surtani
             Fix For: 1.4.1.SP6


The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:

1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to *that* instance of Option.

2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread.  Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread.  But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.

I'll attach a possible patch in a minute.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:05:49 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:05:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
Message-ID: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>

Add configuration for Remoting servlet transport
------------------------------------------------

                 Key: JBMESSAGING-1131
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Ron Sigal
         Assigned To: Tim Fox
             Fix For: 2.0.0 Alpha


In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:05:49 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:05:49 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7979492.1193864749502.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]

Ron Sigal updated JBMESSAGING-1131:
-----------------------------------

    Description: In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works.   (was: In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. )

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:12:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:12:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <88778.1193865164657.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]

Ron Sigal updated JBMESSAGING-1131:
-----------------------------------

    Attachment: messaging-servlet-service.xml
                ServletExample.java
                build.xml

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>         Attachments: build.xml, messaging-servlet-service.xml, ServletExample.java
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:14:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:14:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <23065025.1193865284853.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=all ]

Ron Sigal updated JBMESSAGING-1131:
-----------------------------------

    Attachment: remoting-servlet-service.xml
                web.xml

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>         Attachments: build.xml, messaging-servlet-service.xml, remoting-servlet-service.xml, ServletExample.java, web.xml
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:18:46 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:18:46 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1131) Add
 configuration for Remoting servlet transport
In-Reply-To: <11651844.1193864749155.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <21245804.1193865526087.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-1131?page=comments#action_12385414 ] 
            
Ron Sigal commented on JBMESSAGING-1131:
----------------------------------------

I've attached the various files relevant to this example.

1. build.xml, messaging-servlet-service.xml and ServletExample.java go in <root>/docs/examples/servlet 

2. remoting-servlet-service.xml goes in <root>/src/etc/remoting

3. web.xml goes in <root>/src/etc/remoting/remoting-servlet-invoker.war/WEB-INF

> Add configuration for Remoting servlet transport
> ------------------------------------------------
>
>                 Key: JBMESSAGING-1131
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Ron Sigal
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Alpha
>
>         Attachments: build.xml, messaging-servlet-service.xml, remoting-servlet-service.xml, ServletExample.java, web.xml
>
>
> In addition to the "http" transport, Remoting also has the http-based "servlet" transport.  The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side.  In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads.  But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker.  The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850  and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218 ), is that only one ServerSocket is used.  In principle, it's the appropriate transport to use when the server is running inside JBossAS.  In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet.  However, there have been a couple of problems.  For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker").  For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker").  However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. 

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 17:33:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 17:33:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1132) Use blocking
 mode for callbacks with Remoting http transport
Message-ID: <33520361.1193866424644.JavaMail.jira@cloud.prod.atl2.jboss.com>

Use blocking mode for callbacks with Remoting http transport
------------------------------------------------------------

                 Key: JBMESSAGING-1132
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1132
             Project: JBoss Messaging
          Issue Type: Task
            Reporter: Ron Sigal
         Assigned To: Tim Fox
             Fix For: 2.0.0 Alpha


In response to JBREM-641 "re-implement the callback polling for http transport to reduce latency", an alternative way of handling callbacks was introduced in Remoting.  In particular, instead of the client periodically polling for callbacks, in "blocking" mode, the request to download callbacks blocks on the server until either (1) a callback is available, or (2) the timeout period has expired.  The advantage is reduced latency in retrieving callbacks.  In fact, some JBM http transport stress tests which fail in "nonblocking" mode now pass in "blocking" mode.

1. The default mode is "nonblocking", so it is necessary to explicitly configure "blocking" mode.  One way to do so is to add the appropriate parameter to the metadata map when installing the callback listener.  E.g., add the following line to org.jboss.jms.client.remoting.JMSRemotingConnection.createCallbackMetadata():

         if (reportPollingStatistics != null)
         {
            metadata.put(CallbackPoller.REPORT_STATISTICS, reportPollingStatistics);
         }

         metadata.put(ServerInvoker.BLOCKING_MODE, ServerInvoker.BLOCKING);  //  <<=== add this line
         metadata.put(ServerInvoker.BLOCKING_TIMEOUT, "7777");                              // optional: default is 5000 milliseconds

2. The line

   <attribute name="callbackPollPeriod" isParam="true">102</attribute>

may be removed from remoting-http-service.xml, since it's no longer relevant.


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:40:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:40:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-827) Define a management
 interface for JBoss Remoting
Message-ID: <21180814.1193866844566.JavaMail.jira@cloud.prod.atl2.jboss.com>

Define a management interface for JBoss Remoting
------------------------------------------------

                 Key: JBREM-827
                 URL: http://jira.jboss.com/jira/browse/JBREM-827
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M2




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:43:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:43:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-824) Allow server to shut
 down connections from specified clients
In-Reply-To: <17720506.1193108054695.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8722207.1193867024700.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-824?page=all ]

David Lloyd closed JBREM-824.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Done
         Assignee:     (was: Trustin Lee)

Won't fix in the 2.x series.  Remoting 3 has a management interface defined in the roadmap; see JBREM-827.

> Allow server to shut down connections from specified clients
> ------------------------------------------------------------
>
>                 Key: JBREM-824
>                 URL: http://jira.jboss.com/jira/browse/JBREM-824
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP2, 2.2.2.GA_CP01, 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>
> From Jay Howell:  
> Several customers have asked for a management method to drop client connections from the server by ip address and by client id.
> So there would be two cases.
>    By ipaddress - this would stop the pinger and also close all connections associated with that client ip address. Only one pinger exists for an ip address, so this would require closing of the pinger connection also.
>    By clientid - this would close the pinger thread only if there are no other connections present.
> In each of the cases, clients should get an asynchronous onException call. 
> This facility would be necessary to support JBMESSAGING-1117.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:45:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:45:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-819) Consider removing
 dependency on jboss-commons
In-Reply-To: <26278208.1192488064482.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <8579564.1193867144761.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-819?page=all ]

David Lloyd closed JBREM-819.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Won't Fix

Won't fix in the 2.x series.  Remoting 3 does not depend on JBoss commons though.

> Consider removing dependency on jboss-commons
> ---------------------------------------------
>
>                 Key: JBREM-819
>                 URL: http://jira.jboss.com/jira/browse/JBREM-819
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.GA
>            Reporter: Ron Sigal
>         Assigned To: Trustin Lee
>
> From Greg Hinkle of the JBoss Operations Network group:  
> "... not only are the including tons of crap in the garbage pale called commons, but they dictate tons of library dependencies and serialization versions. For a group like ours that has to be able to simultaneously connect to every version of jboss released in the last 3 years it is not a good situation. We end up having to create a separate class loader per connection.
> "Now with remoting, we're actually using it as a core infrastructure piece. That means its in parent classloaders to these connection classloaders. As long as commons is in that required list we can't use remoting this way. We're going to have to do some serious classloader restructuring to be able to support our needs."

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:45:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:45:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-812) Specify an API to
 discover services
In-Reply-To: <11944998.1191360663233.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <14788143.1193867144890.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-812?page=all ]

David Lloyd updated JBREM-812:
------------------------------

    Fix Version/s: Remoting 3 M1
                       (was: 3.0.0.Alpha1 (Otter))

> Specify an API to discover services
> -----------------------------------
>
>                 Key: JBREM-812
>                 URL: http://jira.jboss.com/jira/browse/JBREM-812
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: r3 api
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>            Priority: Minor
>             Fix For: Remoting 3 M1
>
>
> The Remoting 3 API presently has a mechanism to discover endpoints and supply information about how to connect to discovered endpoints.
> A mechanism is also needed to allow a user to find any endpoint that provides a specific service.  This mechanism would preferably work in tandem with the existing discovery API.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:49:48 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:49:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-759) Client
 username/password
 authentication mechanism to provide JAAS UserPrincipal
In-Reply-To: <22936251.1182273876546.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <32215262.1193867388802.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-759?page=all ]

David Lloyd closed JBREM-759.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Out of Date

Remoting 3 already specifies an authentication API that should meet this need.

> Client username/password authentication mechanism to provide JAAS UserPrincipal
> -------------------------------------------------------------------------------
>
>                 Key: JBREM-759
>                 URL: http://jira.jboss.com/jira/browse/JBREM-759
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: security
>            Reporter: Clark Updike
>
> Per the forum thread, Remoting needs a username/password-style authentication mechanism similar to JNDI for situations that require secure authentication but cannot support the infrastructure required for client certificates.  The mechanism should populate a JAAS UserPrinciple that can be used to access the authenticated client identity on the remote side.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:53:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-718) Support for more
 message-based protocols
In-Reply-To: <13567351.1173182602514.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <16671778.1193867624694.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-718?page=all ]

David Lloyd closed JBREM-718.
-----------------------------

    Fix Version/s:     (was: 3.0.0.Alpha1 (Otter))
       Resolution: Deferred

Remoting 3 has the ability to plug in transports.  That said, the default transports provided will probably be limited to the default (JRPP), HTTP, and a couple of loopback transports.

> Support for more message-based protocols
> ----------------------------------------
>
>                 Key: JBREM-718
>                 URL: http://jira.jboss.com/jira/browse/JBREM-718
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Mark Little
>
> It would be good if Remoting supported more message-oriented protocols, such as JMS, FTP, email etc. RPC semantics could be layered on those, or simply say that the one-way approach is all that is supported. One slight worry might be if a supported plugin implementation for JBoss Remoting itself used JBoss Remoting (e.g., plugging JBoss Messaging into JBoss Remoting). This may set up some interesting circularities.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:55:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Reopened: (JBREM-103) Transport progress
 notification for client
Message-ID: <22337093.1193867745342.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd reopened JBREM-103:
-------------------------------

             
Reopening to update the fix version...

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:55:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-103) Transport progress
 notification for client
Message-ID: <23374398.1193867745511.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-103?page=all ]

David Lloyd closed JBREM-103.
-----------------------------

    Fix Version/s: Remoting 3 M1
       Resolution: Done

> Transport progress notification for client
> ------------------------------------------
>
>                 Key: JBREM-103
>                 URL: http://jira.jboss.com/jira/browse/JBREM-103
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: r3 api
>    Affects Versions: 1.0.2 final
>            Reporter: Philipp Meier
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>
> At the moment there is no way for the client or the server to be notified about the progress of the request / response transmission. Especially for rich clients it would be desireable to be able to register something like a ProgressListener to be notified about the transport progress (push model) or the request the current progress from the remoting implementation (pull model). The discussion in the remoting forum came to the conclusion that this would need some major enhancements of the marshaller.
> I set the priority to major because of the major usefulness for richt clients and large dataset.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 17:58:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 17:58:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-38) SSH transport
Message-ID: <4265622.1193867924715.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-38?page=all ]

David Lloyd closed JBREM-38.
----------------------------

    Resolution: Won't Fix
      Assignee:     (was: Tom  Elrod)

SSH transport is not currently on the roadmap, as the default transport already does encryption without key management.  However this can be reopened if there is a use case.

> SSH transport
> -------------
>
>                 Key: JBREM-38
>                 URL: http://jira.jboss.com/jira/browse/JBREM-38
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: transport
>    Affects Versions: 1.0.1 beta
>            Reporter: Tom  Elrod
>            Priority: Optional
>
> Check out http://www.jcraft.com/jsch/index.html and see if can be used for a SSH transport.  Also see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=58498 for more comments on this topic.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:00:50 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:00:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-433) point to multipoint
	invocation api
Message-ID: <286787.1193868050849.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-433?page=all ]

David Lloyd closed JBREM-433.
-----------------------------

    Resolution: Deferred

Closed until/unless a use case is identified.

> point to multipoint invocation api
> ----------------------------------
>
>                 Key: JBREM-433
>                 URL: http://jira.jboss.com/jira/browse/JBREM-433
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.2.2.GA
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>
> Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time.  The responses for each target server would be aggregated into one response as return to the client call.  Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for 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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:00:51 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:00:51 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-305) Provide support for
	JMS transport
Message-ID: <544030.1193868051293.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-305?page=all ]

David Lloyd closed JBREM-305.
-----------------------------

    Resolution: Deferred

JBoss Remoting may have a JMS transport at some point in the future.  However IF it does, the format of the message will be a black box, and no interoperability guarantees will be made.

> Provide support for JMS transport
> ---------------------------------
>
>                 Key: JBREM-305
>                 URL: http://jira.jboss.com/jira/browse/JBREM-305
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0 beta
>            Reporter: Thomas Diesler
>         Assigned To: David Lloyd
>
> The web service layer has a need for JMS transport

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:02:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:02:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-48) JGroups transport
Message-ID: <28092129.1193868164945.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-48?page=all ]

David Lloyd closed JBREM-48.
----------------------------

    Resolution: Deferred
      Assignee:     (was: Tom  Elrod)

Deferred until a use case is identified.

> JGroups transport
> -----------------
>
>                 Key: JBREM-48
>                 URL: http://jira.jboss.com/jira/browse/JBREM-48
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>          Components: transport
>    Affects Versions: 1.0.1 beta
>            Reporter: Tom  Elrod
>
> Would like to add JGroups as a transport. In particular, would like to be able to add concept of being able to invoker on multiple servers and consolidate the responses. One use case would be for making two phase commit calls on distributed cache, so can verify that all servers successfully prepare.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:02:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:02:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-237) There is No String
 and Guage monitors in jboss
Message-ID: <3925671.1193868165152.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-237?page=all ]

David Lloyd closed JBREM-237.
-----------------------------

    Resolution: Rejected

No updates, and no idea what this issue is about.

> There is No String and Guage monitors in jboss
> ----------------------------------------------
>
>                 Key: JBREM-237
>                 URL: http://jira.jboss.com/jira/browse/JBREM-237
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: jmx remoting
>            Reporter: sree roja
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:04:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:04:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-381) IIOP transport impl
	for remoting
Message-ID: <27428013.1193868284929.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-381?page=all ]

David Lloyd closed JBREM-381.
-----------------------------

    Resolution: Deferred
      Assignee: David Lloyd  (was: Ron Sigal)

At the moment there are no plans for an IIOP transport for Remoting 3.  Reopen if there are *specific* requirements.

> IIOP transport impl for remoting
> --------------------------------
>
>                 Key: JBREM-381
>                 URL: http://jira.jboss.com/jira/browse/JBREM-381
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1 final
>            Reporter: Tom  Elrod
>         Assigned To: David Lloyd
>            Priority: Minor
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:08:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:08:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-68) Add persistent store
 for oneway messages
Message-ID: <8550013.1193868524649.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-68?page=all ]

David Lloyd closed JBREM-68.
----------------------------

    Resolution: Rejected
      Assignee:     (was: Tom  Elrod)

Remoting 3 won't have this type of delivery guarantee, but a user could layer it on pretty easily.

> Add persistent store for oneway messages
> ----------------------------------------
>
>                 Key: JBREM-68
>                 URL: http://jira.jboss.com/jira/browse/JBREM-68
>             Project: JBoss Remoting
>          Issue Type: Task
>          Components: transport
>    Affects Versions: 1.0.1 final
>            Reporter: Tom  Elrod
>            Priority: Optional
>
> Need to add ability to persist invocation messages on server when using oneway on the server side.  This will ensure that if server crashes and one message has made it to server worker pool, it will be processed when the server is restarted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:12:54 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 18:12:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBCACHE-1209) Restore existing
 Option to InvocationContext in TreeCache._gravitateData
In-Reply-To: <10112660.1193863724684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <12731553.1193868774939.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBCACHE-1209?page=all ]

Brian Stansberry updated JBCACHE-1209:
--------------------------------------

    Attachment: TreeCache.patch

Possible patch.  With this in place, the 150 AS testsuite failures I was seeing went away.

Running the full JBC testsuite w/ this now (w/ 1.4.1.SP6 tag).

The above patch may be a bit of a sledgehammer; perhaps just the stuff in the finally block would take care of the problem. But I figured restoring the Option after each get(Fqn) call was just safer.

> Restore existing Option to InvocationContext in TreeCache._gravitateData
> ------------------------------------------------------------------------
>
>                 Key: JBCACHE-1209
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1209
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP6
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: TreeCache.patch
>
>
> The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:
> 1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to *that* instance of Option.
> 2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread.  Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread.  But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.
> I'll attach a possible patch in a minute.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:12:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:12:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-315) allow chaining of
 marshaller/unmarshallers
Message-ID: <26091351.1193868775104.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-315?page=all ]

David Lloyd closed JBREM-315.
-----------------------------

    Resolution: Done
      Assignee:     (was: Tom  Elrod)

The idea is sound - but implementation-wise, the interceptor stack should be negotiated between the two participants rather than relying on a static configuration.  This will be designed in to Remoting 3.

> allow chaining of marshaller/unmarshallers
> ------------------------------------------
>
>                 Key: JBREM-315
>                 URL: http://jira.jboss.com/jira/browse/JBREM-315
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 1.4.0 final
>            Reporter: Tom  Elrod
>
> I was thinking of paired marshaller/unmarshaller, which would be
> beneficial for more than just this example (compressing payload comes to
> mind).  Would like to be able to declare a chain of marshallers.  For
> example:
> <marshallers>
> <marshaller>org.jboss.remoting.marshall.CompressedMarshaller</marshaller>
> <marshaller>org.jboss.remoting.marshall.InvocationMarshaller</marshaller>
> <marshaller>org.jboss.remoting.marshall.CountingMarshaller</marshaller>
> </marshallers>
> <unmarshallers>
> <unmarshaller>org.jboss.remoting.marshall.InvocationUnMarshaller</unmarshaller>
> <unmarshaller<org.jboss.remoting.marshall.CompressedUnMarshaller</unmarshaller>
> of course packaging and order may not be correct in this example.  Just
> trying to show how would be nice to configure the chain that is used and
> that would not require to by symmetrical if didn't want to.
> In this example, the CompressedMarshaller would compress the payload,
> then write to the InvocationMarshaller, which would write to the
> CountingMarshaller, which would then keep track of number of bytes
> written and send notifications as was being written.  On the server
> side, might not need to know number of bytes being read, so would just
> have the InvocationUnMarshaller, then CompressedUnMarshaller to
> uncompress the payload.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:12:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:12:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-828) Interceptor
	negotiation mechanism
Message-ID: <26398467.1193868775254.JavaMail.jira@cloud.prod.atl2.jboss.com>

Interceptor negotiation mechanism
---------------------------------

                 Key: JBREM-828
                 URL: http://jira.jboss.com/jira/browse/JBREM-828
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
         Assigned To: David Lloyd
             Fix For: Remoting 3 M1


The participants need to negotiate what interceptors should exist on a per-service basis.  Work out further requirements, and implement.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:21:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:21:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-269) Create RMI/IIOP
 transport implementation
Message-ID: <16413833.1193869305497.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-269?page=all ]

David Lloyd closed JBREM-269.
-----------------------------

    Resolution: Rejected

No IIOP transport is planned for Remoting 3.  Probably we need a separate invoker layer that would cover this kind of thing.

If this is wrong, reopen and provide specific requirements.

> Create RMI/IIOP transport implementation
> ----------------------------------------
>
>                 Key: JBREM-269
>                 URL: http://jira.jboss.com/jira/browse/JBREM-269
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Scott M Stark
>
> We need an RMI/IIOP implementation for ejb3. This should be coming from the remoting implementation. We need to look into porting the existing detached iiop invoker code in the iiop module to a remoting implementation.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:21:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:21:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-324) Facility for
 real-time decision
 on best InvokerLocator by which to contact a given handler.
Message-ID: <13988511.1193869305700.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-324?page=comments#action_12385438 ] 
            
David Lloyd commented on JBREM-324:
-----------------------------------

As far as I'm concerned this can be closed, as it is an integral part of the R3 routing API.  Otherwise it should be assigned to a specific version.

> Facility for real-time decision on best InvokerLocator by which to contact a given handler.
> -------------------------------------------------------------------------------------------
>
>                 Key: JBREM-324
>                 URL: http://jira.jboss.com/jira/browse/JBREM-324
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>            Priority: Minor
>
> The basic idea is to be able to communicate with a single handler by way of different InvokerLocators.  For example, if you're working over the internet, compression might be advantageous, but if you're local it might not be.  So you could have two Connectors sharing a handler, one using the compression marshaller and one not.
> How about a client that
> 1. gets the InvokerLocators for all of the Connectors for a certain handler, via a detector,
> 2. sends some sample invocations to each and times them, and
> 3. displays the results.
> It could be used for real time decision making or to collect information for a set of rules.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:23:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:23:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-416) create
 jboss-remoting-client-pda.jar
Message-ID: <5852705.1193869435346.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-416?page=all ]

David Lloyd closed JBREM-416.
-----------------------------

    Resolution: Deferred
      Assignee:     (was: Tom  Elrod)

No plans currently to tackle a J2ME release.  Can be reopened if this is to be put on the roadmap.

> create jboss-remoting-client-pda.jar
> ------------------------------------
>
>                 Key: JBREM-416
>                 URL: http://jira.jboss.com/jira/browse/JBREM-416
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta1
>            Reporter: Tom  Elrod
>
> Need a remoting client distribution that can run within J2ME environment (PDA to be specific).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:23:55 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:23:55 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-417) create J2ME
 compatible socket client invoker
Message-ID: <33452540.1193869435470.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-417?page=all ]

David Lloyd closed JBREM-417.
-----------------------------

    Resolution: Deferred
      Assignee:     (was: Tom  Elrod)

No plans currently to tackle a J2ME release. Can be reopened if this is to be put on the roadmap.

> create J2ME compatible socket client invoker
> --------------------------------------------
>
>                 Key: JBREM-417
>                 URL: http://jira.jboss.com/jira/browse/JBREM-417
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta1
>            Reporter: Tom  Elrod
>
> There are a few API calls in current SocketClientInvoker that is not allowed in J2ME.  Need to create an extention of the SocketClientInvoker (maybe MicroSocketClientInvoker?) that will remove these calls so can be used within J2ME environment.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:27:51 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 18:27:51 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Closed: (JBREM-736)
 [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling
 exception, exiting  java.lang.ClassNotFoundException:
 [Ljava.lang.StackTraceElement;
In-Reply-To: <10442416.1176842850531.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <25677704.1193869671366.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-736?page=all ]

David Lloyd closed JBREM-736.
-----------------------------

    Resolution: Cannot Reproduce Bug

No response from user.

> [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting  java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement; 
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-736
>                 URL: http://jira.jboss.com/jira/browse/JBREM-736
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: marshall
>    Affects Versions: 1.4.3.GA
>         Environment: Jboss 4.0.4.GA/EJB3/JDK1.6
>            Reporter: Ravi Alagappan
>         Assigned To: David Lloyd
>
> I am throwing custom application exception from bean and trying to catch that in client. But I am getting 
> 2007-04-17 09:57:15,480 DEBUG [org.jboss.remoting.transport.socket.SocketClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker at 16a38b5
> 2007-04-17 09:57:15,558 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
> java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> 	at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
> 	at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> 	at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
> 	at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
> 	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
> 	at org.jboss.remoting.Client.invoke(Client.java:525)
> 	at org.jboss.remoting.Client.invoke(Client.java:488)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> 	at $Proxy0.save(Unknown Source)
> 	at linc.document.service.RepositoryClient.save(RepositoryClient.java:109)
> 	at linc.document.service.DocumentService.save(DocumentService.java:35)
> 	at linc.document.service.DocumentService.main(DocumentService.java:184)
> 2007-04-17 09:57:15,573 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Error loading classes from remote call result.
> java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement;
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
> 	at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50)
> 	at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139)
> 	at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> 	at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> 	at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
> 	at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
> 	at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> 	at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
> 	at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
> 	at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
> 	at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
> 	at org.jboss.remoting.Client.invoke(Client.java:525)
> 	at org.jboss.remoting.Client.invoke(Client.java:488)
> 	at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:78)
> 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
> 	at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
> 	at $Proxy0.save(Unknown Source)
> 	at linc.document.service.RepositoryClient.save(RepositoryClient.java:109)
> 	at linc.document.service.DocumentService.save(DocumentService.java:35)
> 	at linc.document.service.DocumentService.main(DocumentService.java:184)
> But no exception with jdk1.5. With JDK1.5 client able to catch custom exception.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 18:54:44 2007
From: jira-events at lists.jboss.org (Chris Laprun (JIRA))
Date: Wed, 31 Oct 2007 18:54:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1712) Make producer
 tests go through the WS stack
In-Reply-To: <22960492.1190516351026.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <27496979.1193871284830.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1712?page=all ]

Chris Laprun resolved JBPORTAL-1712.
------------------------------------

    Resolution: Rejected

Actually, the tests are going through the WS stack as it is and I managed to fix them (by not using the unmarshalled exceptions but directly RemoteException and checking the error code) though I am not quite sure how changing code on the client has an impact on the test result... I suspect it has to do with JBoss WS somewhat flaky support for SOAPFaultException... I guess I will need to investigate this more. Closing this task.

> Make producer tests go through the WS stack
> -------------------------------------------
>
>                 Key: JBPORTAL-1712
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1712
>             Project: JBoss Portal
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Portal WSRP
>    Affects Versions: 2.8 Final, 2.6.1 Final, 2.6.2 Final
>            Reporter: Chris Laprun
>         Assigned To: Chris Laprun
>             Fix For: 2.6.3 Final, 2.8 Final
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 19:14:44 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 19:14:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4923) No valid security
 context for the caller identity
In-Reply-To: <10731708.1193742121578.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <5657940.1193872484661.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4923?page=all ]

Scott M Stark resolved JBAS-4923.
---------------------------------

    Resolution: Done

The setting has been moved to the standardjboss.xml 

[starksm at valkyrie jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test one-test
...

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.DocEJBTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 28.953 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcDIIConfiguredC
allTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.062 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcDIIUnconfigure
dCallTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.61 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcEJBTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.188 sec
    [junit] Running org.jboss.test.ws.jaxrpc.samples.jsr109ejb.RpcProxyTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.234 sec


> No valid security context for the caller identity
> -------------------------------------------------
>
>                 Key: JBAS-4923
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4923
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Anil Saldhana
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxrpc/samples/jsr109ejb test
> Caused by: java.lang.IllegalStateException: No valid security context for the caller identity
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipalInternal(EnterpriseContext.java:398)
>         at org.jboss.ejb.EnterpriseContext$EJBContextImpl.getCallerPrincipal(EnterpriseContext.java:359)
>         at org.jboss.ejb.StatelessSessionEnterpriseContext$SessionContextImpl.getCallerPrincipal(StatelessSessionEnterpriseContext.java:228)
>         at org.jboss.test.ws.jaxrpc.samples.jsr109ejb.JaxRpcEJBEndpoint.echoString(JaxRpcEJBEndpoint.java:48)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 19:18:54 2007
From: jira-events at lists.jboss.org (Scott M Stark (JIRA))
Date: Wed, 31 Oct 2007 19:18:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBAS-4924) NPE caused by
 SessionContainer.createService
In-Reply-To: <17592694.1193743141413.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28034430.1193872734931.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBAS-4924?page=all ]

Scott M Stark resolved JBAS-4924.
---------------------------------

    Resolution: Done

The tests fail for other reasons than passing a null ejb-class to the class loader.

16:16:42,437 INFO  [TomcatDeployment] deploy, ctxPath=/jaxws-samples-webservicer
ef-servlet-client, vfsUrl=
16:16:43,875 INFO  [ServletClient] doGet: HelloWorld
16:16:45,343 INFO  [TestEndpointImpl] HelloWorld
16:16:45,343 INFO  [TestEndpointImpl] HelloWorld
16:16:45,359 INFO  [TestEndpointImpl] HelloWorld
16:16:45,375 INFO  [TestEndpointImpl] HelloWorld
16:16:45,375 INFO  [TestEndpointImpl] HelloWorld
16:16:45,390 INFO  [TestEndpointImpl] HelloWorld
16:16:45,406 INFO  [TestEndpointImpl] HelloWorld
16:16:45,421 INFO  [TestEndpointImpl] HelloWorld
16:16:45,437 INFO  [TestEndpointImpl] HelloWorld
16:16:45,437 INFO  [TestEndpointImpl] HelloWorld
16:16:45,453 INFO  [TestEndpointImpl] HelloWorld
16:16:45,468 INFO  [TestEndpointImpl] HelloWorld
16:16:45,500 INFO  [TestEndpointImpl] HelloWorld
16:16:45,500 INFO  [TestEndpointImpl] HelloWorld
16:16:45,515 INFO  [TestEndpointImpl] HelloWorld
16:16:45,609 INFO  [TomcatDeployment] undeploy, ctxPath=/jaxws-samples-webservic
eref-servlet-client, vfsUrl=
16:16:45,656 INFO  [TomcatDeployment] undeploy, ctxPath=/jaxws-samples-webservic
eref, vfsUrl=
16:16:45,687 INFO  [DefaultEndpointRegistry] remove: jboss.ws:context=jaxws-samp
les-webserviceref,endpoint=TestEndpoint

tests-run-internal:
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase
    [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 5.75 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefClientTestCase FAILED
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefEJB3TestCase
    [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 3.078 sec
    [junit] Test org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefEJB3TestCase FAILED
    [junit] Running org.jboss.test.ws.jaxws.samples.webserviceref.WebServiceRefServletTestCase
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6.094 sec


> NPE caused by SessionContainer.createService
> --------------------------------------------
>
>                 Key: JBAS-4924
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4924
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Thomas Diesler
>         Assigned To: Carlo de Wolf
>             Fix For:  JBossAS-5.0.0.Beta3
>
>
> [tdiesler at tddell jbossws-native-2.0.2]$ ant -Dtest=jaxws/samples/webserviceref test
> 12:14:00,604 INFO  [MainDeployer] deploy, url=file:/home/tdiesler/svn/jbossws/stack/native/branches/jbossws-native-2.0.2/output/tests/libs/jaxws-samples-webserviceref-ejb3-client.jar
> 12:14:01,515 WARN  [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors()
> 12:14:05,999 INFO  [EjbModule] Deploying EJB3Client
> 12:14:07,863 ERROR [AbstractKernelController] Error installing to Create: name=jboss.j2ee:jndiName=local/EJB3Client at 9657493,service=EJB state=Configured mode=Manual requiredState=Create
> java.lang.NullPointerException
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
>         at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
>         at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:224)
>         at org.jboss.mx.loading.RepositoryClassLoader.getCachedClass(RepositoryClassLoader.java:160)
>         at org.jboss.classloading.spi.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:74)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:92)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at org.jboss.ejb.Container.createService(Container.java:854)
>         at org.jboss.ejb.SessionContainer.createService(SessionContainer.java:160)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:51:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:51:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-829) SRP SASL Provider
Message-ID: <16521012.1193878304574.JavaMail.jira@cloud.prod.atl2.jboss.com>

SRP SASL Provider
-----------------

                 Key: JBREM-829
                 URL: http://jira.jboss.com/jira/browse/JBREM-829
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: r3 core
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:53:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-830) Remoting 3 API
Message-ID: <32416860.1193878424623.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting 3 API
--------------

                 Key: JBREM-830
                 URL: http://jira.jboss.com/jira/browse/JBREM-830
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:53:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:53:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-831) Remoting 3 Core
	Implementation
Message-ID: <588287.1193878424796.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting 3 Core Implementation
------------------------------

                 Key: JBREM-831
                 URL: http://jira.jboss.com/jira/browse/JBREM-831
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-832) JRPP Implementation
Message-ID: <18439719.1193878544710.JavaMail.jira@cloud.prod.atl2.jboss.com>

JRPP Implementation
-------------------

                 Key: JBREM-832
                 URL: http://jira.jboss.com/jira/browse/JBREM-832
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-830) Remoting 3 API
In-Reply-To: <32416860.1193878424623.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <18079046.1193878544851.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-830?page=all ]

David Lloyd reassigned JBREM-830:
---------------------------------

    Assignee: David Lloyd

> Remoting 3 API
> --------------
>
>                 Key: JBREM-830
>                 URL: http://jira.jboss.com/jira/browse/JBREM-830
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-829) SRP SASL Provider
In-Reply-To: <16521012.1193878304574.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <31764949.1193878544975.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-829?page=all ]

David Lloyd reassigned JBREM-829:
---------------------------------

    Assignee: David Lloyd

> SRP SASL Provider
> -----------------
>
>                 Key: JBREM-829
>                 URL: http://jira.jboss.com/jira/browse/JBREM-829
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: r3 core
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 20:55:45 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 20:55:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Assigned: (JBREM-831) Remoting 3 Core
	Implementation
In-Reply-To: <588287.1193878424796.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22377390.1193878545177.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-831?page=all ]

David Lloyd reassigned JBREM-831:
---------------------------------

    Assignee: David Lloyd

> Remoting 3 Core Implementation
> ------------------------------
>
>                 Key: JBREM-831
>                 URL: http://jira.jboss.com/jira/browse/JBREM-831
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:11:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 21:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-833) HTTP Transport
	Implementation
Message-ID: <16108849.1193879504581.JavaMail.jira@cloud.prod.atl2.jboss.com>

HTTP Transport Implementation
-----------------------------

                 Key: JBREM-833
                 URL: http://jira.jboss.com/jira/browse/JBREM-833
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M2




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:15:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 21:15:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-829) SRP SASL Provider
In-Reply-To: <16521012.1193878304574.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <28711532.1193879744579.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-829?page=comments#action_12385452 ] 
            
David Lloyd commented on JBREM-829:
-----------------------------------

Implementation is complete.  Need tests.

> SRP SASL Provider
> -----------------
>
>                 Key: JBREM-829
>                 URL: http://jira.jboss.com/jira/browse/JBREM-829
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: r3 core
>            Reporter: David Lloyd
>         Assigned To: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:19:54 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 21:19:54 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-166) JMXConnectorServer
 will not start if using rmi invoker elsewhere
Message-ID: <25833573.1193879994929.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-166?page=all ]

Ron Sigal updated JBREM-166:
----------------------------

    Fix Version/s: 2.4.0.Beta1 (Pinto)
         Assignee:     (was: Tom  Elrod)

Adding fix version 2.4.0.Beta1.  

This issue seems to be related to JBAS-3885: JMXConnectorServer not respecting the -b value, recently fixed by Dimitris, who changed the creation of the RMI registry in org.jboss.mx.remoting.service.JMXConnectorServerService.start() to use a ServerSocketFactory that binds to a single host.  Maybe the same needs to be done in org.jboss.remoting.transport.rmi.RMIServerInvoker.

> JMXConnectorServer will not start if using rmi invoker elsewhere
> ----------------------------------------------------------------
>
>                 Key: JBREM-166
>                 URL: http://jira.jboss.com/jira/browse/JBREM-166
>             Project: JBoss Remoting
>          Issue Type: Bug
>          Components: jmx remoting
>    Affects Versions: JMX Remoting 1.0.1
>            Reporter: Tom  Elrod
>             Fix For: JMX Remoting 1.0.2, 2.4.0.Beta1 (Pinto)
>
>
> If have a remoting invoker using rmi transport, it will create a rmi registry.  Then when the JMXConnectorServer starts, it will also try to create one.  Even though is on a different port, will get the following exception:
> java.rmi.server.ExportException: internal error: ObjID already in use
> 	at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
> 	at sun.rmi.transport.Transport.exportObject(Transport.java:69)
> 	at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190)
> 	at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
> 	at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
> 	at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
> 	at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
> 	at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
> 	at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
> 	at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91)

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:22:45 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 21:22:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBFORUMS-231) Simplify
	ResourceBundle
In-Reply-To: <11029871.1178674432213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <19911638.1193880165047.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBFORUMS-231?page=all ]

Ryszard Kozmik updated JBFORUMS-231:
------------------------------------

    Fix Version/s: 1.1.0 Alpha

> Simplify ResourceBundle
> -----------------------
>
>                 Key: JBFORUMS-231
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-231
>             Project: JBoss Forums
>          Issue Type: Task
>          Components: Forum View Layer, Portlet Productization
>            Reporter: Ryszard Kozmik
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC, 1.1.0 Alpha
>
>          Time Spent: 3 hours
>
> There are a lot of useless entries in ResourceBundle for JBoss Forums, those should be deleted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:39:44 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 21:39:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Resolved: (JBFORUMS-231) Simplify
	ResourceBundle
In-Reply-To: <11029871.1178674432213.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <15415639.1193881184735.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBFORUMS-231?page=all ]

Ryszard Kozmik resolved JBFORUMS-231.
-------------------------------------

    Resolution: Done

> Simplify ResourceBundle
> -----------------------
>
>                 Key: JBFORUMS-231
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-231
>             Project: JBoss Forums
>          Issue Type: Task
>          Components: Forum View Layer, Portlet Productization
>            Reporter: Ryszard Kozmik
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC, 1.1.0 Alpha
>
>          Time Spent: 3 hours
>
> There are a lot of useless entries in ResourceBundle for JBoss Forums, those should be deleted.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 21:51:50 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 21:51:50 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBFORUMS-247) forums and
 commons-fileupload-1.1
In-Reply-To: <1722719.1184003911960.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10107762.1193881910485.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBFORUMS-247?page=comments#action_12385457 ] 
            
Ryszard Kozmik commented on JBFORUMS-247:
-----------------------------------------

Luca the zip archive  patch_multiple_forums_src_1.1.0_30_sep_2007.zip (51 kb) is here only by mistake, right?

> forums and commons-fileupload-1.1
> ---------------------------------
>
>                 Key: JBFORUMS-247
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-247
>             Project: JBoss Forums
>          Issue Type: Bug
>          Components: Portlet Productization, Forum Model Layer
>         Environment: JBoss as from http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_CP06, 
> JBoss Portal from http://anonsvn.jboss.org/repos/portal/trunk since 9 july 2007,
> JBoss Forums from http://anonsvn.jboss.org/repos/labs/labs/jbossforums/branches/forums101P26 since 9 july 2007
>            Reporter: Luca Stancapiano
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC
>
>         Attachments: ForumsJSFPortlet.java, patch_multiple_forums_src_1.1.0_30_sep_2007.zip
>
>
> hi....I send you to see http://jira.jboss.com/jira/browse/JBPORTAL-1550 by me reported. It is the same problem......if you post messages using 'multipart/form-data' through commons-fileupload libs, you miss character encoding because there is a incompatibility between tomcat 5.5.23 and fileupload 1.1, and then if you try to send messages with characters as ?, ?, ?, ?, ? you 'll get problems of decoding with strange characters of response. Also for Forums I send you a patch. I substituted getString() method of org.apache.commons.fileupload.disk.DiskFileItem class with getString( String ...) method, passing inside the character encoding of the request:
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 560
>      I write :
>   
>                newParams.put(item.getFieldName(), new String[]{item.getString(req.getCharacterEncoding())});
>     instead of:
>              newParams.put(item.getFieldName(), new String[]{item.getString()});
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 564
>   
>       I write:
>             String value = item.getString(req.getCharacterEncoding());
>       instead of:
>             String value = item.getString();

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 22:07:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:07:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-834) Remoting 3
 Transaction API/Interceptor
Message-ID: <3086336.1193882864651.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting 3 Transaction API/Interceptor
--------------------------------------

                 Key: JBREM-834
                 URL: http://jira.jboss.com/jira/browse/JBREM-834
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M1




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:11:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-835) Interceptor API
Message-ID: <10909073.1193883104599.JavaMail.jira@cloud.prod.atl2.jboss.com>

Interceptor API
---------------

                 Key: JBREM-835
                 URL: http://jira.jboss.com/jira/browse/JBREM-835
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd




-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:11:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:11:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-835) Interceptor API
In-Reply-To: <10909073.1193883104599.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <17196.1193883104766.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-835?page=all ]

David Lloyd updated JBREM-835:
------------------------------

    Fix Version/s: Remoting 3 M1

> Interceptor API
> ---------------
>
>                 Key: JBREM-835
>                 URL: http://jira.jboss.com/jira/browse/JBREM-835
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>             Fix For: Remoting 3 M1
>
>


-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:16:44 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 22:16:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <4705690.1193883404714.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385458 ] 
            
Ron Sigal commented on JBREM-675:
---------------------------------

The default exception handling behavior is now to return the exception thrown by the invocation handler.  To turn off that behavior, so that an error message is returned, it is necessary to add the parameter org.jboss.remoting.transport.http.HTTPMetadataConstants.DONT_RETURN_EXCEPTION (actual value "dont-return-exception") with a value of "true" to the metadata map received by ServerServletInvoker.  For example, "dont-return-exception=true" could be added to the InvokerLocator.

This change is related to JBREM-813 "ServletServerInvoker should return an exception instead of just an error message".

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:23:45 2007
From: jira-events at lists.jboss.org (Ryszard Kozmik (JIRA))
Date: Wed, 31 Oct 2007 22:23:45 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBFORUMS-247) forums and
 commons-fileupload-1.1
In-Reply-To: <1722719.1184003911960.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <10734199.1193883825132.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBFORUMS-247?page=comments#action_12385459 ] 
            
Ryszard Kozmik commented on JBFORUMS-247:
-----------------------------------------

Indeed it helps for ?, ?, ?, ?, ? but it e.g. doesn't for Polish diacritical characters like ?,?,?,?,?,?,?,?. (I have URIEncoding="UTF-8" in my 8080 connector in server.xml of tomcat). Do you have any idea what can be wrong?

> forums and commons-fileupload-1.1
> ---------------------------------
>
>                 Key: JBFORUMS-247
>                 URL: http://jira.jboss.com/jira/browse/JBFORUMS-247
>             Project: JBoss Forums
>          Issue Type: Bug
>          Components: Portlet Productization, Forum Model Layer
>         Environment: JBoss as from http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_0_5_GA_CP06, 
> JBoss Portal from http://anonsvn.jboss.org/repos/portal/trunk since 9 july 2007,
> JBoss Forums from http://anonsvn.jboss.org/repos/labs/labs/jbossforums/branches/forums101P26 since 9 july 2007
>            Reporter: Luca Stancapiano
>         Assigned To: Ryszard Kozmik
>             Fix For: 1.0.1 RC
>
>         Attachments: ForumsJSFPortlet.java, patch_multiple_forums_src_1.1.0_30_sep_2007.zip
>
>
> hi....I send you to see http://jira.jboss.com/jira/browse/JBPORTAL-1550 by me reported. It is the same problem......if you post messages using 'multipart/form-data' through commons-fileupload libs, you miss character encoding because there is a incompatibility between tomcat 5.5.23 and fileupload 1.1, and then if you try to send messages with characters as ?, ?, ?, ?, ? you 'll get problems of decoding with strange characters of response. Also for Forums I send you a patch. I substituted getString() method of org.apache.commons.fileupload.disk.DiskFileItem class with getString( String ...) method, passing inside the character encoding of the request:
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 560
>      I write :
>   
>                newParams.put(item.getFieldName(), new String[]{item.getString(req.getCharacterEncoding())});
>     instead of:
>              newParams.put(item.getFieldName(), new String[]{item.getString()});
> org.jboss.portlet.forums.ui.ForumsJSFPortlet : row 564
>   
>       I write:
>             String value = item.getString(req.getCharacterEncoding());
>       instead of:
>             String value = item.getString();

-- 
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

       



From jira-events at lists.jboss.org  Wed Oct 31 22:27:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:27:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-836) Remoting
 Endpoint/Listener Deployer
Message-ID: <29335891.1193884064741.JavaMail.jira@cloud.prod.atl2.jboss.com>

Remoting Endpoint/Listener Deployer
-----------------------------------

                 Key: JBREM-836
                 URL: http://jira.jboss.com/jira/browse/JBREM-836
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd


Deployer for the Microcontainer that creates and configures a Remoting Endpoint.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:27:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:27:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Updated: (JBREM-836) Remoting
 Endpoint/Listener Deployer
In-Reply-To: <29335891.1193884064741.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <22377647.1193884064942.JavaMail.jira@cloud.prod.atl2.jboss.com>

     [ http://jira.jboss.com/jira/browse/JBREM-836?page=all ]

David Lloyd updated JBREM-836:
------------------------------

    Fix Version/s: Remoting 3 M3

> Remoting Endpoint/Listener Deployer
> -----------------------------------
>
>                 Key: JBREM-836
>                 URL: http://jira.jboss.com/jira/browse/JBREM-836
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: David Lloyd
>             Fix For: Remoting 3 M3
>
>
> Deployer for the Microcontainer that creates and configures a Remoting Endpoint.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:29:44 2007
From: jira-events at lists.jboss.org (David Lloyd (JIRA))
Date: Wed, 31 Oct 2007 22:29:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Created: (JBREM-837) Static
	Discovery/Route Deployer
Message-ID: <25603332.1193884184593.JavaMail.jira@cloud.prod.atl2.jboss.com>

Static Discovery/Route Deployer
-------------------------------

                 Key: JBREM-837
                 URL: http://jira.jboss.com/jira/browse/JBREM-837
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
            Reporter: David Lloyd
             Fix For: Remoting 3 M3


Mechanism to allow static Discoveries to be deployed/undeployed for a given Endpoint.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:40:44 2007
From: jira-events at lists.jboss.org (Brian Stansberry (JIRA))
Date: Wed, 31 Oct 2007 22:40:44 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1209) Restore
 existing Option to InvocationContext in TreeCache._gravitateData
In-Reply-To: <10112660.1193863724684.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <30451126.1193884844716.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBCACHE-1209?page=comments#action_12385460 ] 
            
Brian Stansberry commented on JBCACHE-1209:
-------------------------------------------

JBC testsuite ran fine as did the ejb3 clustering tests from AS 4.2.2.

> Restore existing Option to InvocationContext in TreeCache._gravitateData
> ------------------------------------------------------------------------
>
>                 Key: JBCACHE-1209
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1209
>             Project: JBoss Cache
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.1.SP6
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 1.4.1.SP6
>
>         Attachments: TreeCache.patch
>
>
> The fix for JBCACHE-1192 has introduced a couple of problems that are manifesting themselves in numerous errors in the test suite:
> 1) _gravitateData changes the value of skipDataGravitation for the Option associated with the call, but then doesn't restore the correct value to *that* instance of Option.
> 2) _gravitateData calls get(Fqn), and that call actually results in the instance of Option that is associated with the thread being changed (see impl of get(Fqn). But, _gravitateData does not restore the original Option to the thread.  Maybe not a problem if _gravitateData is called remotely, since there is no meaningful Option associated with the thread.  But _gravitateData can now also be called by DataGravitationInterceptor.localBackupGet, and in that case there very well could be a meaningful Option associated with the thread, and it needs to be restored before _gravitateData returns.
> I'll attach a possible patch in a minute.

-- 
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

        


From jira-events at lists.jboss.org  Wed Oct 31 22:46:48 2007
From: jira-events at lists.jboss.org (Ron Sigal (JIRA))
Date: Wed, 31 Oct 2007 22:46:48 -0400 (EDT)
Subject: [jboss-jira] [JBoss JIRA] Commented: (JBREM-675) Problems with
	Servlet invoker
In-Reply-To: <31877928.1169187776095.JavaMail.jira@cloud.prod.atl2.jboss.com>
Message-ID: <7271629.1193885208404.JavaMail.jira@cloud.prod.atl2.jboss.com>

    [ http://jira.jboss.com/jira/browse/JBREM-675?page=comments#action_12385461 ] 
            
Ron Sigal commented on JBREM-675:
---------------------------------

Testing:

1. New unit test:  org.jboss.test.remoting.transport.servlet.ServletInvokerNoExceptionTestClient.

2. Ran EJB3 example from wiki page Accessing_EJB3s_over_HTTP_HTTPS, after updating example (see EJBTHREE-1094 "Update wiki page "Accessing_EJB3s_over_HTTP_HTTPS" for Remoting 2.4.0").  It ran with HTTP and HTTPS with the non-APR connector.  With the APR connector, the example ran with HTTP, but there is a problem with HTTPS.  It seems that the APR connector expects the keystore in openssl format.  See also JBREM-825 "Verify that CoyoteInvoker works with Apache Portable Runtime".

3. Created a servlet example in JBossMessaging, parallel to the http example, and it ran correctly.  See JBMESSAGING-1131 "Add configuration for Remoting servlet transport".

> Problems with Servlet invoker
> -----------------------------
>
>                 Key: JBREM-675
>                 URL: http://jira.jboss.com/jira/browse/JBREM-675
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon)
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>         Attachments: ServletServerInvoker.java
>
>
> Several problems with servlet invoker:
> 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java
> 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag).

-- 
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

        


